This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: Problems when linking


I thought that as a front end gcc would have command line options to be
someway mapped to the backend tools (gas in this case) or that cygwin gcc
would generate different default object outputs from gcc compiled in an
unix/elf system (I mean: indirectly, using gas). Are you saying that I
should generate the assembler output with gcc and then use gas to generate
the pretended object format?
Sorry if I'm still out of topic.

Thank you,
    Carlos

----- Original Message -----
From: "Toshi Morita" <tm2@best.com>
To: <cpita@tycdigital.com.ar>
Cc: <gcc@gcc.gnu.org>
Sent: Thursday, April 19, 2001 1:48 PM
Subject: Re: Problems when linking


>
> Carlos Pita wrote:
>
> > Hi!
> >     I'm using gcc 2.95.2 with cygwin. I'm also assembling with nasm,
then
> > trying to link object files from the c compilation and from the
assembling.
> > The problem is that the linker can't found the global symbols in the
> > assembler code that are invoked from the c code. I think this is related
to
> > the format of the object files that I'm generating. I'm not sure about
how
> > does cygwin gcc work in this respect. With nasm I can generate at least
obj
> > or elf outputs.
> > Can you help me?
>
> GCC doesn't generate binary object file formats. It generates assembly
output
> which is then assembled by GAS, the GNU assembler.
>
> Any questions about object file format therefore should be posted to the
> binutils mailing list.
>
> Toshi
>
>
>



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