newlib and libmaple « LeafLabs Garden

LeafLabs Garden » Community » The Lounge

newlib and libmaple

(9 posts) (3 voices)

Started 1 year ago by paulj
Latest reply from paulj

paulj
Member
I am running Gentoo Linux, and I have the arm-none-eabi toolchain already installed. gcc is at version 4.7.2, and newlib at version 2.0.0. When compiling libmaple, I get the following error:
```
build/./wirish/syscalls.o: In function

_exit':
/home/paul/maple/libmaple/./wirish/syscalls.c:60: multiple definition of
```
_sbrk'
/usr/lib/gcc/arm-none-eabi/4.7.3/../../../../arm-none-eabi/lib/libc.a(lib_a-syscalls.o):/var/tmp/portage/cross-arm-none-eabi/newlib-2.0.0/work/newlib-2.0.0/newlib/libc/sys/arm/syscalls.c:482: first defined here
/usr/lib/gcc/arm-none-eabi/4.7.3/../../../../arm-none-eabi/lib/libc.a(lib_a-syscalls.o): In function `_sbrk':
syscalls.c:(.text+0x6a8): undefined reference to `end'
collect2: error: ld returned 1 exit status
make: *** [build/maple.elf] Error 1
`

This appears to be a clash between the newlib library and the libmaple library.

So my question is this: what do I need to do to stop the compiler linking to the newlib code (assuming it is not necessary?). I compile following the instructions in the "Command Line Tools" section of the wiki.

Alternatively, do I have to do something else, such as loading an earlier version of newlib, or compiling it with some options set when making the toolchain?

Many thanks for your help!

Rgds.,
Paul
Posted 1 year ago #
ala42
Member

Not sure how this is solved in the maple environment. If you use a makefile to build your maple stuff, add -nostartfiles to the linker options used to build the .elf file.

Posted 1 year ago #
paulj
Member

Thanks for the quick response. It looks like even with that option, it is referencing newlib:

build/./libraries/Wire/Wire.o: In function `__static_initialization_and_destruction_0':
/home/paul/maple/libmaple/./libraries/Wire/Wire.cpp:182: undefined reference to `__dso_handle'
/usr/lib/gcc/arm-none-eabi/4.7.3/../../../../arm-none-eabi/lib/libc.a(lib_a-init.o): In function `__libc_init_array':
/var/tmp/portage/cross-arm-none-eabi/newlib-2.0.0/work/newlib-2.0.0/newlib/libc/misc/init.c:37: undefined reference to `_init'
/usr/libexec/gcc/arm-none-eabi/ld: build/maple.elf: hidden symbol `__dso_handle' isn't defined
/usr/libexec/gcc/arm-none-eabi/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make: *** [build/maple.elf] Error 1

At the moment, I am working with the demo program and Makefile which comes with libmaple. I am not working in the maple environment, but on the command line. If I install the Sourcery toolchain bundle pointed at by Maple, everything works, but I wanted to be able to use the system wide tools I have installed already. I suppose I want to learn enough to get around these problems!

Thanks again for your response.

Posted 1 year ago #
gbulmer
Moderator

paulj - have you tried a slightly simpler program, e.g blink?
That might reduce the number and type of errors.

(Full disclosure: I am not a member of Leaflabs staff.)

Posted 1 year ago #
paulj
Member

gbulmer - thanks for the suggestion.

With the blink program, the result is very similar:

[code]
build/./libraries/Wire/Wire.o: In function `__static_initialization_and_destruction_0':
/home/paul/maple/libmaple/./libraries/Wire/Wire.cpp:182: undefined reference to `__dso_handle'
/usr/lib/gcc/arm-none-eabi/4.7.3/../../../../arm-none-eabi/lib/libc.a(lib_a-init.o): In function `__libc_init_array':
/var/tmp/portage/cross-arm-none-eabi/newlib-2.0.0/work/newlib-2.0.0/newlib/libc/misc/init.c:37: undefined reference to `_init'
/usr/libexec/gcc/arm-none-eabi/ld: build/maple.elf: hidden symbol `__dso_handle' isn't defined
/usr/libexec/gcc/arm-none-eabi/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make: *** [build/maple.elf] Error 1
[/code]

I am looking all over the place for solutions, but as yet not come across anything. If anyone has any other ideas - I am keen to try them!

Thanks!

Posted 1 year ago #
paulj
Member

PS - How do I get the markup to work in this forum? The instructions are quite terse! :)

Posted 1 year ago #
paulj
Member

Ok - got it sorted. Instead of using the crossdev tool supplied with Gentoo, I compiled the toolchain and libraries from source, and installed them in my local user bin directory. Compilation is working, I now need to confirm the programs are working correctly. I will document what I did (basically followed http://kunen.org/uC/gnu_tool.html, but with updated versions of the tools), and post a link in case others have similar issues.

Thanks for your help!

Posted 1 year ago #
gbulmer
Moderator
paulj - Thank you for updating the thread. That is a very helpful. Presumably the libraries were compiled incorrectly?

I hope everything goes smoothly now.

Yes, forum markup is a bit odd, and very hard to describe as it is so primitive, and gobble up the description.

I never use the code tag. I use the single backquote, \`, aka backtick (The backslash \ needs to be there because the markup is so poor I haven't found a way to show a backquote alone.)

Just put it around as many lines of code as you need to quote as code.
```
block
of
code
```
like that.
Then the other markup is very xml-ish <word>text to effect</word>
and the opening '<' 'a' anchor contains href=URL then '>' your link text '<' '/' 'a' '>'
Posted 1 year ago #
paulj
Member

I guess some of the options auto selected by crossdev are creating the libraries in a way which then leads to the problems I experienced. I am sure crossdev is a good tool, but I would rather understand the process detail so when I have a problem like this I can fix it. I will probably follow the non-crossdev route for other cross compilation environments I have in future. Thanks for the markup information. The output from make actually has backticks in it, so I guess that is difficult for the forum software to understand. I will use the xml style approach next time!

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.