On 5/5/07, Aitor Pérez Iturri <[EMAIL PROTECTED]> wrote:
> Hi everybody.
>
> Here comes some patches i made for BootStrap and related Scripts:
>
> For ChrootCompile:
> 1. Patch: ChrootCompile.1.diff
> Patch against: /ChrootCompile/1.57/Thu Mar 29 07:50:56 2007//
> * Added a "makedir -p " command to create_root function
+ mkdir -p ${rootdir}/${prefix%/*}a
That's fine. I just removed the extra 'a' in the end, as it looks like
it was a typo.
Just a note: you don't need to put extra comments around the lines
added by you. Credits are already going into the CVS logs :-) (it
makes it easier to apply the patches, too).
> Needed to ensure that works with no std locations.
> * s/sudo/$sudo in some lines.
Ok.
> 2. Patch: SetupChrootEnv.1.diff
> Patch against: /SetupChrootEnv/1.7/Sat May 5 12:01:44 2007//
> * s/Is_Entry_Set/Boolean/
Ok.
> For Bootstrap:
> 1. Patch: CreateGoboLinuxTree.1.diff
> Patch against: /CreateGoboLinuxTree/1.10/Sun Dec 24 15:40:17
> 2006//
> * Added a "mkdir -p" command to ensure that works with no std
> locations.
Ok.
> I have some questions, i don't know if they are bugs in Bootstrap or
> they are only because i'm new with it and i don't know very well how it
> works.
>
> * InstallDependecies, downloads all required packages into
> BaseDependencies (throught SetupChrootEnv), and then it make some checks
> for Cross-Files and Compile package, but Compile package is not
> downloaded as a dependenci so it is not there and InstallDependencies
> fails. is this the default behaviour?, maybe this dependency should
> be included into the rsync server or at least tell the user to put that
> dependency under BaseDependencies.
Oh, it should be there, definitely. I'm fixing this now, thanks!
> There are any other packages that
> should be included into BaseDependencies, CVS, needed to get
> TinyInstall at the end of InvokeCompile, Scripts listed into
> ChrootCompile and maybe any others.
Ok, I've added those too. You can synchronize your tree by calling this:
$ cd Bootstrap/chroot
$ SetupChrootEnv
You'll then be able to launch the Bootstrap script again.
> * InvokeCompile tries to get Linux-Headers, if the target is i686, they
> are downloaded from the official repos, otherwise they are downloaded
> from the arch repos at gobo.calica.org. Epia has not his own repos dir
> but the official repos works fine, i added a line to ensure that for
> epia target official repos is used, but this could be done with a
> variable in the Cross-File, what do you think?
What does 'uname -m' return on Epia? Bootstrap checks for the variable
$cross_uname_m, already defined in the Cross-Files. I'd prefer to keep
using that variable and just modify InvokeCompile instead, so that the
Cross files don't grow up.
> * I can't see the cross_optimization_flags when compiling under the
> chroot, i think that is Compile who pass that flags, how are they
> passed?
They are exported together with CFLAGS, so that Compile automatically
uses them. You can take a look at Cross-Common.conf to see where the
friendly-named variables are really used.
> P.D. Lucas the Bootstrap project is cool. Looks very nice, i have
> almost completed the epia GoboLinux system (i want to know now if the
> optimization flags are passed when compiling). Good work, congrats.
Thanks a lot! I'm very happy to see that it's being useful to someone else :-)
> P.D.2 I will send the Config.in file and the Cross-Files for epia when
> the target is done.
Great! By the way, have you managed to compile uClibc? Did you make a
NewVersion, or did you decide to use Glibc instead?
--
Lucas
powered by /dev/dsp
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
