search for: yoursystem

Reid Spencer wrote: > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > When you run it from the command line it will find yoursystem libgcc.so (which works) Not really. For systems that have gcc 4.2 natively installed, like the current Debian testing, the compiler gets GCC_4.2.0 version errors. It isn't easy to work around b/c xgcc wants to link in the 4.2 version of the library. Basically, this is a "me too!"...

Hi Scooter, On Mon, 2006-11-06 at 12:07 -0800, Scott Michel wrote: > Reid Spencer wrote: > > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > > When you run it from the command line it will find yoursystem > libgcc.so (which works) > > Not really. For systems that have gcc 4.2 natively installed, like the > current Debian testing, the compiler gets GCC_4.2.0 version errors. It > isn't easy to work around b/c xgcc wants to link in the 4.2 version of > the library. You're ri...

Hi All Yesterday i had installed wireshark on my centos box which does not have the GUI , It is actually a hardened box. I installed the tool using the following command: yum install wireshark After installation i dont know how to proceed further in capturing the packets. I basically want to capture packets and copy them onto my windows box. On the windows box i can use the Wireshark UI to

This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which will find the libgcc.so that it just built, which is the one