This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why won't my files link?

On Thu, Feb 06, 2003 at 10:22:33AM +1100, Gareth Pearce wrote:
>----- Original Message -----
>From: "Christopher Faylor" <>
>To: <>
>Sent: Thursday, February 06, 2003 10:13 AM
>Subject: Re: Why won't my files link?
>> On Wed, Feb 05, 2003 at 11:09:27PM -0000, Max Bowsher wrote:
>> >Chris, you're skim-reading too fast...
>> >
>> >Christopher Faylor wrote:
>> >> You need to '#include <stdio.h>' in io_functions.c.
>> >
>> >
>> >> On Wed, Feb 05, 2003 at 05:23:45PM -0500, Nick Miller wrote:
>> >
>> >... here's the problem:
>> >
>> >>> 2) I used the SAME io_functions.o file in both Cygwin and Linux.
>> >>> This file was generated by a CS professor at my school using GCC.
>> No, I wasn't skim reading.  I was assuming that no one would actually
>> take an object file from linux and attempt to use it on windows.
>Interesting, where as my assumption was your assumption was that despite the
>fact that indeed there are people out there crazy enough to use the same .o
>file - it wouldnt give that error.

Um, er, right, I think.  I am actually surprised that ld managed to get
that far into linking the file.

That seems to mean that you could make an elf-format object file with all
of the right function "linkages" for cygwin and link it on Windows.

I know that, these days, binutils can handle multiple different formats
by default but I never worked through that this could result in this
kind of behavior.

Learn something new...


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]