[ECOS] Re: Wrongfully compiled code

[Dave Lawrence]

ariga masahiro wrote:
> Hello,
>
> Thank you very much for your confirmation.
> I am much relieved to have found the cause of trouble.
>
> But I do not know how to re-install sh-elf-gcc on Cygwin.
> Could you please teach me how to do it ?
>
> Masahiro Ariga
I found no pre-built version of GCC for this target available for download.
It's 18 months since I built it, and I've only ever built GCC once, so 
I'm just
going off the top of my head, but I did save a python script which goes 
through
the steps of building binutils and GCC.  I've also generated a patch for 
the configure
hack there are two versions attached, "configure.patch" was created 
using SVN
(from the root of that tag) "patch" was created using diff.

You will need the cygwin build of Python installed via the standard 
cygwin installer program from
cygwin.com

The GCC release can be obtained from SVN
svn co svn://gcc.gnu.org/svn/gcc/tags/gcc_4_1_1_release gcc_4_1_1
If you don't have SVN search their website for a tarball.
Obtain the aforementioned versions of newlib and binutils (you'll have 
to search for these
the gcc website and/or google will get you there pretty quickly) and 
unpack them such
that you have the following directory layout

./gcc_4_1_1
./gcc_4_1_1/newlib
./binutils-2.16
./buildall.py
./patch
./configure.patch

Either apply configure.patch using SVN (and I have no idea how to do 
that from the
command line version) or apply "patch" using :
patch gcc_4_1_1/libstdc++-v3/configure -ipatch

Let's assume you want to install to /opt/ecos/gcc411:
run the attached script as
python buildall.py /opt/ecos/gcc411
*
*see also
http://gcc.gnu.org/install/

Good luck!*
*
>>
>>> sh-elf/sh-elf/include
>>> Thread model: single
>>> gcc version 3.2.1
>>
>> We found a bug in this version (probably the same one).  I managed to 
>> compile GCC 4.1.1 using the following sources
>>
>> binutils 2.16
>> Newlib 1.14.0 (copy this to inside the GCC source directory)
>> Gcc 4.1.1
>>
>> I had to make one hack to the configure file.  It fails on a test, 
>> but you can proceed without it, you'll just have to inspect the file 
>> when the problem occurs and comment out that test.  I can't remember 
>> any more details than that sorry.
>>
>> binutils is compiled separately.  Newlib is not strictly needed by 
>> ecos but I found GCC wouldn't compile without it (use the 
>> --with-newlib option in the configure).
>>
>> btw the compile time is measured in hours (about 4.5 on the PC I used)
>>
>>
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>>
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: configure.patch
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20080118/48879bdd/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildall.py
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20080118/48879bdd/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20080118/48879bdd/attachment-0002.ksh>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss