* RE: build trouble with GCC 3.0
@ 2002-01-08 18:07 Khoa Do
0 siblings, 0 replies; 3+ messages in thread
From: Khoa Do @ 2002-01-08 18:07 UTC (permalink / raw)
To: 'Richard.Erlston@za.didata.com'; +Cc: 'gcc-help@gcc.gnu.org'
Oops, I just realized that the cygwin version is 1.3.6 and not
2.125.2.5
-----Original Message-----
From: Khoa Do
Sent: Tuesday, January 08, 2002 1:04 PM
To: 'Richard.Erlston@za.didata.com'
Cc: 'gcc-help@gcc.gnu.org'
Subject: build trouble with GCC 3.0
According to the build status page, I should be able to build GCC
3.0 on i686 cygwin.
Does anybody have the same problems that I have or pointers on what I could
be doing
wrong?
Configuration:
Win2K Advanced Server SP 2,
Cygwin version 2.125.2.5,
GCC 3.0
1. I checked the build status of GCC 3.0 and found:
i686-pc-cygwin Successful: 3.0
2. I then copied all of the GCC 3.0 tarballs
and expanded all of them into the
/home/Administrator directory
3. Then, I opened up my bash shell
and executed the following commands
per instructions on the
url: http://gcc.gnu.org/install/
$ pwd
/home/Administrator/gcc-3.0
$ cd ..
$ pwd
/home/Administrator
$ mkdir gccobjdir
$ cd gccobjdir
$ ../gcc-3.0/configure
[[[A BUNCH OF STUFF HAPPENS]]]...
updating cache ../config.cache
creating ./config.status
creating Makefile
creating install-defs.sh
creating config.h
[[[SO FAR SO GOOD]]]
$ make bootstrap
[[[A BUNCH OF STUFF HAPPENS]]]...
./gencodes.exe ../../gcc-3.0/gcc/config/i386.md > tmp-codes.h
../../gcc-3.0/gcc/config/i386/i386.md:289: unknown rtx code
'define_asm_attribut
ength" "128")'
make[2]: *** [s-codes] Error 1
make[2]: Leaving directory '/home/Administrator/gccobjdir/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory '/home/Adminstrator/gccobjdir/gcc'
make: *** [bootstrap] Error 2
[[[THIS IS WHERE THE TROUBLE STARTS]]]
$ make install
/bin/sh ../gcc-3.0/mkinstalldirs /usr/local /usr/local
make[1]: Entering directory '/home/Administrator/gccobjdir/gcc'
./gencodes.exe ../../gcc-3.0/gcc/config/i386/i386.md > tmp-codes.h
../../gcc-3.0/gcc/config/i386/i386.md: unknown rtx code 'define_asm_attribut
's
../../gcc-3.0/gcc/config/i386/i386.md:289: following context is ' [(set_attr
"l
ength" "128")'
make[1]: *** [s-codes] Error 1
make[1]: Leaving directory '/home/Administrator/gccobjdir/gcc'
make: *** [install-gcc] Error 2
[[[CAN'T GO ANY FURTHER]]]
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: build trouble with GCC 3.0
@ 2002-01-09 11:22 Khoa Do
0 siblings, 0 replies; 3+ messages in thread
From: Khoa Do @ 2002-01-09 11:22 UTC (permalink / raw)
To: 'Dylan Cuthbert'; +Cc: 'gcc-help@gcc.gnu.org'
Thanks that did help. The difference was that I tried the
monolithic package instead of trying to put together different packages like
core, c, c++, java, ... I will have to use the latest stable version and
report to the mailing list my experience.
-----Original Message-----
From: Dylan Cuthbert [mailto:dylan@q-games.com]
Sent: Tuesday, January 08, 2002 6:21 PM
To: Khoa Do
Subject: Re: build trouble with GCC 3.0
I haven't tried with cygwin 1.3.6 but I've got gcc 3.0.2 compiled with 1.3.5
of cygwin and I doubt there's much of a difference.
The only problem I had was with the fastjar directory - it wouldn't compile
so I simply created a dummy makefile in that directory and it went through
fine. (ie. I created a Makefile to replace the original one that simply had
install:, all: and clean: on separate lines with no other commands)
...
^ permalink raw reply [flat|nested] 3+ messages in thread
* build trouble with GCC 3.0
@ 2002-01-08 13:05 Khoa Do
0 siblings, 0 replies; 3+ messages in thread
From: Khoa Do @ 2002-01-08 13:05 UTC (permalink / raw)
To: 'Richard.Erlston@za.didata.com'; +Cc: 'gcc-help@gcc.gnu.org'
According to the build status page, I should be able to build GCC
3.0 on i686 cygwin.
Does anybody have the same problems that I have or pointers on what I could
be doing
wrong?
Configuration:
Win2K Advanced Server SP 2,
Cygwin version 2.125.2.5,
GCC 3.0
1. I checked the build status of GCC 3.0 and found:
i686-pc-cygwin Successful: 3.0
2. I then copied all of the GCC 3.0 tarballs
and expanded all of them into the
/home/Administrator directory
3. Then, I opened up my bash shell
and executed the following commands
per instructions on the
url: http://gcc.gnu.org/install/
$ pwd
/home/Administrator/gcc-3.0
$ cd ..
$ pwd
/home/Administrator
$ mkdir gccobjdir
$ cd gccobjdir
$ ../gcc-3.0/configure
[[[A BUNCH OF STUFF HAPPENS]]]...
updating cache ../config.cache
creating ./config.status
creating Makefile
creating install-defs.sh
creating config.h
[[[SO FAR SO GOOD]]]
$ make bootstrap
[[[A BUNCH OF STUFF HAPPENS]]]...
./gencodes.exe ../../gcc-3.0/gcc/config/i386.md > tmp-codes.h
../../gcc-3.0/gcc/config/i386/i386.md:289: unknown rtx code
'define_asm_attribut
ength" "128")'
make[2]: *** [s-codes] Error 1
make[2]: Leaving directory '/home/Administrator/gccobjdir/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory '/home/Adminstrator/gccobjdir/gcc'
make: *** [bootstrap] Error 2
[[[THIS IS WHERE THE TROUBLE STARTS]]]
$ make install
/bin/sh ../gcc-3.0/mkinstalldirs /usr/local /usr/local
make[1]: Entering directory '/home/Administrator/gccobjdir/gcc'
./gencodes.exe ../../gcc-3.0/gcc/config/i386/i386.md > tmp-codes.h
../../gcc-3.0/gcc/config/i386/i386.md: unknown rtx code 'define_asm_attribut
's
../../gcc-3.0/gcc/config/i386/i386.md:289: following context is ' [(set_attr
"l
ength" "128")'
make[1]: *** [s-codes] Error 1
make[1]: Leaving directory '/home/Administrator/gccobjdir/gcc'
make: *** [install-gcc] Error 2
[[[CAN'T GO ANY FURTHER]]]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-01-09 19:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-08 18:07 build trouble with GCC 3.0 Khoa Do
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 11:22 Khoa Do
2002-01-08 13:05 Khoa Do
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 read-only IMAP folder(s) and NNTP newsgroup(s).