This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Fix ac_c99_complex configury


> In any case, what you're saying is that we can't do this because our 
> build system is lame, not for any reason of principle.  I can believe that.

Yep. What would be divine would be for the build directories to mirror
the install directories, so that things could be easily (and
consistently) found. This has come up various times in the past.

I thought I'd made my preference for this new (and so far, imaginary)
behavior known at some point in the past. However, let it categorically
be stated now.

> The fix would be to install the compiler before building V3, or at least 
> do some kind of dummy installation.  We've been wanting to do that for a 
> while; that would avoid all the hokey -B/-L gunk we have to do when 
> building libraries.  But, I can believe that it doesn't work with our 
> current build system.

Yep. This exactly. The goal would be to stage the compiler, then the
compiler support (libgcc, startup files) then the runtime libs with
ordered dependencies in a sane manner, such as libc, libstdc++,
libjava, etc.

When the build is done, you'd get something like

$builddir/install/bin
$builddir/install/lib
$builddir/install/include

or whatever. Then things become much, much easier for the runtime  libs.

-benjamin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]