Hello,
On Wed, Feb 15, 2006 at 11:23:00PM -0800, Chuck Wolber wrote:
> [...] Yet, when I build it, the resulting binary still
> requires libbz2 at runtime.
I cannot guess the reason from your story. It would help if you could
post the results of your work:
please tell us the URL of the source p
Hi Florian,
* Florian Schricker wrote on Wed, Feb 15, 2006 at 03:29:10PM CET:
>
> Well... I get:
>
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
Which is fine.
> on MinGW32, which is good - but still shared objects are build:
>
> if /bi
It seems that Apple's OSX has introduced something known as a
"Universal Binary" in which the compiler conveniently compiles for
both PowerPC and Intel in one whack. Libraries and executables then
automatically "work" for both architectures.
Does anyone else see that this defeats the purpose
On Thu, 16 Feb 2006, Stepan Kasal wrote:
> Hello,
>
> On Wed, Feb 15, 2006 at 11:23:00PM -0800, Chuck Wolber wrote:
> > [...] Yet, when I build it, the resulting binary still
> > requires libbz2 at runtime.
>
> I cannot guess the reason from your story. It would help if you could
> post the r
Hello all,
I've made this macro which seems to solve all my problems with autoconf
and preventing configuration in folder containing sources. It works on
my linux box, and also on my windows box (cygwin, msys and mingw). (Not
tested on mac, the latest Mac I used was an IIgs !) with full, rela
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[redirecting from autoconf-patches]
According to Eric Blake on 2/16/2006 12:36 PM:
>>>Without this patch, AC_FUNC_STRERROR_R (and anything else that uses
>>>AC_CHECK_DECL) gets set incorrectly when configuring with gcc and
>>>CFLAGS='-Wall -Werror'.