Linker Error L1100

done78 — Mon, 11 Oct 2010 21:13:12 GMT

Hello,

I have just imported a project developed with CW 6.3 in the new CW 10.0, using HCS08 Toolchain; when I try to build it, I get a lot of linker errors, i list here below:

ERROR L1100: Segments .absSeg0 (0x0) and .absSeg183 (0x0) overlap

ERROR L1100: Segments .absSeg1 (0x1) and .absSeg184 (0x1) overlap

ERROR L1100: Segments .absSeg2 (0x2) and .absSeg185 (0x2) overlap

ERROR L1100: Segments .absSeg3 (0x3) and .absSeg186 (0x3) overlap

ERROR L1100: Segments .absSeg4 (0x4) and .absSeg187 (0x4) overlap

ERROR L1100: Segments .absSeg5 (0x5) and .absSeg188 (0x5) overlap

ERROR L1100: Segments .absSeg6 (0x6) and .absSeg189 (0x6) overlap

ERROR L1100: Segments .absSeg7 (0x7) and .absSeg190 (0x7) overlap

ERROR L1100: Segments .absSeg8 (0x8) and .absSeg191 (0x8) overlap

ERROR L1100: Segments .absSeg9 (0x9) and .absSeg192 (0x9) overlap

ERROR L1100: Segments .absSeg10 (0xA) and .absSeg193 (0xA) overlap

ERROR L1100: Segments .absSeg11 (0xB) and .absSeg194 (0xB) overlap

ERROR L1100: Segments .absSeg12 (0xC) and .absSeg195 (0xC) overlap

ERROR L1100: Segments .absSeg13 (0xD) and .absSeg196 (0xD) overlap

ERROR L1100: Segments .absSeg14 (0xE) and .absSeg197 (0xE) overlap

ERROR L1100: Segments .absSeg15 (0xF) and .absSeg198 (0xF) overlap

ERROR L1100: Segments .absSeg16 (0x10) and .absSeg199 (0x10) overlap

ERROR L1100: Segments .absSeg17 (0x11) and .absSeg200 (0x11) overlap

ERROR L1100: Segments .absSeg153 (0x12) and .absSeg336 (0x12) overlap

ERROR L1100: Segments .absSeg154 (0x14) and .absSeg337 (0x14) overlap

ERROR L1100: Segments .absSeg18 (0x16) and .absSeg201 (0x16) overlap

ERROR L1100: Segments .absSeg19 (0x17) and .absSeg202 (0x17) overlap

ERROR L1100: Segments .absSeg20 (0x18) and .absSeg203 (0x18) overlap

ERROR L1100: Segments .absSeg21 (0x19) and .absSeg204 (0x19) overlap

ERROR L1100: Segments .absSeg22 (0x1A) and .absSeg205 (0x1A) overlap

ERROR L1100: Segments .absSeg23 (0x1B) and .absSeg206 (0x1B) overlap

ERROR L1100: Segments .absSeg24 (0x1C) and .absSeg207 (0x1C) overlap

ERROR L1100: Segments .absSeg25 (0x1D) and .absSeg208 (0x1D) overlap

ERROR L1100: Segments .absSeg26 (0x1E) and .absSeg209 (0x1E) overlap

ERROR L1100: Segments .absSeg27 (0x1F) and .absSeg210 (0x1F) overlap

ERROR L1100: Segments .absSeg155 (0x20) and .absSeg338 (0x20) overlap

ERROR L1100: Segments .absSeg28 (0x22) and .absSeg211 (0x22) overlap

ERROR L1100: Segments .absSeg29 (0x23) and .absSeg212 (0x23) overlap

ERROR L1100: Segments .absSeg30 (0x24) and .absSeg213 (0x24) overlap

ERROR L1100: Segments .absSeg31 (0x25) and .absSeg214 (0x25) overlap

ERROR L1100: Segments .absSeg32 (0x26) and .absSeg215 (0x26) overlap

ERROR L1100: Segments .absSeg33 (0x27) and .absSeg216 (0x27) overlap

ERROR L1100: Segments .absSeg34 (0x28) and .absSeg217 (0x28) overlap

ERROR L1100: Segments .absSeg35 (0x29) and .absSeg218 (0x29) overlap

ERROR L1100: Segments .absSeg36 (0x2A) and .absSeg219 (0x2A) overlap

ERROR L1100: Segments .absSeg37 (0x2B) and .absSeg220 (0x2B) overlap

ERROR L1100: Segments .absSeg38 (0x2D) and .absSeg221 (0x2D) overlap

ERROR L1100: Segments .absSeg39 (0x2E) and .absSeg222 (0x2E) overlap

ERROR L1100: Segments .absSeg40 (0x2F) and .absSeg223 (0x2F) overlap

ERROR L1100: Segments .absSeg41 (0x30) and .absSeg224 (0x30) overlap

ERROR L1100: Segments .absSeg42 (0x31) and .absSeg225 (0x31) overlap

ERROR L1100: Segments .absSeg43 (0x32) and .absSeg226 (0x32) overlap

ERROR L1100: Segments .absSeg44 (0x33) and .absSeg227 (0x33) overlap

ERROR L1100: Segments .absSeg45 (0x34) and .absSeg228 (0x34) overlap

ERROR L1100: Segments .absSeg46 (0x35) and .absSeg229 (0x35) overlap

It seems OK to me; please can someone explain me which steps i should take to spot where the error is ?

Thanks!!

Re: Linker Error L1100

Lundin — Tue, 12 Oct 2010 13:38:41 GMT

Abs seg refers to variables allocated with the non-standard @ operator. Unless you used this operator in your own code, the error is most likely caused by the Codewarrior register maps. Perhaps somehow the registers are allocated twice?

The best solution around the problem is to avoid the crappy Codewarrior register maps entirely, they aren't written in valid C and completely non-portable.

Re: Linker Error L1100

done78 — Tue, 12 Oct 2010 14:03:39 GMT

Thank you Lundin,

problem is that the project seemed to work correctly on CW 6.3; unluckily i can't use that version anymore since it doesn't run on Windows 7. I suspect it to be something gone wrong in importing the project in the new CW, might it be that ?

I didn't use the '@' operator, but ubluckily the problem seems to arise because of a third party library i have included in my project (a .lib file) and whose source code I'm not able to read. I really don't know....

Re: Linker Error L1100

Lundin — Tue, 12 Oct 2010 19:02:11 GMT

Yeah well... "importing projects" from older versions to newer versions have never worked flawlessly on any IDE, compiler or platform known to mankind.

Are you sure that library is written in pure ISO C?

Re: Linker Error L1100

CrasyCat — Wed, 13 Oct 2010 15:45:04 GMT

Hello

It looks like the I/O registers are defined twice using @ operator.

Check in your source code where you define 2 objects at address 0x00 for example.

Note you can remap this message to an information or directly disable it using the option -MsgSi1100 (Remap message to information) or MsgSd1100 (disable message).

CrasyCat

topic Linker Error L1100 in CodeWarrior for MCU

Linker Error L1100

Re: Linker Error L1100

Re: Linker Error L1100

Re: Linker Error L1100

Re: Linker Error L1100