Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-16 Thread Umut Tezduyar Lindskog
For the reference, -flto option was preventing static linker from making the assignments. Could be very well something specific to our toolchain. On Fri, Dec 12, 2014 at 11:50 PM, Umut Tezduyar Lindskog wrote: > On Fri, Dec 12, 2014 at 4:46 PM, Lennart Poettering > wrote: >> On Fri, 12.12.14 10:

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-12 Thread Umut Tezduyar Lindskog
On Fri, Dec 12, 2014 at 4:46 PM, Lennart Poettering wrote: > On Fri, 12.12.14 10:10, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > >> > >> > https://sourceware.org/bugzilla/show_bug.cgi?id=11133 >> > >> > But that's 4y old... Or is your toolchain that old? >> >> Shouldn't be: >> >> mipsisa32

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-12 Thread Lennart Poettering
On Fri, 12.12.14 10:10, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > > > > https://sourceware.org/bugzilla/show_bug.cgi?id=11133 > > > > But that's 4y old... Or is your toolchain that old? > > Shouldn't be: > > mipsisa32r2el-axis-linux-gnu-gcc --version > mipsisa32r2el-axis-linux-gnu-gcc

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-12 Thread Umut Tezduyar Lindskog
In case someone has an idea, here is the full linker command: /bin/sh ./libtool --tag=CC --mode=link mipsisa32r2el-axis-linux-gnu-gcc -isystem /build/target/mipsisa32r2el-axis-linux-gnu/include -isystem /build/target/mipsisa32r2el-axis-linux-gnu/usr/include -std=gnu99 -pipe -Wall -Wextra -Wno-

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-12 Thread Umut Tezduyar Lindskog
On Fri, Dec 12, 2014 at 12:24 AM, Lennart Poettering wrote: > On Thu, 11.12.14 23:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > >> Trying to build 218 but I am getting undefined reference error. The >> source code of bus-error.c mentions that gcc magically maps these >> variables but not

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-12 Thread Umut Tezduyar Lindskog
Hi, On Fri, Dec 12, 2014 at 7:56 AM, Matthias Urlichs wrote: > Hi, > > Lennart: >> >> The idea is that any .c file linked into a binary can define >> additional maps, and we collect them all simply by iterating through >> __start_BUS_ERROR_MAP to __stop_BUS_ERROR_MAP. >> > Unless there are none o

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-11 Thread Matthias Urlichs
Hi, Lennart: > > The idea is that any .c file linked into a binary can define > additional maps, and we collect them all simply by iterating through > __start_BUS_ERROR_MAP to __stop_BUS_ERROR_MAP. > Unless there are none of these entries. Umut: Does the cross compiling somehow not include any d

Re: [systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-11 Thread Lennart Poettering
On Thu, 11.12.14 23:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > Trying to build 218 but I am getting undefined reference error. The > source code of bus-error.c mentions that gcc magically maps these > variables but not for me. > > What is doing the mapping? __attribute__ ((__section_

[systemd-devel] Build error with 218 - undefined reference to `__start_BUS_ERROR_MAP'

2014-12-11 Thread Umut Tezduyar Lindskog
Trying to build 218 but I am getting undefined reference error. The source code of bus-error.c mentions that gcc magically maps these variables but not for me. What is doing the mapping? __attribute__ ((__section__("BUS_ERROR_MAP"))) ? Could it be that mentioned "gcc magic" is not supported on cr