Re: Adding additional system paths to a custom GCC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 16, 2012 at 12:06 PM, Tim Schumacher <schumact@xxxxxxxxx> wrote:
>
> I build boost with the new gcc I just built, and the same --prefix I used
> for the gcc.  Now all the includes and libraries (only static in my case)
> are placed where gcc can find them.  Next ... drum roll ... I unpack all the
> static boost libraries and also the lidstdc++.a file and re-archive all the
> resulting .o files back into libstdc++.a.  Now all the boost objects are
> magically available whenever I compile any c++ program.
>
> Is that crazy enough to work?

By default GCC will link against the dynamic libstdc++, libstdc++.so.
If you override that one way or another, then, yes, your scheme should
work, until you update to the next version at which point you will
have to do it again.

Ian


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux