Message

Reply | Reply all

Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

From: Balint Cristian<cristian.balint@o...>
Date: Wed Sep 14 11:59:04 CEST 2005
Subject: [openrisc] Problems with GNU toolchain instalation Mandrake 10.1
On Wednesday 14 September 2005 12:52, Aleksandar Sutic wrote:
>     OK, I'll see to rebuild binutils and try to install gcc then.
>
>     If this doesn't help, I'm planning to install FC4 and to use RPMs from your site. Then I would install the following:
>    
>     binutils-or32-2.15-1.i386.rpm   
>     binutils-or32-debuginfo-2.15-1.i386.rpm   
>     gcc-or32-3.4.2-2.i386.rpm
>     gcc-or32-debuginfo-3.4.2-2.i386.rpm
>     glibc-kernheaders-or32-2.4-9.1.87.i386.rpm   
>     or1ksim-1.9-1.i386.rpm
>     or1ksim-debuginfo-1.9-1.i386.rpm

Yes, these are enough.

But *-debuginfo-* is not neccesary, these are only for debug binutils/gcc itself.

I try to build up gdb-or32 for or32 target today.
Olso plan to rebuild/update latest today-released or1k-sim !

>
>     Is this OK with you? Is there anything else I should install before installing these RPMs? What about GDB? I guess it is not included in these RPMs. DDD or Insigth?
>
>     And Balint, could you send me a screenshoot of your or32 envieronment? It may be helpfull to see.

Well, i can send you but i use/work in text mode only, i can send an or32-kernel
booting in or1k-sim [a bit later please, now i am at my work-office]


>
>     Please excuse my ignorance. I hope I'm not asking tou much.

No, you are always welcome !


>
>     Aleksandar
>
> Balint Cristian wrote:
> On Wednesday 14 September 2005 11:42, Aleksandar Sutic wrote:
>
>     I've installed binutils before building GCC, of course. Everything went smoothly and they are installed in /usr/or32-uclinux /bin. I configured Makefile with the line you suggested but the problem remains. Any ideas?
>
>     Could it be that installing in /usr directory leads to these poblems? I know that this is not likely, but maybe there are some predefined paths in configure file.
>
>     Remark: I also tryed something like
>
>     ./configure --target=or32-uclinux --exec-prefix=/usr/or32-uclinux --enable-languages=c
>
>
> Try not pass this: --exec-prefix=/usr/or32-uclinux
>
> Rebuild binutils than build gcc.
>
> It anyway will be located in /usr/or32-uclinux with/without the --exec-prefix=/usr/or32-uclinux.
>
>
>
>
>
>
>     and the error occured stating that arm-uclinux-ar tool could not be found. This makes me think that more parameters should be passed to configure in order to build everything properly?!?
>
>     Thanks,
>        Aleksandar
>
> Balint Cristian wrote:
>  
> ----- Original Message -----
> From: Aleksandar Sutic
> To: Balint Cristian ; openrisc@o...
> Sent: Tuesday, September 13, 2005 9:56 AM
> Subject: Re: [openrisc] Problems with GNU toolchain instalation Mandrake 10.1
>
>
>     Baliant,
>
>     Thanks for your help. I've install flex/byacc/bison tools and I was able to install binutils. However, now I have problems with building GCC. Here is what I did:
>
> # mkdir b-gcc
> # cd b-gcc
> # ../gcc-3.4.2/configure --target=or32-uclinux --prefix=/usr/or32-uclinux/ --exec-prefix=/usr/or32-uclinux/or32-uclinux/ --with-gnu-as --with-gnu-ld --verbose --enable-languages=c 2>&1 | tee configure.log
>
> This line below is enough, dont pass --with-gnu-ld argument:
> ./configure --target=or32-uclinux --enable-languages=c
>  
> gcc must be builded only after you have binutils installed for or32-uclinux !!
>  
>
>     I used here exec-prefix instead of local-prefix since my system told me that local-prefix does not exist (or something like that). I searched through configure file and the only thing that seamed to look like local-prefix was exec-prefix (I look for the appropriate paths). Since I'm a quite newbee for Linux, I have no idea if this is OK.
>
>     Anyway, configure went fine and the Makefile was generated. Then I did:
>
> #make all 2>&1 | tee make.log
>
>     and the make process produced errors. Here is the end of the output:
>
>     /home/sasa/or1k/b-gcc/gcc/xgcc -B/home/sasa/or1k/b-gcc/gcc/ -B/usr/or32-uclinux/or32-uclinux/or32-uclinux/bin/ -B/usr/or32-uclinux/or32-uclinux/or32-uclinux/lib/ -isystem /usr/or32-uclinux/or32-uclinux/or32-uclinux/include -isystem /usr/or32-uclinux/or32-uclinux/or32-uclinux/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include     -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc-3.4.2/gcc -I../../gcc-3.4.2/gcc/. -I../../gcc-3.4.2/gcc/../include  -DL__mulsi3 -xassembler-with-cpp -c ../../gcc-3.4.2/gcc/config/or32/or32.S -o libgcc/./__mulsi3.o
> ../../gcc-3.4.2/gcc/config/or32/or32.S: Assembler messages:
> ../../gcc-3.4.2/gcc/config/or32/or32.S:12: Error: invalid character '.' in mnemonic
> ../../gcc-3.4.2/gcc/config/or32/or32.S:13: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:14: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:15: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:16: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:18: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:19: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:20: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:21: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:22: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:24: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:25: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:26: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:28: Error: invalid character '.' in mnemonic > ../../gcc-3.4.2/gcc/config/or32/or32.S:29: Error: invalid character '.' in mnemonic > make[2]: *** [libgcc/./__mulsi3.o] Error 1 > make[2]: Leaving directory `/home/sasa/or1k/b-gcc/gcc' > make[1]: *** [libgcc.a] Error 2 > make[1]: Leaving directory `/home/sasa/or1k/b-gcc/gcc' > make: *** [all-gcc] Error > >     This tells me that make process does not understand or32 instruction set and it gets confused by dots in each instruction. Do I still miss some tools on my system? Is there any problem in configuration? I've attached the log files. > >      I hope you, or somebody else will be able to help me. Thanks! > >     Best regards, >        Aleksandar > > > Balint Cristian wrote: > On Tuesday 16 August 2005 10:20, Aleksandar Sutic wrote: > > Hi! > > I have problem in compiling or32 GNU toolchain on Mandrake 10.1 > distro. Since I'm real newbie for OR321000 architecture (and to Linux > also), I would be happy if some of you guy could help and give me some > guidelines. > > I started following the instructions I've found at > http://www.opencores.org/projects.cgi/web/or1k/gnu_toolchain_port, but I > couldn't pass the first step, i.e. errors occurred when I tried to build > binutils. Here's what I did: > > mkdir b-b > cd b-b > ../binutils/configure --target=or32-elf --prefix=/usr/local/or32-elf > (also tried with other targets) > make > > And after make I have errors: > ... > bucomm.o(.text+0x3f5): In function `make_tempname': > ../../binutils/binutils/bucomm.c:236: warning: the use of `mktemp' is > dangerous, better use `mkstemp' > /bin/sh ../../binutils/binutils/../ylwrap "" > ../../binutils/binutils/arparse.y y.tab.c arparse.c y.tab.h arparse.h -- -d > ../../binutils/binutils/../ylwrap: line 86: -d: command not found > make[3]: *** [arparse.c] Error 1 > make[3]: Leaving directory `/home/sasa/or1k/b-b/binutils' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/sasa/or1k/b-b/binutils' > make[1]: *** [all-recursive-am] Error 2 > make[1]: Leaving directory `/home/sasa/or1k/b-b/binutils' > make: *** [all-binutils] Error > > I've attached both log files so that you may be able to see what > went wrong. I've read somewhere that the or32 architecture, with the > necessary tools, is only tested under RedHat distro, so I guess that > there might exist problems with other distros. Any comment on this? > > > BTW as comment: > No, i dont thing other distros is a problem, i personaly builded some toolchain in rpm format but only for > Fedora. > > http://openrisc.rdsor.ro/ToolChain/ > > > Also, I would like to know what is the current status of the Linux > 2.6 port, and if there is newer version of uCLinux for or32 architecture? > > Regards, > Aleksandar > > > > > > > > > -- Balint Cristian area network engineer ............................................................................. RCS & RDS Oradea Tel.: +40359.400.400 Fax: +40359.400.444 http://www.rcs-rds.ro suport@r... .................................................................................... Privileged/Confidential Information may be contained in this message. If you are not in the addresses indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such a case, you should destroy this message and kindly notify the sender by reply e-mail.

Reference	Author
[openrisc] Problems with GNU toolchain instalation Mandrake 10.1	Aleksandar Sutic