Quoting Asser <[email protected]>: > I linked with -static-libgcc flag, and the problem still occurs on Arch > linux. I'm guessing this points to a problem with kernel?
Hi Asser, This will not cause libusb to be linked statically, so the problem could still be in libusb. I tried my original instructions and it looks like an easier way to do this might be to try this for linking: cc -static -s -o mspdebug main.o fet.o rf2500.o dis.o uif.o olimex.o ihex.o elf32.o stab.o util.o bsl.o sim.o symmap.o gdb.o btree.o rtools.o sym.o devcmd.o reader.o vector.o output_util.o expr.o fet_error.o binfile.o fet_db.o usbutil.o titext.o srec.o device.o coff.o opdb.o output.o cmddb.o stdcmd.o prog.o flash_bsl.o -lreadline /usr/lib/libusb.a It'll still be a shared binary, but with a static libusb. If that works ok, then your problem is probably libusb on Arch Linux. Cheers, Daniel -- D.L. Beer Engineering www.dlbeer.co.nz ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
