On 5/5/07, Aitor Pérez Iturri <[EMAIL PROTECTED]> wrote: > > 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. > > mmm really i don't know :). That's why i will not send you the epia > target files until i have it well configured. The idea to change > InvokeCompile sounds nice, i will try to do it tomorrow.
Ah, ok. I would expect to see Epia returning 'i686' there as well, in which case no modifications should be needed. Just check that later to see if there are something to change in the scripts. > > Great! By the way, have you managed to compile uClibc? Did you make a > > NewVersion, or did you decide to use Glibc instead? > > I forgot that in my post! I make a new recipe that works fine, with > an epia archsubdir inside. Compiled without problems. > > Now i made another change into these files: > Changed: > InvokeCompile > ChrootCompile > Added > functions/CrossBlackList > > I added support for a dimanyc cross_black_list into ChrootCompile (i > need that to ensure that Glibc is not treated as a dep, i'm using > UClibc). > Tomorrow i will send the patches. Hmm, we already have a file named /System/Settings/Scripts/CompatibilityList. The default file, shipped with the Scripts package, has the following line, among others: Glibc: UClibc Rootless This means that if a recipe/package requires Glibc and you have either UClibc or Rootless, it will consider that dependency as installed. I think it's case-sensitive, so you need to ensure that your package is named UClibc. > I have added too Dietlibc as an option to Glibc into Config.in. > Maybe recipes or InvokeCompile could know what is your election and > configure recipes for the use of each Glibc implementation. Some > recipes need to be configured to use dietlibc for example. I won't send > this change until it will be usseful. Theorically it should be just a matter of adding Dietlibc to CompatibilityList, and then InvokeCompile should just ignore references to Glibc. If it's not working then it's possible that something got broken in the middle of the Dependencies cleanups commited some days ago. > I got my epia distro (at the moment with very few packages inside) > fully. > > I have some problems with BusyBox, compiled fine, but doesn't install > the busybox binary neither any links to the tools, tomorrow i will see > what happened. > > This week i want to make a full GoboPBX, Gobo in my phones :). > > I will keep you informed about the project. Cool! Good luck :-) -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
