Build errors with L4
Bob Stewart
robjsstewart at verizon.net
Mon Jul 29 16:16:52 CEST 2013
Thanks Matthias.
Bob
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 29, 2013 9:12:02 AM Matthias Lange <mlange at sec.t-labs.tu-berlin.de>
wrote:
> On 29.07.2013, at 14:05, Bob Stewart <robjsstewart at verizon.net> wrote:
>
> > Let me more precise now that I'm on the machine I was trying to build on.
> > Following the directions on the L4 Runtime Environment page, I completed
> steps 1, 2 and 3. On step 4, configuring the build tree, I selected my
> target architecture and platform and left the Building options as they
> were. This make failed with the error "no suitable compiler found". This
> message appeared to come from the script .arm-linux-SCRIPT which looks in
> various places for an arm gcc compiler. No seeing instructions on tools to
> be installed, I decided to create a directory of links to the tools from
> Genode which I had previously installed. That directory of links was added
> to PATH. So, for example, the link to arm-linux-gcc points to
> /usr/local/genode-gcc/bin/genode-arm-gcc. Step 4 now completed and the make
> in step ran until the error with the static library references occurred.
> > What is the corrected set of tools to be using for this?
>
> Mentor Graphic's CodeBench Lite Edition [1] is known to work. Just extract
> the archive to /usr/local/gcc and adapt the path in the .arm-linux-SCRIPT
> accordingly.
>
> Best,
> Matthias.
>
> [1]
> http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/request?id=478dff82-62bc-44b2-afe2-4684d83b19b9&downloadlite=scblite2012&fmpath=/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/form
>
> > Thank you
> > Bob Stewart
> >
> > Sent with AquaMail for Android
> > http://www.aqua-mail.com
> >
> > On July 29, 2013 6:37:46 AM Bob Stewart <robjsstewart at verizon.net> wrote:
> >> 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
> >>
> >> 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
> >
> > _______________________________________________
> > 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