From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-user@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem compiling egcs
Date: Sun, 30 May 1999 14:21:25 +0200 [thread overview]
Message-ID: <37512D45.1088A55A@wanadoo.fr> (raw)
In-Reply-To: 374E4267.5BF46F98@wanadoo.fr
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. ]]
next parent reply other threads:[~1999-05-30 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <374E4267.5BF46F98@wanadoo.fr>
1999-05-30 12:21 ` Martin Costabel [this message]
1999-05-31 14:19 ` Kernel sources Jerry Quinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37512D45.1088A55A@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).