OpenCores
no use no use 1/1 no use no use
building toolchain
by Unknown on Dec 18, 2004
Not available!
Hi All, A few small details trying to follow the directions on http://www.opencores.org/projects.cgi/web/or1k/gnu_toolchain_port: 1) cvs -d :pserver:cvs@cvs.opencores.org:/home/oc/cvs -z9 co or1k/uclibc reports an error: cvs server: cannot find module `or1k/uclibc' - ignored cvs [checkout aborted]: cannot expand modules I must be missing something but i can't figure out what. please gimme a hint :) 2) configure command for gcc has wrong path in it (gcc-3.1 instead of gcc-3.2.3) 3) small problem building gdb on gcc-3.4.3. here is a patch that fixes the problem: --- gdb/or1k-tdep.c 9 Apr 2003 20:40:10 -0000 1.21 +++ gdb/or1k-tdep.c 18 Dec 2004 04:42:05 -0000 @@ -2381,7 +2381,7 @@ td = (struct htrace_data_struct *) malloc (TRACE_DATA_SIZE * length); length = fread (td, TRACE_DATA_SIZE, length, f); for (i = 0; i
building toolchain
by Unknown on Dec 18, 2004
Not available!
* Vladimir Senkov (hangup@gmail.com) wrote:
Hi All, A few small details trying to follow the directions on http://www.opencores.org/projects.cgi/web/or1k/gnu_toolchain_port: 1) cvs -d :pserver:cvs@cvs.opencores.org:/home/oc/cvs -z9 co or1k/uclibc reports an error: cvs server: cannot find module `or1k/uclibc' - ignored cvs [checkout aborted]: cannot expand modules I must be missing something but i can't figure out what. please gimme a hint :) 2) configure command for gcc has wrong path in it (gcc-3.1 instead of gcc-3.2.3) 3) small problem building gdb on gcc-3.4.3. here is a patch that fixes the problem: --- gdb/or1k-tdep.c 9 Apr 2003 20:40:10 -0000 1.21 +++ gdb/or1k-tdep.c 18 Dec 2004 04:42:05 -0000 @@ -2381,7 +2381,7 @@ td = (struct htrace_data_struct *) malloc (TRACE_DATA_SIZE * length); length = fread (td, TRACE_DATA_SIZE, length, f); for (i = 0; i


thanks for corrections...

the uclibc that used to be in or1k/uclibc is now in or1k/obsolete/uclibc
(i suggest you use it only if building uclibc).

the uclibc for use with linux is now in or1k/linux/uclibc.

best regards,
p.

building toolchain
by Unknown on Dec 18, 2004
Not available!
Matjaz,

Thanks a lot for such a quick answer!
or1k/obsolete/uclibc works, but or1k/linux/uclibc gives me the same error:
cvs server: cannot find module `or1k/linux/uclibc' - ignored
cvs [checkout aborted]: cannot expand modules
What should i read
Anything i'm missing here?

Regards,
Vladimir.
building toolchain
by Unknown on Dec 18, 2004
Not available!
* Vladimir Senkov (hangup@gmail.com) wrote:
Matjaz,

Thanks a lot for such a quick answer!
or1k/obsolete/uclibc works, but or1k/linux/uclibc gives me the same error:
cvs server: cannot find module `or1k/linux/uclibc' - ignored
cvs [checkout aborted]: cannot expand modules
What should i read
Anything i'm missing here?
sorry, my mistake, it acctually: or1k/linux/uClibc (notice the capital 'C') regards, p. PS. You can also browse CVS here http://www.opencores.org/cvsweb.shtml/
building toolchain
by Unknown on Dec 19, 2004
Not available!
Hi Matjaz, Thanks again for such a quick response. This worked fine! cvsweb works great too. I'm now having an issue that i'm not quite sure about: when i'm trying to build this uClibc, i'm getting an error: vfork.c:6: `__NR_vfork' undeclared i'm suspeciting something is wrong with: ldso/include/ld_syscalls.h -> ../ldso/or32/ld_syscalls.h this link points to a file that does not exist. i don't have or32 directory in ldso :( Anything obvious i'm missing here? I was able to successfully build the "obsolete" uclibc, but when trying to configure simulator test progs i got errors: /opt/or32-uclinux/bin/../lib/gcc-lib/or32-uclinux/3.2.3/../../../libc.a(__uClibc_main.o): In function `___uClibc_main': __uClibc_main.o(.text+0x2c): undefined reference to `___init_stdio' __uClibc_main.o(.text+0x30): undefined reference to `___init_stdio' so i guess i really need to use linux/uClibc instead. Regards, Vladimir. On Sat, 18 Dec 2004 22:22:14 +0100, Matjaz Breskvar phoenix@opencores.org> wrote:
* Vladimir Senkov (hangup@gmail.com) wrote:
> Matjaz,
>
> Thanks a lot for such a quick answer!
> or1k/obsolete/uclibc works, but or1k/linux/uclibc gives me the same error:
> cvs server: cannot find module `or1k/linux/uclibc' - ignored
> cvs [checkout aborted]: cannot expand modules
> What should i read
> Anything i'm missing here?
sorry, my mistake, it acctually: or1k/linux/uClibc (notice the capital 'C') regards, p. PS. You can also browse CVS here http://www.opencores.org/cvsweb.shtml/



--
Regards,
Vladimir

building toolchain
by Unknown on Dec 19, 2004
Not available!
* Vladimir Senkov (hangup@gmail.com) wrote:
Hi Matjaz,

Thanks again for such a quick response.
This worked fine! cvsweb works great too.
I'm now having an issue that i'm not quite sure about:
when i'm trying to build this uClibc, i'm getting an error:
vfork.c:6: `__NR_vfork' undeclared
i'm suspeciting something is wrong with:
ldso/include/ld_syscalls.h -> ../ldso/or32/ld_syscalls.h
this link points to a file that does not exist. i don't have or32
directory in ldso :(
Anything obvious i'm missing here?


hmm, are you trying to build uclibc with ld.so
(dynamic linker) support ? The dynamic linker for or32 in uclibc
is not yet implemented. For a start i'd also suggest you try the default
or32 config for uclibc. If you've done so then please send me more datails
about how you tried to build linux and then uclibc...

I was able to successfully build the "obsolete" uclibc, but when
trying to configure simulator test progs i got errors:
/opt/or32-uclinux/bin/../lib/gcc-lib/or32-uclinux/3.2.3/../../../libc.a(__uClibc_main.o):
In function `___uClibc_main':
__uClibc_main.o(.text+0x2c): undefined reference to `___init_stdio'
__uClibc_main.o(.text+0x30): undefined reference to `___init_stdio'


this could be binutils/linker bug. can you try extracting '__init_stdio.o'
from libc.a and then link your program explicitly with it. (you can use ar
for that, and i think the complete procedure must be in the mailing list
archives...)

regards,
p.

no use no use 1/1 no use no use
© copyright 1999-2026 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.