On 5/1/07, Aitor Pérez Iturri <[EMAIL PROTECTED]> wrote: > Well i added the epia as a new port, added entries in the Config.in (i > want to have the choice when make menuconfig is executed), modified the > functions/Platforms and created a new Cross-Epia-C3.conf file for keep > the optimization flags. > I choose this way beouse there are some many processors in the epia > boards and they need different compilation flags.
Ah, that's ok. Feel free to share your modifications with us, if you want to. You can use the CVS snapshot of Bootstrap and just provide the output for 'cvs diff -u' after doing your local changes, and then we can integrate them back into it. > > And while talking about embedded: please note that our recipe for > > uClibc is very outdated and probably broken. I've been using Glibc, > > which is perfectly fine for my needs. > > Ok, i choose uClibc for my build, i will see what happens later :). I guess that it will break :-) > At the moment i was taking a look at the scripts in Bootstrap and in > ChrootCompile. > > I needed to modify SetupChrootEnv script in order to get it work > correctly, it uses Is_Entry_set "complete" when looking for a Boolean > entry and it never tried to get the chrootcompile repository. I changed > 'Is_Entry_Set' by 'Boolean'. Thanks for the fix, I've just commited that change in the CVS. > Why is needed to download all that packages in order to compile the > new system? All the compilation is done inside a chroot environment, to avoid having the host system to interfere on dependencies, while allowing reproducible builds at any time. I also had some strange feelings about it in the start, but ChrootCompile proved to be an excellent tool. Once you are started with it I'm pretty sure you'll like it, too ;-) -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
