Hello Ralf, I think I fixed the problem, and compiled my executable successfully.
I removed all .la files in the folder /opt/montavista/cge/devkit/ppc/74xx/targets/usr/lib, which I'm providing with -L option. I also observed that after doing this change, it is not linking libstdc++ at all. Any ways, I don't care about it, as my executable doesn't require it to be linked with libstdc++ at first place. Thanks Vishal Soni. -----Original Message----- From: Ralf Wildenhues [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 2:28 AM To: Vishal Soni-G20083 Cc: [email protected]; Liviu Nicoara Subject: Re: Wrong libstdc++ picked Hello Vishal, Thanks for the report. * Vishal Soni-G20083 wrote on Wed, Apr 25, 2007 at 03:14:43PM CEST: > > This is the typical problem faced by many users, but I'm unable to > find concrete answer to the problem on the forum. Please read the recent thread starting at <http://lists.gnu.org/archive/html/libtool/2007-04/msg00043.html>. By going through the questions I asked Liviu and answering them, you (or we) can find out whether the underlying bug is the same or not. Please provide those information as well. > But still at one point of time I'm getting libtool is picking > libstdc++ from /usr/lib instead of the path provided with "-L". One hacky workaround I suppose it to temporarily remove /usr/lib/libstdc++.la (only the .la file, not the actual library or any symlinks to it). Sorry Liviu for not mentioning this earlier, I think this would work for your case as well. Thanks, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
