Re: Problem compiling egcs

Re: Problem compiling egcs

[Martin Costabel]

Just to set the record straight:

This problem is now solved. It came from a kernel header file
include/asm-ppc/ptrace.h which, in the vger version 2.3.3 of the last 2
weeks, contained the definition
   #define REG unsigned long
It has been fixed yesterday. Thanks, Cort.

Martin Costabel wrote on Fri, 28 May 1999:
> 
> When trying to compile egcs-1.1.2 from the src.rpm, I get the following
> error:
> 
>   gcc  -DIN_GCC    -g  -DHAVE_CONFIG_H -DHAIFA    -I.
> -I/usr/src/redhat/BUILD/egcs-1.1.2/gcc
> -I/usr/src/redhat/BUILD/egcs-1.1.2/gcc/config  \
>     -DTARGET_NAME=\"ppc-redhat-linux\" \
>     -c `echo /usr/src/redhat/BUILD/egcs-1.1.2/gcc/toplev.c | sed
> 's,^\./,,'`
>   In file included from /usr/src/redhat/BUILD/egcs-1.1.2/gcc/rtl.h:41,
>                  from /usr/src/redhat/BUILD/egcs-1.1.2/gcc/toplev.c:49:
>   /usr/src/redhat/BUILD/egcs-1.1.2/gcc/rtl.def:549: parse error before
> `unsigned'
>   make[2]: *** [toplev.o] Error 1
>   make[2]: Leaving directory `/mnt/root2/BUILD/obj-ppc-linux/gcc'
>   make[1]: *** [bootstrap-lean] Error 2
> 
> The same error occured when I tried to compile gcc-2.95 from the cvs
> tree. I am using egcs-1.1.2-1c on pre-R5 with
> binutils-2.9.1.0.990418-1c. Processor is 603ev (PMac 6400/200).
> 
> There is no `unsigned' in gcc/rtl.def anywhere. Line 549 reads
>   DEF_RTL_EXPR(REG, "reg", "i0", 'o')
> 
> Since no one else seems to have this problem, I am beginning to believe
> that it is 603 related. Is this possible?
> 
> Any help appreciated.
> 
> --
> Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Kernel sources

[Jerry Quinn]

I'm a little confused about what the correct kernel sources are for
linuxppc.

There are the main sources from Linus at kernel.org mirrored
everywhere.  There is the vger CVS tree.  And there are sources at
ftp.linuxppc.org for several kernels. Can someone please fill me in on
how things are operating?

Thanks,

-- 
Jerry Quinn                             Tel: (514) 761-8737
jquinn@nortelnetworks.com               Fax: (514) 761-8505
Speech Recognition Research

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

kernel sources

[Ira K Weiny]

Where is the proper place to get the kernel source?

I have both 2.2.12 and 2.3.16 from kernel.org but neither seem to be in sync
with the other developers on this list.  (I had to hand patch the PCI changes
submitted. And the 2.3.16 will not even build due to a missing header?)

I know 2.3.16 is a development snapshot and I can't complain about that.  I
have seen many posts for the "vger" trees and the only web/ftp site I have
found was for Sparc and only has 2.1 version kernels?

What am I missing?
Ira Weiny


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: kernel sources

[Martin Costabel]

Ira K Weiny wrote:
> 
> Where is the proper place to get the kernel source?
> 
> I have both 2.2.12 and 2.3.16 from kernel.org but neither seem to be in sync
> with the other developers on this list.  (I had to hand patch the PCI changes
> submitted. And the 2.3.16 will not even build due to a missing header?)
> 
> I know 2.3.16 is a development snapshot and I can't complain about that.  I
> have seen many posts for the "vger" trees and the only web/ftp site I have
> found was for Sparc and only has 2.1 version kernels?

Look at http://www.ppc.kernel.org/homepage.html#kernel
There is the link to anonymous cvs access to the vger tree.
The link to Paul Mackerras' site on that page doesn't work, but if you
browse the list archive  of the last week or so, you'll find this, too.

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/