[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openpkg-dev
Subject:    Re: AIX and GNU linker
From:       Henri Gomez <henri.gomez () gmail ! com>
Date:       2005-05-18 9:45:30
Message-ID: 6291fc8505051802455027776e () mail ! gmail ! com
[Download RAW message or body]

Here is what you could find in SPECS for AIX Toolbox for Linux :

binutils :

# The "ld" command is renamed to "gld".  For proper linking, please
# use the native AIX ld command, /usr/bin/ld.
# The "strip" command is not functioning correctly in all cases, so
# it has been renamed to "gstrip".  We strongly recommend the use
# of the native AIX strip command, /usr/bin/strip.
# Ditto for ranlib.
mv bin/ld bin/gld
mv bin/strip bin/gstrip
mv bin/ranlib bin/granlib
chmod 444 bin/gld bin/gstrip bin/granlib

gcc :

rm -rf objdir
mkdir objdir
cd objdir
CC=cc \
CFLAGS="-O2" \
CXXFLAGS="-O2" \
LIBCFLAGS="-O2" \
LIBCXXFLAGS="-O2 -fno-implicit-templates" \
../configure \
--with-as=/usr/bin/as \
--with-ld=/usr/bin/ld \
--disable-nls \
--enable-languages=c,c++ \
--prefix=%{_prefix} \
--enable-threads \
--enable-version-specific-runtime-libs \
--host=%{buildhost}
gmake bootstrap-lean

We should probably do something similar ?

2005/5/18, Henri Gomez <henri.gomez@gmail.com>:
> Good link to read :
> 
> http://www-106.ibm.com/developerworks/eserver/articles/gnu.html?ca=dnp-43
> 
> Question: Could I put a `uname` in binutils and gcc specs to :
> 
> binutils :
> 
> rename ld into gld (IBM does also that in ther AIX Toolbox for Linux)
> 
> gcc :
> 
> specify to use /usr/bin/ld (AIX LINKER)
> 
> Regards
> 
> 2005/5/18, Henri Gomez <henri.gomez@gmail.com>:
> > While building the gcc 3.4.3 I see this warning :
> >
> > updating cache ./config.cache
> > loading cache ./config.cache within ltconfig
> >
> > *** Warning: the GNU linker, at least up to release 2.9.1, is reported
> > *** to be unable to reliably create shared libraries on AIX.
> > *** Therefore, libtool is disabling shared libraries support.  If you
> > *** really care for shared libraries, you may want to modify your PATH
> > *** so that a non-GNU linker is found, and then restart.
> >
> > checking for objdir... .libs
> > checking for /QOpenSys/openpkg/RPM/TMP/gcc-3.4.3/obj/gcc/xgcc option
> > to produce PIC...  -DPIC
> > checking if /QOpenSys/openpkg/RPM/TMP/gcc-3.4.3/obj/gcc/xgcc PIC flag
> > -DPIC works... yes
> > checking if /QOpenSys/openpkg/RPM/TMP/gcc-3.4.3/obj/gcc/xgcc static
> > flag -static works... no
> > finding the maximum length of command line arguments... 12289
> > checking if /QOpenSys/openpkg/RPM/TMP/gcc-3.4.3/obj/gcc/xgcc supports
> > -c -o file.o... yes
> > checking if /QOpenSys/openpkg/RPM/TMP/gcc-3.4.3/obj/gcc/xgcc supports
> > -fno-rtti -fno-exceptions ... no
> > c
> >
> > Should we hide (rename) the gnu linker, ld into gld, to avoid such problems ?
> >
>
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

[prev in list] [next in list] [prev in thread] [next in thread]