The testsuite.log showing a failed test under Solaris 10 is attached.
Please let me know if the release is still safe to use based on what
failed.
Thanks,
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick
Hi Bob,
* Bob Friesenhahn wrote on Wed, Sep 10, 2008 at 07:42:24PM CEST:
> If autoconf 2.63 fails this test under Solaris 10 with GNU m4 1.4.11, is
> it safe to use?
>
> 144: Input/OutputFAILED (base.at:303)
Please send tests/testsuite.log.
Thanks,
Ralf
___
If autoconf 2.63 fails this test under Solaris 10 with GNU m4 1.4.11,
is it safe to use?
144: Input/OutputFAILED (base.at:303)
Thanks,
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
On Wed, 10 Sep 2008, Bruno Haible wrote:
Right. There is also value to separate between some libraries which
use the same ABI but with different run-time behavior. For example,
libraries instrumented for profiling could go in a different
directory.
Sure, there are several use-cases:
1) Ther
On Wed, Sep 10, 2008 at 2:33 PM, Eric Blake <[EMAIL PROTECTED]> wrote:
> According to tsuna on 9/10/2008 2:39 AM:
>>
>> I tried to use m4_rename like so:
>> m4_rename([SOME_DEP], [SAVED_SOME_DEP])dnl <-- this is line 300
>> AC_DEFUN([SOME_DEP], [echo hooked cheap dep])
>> # my test with MY_MACOR he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to tsuna on 9/10/2008 2:39 AM:
>
> I tried to use m4_rename like so:
> m4_rename([SOME_DEP], [SAVED_SOME_DEP])dnl <-- this is line 300
> AC_DEFUN([SOME_DEP], [echo hooked cheap dep])
> # my test with MY_MACOR here
> m4_rename([SAVED_SOME_DEP
> Some care needs to be taken, though, because the gcc compiler on MacOS X 10.5
> (which produces 32-bit code by default) is configured like this:
>
> $ gcc -print-multi-os-directory
> .
> $ gcc -print-multi-os-directory -m64
> x86_64
> $ gcc -print-multi-os-directory -m32
> .
> $ gcc -print-mult
> How about changing the libdir default (currently $exec_prefix/lib) to be
> $exec_prefix/lib64 or $exec_prefix/lib/64, respectively, when
> - not cross-compiling, and
> - $CC $CPPFLAGS generates 64-bit mode object files, and
> - 64-bit mode object files are installed in /usr/lib64 or /usr/l
Paolo Bonzini wrote:
> I think the right way would be to set the libdir default to
>
> $exec_prefix/lib/`$CC -print-multi-os-directory $CFLAGS $CPPFLAGS`
Thanks for mentioning -print-multi-os-directory; it is currently undocumented
but appears to fit the bill on Linux/x86_64 machines:
$ gcc -pri
Bob Friesenhahn wrote:
> There is no shortage of reasons to want to put libraries in different
> directories and autoconf/libtool should not stand in the way of
> freedom.
The proposal is to change the _default_ value of $(libdir). The --libdir
option still gives the user full freedom.
> > The
Hi list,
I'm maintaining a set of M4 macros and want to write regression tests
as people report bugs. Running end-to-end tests where I generate a
configure script and run it and see if it works as expected is taking
too long (I already do that by re-using autoconf's own testsuite and
it takes 20 m
11 matches
Mail list logo