Hi,

I have been trying to build the latest gnu-tool chain release, for bare metal (or32-elf-xxx), using following command..

./bld-all.sh --force --prefix /data/packages/or32-elf --or1ksim-dir /data/packages/or1ksim --no-uclibc --no-or32-linux

The build process breaks giving following error.. plz help, if im missing somethings.

--------------------------------------------
checking for suffix of object files... configure: error: in `/pekon/projects/downloads/gnu-src/bd-elf/or32-elf/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make: *** [configure-target-libgcc] Error 1
make (all-target-libgcc all-target-libstdc++-v3 all-target-newlib all-target-libgloss) failed.
--------------------------------------------

(attaching config.log generated from automake for analysis)


with regards, pekon

Hi pekon

My guess is that something is not working correctly on 64-bit. The failure is in the OpenRISC cross-compiler, which at present is only tested on 32-bit. Almost certainly there is a 32-bit assumption somewhere in the code.

You might like to post the corresponding configure script, so I can check exactly what it was trying to do.

It will be a little while before I get round to testing on 64-bit architectures (others may do so sooner). In the meantime could you file this as a bug.

Jeremy

--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com

Hi,
I run the script on my 64-bit Ubuntu 10.4 machine and it worked correctly. I executed:
./bld-all.sh --force --prefix /opt/openrisc --or1ksim-dir /opt/or1ksim --uclibc-dir uclibc --linux-dir linux --languages c --binutils-dir binutils-2.20.1/ --newlib-dir newlib-1.18.0/

the version of gnu-src I got is r569. Mine is no AMD but Intel i7.

Alonzo.

Now that is really weird. I wonder if there was a fail in your original SVN checkout (sometimes it seems files get left behind). You could try an svn update to see if anything more is downloaded.

If would also be useful to diff the directories on the two machines, to see if there are any differences. What OS was the non-Ubuntu machine running?

This problem does need to be tracked down.

Best wishes,

Jeremy

Hi Jeremy,

Sorry for delayed reply.. Some how i was not getting OpenRisc forum updates on my discussion.. so i missed tracking them..
Problem seems to be that build-script is not able to identify my system architecture (which is AMD64)
following is extract from my config.log.. (attaching the complete config.log also)

---------------------------------------------
hostname = pekon
uname -m = x86_64
uname -r = 2.6.38-8-generic
uname -s = Linux
uname -v = #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
---------------------------------------------

with regards, pekon

Also, I have filed a bug on opencore Bugzilla.. But somehow i cannot edit or update it (some permission issues).. Following is link to it
http://bugzilla.opencores.org/show_bug.cgi?id=54

with regards, pekon

Hi Pekon,

Thanks for filing this. We need to get serious about 64-bit with the tool chain. I haven't got to the bottom of why Bugzilla permissions aren't quite right. I'd like it that bugs can be updated, but all I seem to be able to give people is full permission to modify the bug.

Jeremy

Hey Alonzo,
Is it possible for you to send me following files
(1) "config.in" (created while building bare-metal or1200 tool-chain on Ubuntu x86_64i7 Intel)
(2) "list of installed packages" of your OS (created via Synaptic Package Manager)

I want to track down why build is not recognizing my OS version.. or if its some package version issue..

thanks..
with regards, pekon

I installed the toolchain under Ubuntu 10.04 LTS on a 64 bit machine and ran into this error.
It turned out that the checkout of the repository was not complete.
It worked out fine after I ran multiple svn checkouts until I had the complete repository.

Hi Clockworkred

Have you had that problem recently. The SVN issue should have been fixed a month or two ago.

Jeremy

Hi Jeremy,

svn checkout stopped several times with a connection lost message.
In my first checkout, another svn co brought up a message that the repository's location
had changed, actually to the same address I checked out from, and that I should relocate.

So after some tries I checked it out again. Connection was also lost a few times,
but this time I did not get the relocate message and in the end I got the checkout complete
message.

Sorry, I don't have the shell open anymore to copy the error messages.

Anyway, I just made the post, because when I tried installing the first time I ran
into the above mentioned error message and first thought it is a problem with a missing
library. So thought I mentioned it, that the above error can also mean a non-complete svn co.

Daniel