rebuild -- on or off by default

Phil Edwards pedwards@jaj.com
Sat Apr 1 00:00:00 GMT 2000


> > Should this be checked in?  Currently we require the libstdc++-v3 sources
> > to be underneath the EGCS sources, but we're still allowing the library to
> > be built by itself.  This change would additionally require that the build
> > directories also be merged, unless the user passes --disable-libgcc-rebuild.
> > Users who just want to get the library by itself couldn't just do 'configure
> > && make install' anymore.  :-(
>
> but they could do configure --disable-libgcc-rebuild --disable-namespaces 
> && make install, right?

Yes.  Even leaving --diable-namespaces out works; they get the warning
about rebuilding libgcc.a, but it will still build.


> can you clarify "build directories also be merged"

I may be making that more difficult than it needs to be.

Rather than making a libstdc++ builddir and just building the library,
they'll have to make a GCC builddir and regenerate large chunks of
the compiler itself.  The "If you deleted your GCCobjdir, or never had
one" fakeout described in gccrebuild.html won't work.  Calling the EGCS
configure and then running "make all" (rather than "make bootstrap") works,
but you get a lot of extra work in there if all you wanted was libstdc++
and a rebuilt libgcc...


> See what everybody else says, but I say check it in later tonight if you 
> haven't heard strong arguments against it. You've given all of us
> sufficent warning of pending changes.

'Kay.


Phil



More information about the Libstdc++ mailing list