On 2011-03-06 at 23:50:36 [+0100], scottmc <scottmc2@xxxxxxxxx> wrote: > >> 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? One problem is that some ported software hard-codes some absolute paths. Moving files around might break them. > > 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. Well, there's also the other problem that some software might need to be installed twice for hybrid builds. E.g. on a gcc 2 hybrid a gcc 4 version of OpenSSL is needed for WebPositive and a gcc 2 version for Mail, ssh, etc. So one would also have to adjust the build system to support that case and make sure that the packages don't clash with each other. > Is this issue big enough to be a blocker for alpha3 or can it just be > mentioned on the known issues list? Good question. If the status quo appears to work and we want to do a release soon, we might indeed want to sit this issue out until package management is introduced (hopefully before the subsequent release). CU, Ingo