public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Mahesh Basavaraj Shavari <Mahesh.Shavari@kpitcummins.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: MinGW toolchain build failure for M16CM32C
Date: Fri, 29 May 2009 16:02:00 -0000	[thread overview]
Message-ID: <90baa01f0905290317x1ada018aobfa00f1a9b5abb3b@mail.gmail.com> (raw)
In-Reply-To: <90baa01f0905290312g32169defi624094f82d5913c8@mail.gmail.com>

2009/5/29 Kai Tietz <ktietz70@googlemail.com>:
> 2009/5/29 Mahesh Basavaraj Shavari <Mahesh.Shavari@kpitcummins.com>:
>> Hi,
>> I am trying to build a MinGW toolchain for M16CM32C target using the following sources:
>>
>> GCC-4.4.0
>> Binutils-2.19
>> Newlib-1.17
>>
>> The linux toolchain was built successfully, however MinGW toolchain build failed.
>> During make, I get the following error.
>>
>> ----------------------------------------------------------------------------------------------------------------------
>> i386-pc-mingw32msvc-gcc -c -g -O2 -D__USE_MINGW_ACCESS -Wall -Wconversion  -I"/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/../generic" -I"/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win" -mwin32  -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  -DBUILD_tcl /home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/../compat/strtoll.c -o strtoll.o i386-pc-mingw32msvc-gcc -c -g -O2 -D__USE_MINGW_ACCESS -Wall -Wconversion  -I"/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/../generic" -I"/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win" -mwin32  -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  -DBUILD_tcl /home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/../compat/strtoull.c -o strtoull.o
>> o tcl.res.o   --include "/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/../generic" --include "/home/RX_FINAL_V0901/KPIT/src-cross/tcl/win" /home/RX_FINAL_V0901/KPIT/src-cross/tcl/win/tcl.rc
>> /bin/sh: o: command not found
>> make[3]: [tcl.res.o] Error 127 (ignored)
>> i386-pc-mingw32msvc-gcc -shared -g -O2 -D__USE_MINGW_ACCESS -Wl,--stack,8388608 -o tcl84.dll -mwin32            -Wl,--out-implib,libtcl84.a regcomp.o regexec.o regfree.o regerror.o tclAlloc.o tclAsync.o tclBasic.o tclBinary.o tclCkalloc.o tclClock.o tclCmdAH.o tclCmdIL.o tclCmdMZ.o tclCompCmds.o tclCompExpr.o tclCompile.o tclDate.o tclEncoding.o tclEnv.o tclEvent.o tclExecute.o tclFCmd.o tclFileName.o tclGet.o tclHash.o tclHistory.o tclIndexObj.o tclInterp.o tclIO.o tclIOCmd.o tclIOGT.o tclIOSock.o tclIOUtil.o tclLink.o tclLiteral.o tclListObj.o tclLoad.o tclMain.o tclNamesp.o tclNotify.o tclObj.o tclPanic.o tclParse.o tclParseExpr.o tclPipe.o tclPkg.o tclPosixStr.o tclPreserve.o tclProc.o tclRegexp.o tclResolve.o tclResult.o tclScan.o tclStringObj.o tclStubInit.o tclStubLib.o tclThread.o tclThreadAlloc.o tclThreadJoin.o tclTimer.o tclUtf.o tclUtil.o tclVar.o tclWin32Dll.o tclWinChan.o tclWinConsole.o tclWinSerial.o tclWinError.o tclWinFCmd.o tclWinFile.o tclWinInit.o tclWinLoad.o tclWinMtherr.o tclWinNotify.o tclWinPipe.o tclWinSock.o tclWinThrd.o tclWinTime.o  strftime.o strtoll.o strtoull.o tcl.res.o
>> i386-pc-mingw32msvc-gcc: tcl.res.o: No such file or directory
>> make[3]: *** [tcl84.dll] Error 1
>> --------------------------------------------------------------------------------------------------------------
>>
>> The native MinGW toolchain (i386-pc-mingw32msvc-gcc) for i386 was built using the following source.
>> GCC-3.4.5
>>
>> Any help would be highly appreciated.
>> Thanking you in anticipation.
>>
>> Regards,
>> Mahesh Shavari
>>
>>
>
> Hello,
>
> it seems so that you makefile tries to compile resource file (.rc) via
> gcc frontend. This fails AFAIK. Instead the windres tool (part of
> binutils) have to be invoked here. This should fix your problem.
>
> Cheers,
> Kai
>
> --
> |  (\_/) This is Bunny. Copy and paste
> | (='.'=) Bunny into your signature to help
> | (")_(") him gain world domination
>

Second remark. In you build line there is a typo. Not sure if this a
paste issue, but

... "win/../compat/strtoull.c -o strtoull.o o tcl.res.o" ...

is wrong. There is a '-' missing before 'o'. It should be something like

... "win/../compat/strtoull.c -o strtoull.o -o tcl.res.o" ...

Cheers,
Kai
-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

  reply	other threads:[~2009-05-29 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 14:23 Mahesh Basavaraj Shavari
2009-05-29 14:54 ` Kai Tietz
2009-05-29 16:02   ` Kai Tietz [this message]
2009-05-29 16:08     ` [OT] " Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=90baa01f0905290317x1ada018aobfa00f1a9b5abb3b@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=Mahesh.Shavari@kpitcummins.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).