Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Sune Foldager" Reply-to: cryo AT worldonline DOT dk To: cygwin AT cygwin DOT com X-CC-Sender: cryo AT worldonline DOT dk Date: Thu, 20 Sep 2001 13:24:15 GMT Subject: Follow up: Problems with ld X-Mailer: DMailWeb Web to Mail Gateway 2.3m, http://netwinsite.com/top_mail.htm Message-id: <3ba9edff.2282.0@worldonline.dk> X-User-Info: 213.237.180.194 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Ok here is a follow-up on my own mail ;) It's turns out that the LD in cygwin is less resistent to weird comman line options. It wants -oformat=binary or --oformat binary. Not -oformat binary. The Linux ld doesn't care. However, here is my extended problem: Back when I compilled the kernel under DOS using djgpp, the compiller mangled the names as usual, so a prototype of: void disable(); Would make the linker expect '_disable' to be defined somewhere. When migrating to Linux, I had to change all my assembler files since the Linux gcc _didn't_ mangle the name, and the linker will look for 'disable' instead. The extended problem then is, that cygwin behaves like djgpp, ie. mangles the names. So far I have not been able to find anywhere in djgpp, gcc on either Linux or cygwin, to change the name mangling behavior. Nor is the behaviour documented anywhere it seems. Anyone can help? :) Kind regards, Sune Foldager. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/