Hi,
I wrote some m4 macros for the boost libraries(see
http://randspringer.de/boost/index.html).
ATM the default behavior is that the user has to give
--with-boost, --with-boost-files-date-time
to the configure script in order to set the boost compile/linker flags
(the last parameter of AC_ARG
Quoting Paul Eggert <[EMAIL PROTECTED]>:
> Patrick Welche <[EMAIL PROTECTED]> writes:
>
> > so the -R made it, and all is well :-)
> >
> > I can't check the opposite though: do systems that don't want rpath get
> > one now?
>
> Yes, they probably do. Perhaps the libtool guys can chime in on
> whe
Patrick Welche <[EMAIL PROTECTED]> writes:
> so the -R made it, and all is well :-)
>
> I can't check the opposite though: do systems that don't want rpath get
> one now?
Yes, they probably do. Perhaps the libtool guys can chime in on
whether the patch was a good idea.
On Mon, Jul 17, 2006 at 10:36:17AM -0700, Paul Eggert wrote:
> Thanks for reporting that. Does the following patch to Autoconf 2.60
> fix the bug for you? I've installed it into Autoconf CVS (for 2.61)
> but I'd like you to verify that it actually works on NetBSD.
>
> 2006-07-17 Paul Eggert <[
Thanks for reporting that. Does the following patch to Autoconf 2.60
fix the bug for you? I've installed it into Autoconf CVS (for 2.61)
but I'd like you to verify that it actually works on NetBSD.
2006-07-17 Paul Eggert <[EMAIL PROTECTED]>
* lib/autoconf/libs.m4 (AC_PATH_XTRA): Do th
Eric Blake <[EMAIL PROTECTED]> writes:
> Now that m4 1.4.5 is released, should we update the web pages to recommend
> it?
OK, thanks, I've done that. I also upgraded the manual and README
as follows.
2006-07-17 Paul Eggert <[EMAIL PROTECTED]>
* README: Recommend M4 1.4.5.
* d
I happen to use an OS (NetBSD) which uses rpath. AC_PATH_XTRA sets X_CFLAGS
and X_LIBS to something sensible for compiling X, however, it misses out
the necessary -rpath or -R.
(libtool --config says
# How to pass a linker flag through the compiler.
wl="-Wl,"
# Flag to hardcode $libdir into a bina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now that m4 1.4.5 is released, should we update the web pages to recommend
it? m4 1.4.4 has some flaws, including an exploitable buffer overflow on
platforms that lack ecvt(3), that are inherited by autom4te.
I haven't seen the mail I sent to autotoo