Problems when linking

[Toshi Morita]

> 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.

You already are generating assembler output with gcc and then using gas to
generate the object format.

Since this is a Windows question, it actually should be posted to the Cygwin
mailing list - sorry about that. Most people who do GCC development aren't
very familiar with Windows, and this is the wrong place to ask this question.

Toshi

> 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
> >
> >
> >
> 
> 
>