public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* WG: linux->mingw crosscompiler
@ 2001-01-03  8:43 Kittenberger, Axel
  2001-01-03 10:58 ` Alexandre Oliva
  0 siblings, 1 reply; 2+ messages in thread
From: Kittenberger, Axel @ 2001-01-03  8:43 UTC (permalink / raw)
  To: gcc-help

> Hi, I'm just trying to build a mingw crosscompiler on linux (gcc
2.95.2) 
> (it's first the gcc compiler that create me .exe's on a linux
machine.)
> 
> I've downloaded bin utils created them, copied the runtime headers
etc. like in the guide, but 
> I still get following error message:
> 
>  
> in _exit _ctors _pure; \
> do \
>   echo ${name}; \
>   /home/axk/cross/mingw-bld/gcc/xgcc -B/home/axk/cross/mingw-bld/gcc/
-B/home/axk/mingw/i386-mingw32/bin/
-I/home/axk/mingw/i386-mingw32/include -O2
-I../../src/gcc/gcc/../winsup/include -DCROSS_COMPILE -DIN_GCC
-I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I.
-I../../src/gcc/gcc -I../../src/gcc/gcc/config
-I../../src/gcc/gcc/../include -c -DL${name} \
>        ../../src/gcc/gcc/libgcc2.c -o ${name}.o; \
>   if [ $? -eq 0 ] ; then true; else exit 1; fi; \
>   i386-mingw32-ar rc tmplibgcc2.a ${name}.o; \
>   rm -f ${name}.o; \
> done
> _muldi3     
> /tmp/ccIfgxDy.s: Assembler messages:
> /tmp/ccIfgxDy.s:134: Error: Unknown pseudo-op:  `.def'
> /tmp/ccIfgxDy.s:134: Error: Unknown pseudo-op:  `.scl'
> /tmp/ccIfgxDy.s:134: Error: ignoring unrecognized symbol type ""
> /tmp/ccIfgxDy.s:134: Error: Rest of line ignored. First ignored
character is `3'.
> /tmp/ccIfgxDy.s:134: Error: Unknown pseudo-op:  `.endef'
> make[1]: *** [libgcc2.a] Error 1
> make[1]: Leaving directory `/home/axk/cross/mingw-bld/gcc'
> make: *** [all-gcc] Error 2          
> 
> Anybody can hint about what's going wrong?
> 
> I did create a i386-mingw32-ar however make/gcc seems to invoke the
wrong one at this step, as it isn't disturbed when I delete it ;o)
> 
> However I don't have any idea on which screw to modify so the correct
assembler gets invoked.
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: WG: linux->mingw crosscompiler
  2001-01-03  8:43 WG: linux->mingw crosscompiler Kittenberger, Axel
@ 2001-01-03 10:58 ` Alexandre Oliva
  0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2001-01-03 10:58 UTC (permalink / raw)
  To: Kittenberger, Axel; +Cc: gcc-help

On Jan  3, 2001, "Kittenberger, Axel" <Axel.Kittenberger@datentechnik.com> wrote:

>> /tmp/ccIfgxDy.s: Assembler messages:
>> /tmp/ccIfgxDy.s:134: Error: Unknown pseudo-op:  `.def'

>> I did create a i386-mingw32-ar however make/gcc seems to invoke the
> wrong one at this step, as it isn't disturbed when I delete it ;o)

It doesn't get to run it.  The problem shows up while compiling the
object file that would be added to the library with ar.  Most likely,
GCC is using the wrong assembler.  Run 

/home/axk/cross/mingw-bld/gcc/xgcc -B/home/axk/cross/mingw-bld/gcc/ \
-B/home/axk/mingw/i386-mingw32/bin/ \
-I/home/axk/mingw/i386-mingw32/include -O2 \
-I../../src/gcc/gcc/../winsup/include -DCROSS_COMPILE -DIN_GCC \
-I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. \
-I../../src/gcc/gcc -I../../src/gcc/gcc/config \
-I../../src/gcc/gcc/../include -c -DL_muldi3 \
        ../../src/gcc/gcc/libgcc2.c -o _muldi3.o -v

and see which assembler it runs.  The FAQ has some suggestion on how
to arrange for GCC to run the appropriate assembler.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-01-03 10:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-03  8:43 WG: linux->mingw crosscompiler Kittenberger, Axel
2001-01-03 10:58 ` Alexandre Oliva

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).