Build errors with L4

Bob Stewart robjsstewart at verizon.net
Mon Jul 29 12:37:46 CEST 2013


Because I was using the genode toolchain whose tools don't have the 
arm-linux- prefix, I created a directory of links which have that prefix 
(e.g. arm-linux-gcc) which link to the appropriate tool in the genode tools 
directory (/usr/local/genode).

Bob Stewart


Sent with AquaMail for Android
http://www.aqua-mail.com


On July 28, 2013 6:14:41 PM Adam Lackorzynski <adam at os.inf.tu-dresden.de> 
wrote:
> On Sat Jul 27, 2013 at 16:36:24 -0400, Bob Stewart wrote:
> > I pulled down revisions 56 of l4re per the l4re download
> > instructions on an x86 platform running Ubuntu 13.04. I'm cross
> > compiling for an ARM 8 Beaglebone platform. I created a set of tool
> > links pointing to gcc, g++, ar, ld, etc. from the current Genode
> > toolchain. I then followed the l4 build instructions. The build
> > proceeded normally until is started to link in libc static libraries
> > at which point the following errors killed the build:
> > ...
> >   ==> Linking loader
> > /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__exit_handler.o):
> > In function `__new_exitfn':
> > 
> /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/_atexit.c:259:
> > undefined reference to `__emutls_v.__libc_errno'
> > Is there some undocumented compiler flag related to TLS I should be
> > setting somewhere to fix these library references?
>
> Not that I know of, it should just work. What do you mean with that you
> created links to binutils and gcc? When cross-compiling to ARM the tools
> should just be prefixed with arm-linux- and gcc/g++ etc. target the
> host.
>
>
> Adam
> --
> Adam                 adam at os.inf.tu-dresden.de
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers






More information about the l4-hackers mailing list