On Tue, Nov 27, 2012 at 6:51 PM, Phillip Moore <[email protected]> wrote: > Nothing to fix -- part of bootstrapping the compilers is defining > those releasealiases, since I do *NOT* bundle them with the uploaded > efsdeploy builds. The upload process only includes releasealiases > which are substr's of the actual release string.
What needs to happen to change that? ie, efs_bootstrap_content fails because of the missing releaselink. I know enough to be able to work past it, but a newcomer to EFS needs the process to be more streamlined. > > OTOH, what's missing is any form of documentation on HOW to work > through the bootstrap process. I never did document how to build > the compilers from scratch, although it's not really that hard, > especially with the latest efsdeploy rules. Still, it's not trivial, > either. > I'll be making some commits to help with the documentation. Stay tuned. Steven > On Tue, Nov 27, 2012 at 4:27 PM, Steven Jenkins > <[email protected]> wrote: >> Just a note that rhel/gcc/4.1 depends on rhel/binutils/rhel41, yet no >> such releasealias exists. That's easy enough to work around (ie, by >> manually defining the releaselias), and I'd be happy to fix it >> upstream -- feel free to point me in the right direction. >> >> Thanks, >> Steven >> _______________________________________________ >> EFS-dev mailing list >> [email protected] >> http://mailman.openefs.org/mailman/listinfo/efs-dev > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
