After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 65447 - Version: 1.0.8: breakpoint library have error in Makefile
Version: 1.0.8: breakpoint library have error in Makefile
Status: VERIFIED FIXED
Product: libxslt
Classification: Platform
Component: general
unspecified
Other FreeBSD
: Normal major
: ---
Assigned To: Daniel Veillard
Daniel Veillard
Depends on:
Blocks:
 
 
Reported: 2001-11-26 21:59 UTC by lev
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description lev 2001-11-26 21:59:34 UTC 
breakpoint/Makefile.in have such line:

libxsltbreakpoint_la_LIBADD = -lxml2 $(M_LIBS)

In previous version this line was:

libxsltbreakpoint_la_LIBADD = $(EXTRA_LIBS)

Now package could not be compiled, because -L/usr/local/lib flag is not 
passed to linker, when libbreakpoint.so is linked.

It could be fixed by setting LDFLAGS in environment, but previous versions 
doesn't have such problems at all.
Comment 1 Daniel Veillard 2001-11-26 22:24:28 UTC 
this is a pain, sorry. Can you do the following:

replace it by
libxsltbreakpoint_la_LIBADD = @LIBXML_LIBS@

In the Makefile.in (or Makefile.am if you restart from the
autogen.sh level) and give it a try ?

thanks in advance,

Daniel
Comment 2 lev 2001-11-27 09:47:00 UTC 
Yes, I've done (really, BEFORE sending bugreport) in such way:

libxsltbreakpoint_la_LIBADD = $(LIBXML_LIBS)

for FreeBSD port. The same effect, everything works.
But I think, "libxsltbreakpoint_la_LIBADD = -lxml2 $(M_LIBS)" could 
be problem not only for FreeBSD and not only for ports(package)...
Comment 3 Daniel Veillard 2001-11-27 09:50:23 UTC 
Thanks for the report !
Yes, this is a potential problem for all Unix users. I pointed
people to the possible solution, if the current fix is deemed
good enough I will make a quick new release.

  Thanks a lot !

Daniel
Comment 4 Daniel Veillard 2001-12-08 10:53:35 UTC 
This is expected to be fixed in release 1.0.9 made yesterday,

  thanks,

Daniel