This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: build issue
- From: Ian Lance Taylor <iant at google dot com>
- To: FranÃois Dumont <francois dot cppdevs at free dot fr>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Thu, 04 Nov 2010 22:10:05 -0700
- Subject: Re: build issue
- References: <4CD31991.1080100@free.fr>
FranÃois Dumont <francois.cppdevs@free.fr> writes:
> Am I the only one to experiment build issues with current SVN trunk ?
If you had an existing working directory that suddenly started to fail,
then most likely the problem is that formerly lto was being
automatically disabled because you did not have libelf, and now it is
enabled because libelf is no longer required. An odd consequence of
this change is that when the LTO plugin is used a -fPIC version of
libiberty is required. But when the LTO plugin is not used, that
version of libiberty is not required. The change to build LTO did not
force libiberty to be reconfigured. So if you have an existing
libiberty object directory, then the problem is most likely that you
need to reconfigure it.
One simple way to fix this, short of removing your build directory, is
to simply remove the libiberty directory from your build directory (and
also remove stage*-libiberty). That will cause the right thing to
happen.
Ian