On Sun, Mar 6, 2011 at 16:50, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > On 2011-03-06 at 13:15:34 [+0100], Matt Madia <mattmadia@xxxxxxxxx> wrote: .... > the build system won't install both sets of >> libraries -- both due to the way optional packages are tracked with >> the subjam process and not automagically moving the affected bits into >> the alt-gcc-subdir. ...Or am i overlooking something? > > Ah, now I'm getting what you're talking about. :) > Indeed, ATM gcc 4 library > packages are not installed correctly on a gcc 2 hybrid, since there isn't any > package built in such a way (i.e. with the libraries in the gcc4 subdirectory > and ideally not clashing with the other version either) and the build system > isn't handling this case anyway. I guess this also means that one actually > would have to build those packages under a gcc 2 hybrid. Would it be worthwhile to update the build system to support installing both sets & automatically moving the necessary bits into the alt-gcc-subdirectory? Possibly similar to how isGCCAgnostic was implemented... * replace OptionalPackages & friends to use separate `if gcc2 || hybrid`, `if gcc4 || hybrid` tests instead of the current if-else logic. * include a 'gcc2' or 'gcc4' argument to indicate "built for gcc2" or "built for gcc4" with the InstallOptionalHaikuImagePackage invocation * modify build_haiku_image::extractFile(), to perform magic. how -- i'm not sure yet. --mmadia