Re: Linux 2.4.3 Compile Errors - Power Mac
Jeff Galloway wrote: > > Sorry, Tom about the word doc faux pas. I've set out my problem in plain > text below. I got my source from ftp.kernel.org. Hi Jeff, Well that's problem #1. Source from kernel.org for 2.4 tends to not work on PPC as it has been lagging on important patches and such. We're hoping to get kernel.org caught up ASAP. Visit here to get the up to date and sometime bleeding edge source for PPC. http://www.fsmlabs.com/linuxppcbk.html > Here's my problem: > > Problem in compiling linux 2.4.3 > > Compile error message: > > After the compiler message: > > gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall > Wstrict-prototypes O2 fomit-frame-pointer fno-strict-aliasing > D__powerpc__ -fsigned-char msoft-float pipe ffixed-r2 Wno-uninitialized > mmultiple mstring-c o fork.o fork.c > > Compiler error message: > > fork.c: In function ?copy_mm¹: > fork.c:353: fixed or forbidden register 68 (0) was spilled for class > CR0_REGS. > This may be due to a compiler bug or to impossible asm statements or > clauses. Which version of gcc do you have? You want either 2.95.2 or 2.95.3 > cpp: output pipe has been closed > make[2]: *** [fork.o] Error 1 > make[2]: Leaving directory ?/home/jeff/kernel/linux/kernel¹ > make[1]: *** [first_rule] Error 2 > make[1]: Leaving directory ?/home/jeff/kernel/linux/kernel¹ > make: *** [_dir_kernel] Error 2 > > Compiling on Power Mac 7600, with dual processor (604e/180) installed, > running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog > distribution. Ah YDL ... good stuff. Hope you are on 1.2 at least. 8-) Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.3 Compile Errors - Power Mac
Jeff Galloway wrote: Sorry, Tom about the word doc faux pas. I've set out my problem in plain text below. I got my source from ftp.kernel.org. Hi Jeff, Well that's problem #1. Source from kernel.org for 2.4 tends to not work on PPC as it has been lagging on important patches and such. We're hoping to get kernel.org caught up ASAP. Visit here to get the up to date and sometime bleeding edge source for PPC. http://www.fsmlabs.com/linuxppcbk.html Here's my problem: Problem in compiling linux 2.4.3 Compile error message: After the compiler message: gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall Wstrict-prototypes O2 fomit-frame-pointer fno-strict-aliasing D__powerpc__ -fsigned-char msoft-float pipe ffixed-r2 Wno-uninitialized mmultiple mstring-c o fork.o fork.c Compiler error message: fork.c: In function ?copy_mm: fork.c:353: fixed or forbidden register 68 (0) was spilled for class CR0_REGS. This may be due to a compiler bug or to impossible asm statements or clauses. Which version of gcc do you have? You want either 2.95.2 or 2.95.3 cpp: output pipe has been closed make[2]: *** [fork.o] Error 1 make[2]: Leaving directory ?/home/jeff/kernel/linux/kernel make[1]: *** [first_rule] Error 2 make[1]: Leaving directory ?/home/jeff/kernel/linux/kernel make: *** [_dir_kernel] Error 2 Compiling on Power Mac 7600, with dual processor (604e/180) installed, running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog distribution. Ah YDL ... good stuff. Hope you are on 1.2 at least. 8-) Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FW: Linux 2.4.3 Compile Errors - Power Mac
Jeff Galloway wrote: > > I sent this report to the people indicated below, whose names I got from the > MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr. > MacKerras is no longer good and Mr. Chastain wrote me back that he is not > following 2.4 issues. Hi Jeff, Hmm Paul is around his email just changed and the pmac maintainer is now Ben, but that issue aside where did you get your 2.4.3 sources from that you are trying to build? http://www.fsmlabs.com/linuxppcbk.html is the location you want to pull stuff from. > I have not yet heard from Mr. Owens. > > Any suggestions on the solution to my problem? Well suggestion one is DON'T GIVE US A WORD DOCUMENT! Plain text please, then we can actually read what's wrong. Best to post to [EMAIL PROTECTED] That's one of the lists that the PPC Linux watches. Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: FW: Linux 2.4.3 Compile Errors - Power Mac
Jeff Galloway wrote: I sent this report to the people indicated below, whose names I got from the MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr. MacKerras is no longer good and Mr. Chastain wrote me back that he is not following 2.4 issues. Hi Jeff, Hmm Paul is around his email just changed and the pmac maintainer is now Ben, but that issue aside where did you get your 2.4.3 sources from that you are trying to build? http://www.fsmlabs.com/linuxppcbk.html is the location you want to pull stuff from. I have not yet heard from Mr. Owens. Any suggestions on the solution to my problem? Well suggestion one is DON'T GIVE US A WORD DOCUMENT! Plain text please, then we can actually read what's wrong. Best to post to [EMAIL PROTECTED] That's one of the lists that the PPC Linux watches. Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
pmd_alloc, pte_alloc, Was Re: 2.4.3 and Alpha
Hi All, Alan, I realize I don't keep up with the linux kernel mailing list like i should but the change to pmd_alloc and pte_alloc has me a little worried. I'm working on the ppc64 port (sources soon to be posted) and this change affects one of the design attributes that we've had. Basically in the pmd, it would seem that the current design in 2.4.3 forces you to have pointers in there. Currently in our source we're using offsets instead of a 64 bit pointer... this of course saved us from having to alloc 2 contiguous pages in memory. This isn't the end of the world, we can change over to using pointers but I just wanted to confirm that that was the intent or maybe I'm missing something and there is still a way out and still have our own arch dependant implementations of pte_alloc and pmd_alloc. Regards, Tom Alan Cox wrote: > > > `pmd_alloc' > > /usr/src/redhat/linux/include/linux/mm.h:412: previous declaration of > > `pmd_alloc' > > make: *** [init/main.o] Error 1 > > > > > > 2.4.1 compiled fine, and as far as I can see, some changes has been made > > to mm.h since then. I think these changes was followed up by i386, ppc, > > s390 and sparc64 kernels but not on others. Any plans on when this is > > done ? > > Its fixed in the -ac tree but I've yet to push that set of changes to Linus -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
pmd_alloc, pte_alloc, Was Re: 2.4.3 and Alpha
Hi All, Alan, I realize I don't keep up with the linux kernel mailing list like i should but the change to pmd_alloc and pte_alloc has me a little worried. I'm working on the ppc64 port (sources soon to be posted) and this change affects one of the design attributes that we've had. Basically in the pmd, it would seem that the current design in 2.4.3 forces you to have pointers in there. Currently in our source we're using offsets instead of a 64 bit pointer... this of course saved us from having to alloc 2 contiguous pages in memory. This isn't the end of the world, we can change over to using pointers but I just wanted to confirm that that was the intent or maybe I'm missing something and there is still a way out and still have our own arch dependant implementations of pte_alloc and pmd_alloc. Regards, Tom Alan Cox wrote: `pmd_alloc' /usr/src/redhat/linux/include/linux/mm.h:412: previous declaration of `pmd_alloc' make: *** [init/main.o] Error 1 2.4.1 compiled fine, and as far as I can see, some changes has been made to mm.h since then. I think these changes was followed up by i386, ppc, s390 and sparc64 kernels but not on others. Any plans on when this is done ? Its fixed in the -ac tree but I've yet to push that set of changes to Linus -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Obtaining new Device Numbers
Hi All, According to Documentation/devices.txt to request new major / numbers, all you should have to do is get ahold of H. Peter Anvin. Does anybody know if he is still doing this? Perhaps has he passed this duty on to someone else? It would appear he isn't answering requests mailed to [EMAIL PROTECTED] I'm trying to get the major / minor number issues resolved for the Linux port to the IBM AS/400 aka iSeries. We have released our first set of patches and before we put out the next set we'd like to get this nailed down as we're using bogus major / minor numbers that we just grabbed out of mid-air... obviously not the right thing. For those interested in the patches, take a gander to oss.software.ibm.com/developerworks/opensource/linux/projects/ppc/iSeries_notes.php Thanks much for any info! Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Obtaining new Device Numbers
Hi All, According to Documentation/devices.txt to request new major / numbers, all you should have to do is get ahold of H. Peter Anvin. Does anybody know if he is still doing this? Perhaps has he passed this duty on to someone else? It would appear he isn't answering requests mailed to [EMAIL PROTECTED] I'm trying to get the major / minor number issues resolved for the Linux port to the IBM AS/400 aka iSeries. We have released our first set of patches and before we put out the next set we'd like to get this nailed down as we're using bogus major / minor numbers that we just grabbed out of mid-air... obviously not the right thing. For those interested in the patches, take a gander to oss.software.ibm.com/developerworks/opensource/linux/projects/ppc/iSeries_notes.php Thanks much for any info! Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PowerPC branch out of date
Hi Linus, I'm one of the folks that works on the PowerPC portion of the kernel. I've noticed for some time that what's available at kernel.org and what's being worked on by those of us who maintain our little portion of the PowerPC tree is more and more out of sync. How it's got there etc etc etc at this stage isn't important. First how to fix it and how to make sure it doesn't happen again does concern me. Currently the diff between test13-preX and the master fsmlabs.com ppc tree is about 450k. Is the right thing to start with that patch get that into the test13-preX series? I would REALLY appreciate it if this could be made to happen. I've got a whole boatload of RS/6000 (aka pSeries) hardware that will be starting to work once this patch is in. It's truely a shame to have to explain to people that kernel.org *SHOULD* be the place to get a good kernel but given that things are out of sync to have to point them somewhere else. Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PowerPC branch out of date
Hi Linus, I'm one of the folks that works on the PowerPC portion of the kernel. I've noticed for some time that what's available at kernel.org and what's being worked on by those of us who maintain our little portion of the PowerPC tree is more and more out of sync. How it's got there etc etc etc at this stage isn't important. First how to fix it and how to make sure it doesn't happen again does concern me. Currently the diff between test13-preX and the master fsmlabs.com ppc tree is about 450k. Is the right thing to start with that patch get that into the test13-preX series? I would REALLY appreciate it if this could be made to happen. I've got a whole boatload of RS/6000 (aka pSeries) hardware that will be starting to work once this patch is in. It's truely a shame to have to explain to people that kernel.org *SHOULD* be the place to get a good kernel but given that things are out of sync to have to point them somewhere else. Regards, Tom -- Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://oss.software.ibm.com/developerworks/opensource/linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
