So, just to be clear, are you recommending that the *binary* openpkg gcc-*.rpm be installed first ? Wouldn't that still be considered an "alien" gcc if I'm installing subsequent RPMs into a dir other than /cw (or wherever it goes)?
What I did (although I temporarily defined l_cc in rpmmacros until I got gcc built, it would be similar with the command line opts), was: - built make-*.src.rpm (because gcc-*src.rpm depends on it) using /usr/local/bin/gcc - built gcc-3.2*.src.rpm using /usr/local/bin/gcc - installed the resulting gcc-3.2*.rpm - built rsync-*src.rpm using the newly installed openpkg gcc-3.2 (this was just to test if the new gcc worked) - Now, I've rebuilt gcc-3.2-*.src.rpm using the openpkg gcc-3.2, and I plan on installing that (after uninstalling gcc-*.rpm). - after that, I plan on rebuilding rsync and various other src RPMs (probably make as well, though I might have to force it because of the gcc dependency) Does that sound like a reasonable procedure for bootstrapping from source? Thanks, -- Vinod On Tue, 3 Dec 2002, Ralf S. Engelschall wrote: > I recommend you to immediately install the OpenPKG "gcc" package (plus > is dependencies) and then to start over with regular builds (without > with_cc) and even deinstall the alien cc. Because the C compiler is a > very sensible package and experiences showed that lots of gcc versions > for Solaris which are flying around cause trouble (for instance when it > comes to DSO building, etc). ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
