Issue 42869 - Build problem in libxmlsec
Summary: Build problem in libxmlsec
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 680m77
Hardware: All NetBSD
: P3 Trivial (vote)
Target Milestone: ---
Assignee: maho.nakata
QA Contact: issues@tools
URL:
Keywords: oooqa
Depends on:
Blocks: 42683
  Show dependency tree
 
Reported: 2005-02-15 20:15 UTC by isah
Modified: 2010-07-21 11:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
proposed patch (1.20 KB, patch)
2005-02-15 20:39 UTC, rene 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description isah 2005-02-15 20:15:46 UTC 
libxmlsec build crashes with :
Checking DLL ../../../../../../unxbsdi2.pro/lib/check_libxmlsec-nss.so ...:
ERROR: Shared object "libdl.so.2" not found
dmake:  Error code 1, while making
'../../../../../../unxbsdi2.pro/lib/libxmlsec-nss.so'

The libdl is not directly linked by the compilation line.
Passing the compilation option -DFREEBSD_WORKAROUND allows to build but I could
not find how to put it in a working patch.
Comment 1 rene 2005-02-15 20:38:26 UTC 
Hmm. maybe (did only find one occurance of this conditional in ltmain.sh..) this
can be fixed just by making libxmlsec build using ./congigure, since then the
right things are done. But you probably can also do it in the now existing
hackish wasy with the attached patch...
Comment 2 rene 2005-02-15 20:39:23 UTC 
Created attachment 22673 [details]
proposed patch
Comment 3 pavel 2005-04-20 21:09:27 UTC 
maho: what is the status of this issue?
Comment 4 maho.nakata 2005-04-21 01:36:56 UTC 
pjanik:
I don't encounter this problem for FreeBSD
maybe NetBSD related. so rene's patch seems to be
not appropreate.

isah:
do you still have this problem?
Comment 5 flibby05 2005-04-23 16:30:07 UTC 
set to NEW, oooqa can do nothing about this issue
Comment 6 Martin Hollmichel 2010-07-20 16:32:44 UTC 
mark as invalid due to inactivity
Comment 7 Mechtilde 2010-07-21 11:08:56 UTC 
invalid -> closed