On 14.2.2013 15.26, "Kustaa Nyholm" <kustaa.nyh...@planmeca.com> wrote:
>
>Also, there must be something wrong because I also get:
>
>message: using default linker script
>"/usr/local/share/gputils/lkr/18f4550.lkr"
>
>
>although I specify the linker script on the command line, I must
>have something wrong on that command line so I would appreciate
>if someone had hard look at the above command line and told
>me the problem....

Ok, solved that, there was just an extra space after the -s.

But the -L option does not seem to work as advertised,
it seems to be ignored.

And a curious detail, for a way of testing what library
path is actually used I renamed:

/usr/local/share/sdcc/lib/pic16


to

/usr/local/share/sdcc/lib/pic16x

and now sdcc hangs when compiling, no error message
no nothing, if I rename that back then I'm back
with the original error message.

Maybe I have resort to compiling from source and
use symbolic links as suggest...seems a bit heavy
solution when compared with just telling the compiler
where to look for the libraries.

br Kusti



------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to