dlan^ has quit [Remote host closed the connection]
unclouded has joined #qi-hardware
Ornotermes has quit [*.net *.split]
eintopf has quit [*.net *.split]
freespac1 has quit [*.net *.split]
uwe_mobile__ has quit [*.net *.split]
mth has quit [*.net *.split]
jow_laptop has quit [*.net *.split]
viric has quit [*.net *.split]
Ornotermes has joined #qi-hardware
eintopf has joined #qi-hardware
freespac1 has joined #qi-hardware
uwe_mobile__ has joined #qi-hardware
viric has joined #qi-hardware
mth has joined #qi-hardware
jow_laptop has joined #qi-hardware
eintopf has quit [*.net *.split]
Ornotermes has quit [*.net *.split]
freespac1 has quit [*.net *.split]
uwe_mobile__ has quit [*.net *.split]
Ornotermes has joined #qi-hardware
eintopf has joined #qi-hardware
freespac1 has joined #qi-hardware
uwe_mobile__ has joined #qi-hardware
rz2k has quit [Read error: Connection reset by peer]
rz2k has joined #qi-hardware
kyak has quit [Read error: Operation timed out]
rz2k has quit []
kyak has joined #qi-hardware
kyak has joined #qi-hardware
kyak has quit [Changing host]
kyak has quit [Read error: Operation timed out]
larsc has joined #qi-hardware
kyak has joined #qi-hardware
kyak has quit [Changing host]
kyak has joined #qi-hardware
_whitelogger_ has joined #qi-hardware
FDCX has joined #qi-hardware
wolfspraul has quit [Quit: leaving]
jekhor has joined #qi-hardware
unclouded has quit [Ping timeout: 245 seconds]
kyak has quit [Ping timeout: 256 seconds]
rz2k has joined #qi-hardware
kyak has joined #qi-hardware
kyak has joined #qi-hardware
kyak has quit [Changing host]
rzk has joined #qi-hardware
rz2k has quit [Ping timeout: 264 seconds]
<viric>
zear: don't link with ld. link with gcc!
<viric>
ld is too low level
<viric>
zear: and put -lc at the end. symbols are resolved in the order you supply libraries.
Alarm_ has joined #qi-hardware
<zear>
viric, when using ld, -lc at the end doesn't change anything
<zear>
I will need to modify the internal toolchain's makerules to link with gcc
<viric>
then, don't supply -lc and such things
<viric>
gcc knows how to link a c program.
<zear>
well, -lc is supplied automatically by the internal makerules :)
<viric>
ld is a quite dumb linker. it doesn't know about c.
<zear>
the whole problem is really the lack of dev documentation in the project
<zear>
and decuding everything from the comments of the headers is not exactly the good way to learn about stuff
<zear>
by the way, i always thought that when you link with gcc, it calls ld
<zear>
but seems it's not how it is
<wpwrak>
gcc does call ld for linking. but it provides a number of options you may find hard to guess.
<wpwrak>
you can of course strace it and see what the arguments are, then work from that
<zear>
yes, but then a new version of gcc comes with some better optimizations towards linking
<zear>
so i think always linking with gcc is safer
<wpwrak>
there may not be a lot of changes. but yes, if something changes, then you probably wouldn't notice and spend a lot of time tracking the mystery problem down