|
Message
From: postmaster@h...
Date: Thu, 30 Oct 2003 01:48:53 +0900
Subject: [ERR] [openrisc] remove
Transmit Report:
To: taeho@i..., 2003/10/30 01:48:52, 500, LOOP MAIL DETECTED
At 15:45 29.10.03 +0100, you wrote:
>Hey !
>
>I'm not familiar with MinGW, but if it helps, the toolchain can be compiled
>on Cygwin. So you can run them under Windows (using Cygwin).
>
>regards,
>Damjan
>
>----- Original Message -----
>From: "Felix Bertram" <fbertram@g...>
>To: <openrisc@o...>
>Sent: Tuesday, October 28, 2003 5:45 PM
>Subject: [openrisc] or32 tools on MinGW
>
>
>> Hello everybody,
>>
>> did somebody manage to compile the or32 compiler on Windows/ MinGW?
>> If so, would you mind to share your build script with me?
>>
>> In particular, I am seeing the following probems here:
>> - need 'disable-nls' to avoid some compiler problems
>> - linker problems in gcc/collect2.c: pipe/ kill/ fork unresolved
>>
>> I have the following build system installed:
>> - MinGW-3.1.0-1
>> - MSYS-1.0.9
>> - msysDTK-1.0.1
>> - bison-1.875.0-2003.02.10-1
>> - flex-2.5.4a (from source)
>>
>> Am I missing something obvious here?
>>
>> I found thousands of links on Google of people having problems building
>> a cross-compiling gcc on MinGW. This is the essence I found:
>> * After running configure, edit gcc/Makefile manually as follows:
>> - change COLLECT2 line to 'COLLECT2= '
>> - change STMP_FIXINC line to 'STMP_FIXINC = '
>>
>> Is this sufficient? Are there any better ways? Is there a patch
>> existing for the or32 compilers?
>>
>>
>> Any comments highly appreciated,
>> best regards
>>
>>
>> Felix
>>
>>
>
>
>
--------- Wilhelm Mikroelektronik GmbH ---------
software design - embedded internet - components
Sueggelstr. 31 - 44532 Luenen - Germany
phone ++49 2306 928280 fax: ++49 2306 928289
------------ http://www.wilhelm.de -------------
|
 |
Browse
