El Tue, 1 May 2007 19:20:37 -0300
"Lucas C. Villa Real" <[EMAIL PROTECTED]> escribió

Thanks for your reply Lucas.

> Bootstrap was written with the idea of being able to create a
> filesystem from scratch. So, I think it is suitable for what you want,
> given that it's an embedded board.
> 

Yes, i'm now trying to get it working.

> Since the Epia is a x86 you can just select 'Native compiling'  under
> menuconfig. functions/Platforms should need to be adjusted only if you
> were going to create a port to a new processor, such as MIPS or
> PPC-Embedded.

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.
 
> 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 :). 

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'.

Why is needed to download all that packages in order to compile the
new system?
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to