Command returned error code:1Skipping link step. SOLVED !!!

[Humberto]

Hi all and good 2024 !

I'm one of the "old boys here", so my tools are still MPLB IDE v8.92.00.
Currently my work environment
MCU 18F4680
PCWHD Compiler v5.109

I get the following error in compilation time, during link step ( ...?)
being a single file, whith a couple of .h files

Command returned error code:
Executing: "C:\Program Files (x86)\PICC\ccsc.exe" "Cntrl_BASE.44.c" +FH +DF +LN +T -A +M +Z +Y=9 +EA
Command returned error code:1Skipping link step. Not all sources built successfully.


Any help will be very well apreciated
_________________
Humber

[Ttelmah]

Have you used the setup with multiple full stops before?.
Though Windows now supports this a lot of older code gtes confused
when you have more than one full stop in a filename. Suspect the
old IDE might not like this, and CCS itself also could have problems
with this.

[temtronic]

hmm...

this...
"Cntrl_BASE.44.c"

as a 'human parser', I don't like the period between BASE and 44.

Maybe this is what Mr. T is referring to ?

[Ttelmah]

Yes, exactly.
Historically in Windows, the full stop was the 'extension separator'. The bit
after the full stop was the file extension and the part before the filename.
Now Windows itself does now allow multiple full stops, and will accept them,
but I'd not be surprised if either the old IDE or the compiler itself would
have problems with these. Before long filenames, and the VFAT system,
these weren't allowed. It still causes issues in Windows itself, with some
parts of the OS identifying everything after the first period as being the
extension, while other parts only identify the parts after the last period.
There is a general guidance that says you should only ever have one full
stop in a full filename to avoid issues. Generally it is recommended to
use the _ character instead for earlier name separators. The full stop
is also a 'special character' in filenames, so '\name" selects the current
directory, while "..\name", selects name in the parent etc..
. and .. are 'reserved relative path separators'. Having these inside
a filename is asking for code to have problems.
Historically in 8.3 filenames, the full stop was not actually stored.

[temtronic]

I've been 'bit' by the Windows filenames ONCE in recent history. Downloaded a picture off an auction, great ,looked at it, then could NOT delete it !
Man what a royal pain that was..OK, not the end of the world but yeesh..if Windows can 'see' it to open it, Windows should be able to delete it. Bugged me for 2-3 weeks then someone, somewhere suggested 7-zip. never heard of it. got it 'magically it DID delete the file.

sigh.... I'm getting too old for that kind of 'nonsense' !

[Humberto]

Many thanks Mr T and Jay!! Solved !!
Great teorical and tech level as expect here.

Ttelmah wrote:

[Ttelmah]

Flag the thread as solved please.
Glad we got it.