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
u...@tezduyar.com wrote:
On Fri, Dec 12, 2014 at 4:46 PM, Lennart Poettering
On Fri, Dec 12, 2014 at 12:24 AM, Lennart Poettering
lenn...@poettering.net 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
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
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 (GCC 4.7.2
On Fri, Dec 12, 2014 at 4:46 PM, Lennart Poettering
lenn...@poettering.net 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:
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 cross
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__
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
data
