[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51673: Configure of libtool @2.4.6_13 finds a compiler named "no" on
From: |
Ryan Schmidt |
Subject: |
bug#51673: Configure of libtool @2.4.6_13 finds a compiler named "no" on Mac OS X 10.4.11 |
Date: |
Sun, 7 Nov 2021 18:15:11 -0600 |
On Nov 7, 2021, at 15:25, Peter Dyballa wrote:
> On Mac OS X 10.4.11, Tiger (PPC), configure shows, when trying to install
> with MacPorts:
>
> checking whether we are using the GNU C++ compiler... yes
> checking whether /opt/local/bin/g++-apple-4.2 accepts -g... yes
> checking dependency style of /opt/local/bin/g++-apple-4.2... gcc3
> checking how to run the C++ preprocessor... /opt/local/bin/g++-apple-4.2 -E
> checking for ld used by /opt/local/bin/g++-apple-4.2...
> /opt/local/libexec/apple-gcc42/gcc/powerpc-apple-darwin8/4.2.4/ld
> checking if the linker
> (/opt/local/libexec/apple-gcc42/gcc/powerpc-apple-darwin8/4.2.4/ld) is GNU
> ld... no
> checking whether the /opt/local/bin/g++-apple-4.2 linker
> (/opt/local/libexec/apple-gcc42/gcc/powerpc-apple-darwin8/4.2.4/ld) supports
> shared libraries... yes
> checking for /opt/local/bin/g++-apple-4.2 option to produce PIC...
> -fno-common -DPIC
> checking if /opt/local/bin/g++-apple-4.2 PIC flag -fno-common -DPIC works...
> yes
> checking if /opt/local/bin/g++-apple-4.2 static flag -static works... no
> checking if /opt/local/bin/g++-apple-4.2 supports -c -o file.o... yes
> checking if /opt/local/bin/g++-apple-4.2 supports -c -o file.o... (cached) yes
> checking whether the /opt/local/bin/g++-apple-4.2 linker
> (/opt/local/libexec/apple-gcc42/gcc/powerpc-apple-darwin8/4.2.4/ld) supports
> shared libraries... yes
> checking dynamic linker characteristics... darwin8.11.0 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether no accepts -g... no
> <====
This presumably is not the fault of the libtool project but of the MacPorts
libtool Portfile which sets:
configure.fc no
configure.f77 no
(which causes the environment variables FC and F77 to be set to "no").
Why it does this is explained here:
https://trac.macports.org/ticket/23684#comment:8