From: Roland P. <rp...@ne...> - 2005-01-22 20:09:04
|
Hi, I tried to build 1.3 cvs on a dual Xeon 3.2 with 64 it extension, but I never even got beyond 'prepare' stage. The Kernel configuration stops because it cannot configure this option: * * Processor type and features * Processor family 1. AMD-Opteron/Athlon64 (MK8) > 2. Intel x86-64 (MPSC) 3. Generic-x86-64 (GENERIC_CPU) (NEW) I couldn't find any option to set in the config file for this. It seems to be x86_64 related because it runs fine on my old p3 right now... I've never seen this before, probably because I have never built 2.6.10 on x86_64 before, does anyone know this? Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2005-01-22 20:19:13
|
Roland Pabel wrote: >Hi, >I tried to build 1.3 cvs on a dual Xeon 3.2 with 64 it extension, but I never >even got beyond 'prepare' stage. The Kernel configuration stops because it >cannot configure this option: >* >* Processor type and features >* >Processor family > 1. AMD-Opteron/Athlon64 (MK8) > > >> 2. Intel x86-64 (MPSC) >> >> > 3. Generic-x86-64 (GENERIC_CPU) (NEW) > >I couldn't find any option to set in the config file for this. It seems to be >x86_64 related because it runs fine on my old p3 right now... >I've never seen this before, probably because I have never built 2.6.10 on >x86_64 before, does anyone know this? > > Which CPU type did you select ? -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Roland P. <rp...@ne...> - 2005-01-22 21:27:34
|
On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: > Roland Pabel wrote: > >Hi, [...] > > Which CPU type did you select ? tried 586 and 686 using menuconfig (both for cpu and gcc compile). I didn't change the kernel config files... Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2005-01-22 21:54:50
|
> On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: >> Roland Pabel wrote: >> >Hi, > [...] >> >> Which CPU type did you select ? > tried 586 and 686 using menuconfig (both for cpu and gcc compile). I > didn't > change the kernel config files... OK that's strange. It sounds like the kernel config would be dependend on your current system type, but I can't really believe that. In order to continue and look into the problem later, run the following command inside the chroot: scripts/build.sh build opt=prepare This will allow you to press a key during the kernel config. We had a similar problem a couple of weeks ago, but it went away when I re-created all the kernel config files. It could be that I introduced a new problem when I did this. I attached my DL .config, so you can compare your settings with mine. Additionally I uploaded the current build system to: ftp://ftp.devil-linux.org/pub/devel/testing/build-1.3-20050122.tar.bz2 Because it could also be, that the SF anonymous CVS server is out of sync again. Let us know what you find. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Roland P. <rp...@ne...> - 2005-01-22 23:33:48
|
On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: > > On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: > >> Roland Pabel wrote: > >> >Hi, > > > > [...] > > [...] > > Let us know what you find. thanks, will do that on Monday when I'm at the University again. cu Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Roland P. <rp...@ne...> - 2005-01-25 21:39:18
|
On Sunday 23 January 2005 00:33, Roland Pabel wrote: > On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: > > > On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: > > >> Roland Pabel wrote: > > >> >Hi, > > > > > > [...] > > [...] > > > Let us know what you find. > > thanks, will do that on Monday when I'm at the University again. haven't done it yet, had no time yesterday and forgot to take my USB HDD along today. So I'll try it again tomorrow ('all good things is three' - does that phrase exist in english?) But I'll send the siproxd patch today anyways, because the 1.2 patch works and the 1.3 should, there is not much magic stuff going on there. Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2005-01-22 21:55:33
Attachments:
.config
|
forgott to attach the file ;-) -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Frank P. <pi...@we...> - 2005-01-26 21:12:09
|
On Saturday 22 January 2005 21:08, Roland Pabel wrote: > Hi, > I tried to build 1.3 cvs on a dual Xeon 3.2 with 64 it extension, but I > never even got beyond 'prepare' stage. The Kernel configuration stops > because it cannot configure this option: > * > * Processor type and features > * > Processor family > 1. AMD-Opteron/Athlon64 (MK8) > > > 2. Intel x86-64 (MPSC) > > 3. Generic-x86-64 (GENERIC_CPU) (NEW) > > I couldn't find any option to set in the config file for this. It seems to > be x86_64 related because it runs fine on my old p3 right now... > I've never seen this before, probably because I have never built 2.6.10 on > x86_64 before, does anyone know this? I have not tried yet 1.3, but I can build 1.2 (up to 1.2.2) on my Opteron. Patches for the problems I found (uname, modutils) are applied already by Heiko. May be the kernel config of 2.6.10 tries now another way to find out the actual architecture (looking in /proc ?). Can you try with ARCH ? from toplevel Makefile: # When performing cross compilation for other architectures ARCH shall be set # to the target architecture. (See arch/* for the possibilities). # ARCH can be set during invocation of make: # make ARCH=ia64 # Another way is to have ARCH set in the environment. # The default ARCH is the host where make is executed. Regards Frank |
From: Roland P. <rp...@ne...> - 2005-01-31 21:02:21
|
On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: > > On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: > >> Roland Pabel wrote: > >> >Hi, > > > > [...] > > > >> Which CPU type did you select ? > > > > tried 586 and 686 using menuconfig (both for cpu and gcc compile). I > > didn't > > change the kernel config files... > > OK that's strange. It sounds like the kernel config would be dependend on > your current system type, but I can't really believe that. > > In order to continue and look into the problem later, run the following > command inside the chroot: > scripts/build.sh build opt=prepare > This will allow you to press a key during the kernel config. > > We had a similar problem a couple of weeks ago, but it went away when I > re-created all the kernel config files. It could be that I introduced a > new problem when I did this. > I attached my DL .config, so you can compare your settings with mine. > > Additionally I uploaded the current build system to: > ftp://ftp.devil-linux.org/pub/devel/testing/build-1.3-20050122.tar.bz2 > Because it could also be, that the SF anonymous CVS server is out of sync > again. > > Let us know what you find. Sorry for the delay, was quite busy. I tried your .config file, the build environment you uploaded and a clean lfssystem (lfssystem-6.0-i686.tar.bz2) but nothing helped. It looks like Frank is right and the kernel reads $ARCH from proc-fs: export ARCH=test leads to make: *** No rule to make target `/build/tmp/linux-2.6.10/arch/test/Makefile'. So the choices are among what is listed in linux-2.6.10/arch/* . Using ARCH=x86_64 the build stops exactly where it did in the beginning. ARCH=i386 makes it work again :-) cu Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2005-02-01 01:31:09
|
Roland Pabel wrote: >On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: > > >>>On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: >>> >>> >>>>Roland Pabel wrote: >>>> >>>> >>>>>Hi, >>>>> >>>>> >>>[...] >>> >>> >>> >>>>Which CPU type did you select ? >>>> >>>> >>>tried 586 and 686 using menuconfig (both for cpu and gcc compile). I >>>didn't >>>change the kernel config files... >>> >>> >>OK that's strange. It sounds like the kernel config would be dependend on >>your current system type, but I can't really believe that. >> >>In order to continue and look into the problem later, run the following >>command inside the chroot: >>scripts/build.sh build opt=prepare >>This will allow you to press a key during the kernel config. >> >>We had a similar problem a couple of weeks ago, but it went away when I >>re-created all the kernel config files. It could be that I introduced a >>new problem when I did this. >>I attached my DL .config, so you can compare your settings with mine. >> >>Additionally I uploaded the current build system to: >>ftp://ftp.devil-linux.org/pub/devel/testing/build-1.3-20050122.tar.bz2 >>Because it could also be, that the SF anonymous CVS server is out of sync >>again. >> >>Let us know what you find. >> >> >Sorry for the delay, was quite busy. I tried your .config file, the build >environment you uploaded and a clean lfssystem (lfssystem-6.0-i686.tar.bz2) >but nothing helped. It looks like Frank is right and the kernel reads $ARCH >from proc-fs: >export ARCH=test leads to >make: *** No rule to make target `/build/tmp/linux-2.6.10/arch/test/Makefile'. >So the choices are among what is listed in linux-2.6.10/arch/* . >Using ARCH=x86_64 the build stops exactly where it did in the beginning. >ARCH=i386 makes it work again :-) > > So I guess we should set it on the 'linux' script per default ? -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Roland P. <rp...@ne...> - 2005-02-01 21:34:43
|
On Tuesday 01 February 2005 02:28, Heiko Zuerker wrote: > Roland Pabel wrote: > >On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: > >>>On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: > >>>>Roland Pabel wrote: > >>>>>Hi, > >>> > >>>[...] > >>> [...] > > So I guess we should set it on the 'linux' script per default ? Can't hurt, I guess. Unless 64bit cpus become more common and users demand a 64bit compiled DL version. But I guess that's still not happen so quickly. Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Frank P. <pi...@we...> - 2005-02-01 22:21:54
|
On Tuesday 01 February 2005 22:34, Roland Pabel wrote: > On Tuesday 01 February 2005 02:28, Heiko Zuerker wrote: > > So I guess we should set it on the 'linux' script per default ? > > Can't hurt, I guess. Unless 64bit cpus become more common and users demand > a 64bit compiled DL version. But I guess that's still not happen so > quickly. Roland Great to hear that my wild guess of $ARCH was successful :-) For a 64bit DL same applies also for the configure call in modutils. It also fixed to i386 for now. Because modutils are compiled by default to handle 64bit and 32bit modules, we have to set the architecture, otherwise crosscompile fails. Frank |
From: Heiko Z. <he...@zu...> - 2005-02-01 22:42:54
|
> On Tuesday 01 February 2005 02:28, Heiko Zuerker wrote: >> Roland Pabel wrote: >> >On Saturday 22 January 2005 22:54, Heiko Zuerker wrote: >> >>>On Saturday 22 January 2005 21:16, Heiko Zuerker wrote: >> >>>>Roland Pabel wrote: >> >>>>>Hi, >> >>> >> >>>[...] >> >>> > [...] >> >> So I guess we should set it on the 'linux' script per default ? > Can't hurt, I guess. Unless 64bit cpus become more common and users demand > a > 64bit compiled DL version. But I guess that's still not happen so > quickly. That would require some more changes anyway. -- Regards Heiko Zuerker http://www.devil-linux.org |