mingw-users

[Mingw-users] mingw gcc updates

[Paul B. <pau...@as...>]

A couple of user comments/requests following the recent updates to the mingw 
sourceforge download page:

1.  Could the candidate gcj and proposed gpc packages be recompiled to work 
with the new gcc 3.2.3 main package? One relies on 3.2 and the other on 
3.2.2.

2.  What happened to the snapshot ada-gcc 3.3 package previously on the page?

3.  What has happened to the release dates on the download page?  They all say 
2003-05-11, even the recent update to mingw32-make on 2003-05-30!

Thanks for all the hard work on making mingw so useful.

Paul Butcher
Alton, Hants, UK

Re: [Mingw-users] mingw gcc updates

[Earnie B. <ear...@ya...>]

Paul Butcher wrote:
> A couple of user comments/requests following the recent updates to the mingw 
> sourceforge download page:
> 
> 1.  Could the candidate gcj and proposed gpc packages be recompiled to work 
> with the new gcc 3.2.3 main package? One relies on 3.2 and the other on 
> 3.2.2.
> 

No answer.  I'm thinking this one.

> 2.  What happened to the snapshot ada-gcc 3.3 package previously on the page?
> 

What ada-gcc 3.3 package?  I remember a non functioning 3.2 version.

> 3.  What has happened to the release dates on the download page?  They all say 
> 2003-05-11, even the recent update to mingw32-make on 2003-05-30!
> 

Blame me for this.  The file timestamps are the release for the package. 
  The changes we've made are to help dynamically create the data for the 
download.shtml page.  Unless the release technitian remembers to change 
the ``release date'' for the SF FRS page then that date will remain static.

> Thanks for all the hard work on making mingw so useful.
> 

Mostly pleasurable,
Earnie.

Re: [Mingw-users] mingw gcc updates

[Earnie B. <ear...@ya...>]

Earnie Boyd wrote:
> 
>> 3.  What has happened to the release dates on the download page?  They 
>> all say 2003-05-11, even the recent update to mingw32-make on 2003-05-30!
>>
> 
> Blame me for this.  The file timestamps are the release for the package. 
>  The changes we've made are to help dynamically create the data for the 
> download.shtml page.  Unless the release technitian remembers to change 
> the ``release date'' for the SF FRS page then that date will remain static.
> 

I've updated my script to add file size and timestamp to the table on 
the Download page.  These are the release dates for the file.

Earnie.

[Mingw-users] Re: mingw gcc updates

[Ranjit M. <rm...@ho...>]

> 1.  Could the candidate gcj and proposed gpc packages be recompiled to work 
> with the new gcc 3.2.3 main package? One relies on 3.2 and the other on 
> 3.2.2.

GCJ 3.2 is quite outdated and 3.3 is *far* better,
especially for users on Windows. If you can't
wait till the official MinGW release, you can get
pre-compiled GCJ 3.3 binaries for Win32 at:

     http://www.thisiscool.com/gcc33_mingw.htm

HTH.

Ranjit.

-- 
Ranjit Mathew          Email: rmathew AT hotmail DOT com

Bangalore, INDIA.      Web: http://ranjitmathew.tripod.com/

[Mingw-users] How to build a cross compiler

[Chris B. <ki...@bi...>]

I have been attempting to build a cross compiler that runs under
Windows 2000 but which generates code for i386/linux.

I have had little success so far.

I would be most grateful if anyone could point me at a source of
information on how to do this.

Best regards,

Chris Bishop

Re: [Mingw-users] How to build a cross compiler

[Luke D. <cod...@ho...>]

I don't know where you would find instructions except perhaps on the mailing
list archives (I seem to recall users building MinGW-hosted cross-compilers
for arm-pe or something). Anyway, what exact troubles are you having? Is the
problem with building a cross-binutils or have you already done that and are
trying GCC? Perhaps most importantly, are you using the MSYS shell or Cygwin
or ...? BTW, if you are using the official source releases of binutils/GCC
you might want to try the patched MinGW source instead (the latest
versions).

Luke

----- Original Message ----- 
From: "Chris Bishop" <ki...@bi...>
To: <min...@li...>
Sent: Thursday, June 05, 2003 1:09 PM
Subject: [Mingw-users] How to build a cross compiler


> I have been attempting to build a cross compiler that runs under
> Windows 2000 but which generates code for i386/linux.
>
> I have had little success so far.
>
> I would be most grateful if anyone could point me at a source of
> information on how to do this.
>
> Best regards,
>
> Chris Bishop

Re: [Mingw-users] How to build a cross compiler

[Brenden T. <br...@rc...>]

Cross gcc mailing list here:
http://sources.redhat.com/ml/crossgcc/

Cross gcc FAQ here:
http://www.sthoward.com/CrossGCC/

This FAQ looks kinda old, but I expect the folks on the mailing list 
will know what's up to date and where to get it.

Good luck.


Luke Dunstan wrote:

>I don't know where you would find instructions except perhaps on the mailing
>list archives (I seem to recall users building MinGW-hosted cross-compilers
>for arm-pe or something). Anyway, what exact troubles are you having? Is the
>problem with building a cross-binutils or have you already done that and are
>trying GCC? Perhaps most importantly, are you using the MSYS shell or Cygwin
>or ...? BTW, if you are using the official source releases of binutils/GCC
>you might want to try the patched MinGW source instead (the latest
>versions).
>
>Luke
>
>----- Original Message ----- 
>From: "Chris Bishop" <ki...@bi...>
>To: <min...@li...>
>Sent: Thursday, June 05, 2003 1:09 PM
>Subject: [Mingw-users] How to build a cross compiler
>
>
>  
>
>>I have been attempting to build a cross compiler that runs under
>>Windows 2000 but which generates code for i386/linux.
>>
>>I have had little success so far.
>>
>>I would be most grateful if anyone could point me at a source of
>>information on how to do this.
>>
>>Best regards,
>>
>>Chris Bishop
>>    
>>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
>thread debugger on the planet. Designed with thread debugging features
>you've never dreamed of, try TotalView 6 free at www.etnus.com.
>_______________________________________________
>MinGW-users mailing list
>Min...@li...
>
>You may change your MinGW Account Options or unsubscribe at:
>https://lists.sourceforge.net/lists/listinfo/mingw-users
>
>
>  
>

Re[2]: [Mingw-users] How to build a cross compiler

[Chris B. <ki...@bi...>]

Luke and others who responded to my original message,

Many thanks for your offer of advice etc.  Just got back to this after
having to work on other things.

To repeat what my needs are - I need a tool chain that executes under
Windows 2000 to build applications to run on i386 linux.

My system:
           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
Installed:
           MinGW-2.0.0.3.exe
           MSYS-1.0.8.exe
Obtained copies of:
           binutils-2.13.90-20030111-1-src.tar.gz
           gcc-3.2.3-20030504-1-src.tar.gz
Placed these in directory:
           ~/xmingw
Changed directory to:
           ~/xmingw
Executed:
           gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
           mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
           cd binutils-2.13.90-20030111-1 && ./configure \
                   --target=i386-pc-linux-gnu \
                   --prefix=/opt/xmingw32 \
                   > ../binutils-configure.log 2>&1
           cd binutils-2.13.90-20030111-1 && \
                   make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
(Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
unzips atypically to binutils-2.13.90-20030111-1-src rather than
binutils-2.13.90-20030111-1 and I like to keep things tidy!)

There does not appear to be anything unexpected in the
binutils-configure.log.

The make however fails with the relevant lines in binutils.build.log
being:

make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  bindtextdom.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  dcgettext.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  dgettext.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  gettext.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  finddomain.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  loadmsgcat.c
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  localealias.c
localealias.c:156:42: warning: unknown escape sequence '\M'
localealias.c:156:42: warning: unknown escape sequence '\o'
localealias.c:156:42: \x used with no following hex digits
localealias.c:156:42: warning: unknown escape sequence '\s'
localealias.c:156:42: warning: unknown escape sequence '\l'
make[2]: *** [localealias.o] Error 1

On examining localealias.c, it would appear that the problem is
related to the ":." at the end of aliaspath in
binutils-2.13.90-20030111-1/intl/Makefile.

At least, removing the :. does fix this problem even if it isn't the
correct solution.

With this change (even if not totally appropriate), binutils build
seems to complete OK.

I now execute:
           cd binutils-2.13.90-20030111-1 && \
                   make install > ../binutils-install.log 2>&1

This fails and the last few relevant lines of binutils-install.log
are:

make[4]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/bfd/doc'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/bfd/doc'
gcc -c -I.. -I./.. -I./../../include -I./../../intl -I../../intl  -g -O2 ./chew.c
      0 [main] sh 1352 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
make[3]: *** [chew.o] Segmentation fault (core dumped)

The contents of sh.exe.stackdump are:

Exception: STATUS_ACCESS_VIOLATION at eip=710980DD
eax=312E322C ebx=0A0252D8 ecx=00000108 edx=00000109 esi=0A0253D8 edi=0A0252D0
ebp=0022E1F8 esp=0022E1D0 program=F:\MSys\bin\sh.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022E1F8  710980DD  (710A4020, 0A0252D8, 0022E238, 7109008E)
0022E218  710308B5  (0A0252D8, 0000120E, 0022E5D8, 710434C7)
0022E238  71030728  (0A0252D8, 0A028A58, 534D2F3A, 6C2F7379)
0022E5D8  71044477  (0A01BFDC, 0A0275C0, 0022F9B8, 71061A45)
0022F9B8  71061A55  (00000000, 0A019160, 0A019818, 0A019570)
0022F9F8  710635FA  (00000000, 00000003, 0A019160, 0A019818)
0022FA28  71010A9B  (0A019160, 0A019818, 0A019570, 710A4020)
0022FA48  7108CF76  (0A019160, 0A019818, 0A019570, 710A92E4)
0022FB18  004127A4  (0A019160, 0A019818, 0A019570, 0042B3C4)
0022FB74  00412706  (0A019360, 00000000, 0A0190F8, FFFFFFFF)
0022FBF4  00411CA7  (0A018E10, FFFFFFFF, FFFFFFFF, 00000000)
0022FC54  0040E9C6  (0A018DF8, 00000000, FFFFFFFF, FFFFFFFF)
0022FCA4  004499BB  (0A0188A8, 004022F9, 00000004, 00402F6E)
0022FCD4  00403180  (7159F28C, 710A4368, 0022FD74, 00401858)
0022FD74  00401873  (00000003, 715A03FC, 0A010278, 00000000)
0022FE70  71004568  (00000000, 00000000, 0022BA04, 8044CC2E)
End of stack trace (more stack frames may be present)

My apologies for the length of this message.

Any help would be most appreciated.  I have been fighting this problem
for some time now and no matter what I do I just don't seem to get
anywhere.

Best regards,

Chris Bishop

Thursday, June 5, 2003, 10:35:09 PM, you wrote:


LD> I don't know where you would find instructions except perhaps on the mailing
LD> list archives (I seem to recall users building MinGW-hosted cross-compilers
LD> for arm-pe or something). Anyway, what exact troubles are you having? Is the
LD> problem with building a cross-binutils or have you already done that and are
LD> trying GCC? Perhaps most importantly, are you using the MSYS shell or Cygwin
LD> or ...? BTW, if you are using the official source releases of binutils/GCC
LD> you might want to try the patched MinGW source instead (the latest
LD> versions).

LD> Luke

LD> ----- Original Message ----- 
LD> From: "Chris Bishop" <ki...@bi...>
LD> To: <min...@li...>
LD> Sent: Thursday, June 05, 2003 1:09 PM
LD> Subject: [Mingw-users] How to build a cross compiler


>> I have been attempting to build a cross compiler that runs under
>> Windows 2000 but which generates code for i386/linux.
>>
>> I have had little success so far.
>>
>> I would be most grateful if anyone could point me at a source of
>> information on how to do this.
>>
>> Best regards,
>>
>> Chris Bishop


LD> -------------------------------------------------------
LD> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
LD> thread debugger on the planet. Designed with thread debugging features
LD> you've never dreamed of, try TotalView 6 free at www.etnus.com.
LD> _______________________________________________
LD> MinGW-users mailing list
LD> Min...@li...

LD> You may change your MinGW Account Options or unsubscribe at:
LD> https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

Chris Bishop wrote:
> Luke and others who responded to my original message,
> 
> Many thanks for your offer of advice etc.  Just got back to this after
> having to work on other things.
> 
> To repeat what my needs are - I need a tool chain that executes under
> Windows 2000 to build applications to run on i386 linux.
> 
> My system:
>            Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
> Installed:
>            MinGW-2.0.0.3.exe
>            MSYS-1.0.8.exe

Please try the latest MSYS Snapshot. See 
http://www.mingw.org/download.shtml for references to the snapshot.

Thanks,
Earnie.

Re[2]: [Mingw-users] How to build a cross compiler

[Chris B. <ki...@bi...>]

Earnie,

Thanks for your suggestion.  I have re-installed MinGW and MSys so
details are now:

My system:
           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
Installed:
           MinGW-2.0.0.3.exe
           MSYS-1.0.9-2003.06.05-1.exe
Obtained copies of:
           binutils-2.13.90-20030111-1-src.tar.gz
           gcc-3.2.3-20030504-1-src.tar.gz
Placed these in directory:
           ~/xmingw
Changed directory to:
           ~/xmingw
Executed:
           gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
           mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
           cd binutils-2.13.90-20030111-1 && ./configure \
                   --target=i386-pc-linux-gnu \
                   --prefix=/opt/xmingw32 \
                   > ../binutils-configure.log 2>&1
           cd binutils-2.13.90-20030111-1 && \
                   make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
(Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
unzips atypically to binutils-2.13.90-20030111-1-src rather than
binutils-2.13.90-20030111-1 and I like to keep things tidy!)

There does not appear to be anything unexpected in the
binutils-configure.log.

But the make now fails with the relevant lines in binutils.build.log
being:

make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
      0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
make[2]: *** [intl-compat.o] Segmentation fault (core dumped)

and the sh.exe.stackdump is now:

Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE edi=715C8984
ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
End of stack trace (more stack frames may be present)

Any help would be appreciated.

Best regards,

Chris Bishop

Monday, June 9, 2003, 11:17:46 PM, you wrote:



EB> Chris Bishop wrote:
>> Luke and others who responded to my original message,
>> 
>> Many thanks for your offer of advice etc.  Just got back to this after
>> having to work on other things.
>> 
>> To repeat what my needs are - I need a tool chain that executes under
>> Windows 2000 to build applications to run on i386 linux.
>> 
>> My system:
>>            Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>> Installed:
>>            MinGW-2.0.0.3.exe
>>            MSYS-1.0.8.exe

EB> Please try the latest MSYS Snapshot. See 
EB> http://www.mingw.org/download.shtml for references to the snapshot.

EB> Thanks,
EB> Earnie.

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

I've marked this for my immediate review.

Earnie.

Chris Bishop wrote:
> Earnie,
> 
> Thanks for your suggestion.  I have re-installed MinGW and MSys so
> details are now:
> 
> My system:
>            Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
> Installed:
>            MinGW-2.0.0.3.exe
>            MSYS-1.0.9-2003.06.05-1.exe
> Obtained copies of:
>            binutils-2.13.90-20030111-1-src.tar.gz
>            gcc-3.2.3-20030504-1-src.tar.gz
> Placed these in directory:
>            ~/xmingw
> Changed directory to:
>            ~/xmingw
> Executed:
>            gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
>            mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
>            cd binutils-2.13.90-20030111-1 && ./configure \
>                    --target=i386-pc-linux-gnu \
>                    --prefix=/opt/xmingw32 \
>                    > ../binutils-configure.log 2>&1
>            cd binutils-2.13.90-20030111-1 && \
>                    make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
> (Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
> unzips atypically to binutils-2.13.90-20030111-1-src rather than
> binutils-2.13.90-20030111-1 and I like to keep things tidy!)
> 
> There does not appear to be anything unexpected in the
> binutils-configure.log.
> 
> But the make now fails with the relevant lines in binutils.build.log
> being:
> 
> make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
>       0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> make[2]: *** [intl-compat.o] Segmentation fault (core dumped)
> 
> and the sh.exe.stackdump is now:
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
> eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE edi=715C8984
> ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
> 0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
> 0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
> 0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
> 0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
> 0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
> 0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
> 0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
> 0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
> 0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
> 0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
> 0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
> 0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
> 0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
> 0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
> 0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
> End of stack trace (more stack frames may be present)
> 
> Any help would be appreciated.
> 
> Best regards,
> 
> Chris Bishop
> 
> Monday, June 9, 2003, 11:17:46 PM, you wrote:
> 
> 
> 
> EB> Chris Bishop wrote:
> 
>>>Luke and others who responded to my original message,
>>>
>>>Many thanks for your offer of advice etc.  Just got back to this after
>>>having to work on other things.
>>>
>>>To repeat what my needs are - I need a tool chain that executes under
>>>Windows 2000 to build applications to run on i386 linux.
>>>
>>>My system:
>>>           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>Installed:
>>>           MinGW-2.0.0.3.exe
>>>           MSYS-1.0.8.exe
> 
> 
> EB> Please try the latest MSYS Snapshot. See 
> EB> http://www.mingw.org/download.shtml for references to the snapshot.
> 
> EB> Thanks,
> EB> Earnie.
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

Hmm...

Where did you install MinGW??  MinGW can't live in the bin directory of 
MSYS.  See ``start /doc/msys/README.rtf''.

Earnie.

Chris Bishop wrote:
> Earnie,
> 
> Thanks for your suggestion.  I have re-installed MinGW and MSys so
> details are now:
> 
> My system:
>            Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
> Installed:
>            MinGW-2.0.0.3.exe
>            MSYS-1.0.9-2003.06.05-1.exe
> Obtained copies of:
>            binutils-2.13.90-20030111-1-src.tar.gz
>            gcc-3.2.3-20030504-1-src.tar.gz
> Placed these in directory:
>            ~/xmingw
> Changed directory to:
>            ~/xmingw
> Executed:
>            gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
>            mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
>            cd binutils-2.13.90-20030111-1 && ./configure \
>                    --target=i386-pc-linux-gnu \
>                    --prefix=/opt/xmingw32 \
>                    > ../binutils-configure.log 2>&1
>            cd binutils-2.13.90-20030111-1 && \
>                    make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
> (Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
> unzips atypically to binutils-2.13.90-20030111-1-src rather than
> binutils-2.13.90-20030111-1 and I like to keep things tidy!)
> 
> There does not appear to be anything unexpected in the
> binutils-configure.log.
> 
> But the make now fails with the relevant lines in binutils.build.log
> being:
> 
> make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
>       0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> make[2]: *** [intl-compat.o] Segmentation fault (core dumped)
> 
> and the sh.exe.stackdump is now:
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
> eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE edi=715C8984
> ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
> 0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
> 0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
> 0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
> 0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
> 0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
> 0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
> 0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
> 0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
> 0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
> 0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
> 0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
> 0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
> 0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
> 0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
> 0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
> End of stack trace (more stack frames may be present)
> 
> Any help would be appreciated.
> 
> Best regards,
> 
> Chris Bishop
> 
> Monday, June 9, 2003, 11:17:46 PM, you wrote:
> 
> 
> 
> EB> Chris Bishop wrote:
> 
>>>Luke and others who responded to my original message,
>>>
>>>Many thanks for your offer of advice etc.  Just got back to this after
>>>having to work on other things.
>>>
>>>To repeat what my needs are - I need a tool chain that executes under
>>>Windows 2000 to build applications to run on i386 linux.
>>>
>>>My system:
>>>           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>Installed:
>>>           MinGW-2.0.0.3.exe
>>>           MSYS-1.0.8.exe
> 
> 
> EB> Please try the latest MSYS Snapshot. See 
> EB> http://www.mingw.org/download.shtml for references to the snapshot.
> 
> EB> Thanks,
> EB> Earnie.
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 

Re[2]: [Mingw-users] How to build a cross compiler

[Chris B. <ki...@bi...>]

Earnie,

No - I didn't fall into that trap.

I first installed MinGW from MinGW-2.0.0.3.exe into F:\MSys\MinGW (at
this stage F:\MSys\MinGW did not previously exist).

I then installed MSys from MSYS-1.0.9-2003.06.05-1.exe into F:\MSys.
When asked about location of MinGW, I entered F:/MSys/MinGW

I have also tried installing in completely separate directories:
    MinGW in F:\MinGW
and
    MSys in F:\MSys

But the results are the same.

Other than MinGW and MSys as above, is there anything else I should be
installing?

Best regards,

Chris Bishop

Wednesday, June 11, 2003, 3:29:00 AM, you wrote:

EB> Hmm...

EB> Where did you install MinGW??  MinGW can't live in the bin directory of 
EB> MSYS.  See ``start /doc/msys/README.rtf''.

EB> Earnie.

EB> Chris Bishop wrote:
>> Earnie,
>> 
>> Thanks for your suggestion.  I have re-installed MinGW and MSys so
>> details are now:
>> 
>> My system:
>>            Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>> Installed:
>>            MinGW-2.0.0.3.exe
>>            MSYS-1.0.9-2003.06.05-1.exe
>> Obtained copies of:
>>            binutils-2.13.90-20030111-1-src.tar.gz
>>            gcc-3.2.3-20030504-1-src.tar.gz
>> Placed these in directory:
>>            ~/xmingw
>> Changed directory to:
>>            ~/xmingw
>> Executed:
>>            gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
>>            mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
>>            cd binutils-2.13.90-20030111-1 && ./configure \
>>                    --target=i386-pc-linux-gnu \
>>                    --prefix=/opt/xmingw32 \
>>                    > ../binutils-configure.log 2>&1
>>            cd binutils-2.13.90-20030111-1 && \
>>                    make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
>> (Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
>> unzips atypically to binutils-2.13.90-20030111-1-src rather than
>> binutils-2.13.90-20030111-1 and I like to keep things tidy!)
>> 
>> There does not appear to be anything unexpected in the
>> binutils-configure.log.
>> 
>> But the make now fails with the relevant lines in binutils.build.log
>> being:
>> 
>> make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
>> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
>>       0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>> make[2]: *** [intl-compat.o] Segmentation fault (core dumped)
>> 
>> and the sh.exe.stackdump is now:
>> 
>> Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
>> eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE edi=715C8984
>> ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
>> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>> Stack trace:
>> Frame     Function  Args
>> 0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
>> 0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
>> 0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
>> 0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
>> 0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
>> 0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
>> 0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
>> 0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
>> 0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
>> 0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
>> 0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
>> 0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
>> 0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
>> 0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
>> 0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
>> 0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
>> End of stack trace (more stack frames may be present)
>> 
>> Any help would be appreciated.
>> 
>> Best regards,
>> 
>> Chris Bishop
>> 
>> Monday, June 9, 2003, 11:17:46 PM, you wrote:
>> 
>> 
>> 
>> EB> Chris Bishop wrote:
>> 
>>>>Luke and others who responded to my original message,
>>>>
>>>>Many thanks for your offer of advice etc.  Just got back to this after
>>>>having to work on other things.
>>>>
>>>>To repeat what my needs are - I need a tool chain that executes under
>>>>Windows 2000 to build applications to run on i386 linux.
>>>>
>>>>My system:
>>>>           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>>Installed:
>>>>           MinGW-2.0.0.3.exe
>>>>           MSYS-1.0.8.exe
>> 
>> 
>> EB> Please try the latest MSYS Snapshot. See 
>> EB> http://www.mingw.org/download.shtml for references to the snapshot.
>> 
>> EB> Thanks,
>> EB> Earnie.
>> 
>> 
>> 
>> -------------------------------------------------------
>> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
>> thread debugger on the planet. Designed with thread debugging features
>> you've never dreamed of, try TotalView 6 free at www.etnus.com.
>> _______________________________________________
>> MinGW-users mailing list
>> Min...@li...
>> 
>> You may change your MinGW Account Options or unsubscribe at:
>> https://lists.sourceforge.net/lists/listinfo/mingw-users
>> 



EB> -------------------------------------------------------
EB> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
EB> thread debugger on the planet. Designed with thread debugging features
EB> you've never dreamed of, try TotalView 6 free at www.etnus.com.
EB> _______________________________________________
EB> MinGW-users mailing list
EB> Min...@li...

EB> You may change your MinGW Account Options or unsubscribe at:
EB> https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

Chris Bishop wrote:
> Earnie,
> 
> No - I didn't fall into that trap.
> 
> I first installed MinGW from MinGW-2.0.0.3.exe into F:\MSys\MinGW (at
> this stage F:\MSys\MinGW did not previously exist).
> 
> I then installed MSys from MSYS-1.0.9-2003.06.05-1.exe into F:\MSys.
> When asked about location of MinGW, I entered F:/MSys/MinGW
> 
> I have also tried installing in completely separate directories:
>     MinGW in F:\MinGW
> and
>     MSys in F:\MSys
> 
> But the results are the same.
> 

Ok, just trying to elimnate possibilities with what I was seeing in the 
stackdump.  I'll give it a try here.

> Other than MinGW and MSys as above, is there anything else I should be
> installing?
> 

No, that should be enough.

Earnie.

> Best regards,
> 
> Chris Bishop
> 
> Wednesday, June 11, 2003, 3:29:00 AM, you wrote:
> 
> EB> Hmm...
> 
> EB> Where did you install MinGW??  MinGW can't live in the bin directory of 
> EB> MSYS.  See ``start /doc/msys/README.rtf''.
> 
> EB> Earnie.
> 
> EB> Chris Bishop wrote:
> 
>>>Earnie,
>>>
>>>Thanks for your suggestion.  I have re-installed MinGW and MSys so
>>>details are now:
>>>
>>>My system:
>>>           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>Installed:
>>>           MinGW-2.0.0.3.exe
>>>           MSYS-1.0.9-2003.06.05-1.exe
>>>Obtained copies of:
>>>           binutils-2.13.90-20030111-1-src.tar.gz
>>>           gcc-3.2.3-20030504-1-src.tar.gz
>>>Placed these in directory:
>>>           ~/xmingw
>>>Changed directory to:
>>>           ~/xmingw
>>>Executed:
>>>           gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
>>>           mv binutils-2.13.90-20030111-1-src binutils-2.13.90-20030111-1
>>>           cd binutils-2.13.90-20030111-1 && ./configure \
>>>                   --target=i386-pc-linux-gnu \
>>>                   --prefix=/opt/xmingw32 \
>>>                   > ../binutils-configure.log 2>&1
>>>           cd binutils-2.13.90-20030111-1 && \
>>>                   make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
>>>(Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
>>>unzips atypically to binutils-2.13.90-20030111-1-src rather than
>>>binutils-2.13.90-20030111-1 and I like to keep things tidy!)
>>>
>>>There does not appear to be anything unexpected in the
>>>binutils-configure.log.
>>>
>>>But the make now fails with the relevant lines in binutils.build.log
>>>being:
>>>
>>>make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
>>>gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
>>>      0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>>>make[2]: *** [intl-compat.o] Segmentation fault (core dumped)
>>>
>>>and the sh.exe.stackdump is now:
>>>
>>>Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
>>>eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE edi=715C8984
>>>ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
>>>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>>>Stack trace:
>>>Frame     Function  Args
>>>0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
>>>0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
>>>0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
>>>0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
>>>0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
>>>0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
>>>0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
>>>0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
>>>0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
>>>0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
>>>0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
>>>0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
>>>0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
>>>0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
>>>0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
>>>0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
>>>End of stack trace (more stack frames may be present)
>>>
>>>Any help would be appreciated.
>>>
>>>Best regards,
>>>
>>>Chris Bishop
>>>
>>>Monday, June 9, 2003, 11:17:46 PM, you wrote:
>>>
>>>
>>>
>>>EB> Chris Bishop wrote:
>>>
>>>
>>>>>Luke and others who responded to my original message,
>>>>>
>>>>>Many thanks for your offer of advice etc.  Just got back to this after
>>>>>having to work on other things.
>>>>>
>>>>>To repeat what my needs are - I need a tool chain that executes under
>>>>>Windows 2000 to build applications to run on i386 linux.
>>>>>
>>>>>My system:
>>>>>          Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>>>Installed:
>>>>>          MinGW-2.0.0.3.exe
>>>>>          MSYS-1.0.8.exe
>>>
>>>
>>>EB> Please try the latest MSYS Snapshot. See 
>>>EB> http://www.mingw.org/download.shtml for references to the snapshot.
>>>
>>>EB> Thanks,
>>>EB> Earnie.
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
>>>thread debugger on the planet. Designed with thread debugging features
>>>you've never dreamed of, try TotalView 6 free at www.etnus.com.
>>>_______________________________________________
>>>MinGW-users mailing list
>>>Min...@li...
>>>
>>>You may change your MinGW Account Options or unsubscribe at:
>>>https://lists.sourceforge.net/lists/listinfo/mingw-users
>>>
> 
> 
> 
> 
> EB> -------------------------------------------------------
> EB> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> EB> thread debugger on the planet. Designed with thread debugging features
> EB> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> EB> _______________________________________________
> EB> MinGW-users mailing list
> EB> Min...@li...
> 
> EB> You may change your MinGW Account Options or unsubscribe at:
> EB> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

I've been able to more than once create the linux target with the 
version of the MSYS snapshot just uploaded.

Earnie.

Earnie Boyd wrote:
> Chris Bishop wrote:
> 
>> Earnie,
>>
>> No - I didn't fall into that trap.
>>
>> I first installed MinGW from MinGW-2.0.0.3.exe into F:\MSys\MinGW (at
>> this stage F:\MSys\MinGW did not previously exist).
>>
>> I then installed MSys from MSYS-1.0.9-2003.06.05-1.exe into F:\MSys.
>> When asked about location of MinGW, I entered F:/MSys/MinGW
>>
>> I have also tried installing in completely separate directories:
>>     MinGW in F:\MinGW
>> and
>>     MSys in F:\MSys
>>
>> But the results are the same.
>>
> 
> Ok, just trying to elimnate possibilities with what I was seeing in the 
> stackdump.  I'll give it a try here.
> 
>> Other than MinGW and MSys as above, is there anything else I should be
>> installing?
>>
> 
> No, that should be enough.
> 
> Earnie.
> 
>> Best regards,
>>
>> Chris Bishop
>>
>> Wednesday, June 11, 2003, 3:29:00 AM, you wrote:
>>
>> EB> Hmm...
>>
>> EB> Where did you install MinGW??  MinGW can't live in the bin 
>> directory of EB> MSYS.  See ``start /doc/msys/README.rtf''.
>>
>> EB> Earnie.
>>
>> EB> Chris Bishop wrote:
>>
>>>> Earnie,
>>>>
>>>> Thanks for your suggestion.  I have re-installed MinGW and MSys so
>>>> details are now:
>>>>
>>>> My system:
>>>>           Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>> Installed:
>>>>           MinGW-2.0.0.3.exe
>>>>           MSYS-1.0.9-2003.06.05-1.exe
>>>> Obtained copies of:
>>>>           binutils-2.13.90-20030111-1-src.tar.gz
>>>>           gcc-3.2.3-20030504-1-src.tar.gz
>>>> Placed these in directory:
>>>>           ~/xmingw
>>>> Changed directory to:
>>>>           ~/xmingw
>>>> Executed:
>>>>           gzip -dc binutils-2.13.90-20030111-1-src.tar.gz | tar xf -
>>>>           mv binutils-2.13.90-20030111-1-src 
>>>> binutils-2.13.90-20030111-1
>>>>           cd binutils-2.13.90-20030111-1 && ./configure \
>>>>                   --target=i386-pc-linux-gnu \
>>>>                   --prefix=/opt/xmingw32 \
>>>>                   > ../binutils-configure.log 2>&1
>>>>           cd binutils-2.13.90-20030111-1 && \
>>>>                   make "CFLAGS=-2 -O2" > ../binutils-build.log 2>&1
>>>> (Note: 'mv' line is because binutils-2.13.90-20030111-1-src.tar.gz
>>>> unzips atypically to binutils-2.13.90-20030111-1-src rather than
>>>> binutils-2.13.90-20030111-1 and I like to keep things tidy!)
>>>>
>>>> There does not appear to be anything unexpected in the
>>>> binutils-configure.log.
>>>>
>>>> But the make now fails with the relevant lines in binutils.build.log
>>>> being:
>>>>
>>>> make[2]: Entering directory 
>>>> `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
>>>> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" 
>>>> -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" 
>>>> -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H 
>>>> -I. -I.  -s -O2  intl-compat.c
>>>>      0 [main] sh 1316 open_stackdumpfile: Dumping stack trace to 
>>>> sh.exe.stackdump
>>>> make[2]: *** [intl-compat.o] Segmentation fault (core dumped)
>>>>
>>>> and the sh.exe.stackdump is now:
>>>>
>>>> Exception: STATUS_ACCESS_VIOLATION at eip=71090DBE
>>>> eax=715C8F73 ebx=715C8984 ecx=715CD000 edx=715CC77E esi=715C8FFE 
>>>> edi=715C8984
>>>> ebp=0022E208 esp=0022E200 program=F:\MSys\bin\sh.exe
>>>> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>>>> Stack trace:
>>>> Frame     Function  Args
>>>> 0022E208  71090DBE  (715C8FFE, 715C877C, 0A01ACF3, 71002BAF)
>>>> 0022E238  71090C75  (715C8984, 715C877C, 0022E5D8, 71043D35)
>>>> 0022E5D8  71043D47  (0A01ACFD, 715C9B94, 0022F9B8, 710620C8)
>>>> 0022F9B8  710620D8  (00000000, 0A019288, 0A0192F0, 0A019838)
>>>> 0022F9F8  71063C9A  (00000000, 00000003, 0A019288, 0A0192F0)
>>>> 0022FA28  710114BB  (0A019288, 0A0192F0, 0A019838, 710A5020)
>>>> 0022FA48  7108DB92  (0A019288, 0A0192F0, 0A019838, 710AA608)
>>>> 0022FB18  004127A4  (0A019288, 0A0192F0, 0A019838, 0042B3C4)
>>>> 0022FB74  00412706  (0A019410, 00000000, 0A0191B0, FFFFFFFF)
>>>> 0022FBF4  00411CA7  (0A018D00, FFFFFFFF, FFFFFFFF, 00000000)
>>>> 0022FC54  0040E9C6  (0A018CE8, 00000000, FFFFFFFF, FFFFFFFF)
>>>> 0022FCA4  004499BB  (0A018728, 004022F9, 00000004, 00402F6E)
>>>> 0022FCD4  00403180  (715B3A94, 710A5368, 0022FD74, 00401858)
>>>> 0022FD74  00401873  (00000003, 715B3CB4, 0A010278, 00000000)
>>>> 0022FE70  71004FA8  (00000000, 00000000, 00000006, 8113BDC8)
>>>> 0022FF40  710051F1  (004011C8, 00000006, 811A3B40, 811A39E0)
>>>> End of stack trace (more stack frames may be present)
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Best regards,
>>>>
>>>> Chris Bishop
>>>>
>>>> Monday, June 9, 2003, 11:17:46 PM, you wrote:
>>>>
>>>>
>>>>
>>>> EB> Chris Bishop wrote:
>>>>
>>>>
>>>>>> Luke and others who responded to my original message,
>>>>>>
>>>>>> Many thanks for your offer of advice etc.  Just got back to this 
>>>>>> after
>>>>>> having to work on other things.
>>>>>>
>>>>>> To repeat what my needs are - I need a tool chain that executes under
>>>>>> Windows 2000 to build applications to run on i386 linux.
>>>>>>
>>>>>> My system:
>>>>>>          Windows 2000 SP 3, on AMD Athlon XP1700+, 256MB RAM
>>>>>> Installed:
>>>>>>          MinGW-2.0.0.3.exe
>>>>>>          MSYS-1.0.8.exe
>>>>
>>>>
>>>>
>>>> EB> Please try the latest MSYS Snapshot. See EB> 
>>>> http://www.mingw.org/download.shtml for references to the snapshot.
>>>>
>>>> EB> Thanks,
>>>> EB> Earnie.
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.net email is sponsored by:  Etnus, makers of TotalView, The 
>>>> best
>>>> thread debugger on the planet. Designed with thread debugging features
>>>> you've never dreamed of, try TotalView 6 free at www.etnus.com.
>>>> _______________________________________________
>>>> MinGW-users mailing list
>>>> Min...@li...
>>>>
>>>> You may change your MinGW Account Options or unsubscribe at:
>>>> https://lists.sourceforge.net/lists/listinfo/mingw-users
>>>>
>>
>>
>>
>>
>> EB> -------------------------------------------------------
>> EB> This SF.net email is sponsored by:  Etnus, makers of TotalView, 
>> The best
>> EB> thread debugger on the planet. Designed with thread debugging 
>> features
>> EB> you've never dreamed of, try TotalView 6 free at www.etnus.com.
>> EB> _______________________________________________
>> EB> MinGW-users mailing list
>> EB> Min...@li...
>>
>> EB> You may change your MinGW Account Options or unsubscribe at:
>> EB> https://lists.sourceforge.net/lists/listinfo/mingw-users
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
>> thread debugger on the planet. Designed with thread debugging features
>> you've never dreamed of, try TotalView 6 free at www.etnus.com.
>> _______________________________________________
>> MinGW-users mailing list
>> Min...@li...
>>
>> You may change your MinGW Account Options or unsubscribe at:
>> https://lists.sourceforge.net/lists/listinfo/mingw-users
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 

Re: [Mingw-users] How to build a cross compiler

[Earnie B. <ear...@ya...>]

Chris Bishop wrote:
 >
> make[2]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/intl'
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  intl-compat.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  bindtextdom.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  dcgettext.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  dgettext.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  gettext.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  finddomain.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  loadmsgcat.c
> gcc -c -DLOCALEDIR=\"/opt/xmingw32/share/locale\" -DGNULOCALEDIR=\"/opt/xmingw32/share/locale\" -DLOCALE_ALIAS_PATH=\"/opt/xmingw32/share/locale:.\" -DHAVE_CONFIG_H -I. -I.  -s -O2  localealias.c
> localealias.c:156:42: warning: unknown escape sequence '\M'
> localealias.c:156:42: warning: unknown escape sequence '\o'
> localealias.c:156:42: \x used with no following hex digits
> localealias.c:156:42: warning: unknown escape sequence '\s'
> localealias.c:156:42: warning: unknown escape sequence '\l'
> make[2]: *** [localealias.o] Error 1
> 
> On examining localealias.c, it would appear that the problem is
> related to the ":." at the end of aliaspath in
> binutils-2.13.90-20030111-1/intl/Makefile.
> 
> At least, removing the :. does fix this problem even if it isn't the
> correct solution.
> 

This is a result of translating variables with path lists within MSYS. 
The rule I use is that a path list must contain a \ directory separator 
and not a / directory separator.  This causes the four warnings and one 
error and line 156 because when gcc sees LOCALE_ALIAS_PATH it has a 
value of "C:\MSYS\opt\xmingw32\share\locale:.".  And gcc treats \ as 
translate the next character to an escape sequence.

By removing :. the value is "C:/MSYS/opt/xmingw32/share/locale" and gcc 
likes this.

> With this change (even if not totally appropriate), binutils build
> seems to complete OK.
> 
> I now execute:
>            cd binutils-2.13.90-20030111-1 && \
>                    make install > ../binutils-install.log 2>&1
> 
> This fails and the last few relevant lines of binutils-install.log
> are:
> 
> make[4]: Entering directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/bfd/doc'
> make[4]: Nothing to be done for `install-exec-am'.
> make[4]: Nothing to be done for `install-data-am'.
> make[4]: Leaving directory `/home/kit/xmingw/binutils-2.13.90-20030111-1/bfd/doc'
> gcc -c -I.. -I./.. -I./../../include -I./../../intl -I../../intl  -g -O2 ./chew.c
>       0 [main] sh 1352 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> make[3]: *** [chew.o] Segmentation fault (core dumped)
> 
> The contents of sh.exe.stackdump are:
>

I think I've found this problem.  I'll upload a snapshot shortly.

Earnie.