This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: No libraries (.a) created during 64-bit build
On Thu, Aug 15, 2019 at 05:17:36PM -0400, Michael Huber via binutils wrote:
> On 8/15/2019 2:13 PM, Jim Wilson wrote:
> > On Wed, Aug 14, 2019 at 12:44 PM Michael Huber via binutils
> > <binutils@sourceware.org> wrote:
> > > 2.32. GCC 8.1.0 recognizes the configure options for AS and LD are
> > > recognized, but the compile uses the OS installed AS and LD.
> > Use the same prefix for binutils and gcc, then gcc configure will
> > automatically find and use your binutils install.
> >
> > Jim
>
> First sorry about the cruddy formatting of the configure I used.
>
> -- GCC Configure --
>
> configure --prefix=/usr/local/be2/gcc-8.1.0 --enable-threads=posix
> --with-gnu-as --with-as=/usr/local/be2/binutils-2.32/bin/as --with-gnu-ld
> --with-ld=/usr/local/be2/binutils-2.32/bin/ld
> --enable-languages=c,c++,fortran --enable-__cxa_at_exit --disable-multilib
> --with-pic --without-isl
>
> -- Binutils Configure --
>
> configure --prefix=/usr/local/be2/binutils-2.32
>
> Can you give me an example of what your are suggesting??? I don't follow how
> to use the same prefix for both binutils and gcc, unless it means binutils
> and gcc should be installed into the same location?
Yes, gcc and binutils should be installed into the same location.
eg. I use --prefix=/home/alan/gnu
Avoid --with-as and --with-ld. Those options can result in gcc not
honouring -B to search for as and ld, and this error from the ld
testsuite:
ERROR: ************************************************************************
ERROR: Your compiler driver ignores -B when choosing ld.
ERROR: You will not be testing the new ld in many of the following tests.
ERROR: It seems you will be testing <something else> instead.
ERROR: ************************************************************************
--
Alan Modra
Australia Development Lab, IBM