link path

Has this bug been fixed?
http://www.openqnx.com/jive/thread.jsp?forum=13&thread=8750&message=105303&q=6c6962676c752e736f#105303

I reported that bug back in the 6.1 days, and encountered the
same problem with 6.2.0 last week. I am wondering if the upcoming
6.2.1 has fixed it.

Thanks!
Frank

Ping

liug <liug@mama.indstate.edu> wrote:

Has this bug been fixed?
http://www.openqnx.com/jive/thread.jsp?forum=13&thread=8750&message=105303&q=6c6962676c752e736f#105303

I reported that bug back in the 6.1 days, and encountered the
same problem with 6.2.0 last week. I am wondering if the upcoming
6.2.1 has fixed it.

Thanks!
Frank

Hi.

This issue is a side effect of our development layout. We have to tell gcc
where to find our system libs and object files, and we have to do it from
the specs. This is accomplished by using ā€˜-Lā€™ args to the linker in the specs
file.

So, gcc is doing the right thing, because it is putting all -L args first in
the link line. Our specs files just beat you to it, and currently there is
no way other way for us to do this.

I have submitted a patch to the gcc-patches mailing list that fixes this
issue in the gnu head branch. Hopefully it will be reviewed and accepted
soon. If so, I will then investigate rolling that support into gcc-3.2.2
for the QNX-6.3 release.

Regards,
GP

liug <liug@mama.indstate.edu> wrote:

Has this bug been fixed?
http://www.openqnx.com/jive/thread.jsp?forum=13&thread=8750&message=105303&q=6c6962676c752e736f#105303

I reported that bug back in the 6.1 days, and encountered the
same problem with 6.2.0 last week. I am wondering if the upcoming
6.2.1 has fixed it.

Thanks!
Frank