GNU bug report logs - #14959
automake 1.14 failure on OS X 10.6.8: fort5

Previous Next

Package: automake;

Reported by: Diab Jerius <dj <at> head.cfa.harvard.edu>

Date: Fri, 26 Jul 2013 15:34:01 UTC

Severity: minor

To reply to this bug, email your comments to 14959 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-automake <at> gnu.org:
bug#14959; Package automake. (Fri, 26 Jul 2013 15:34:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Diab Jerius <dj <at> head.cfa.harvard.edu>:
New bug report received and forwarded. Copy sent to bug-automake <at> gnu.org. (Fri, 26 Jul 2013 15:34:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Diab Jerius <dj <at> head.cfa.harvard.edu>
To: bug-automake <at> gnu.org
Subject: automake 1.14 failure on OS X 10.6.8: fort5
Date: Fri, 26 Jul 2013 11:32:18 -0400
[Message part 1 (text/plain, inline)]
The fort5 test fails on Mac OS X 10.6.8.

Attached are the logs from the get-sysconf and fort5 tests.


[get-sysconf.log (text/x-log, attachment)]
[fort5.log (text/x-log, attachment)]

Severity set to 'minor' from 'normal' Request was from Stefano Lattarini <stefano.lattarini <at> gmail.com> to control <at> debbugs.gnu.org. (Mon, 22 Dec 2014 10:19:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-automake <at> gnu.org:
bug#14959; Package automake. (Sun, 20 Feb 2022 19:02:02 GMT) Full text and rfc822 format available.

Message #10 received at 14959 <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: 14959 <at> debbugs.gnu.org
Cc: Diab Jerius <dj <at> head.cfa.harvard.edu>
Subject: Re: automake 1.14 failure on OS X 10.6.8: fort5
Date: Sun, 20 Feb 2022 19:00:40 +0000 (UTC)
On Fri, 26 Jul 2013 11:32:18 -0400, Diab Jerius wrote:
> The fort5 test fails on Mac OS X 10.6.8.

the failing part of the log:

/bin/sh ./libtool  --tag=FC   --mode=link gfortran  -g -O2   -o libhello.la -rpath /usr/local/lib foo.lo bar.lo libgoodbye.la 
libtool: link: gfortran -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libhello.0.dylib  .libs/foo.o .libs/bar.o   -Wl,-force_load,./.libs/libgoodbye.a   -O2   -install_name  /usr/local/lib/libhello.0.dylib -compatibility_version 1 -current_version 1.0 -Wl,-single_module
/usr/bin/libtool: unknown option character `f' in: -force_load
Usage: /usr/bin/libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT]
Usage: /usr/bin/libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table <filename>] [-seg_addr_table_filename <file_system_path>] [-all_load] [-noall_load]
make: *** [libhello.la] Error 1

i can't explain why it's running /usr/bin/libtool in the first place.
the test generated & bundled a local copy of libtool and it is using
that.  is the libtool on macOS falling back to the /usr/bin/libtool ??




Information forwarded to bug-automake <at> gnu.org:
bug#14959; Package automake. (Mon, 21 Feb 2022 00:28:02 GMT) Full text and rfc822 format available.

Message #13 received at 14959 <at> debbugs.gnu.org (full text, mbox):

From: Diab Jerius <djerius <at> cfa.harvard.edu>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: 14959 <at> debbugs.gnu.org
Subject: Re: automake 1.14 failure on OS X 10.6.8: fort5
Date: Sun, 20 Feb 2022 19:27:05 -0500
On 2/20/22 14:00, Mike Frysinger wrote:
> On Fri, 26 Jul 2013 11:32:18 -0400, Diab Jerius wrote:
>> The fort5 test fails on Mac OS X 10.6.8.
> the failing part of the log:
>
> /bin/sh ./libtool  --tag=FC   --mode=link gfortran  -g -O2   -o libhello.la -rpath /usr/local/lib foo.lo bar.lo libgoodbye.la
> libtool: link: gfortran -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libhello.0.dylib  .libs/foo.o .libs/bar.o   -Wl,-force_load,./.libs/libgoodbye.a   -O2   -install_name  /usr/local/lib/libhello.0.dylib -compatibility_version 1 -current_version 1.0 -Wl,-single_module
> /usr/bin/libtool: unknown option character `f' in: -force_load
> Usage: /usr/bin/libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT]
> Usage: /usr/bin/libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table <filename>] [-seg_addr_table_filename <file_system_path>] [-all_load] [-noall_load]
> make: *** [libhello.la] Error 1
>
> i can't explain why it's running /usr/bin/libtool in the first place.
> the test generated & bundled a local copy of libtool and it is using
> that.  is the libtool on macOS falling back to the /usr/bin/libtool ??

Hi,

Thanks for looking at this, but I'm afraid I won't be able to reproduce 
this after this period of time. Mac OS X has changed dramatically since 
2013, and I don't have access to anything that old.

Diab






This bug report was last modified 3 years and 113 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.