From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg) Newsgroups: comp.os.msdos.djgpp Subject: Re: SIGILL 386 (illegal opcode) Date: 9 May 2003 14:13:55 GMT Organization: Ericsson Erisoft AB, Sweden Lines: 28 Message-ID: References: <3eb08a5a$0$79355$cc7c7865 AT news DOT luth DOT se> NNTP-Posting-Host: lws256.lu.erisoft.se X-Newsreader: TIN [version 1.2 PL2] To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Alexei K. (kzua AT kzua DOT udm DOT ru) wrote: : "Martin Str|mberg" сообщил/сообщила в новостях следующее: : news:3eb08a5a$0$79355$cc7c7865 AT news DOT luth DOT se... : > If you get SIGILL we want more information. Like what program and : > source? Command line? Result? : My project works fine with 386 CPU, if it compiles by DJGPP gpp 2.952. : I have just recompiled my project by DJGPP gpp 3.2.2 : (with -m386 option enabled) and program has failed only on 386 PC. : I deeply use STL. Was libstdxx.a library compiled for 386 CPU? : How can I rebuild libstdxx.a? I don't use C++. I don't use that version of GCC. I don't know if this will work and/or break anything else. I haven't tested it. If the problem is where Andris has indicated, you don't have to. You just need to correct a header file. Download gcc322s.zip. Replace lang/cxx/djgpp/bits/atomicity.h ( is probably "-3.22") with gnu/gcc-3.22/libstdc++-v3/config/cpu/generic/bits/atomicity.h from gcc322s.zip. Right, MartinS