Hi miles,
> Why do you think this is a gcc problem...?
I specified a fully qualified path (with protocol) yet I have a link
error. I presume if gcc could consume the {protocol:path} tuple passed
in using '-L' there would not be a link error.
Since it appears GCC cannot use the syntax, what is the syntax I
should use to get GCC to link to a lib on a windows share using a
fully qualified name?
Jeff
On Sun, Oct 17, 2010 at 5:54 PM, Miles Bader <miles@xxxxxxx> wrote:
> Jeffrey Walton <noloader@xxxxxxxxx> writes:
>> GCC silently consumes non-existent paths. So when I do the following,
>> I assume its a failure since I have link problems:
>> gcc ... -L/smb://fileserver/fileshar/dir/ -llibcoolstuff
>
> Why do you think this is a gcc problem...? AFAICT, gcc basically
> doesn't do any mucking about with names given to -L.
>
> You can see exactly what's happening by using "gcc -v" to see exactly
> how gcc invokes the linker, and then run the linker yourself (copying
> the linker line form the gcc -v output) using the "strace -f" or
> something.
>
> -Miles
>
> --
> We live, as we dream -- alone....
>
>
