Hi, On Saturday 24 February 2007 04:49:44 [EMAIL PROTECTED] wrote:
> > On Wednesday 21 February 2007 00:27:13 [EMAIL PROTECTED] wrote: > >> Rene, > >> I'll reply to the t2-list in about another day from now, as I'm > >> travelling. > >> What I will do asap is try the Config script from Vector Linux (which > >> is what I used to use for building T2). If that works, then there is > >> something wrong in Puppy. > >> Puppy uses Busybox, but whenever we have encountered a problem with any > >> Busybox applet we have substituted the full one, so current situation > >> is a mix. Possibly the current problem is due to Busybox (but I would > >> have expected an error mesage if unsupported params were fed to a > >> Busybox > >> applet). > >> Anyway, I'll let you know if Vector works. > > > > I see - this can be a problem because the T2 build scripts rely on some > > non-trivial arguments for some command line utilities. I recently tried > > to change some code pathes to also work with minimal flavours (busybox > > in my case as well) but after 20 not-so-pretty-hacks I stopped doing so > > ... > > Okay, I found out what the problem is. I tested from Vector, but it still > crashed. > It seems that I have a misunderstanding. When running Config script, I > thought that if I chose not to auto-configure the kernel, then I could > just copy my kernel .config file as-is to config/puppy220/ and rename it > to linux.cfg. I did this before running Config, and as soon as the script > gets to the part where it reads linux.cfg, it crashes. Hm, I have to test this too. Of course the Config(urator) should never "crash". > Earlier on, when I perused the various kernel config scripts, I thought > I saw code that just copied linux.cfg as-is to .config before running > make -- in the case of no kernel auto-config. > However, it seems that I am mistaken? > > Which raises the question, if I want to use my own .config file as-is, > how do I do that? I ususally use a target/.../kernel.conf but this is only used if you do leave the linux config style selected with someting != none resulting in the usual T2 auto post-processing on the file, like enabling as many modules possible. For your case I think it is better to add a little package specific code to your target: In your target/.../config.in: SDECFGSET_PKG_LINUX_CONFIG_STYLE='none' and then in a target/.../pkg_linux26_post.conf lx_customconf=$base/target/.../kernel.conf The 2nd is needed as otherwise config/$config/linux.cfg is used which is probably not perfect as you usually want all your target files under version control in target/... > Also, if I have my own pre-patched kernel source and don't want to apply > T2's kernel patches, do I just remove the .patch files out of > package/base/linux26? No, you would need to do this for every new T2 release. Just add a target/puppy.../pkg_linux26_post.conf with: patchfiles="" Yours, -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name +49 (0)30 / 255 897 45
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
