[ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available.

[ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available.

[Jan-Jaap van der Heijden]

I upgraded the tools on my mingw32 page:

  http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html

to the newly released GCC 2.8.0
The good news is that all patches needed to build mingw32 GCC have been
integrated in the FSF source, so no patches are needed anymore.

On this page, you will also find:

	binutils 980103
	libstdc++ 2.8.0
	libg++ 2.8.0
	mingw32 (Colin's 971230 + a few extra prototypes)
	windows32api headers
	GNU make 3.76.1
	GNU bison 1.25
	GNU flex 2.5.4a
	GNU m4 1.4
	gzip 1.2.4

All native mingw32, of course!

Enjoy,
JanJaap

---
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead.  -- RFC1925.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: [ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available.

[Paul Garceau]

On 18 Jan 98 at 20:49, the Illustrious Jan-Jaap van der Heijden wrote:

> 
> I upgraded the tools on my mingw32 page:
> 
>   http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html


	Is there a US Mirror for this?  If there is, I am unaware of it.

	I am assuming, at this point in time, that each of these things can be 
downloaded from the GNU site here in the US.  However, as I understand it, 
there would need to be further modifications completed after the 
downloading from the mit.edu site before the latest version of GCC would 
be useable as a functional part of mingw32.

	I am currently considering putting a US Mirror site together for 
Jan-Jaap, but am not sure if I've got the available disk space.  I do know 
that my ISP tends to support GNU development projects.  It is simply a 
question of need.

	Thanks for any information the participants of this mailing list 
might have.

	Peace,

		Paul G.

Information Systems Consultant
NewDawn Productions
http://www.teleport.com/~pgarceau/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: [ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available.

[Jan-Jaap van der Heijden]

On Tue, 20 Jan 1998, Paul Garceau wrote:

> On 18 Jan 98 at 20:49, the Illustrious Jan-Jaap van der Heijden wrote:
> 
> > 
> > I upgraded the tools on my mingw32 page:
> > 
> >   http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html
> 
> 
> 	Is there a US Mirror for this?  If there is, I am unaware of it.

That makes two of us :-)

> 
> 	I am assuming, at this point in time, that each of these things can be 
> downloaded from the GNU site here in the US.  However, as I understand it, 
> there would need to be further modifications completed after the 
> downloading from the mit.edu site before the latest version of GCC would 
> be useable as a functional part of mingw32.
> 

All patches are with the rest on on the FTP server, same machine:
  ftp://agnes.dida.physik.uni-essen.de/home/janjaap/mingw32/

The tricky part in building GCC yourself is not getting the sources,
but the fact that you need a unix system with a crosscompiler to build
everything. And, I use snapshot binutils (gas) and those sources are not
public.

> 	I am currently considering putting a US Mirror site together for 
> Jan-Jaap, but am not sure if I've got the available disk space.  I do know 
> that my ISP tends to support GNU development projects.  It is simply a 
> question of need.
> 

Current ftp disk usage:
6999    ./binaries
23      ./diffs/CDK
861     ./diffs/attic
956     ./diffs
4333    ./linux
7090    ./misc
316     ./platform-SDK/def
425     ./platform-SDK/import_libs
742     ./platform-SDK

Total: 20122 (plus a few Kb for the www pages)

Greetings,
Jan-Jaap

---
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead.  -- RFC1925.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Problems with mingw32 GCC 2.8.0 !!!

[Fabio Vignoli]

Hi!

I downloaded the mingw32 required packages and tried to install on my hd:

1) In the installation page:

http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/installation.html

You wrote "I shall assume `C:\MINGW32' but another location should be
fine", but it seems that it's not, I tried another directory and gcc
couldn't find the "specs" file in the ...gcc-lib/...

But this is not a big problem ... :^) maybe you forgot a fixed macro in
the code or a new anvironment variable is needed .

2) The problem I encountered when I tried to compile the dlltest or other
tests provided with the packages is more serious, maybe is my inexperience
in using the tool but it seems that WinMain does not exist in any of the
default libraries. (I used jam to compile it).

I can't report the exact error message because I'm not at home but it
seems that it can't find a reference to WinMain@16.

Thanks for your attention,
Fabio  
-----------------------------ooooO*O*Ooooo---------------------------
Fabio Vignoli                      o o  (e-mail: bafio@dist.unige.it)
http://www-dsp.com.dist.unige.it/   ^   (             vignoli@ebi.it)
DIST University of GENOVA          `-'  (        tel ++39.10.3532803)
PGP fingerprint =  E4 44 95 92 3B 23 2F 77    5D 15 44 9B 46 E6 8B B5
-----------------------------ooooO*O*Ooooo---------------------------

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Mumit Khan]

Fabio Vignoli <bafio@dist.unige.it> writes:
> 
> 2) The problem I encountered when I tried to compile the dlltest or other
> tests provided with the packages is more serious, maybe is my inexperience
> in using the tool but it seems that WinMain does not exist in any of the
> default libraries. (I used jam to compile it).

Chances are that the jamfile uses "-dll" option, which has since been
renamed to -mdll. That should fix your problem.

Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Jan-Jaap van der Heijden]

On Tue, 27 Jan 1998, Fabio Vignoli wrote:

> Hi!
> 
> I downloaded the mingw32 required packages and tried to install on my hd:
> 
> 1) In the installation page:
> 
> http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/installation.html
> 
> You wrote "I shall assume `C:\MINGW32' but another location should be
> fine", but it seems that it's not, I tried another directory and gcc
> couldn't find the "specs" file in the ...gcc-lib/...
>

I cannot reproduce this, even when the compiler is executed from a
different drive. 
1) Did you preserve the trailing slash in GCC_EXEC_PREFIX ?
2) You did replace all `C:\MINGW32' with your alternative path, right?

> 2) The problem I encountered when I tried to compile the dlltest or other
> tests provided with the packages is more serious, maybe is my inexperience
> in using the tool but it seems that WinMain does not exist in any of the
> default libraries. (I used jam to compile it).
> 
> I can't report the exact error message because I'm not at home but it
> seems that it can't find a reference to WinMain@16.
> 

The problem is an old version of `jam'.

It uses GCC's former `-dll' option, which has been renamed to `-mdll'.
So, instead of building a DLL, GCC will try to link a .EXE, and fail
miserably.

I guess Colin will fix this in a future release of jam.
In the mean time, I will update my www page to mention the jam problem.

Greetings,
JanJaap

---
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead.  -- RFC1925.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Mikey]

Jan, Colin, Mumit, Geoff, and all other developers/maintainers

using -mXXX is a very BAD idea for a gcc option.

-m is reserved for processor specifications

-mXXX always gets interpreted as a processor
specification in the specs file, which makes it impossible
to use that switch for -I/dir lines to cpp. (or pass down -D option
to cc1/plus)

-mwindows is a perfect example
-dll worked fine, why was it changed?

On Wed, 28 Jan 1998 01:22:46 +0000 (WET), you wrote:

>On Tue, 27 Jan 1998, Fabio Vignoli wrote:
>
>> Hi!
>> 
>> I downloaded the mingw32 required packages and tried to install on my hd:
>> 
>> 1) In the installation page:
>> 
>> http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/installation.html
>> 
>> You wrote "I shall assume `C:\MINGW32' but another location should be
>> fine", but it seems that it's not, I tried another directory and gcc
>> couldn't find the "specs" file in the ...gcc-lib/...
>>
>
>I cannot reproduce this, even when the compiler is executed from a
>different drive. 
>1) Did you preserve the trailing slash in GCC_EXEC_PREFIX ?
>2) You did replace all `C:\MINGW32' with your alternative path, right?
>
>> 2) The problem I encountered when I tried to compile the dlltest or other
>> tests provided with the packages is more serious, maybe is my inexperience
>> in using the tool but it seems that WinMain does not exist in any of the
>> default libraries. (I used jam to compile it).
>> 
>> I can't report the exact error message because I'm not at home but it
>> seems that it can't find a reference to WinMain@16.
>> 
>
>The problem is an old version of `jam'.
>
>It uses GCC's former `-dll' option, which has been renamed to `-mdll'.
>So, instead of building a DLL, GCC will try to link a .EXE, and fail
>miserably.
>
>I guess Colin will fix this in a future release of jam.
>In the mean time, I will update my www page to mention the jam problem.
>
>Greetings,
>JanJaap
>
>---
>With sufficient thrust, pigs fly just fine. However, this is not
>necessarily a good idea. It is hard to be sure where they are going
>to land, and it could be dangerous sitting under them as they fly
>overhead.  -- RFC1925.
>
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".


=====================================================
Linux a platform built by, and for users, standing on
the firm legs of reliability, and speed.

Microsoft Windows, a platform without a leg to stand on.

(jeffdbREMOVETHIS@netzone.com)
delete REMOVETHIS from the above to reply
         Mikey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Fabio Vignoli]

> > You wrote "I shall assume `C:\MINGW32' but another location should be
> > fine", but it seems that it's not, I tried another directory and gcc
> > couldn't find the "specs" file in the ...gcc-lib/...
> > 
> I cannot reproduce this, even when the compiler is executed from a
> different drive. 
> 1) Did you preserve the trailing slash in GCC_EXEC_PREFIX ?
> 2) You did replace all `C:\MINGW32' with your alternative path, right?

1) Yes, I paied attention for that.
2) I suppose yes, maybe the problem is in the pathname with double quotes:
   I installed the packages in the <c:\"Program Files"\mingw32> directory.

Just to joke:
try in a MSDOS shell on windows NT : cd Program Files (it works) 
                                     cd "Program Files" (it works)
                                     dir Program Files (DOES NOT WORK!!!)
                                     dir "Program Files" (it works)
Does anybody can tell me why?

> The problem is an old version of `jam'.
> 
> It uses GCC's former `-dll' option, which has been renamed to `-mdll'.
> So, instead of building a DLL, GCC will try to link a .EXE, and fail
> miserably.

Thanks, I'll try to compile it by hand ...

Bye,
Fabio
-----------------------------ooooO*O*Ooooo---------------------------
Fabio Vignoli                      o o  (e-mail: bafio@dist.unige.it)
http://www-dsp.com.dist.unige.it/   ^   (             vignoli@ebi.it)
DIST University of GENOVA          `-'  (        tel ++39.10.3532803)
PGP fingerprint =  E4 44 95 92 3B 23 2F 77    5D 15 44 9B 46 E6 8B B5
-----------------------------ooooO*O*Ooooo---------------------------

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Isaac Kohn]

> Just to joke:
> try in a MSDOS shell on windows NT : cd Program Files (it works) 
>                                      cd "Program Files" (it works)
>                                      dir Program Files (DOES NOT WORK!!!)
>                                      dir "Program Files" (it works)
> Does anybody can tell me why?

I assume the reason is that 'cd' never takes more than one arg, namely,
the directory to change to -- whereas dir can take many options and
switches and whatnot.  Because of this, cd knows that everything on the
command line is a directory name and it can allow this sort of thing --
whereas dir cannot allow this because it needs to look for other
arguments.

regards,
isaac

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Benjamin Riefenstahl]

Fabio Vignoli wrote:
> Just to joke:
> try in a MSDOS shell on windows NT : cd Program Files (it works)
>                                      cd "Program Files" (it works)
>                                      dir Program Files (DOES NOT WORK!!!)
>                                      dir "Program Files" (it works)
> Does anybody can tell me why?

;-)

If I had to guess I'd say it's just programmer's laziness and probably
backwards compatibility afterwards. You have to remember that in
DOS/Windows the command line is not parsed by the shell but by the
programs themselfs. That makes for a lot of inconsistencies between
applications and commands and seemingly even between command.com
built-ins.

The story probably was: The cd command has no options (or at least it
didn't use to), so the programmer of command.com did not bother to parse
the command line, he just took it and used it as a whole. In later
versions he added code to strip the quotes for compatibility with other
commands but he didn't use the full command-line parser, because that
might not have been backwards compatible with the use of the cd command
in older batch scripts. The dir command OTOH has a lot of options, so
the command line *has* to be parsed and after parsing Program Files
becomes two arguments.

All just guesswork, of course ;-)
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ophagen 16a, D-20257 Hamburg, Germany
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Earnie Boyd]

From owner-gnu-win32@cygnus.com Tue Jan 27 04:52:59 1998
>Received: (from majordom@localhost)
>	by runyon.cygnus.com (8.8.7-cygnus/8.8.7) id CAA29307;
>	Tue, 27 Jan 1998 02:27:36 -0800 (PST)
>Received: from dist.dist.unige.it (dist.dist.unige.it [130.251.1.4])
>	by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with SMTP id CAA29303
>	for <gnu-win32@cygnus.com>; Tue, 27 Jan 1998 02:27:24 -0800 (PST)
>Received: from split.com.dist.unige.it (split.com.dist.unige.it 
[130.251.8.20]) by dist.dist.unige.it (8.6.12/8.6.12) with SMTP id 
LAA15423; Tue, 27 Jan 1998 11:28:02 +0100
>Date: Tue, 27 Jan 1998 11:26:05 +0100 (MET)
>From: Fabio Vignoli <bafio@dist.unige.it>
>X-Sender: bafio@split.com.dist.unige.it
>To: Jan-Jaap van der Heijden <janjaap@Wit381304.student.utwente.nl>
>cc: GNU-Win32 list <gnu-win32@cygnus.com>
>Subject: Problems with mingw32 GCC 2.8.0 !!!
>In-Reply-To: 
< Pine.LNX.3.96.980123111013.492A-100000@zoo-station.student.utwente.nl >
>Message-ID: 
< Pine.SOL.3.95.980127111117.5547C-100000@split.com.dist.unige.it >
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Sender: owner-gnu-win32@cygnus.com
>Precedence: bulk
>
>Hi!
>
>I downloaded the mingw32 required packages and tried to install on my 
hd:
>
>1) In the installation page:
>
> http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/installation.html
>
>You wrote "I shall assume `C:\MINGW32' but another location should be
>fine", but it seems that it's not, I tried another directory and gcc
>couldn't find the "specs" file in the ...gcc-lib/...

I use MINGW32 in a different path than C:\MINGW32.  You need to check 
your environment variables.  Make sure that the GCC_EXEC_PREFIX is 
correct.  You must have MSDOS style paths and path separators.  You must 
end GCC_EXEC_PREFIX with a \

>
>But this is not a big problem ... :^) maybe you forgot a fixed macro in
>the code or a new anvironment variable is needed .
>
>2) The problem I encountered when I tried to compile the dlltest or 
other
>tests provided with the packages is more serious, maybe is my 
inexperience
>in using the tool but it seems that WinMain does not exist in any of 
the
>default libraries. (I used jam to compile it).
>
>I can't report the exact error message because I'm not at home but it
>seems that it can't find a reference to WinMain@16.
>

I believe you need to add a switch to indicate windows. In cygwin32 it 
is -mwindows.  I don't know if it has changed for MINGW32.

>Thanks for your attention,
>Fabio  
>-----------------------------ooooO*O*Ooooo---------------------------
>Fabio Vignoli                      o o  (e-mail: bafio@dist.unige.it)
> http://www-dsp.com.dist.unige.it/   ^   (             vignoli@ebi.it)
>DIST University of GENOVA          `-'  (        tel ++39.10.3532803)
>PGP fingerprint =  E4 44 95 92 3B 23 2F 77    5D 15 44 9B 46 E6 8B B5
>-----------------------------ooooO*O*Ooooo---------------------------
>
>-
>For help on using this list (especially unsubscribing), send a message 
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>


-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------

Check out these great gnu-win32 related sites:
ftp://ftp.cygnus.com/pub/gnu-win32/latest/           (ftp site)
http://www.cygnus.com/pubs/gnupro/                   (Comercial Page)
http://www.cygnus.com/misc/gnu-win32/                (Project Page)
http://www.cygnus.com/ml/gnu-win32                   (Mail Archives)
http://www.itribe.net/virtunix/winhelp-man-pages/    (HTML Man Pages)
http://www.lexa.ru/sos                               (Sergey Okhapkin)
ftp://www.lexa.ru/pub/domestic/sos/                (Sergey's ftp site)
http://www.fu.is.saga-u.ac.jp/~colin/gcc.html        (Colin Peters)
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ (Mumit Khan)
http://gnu-win32.paranoia.ru                   (Chuck Bogorad's ports)
ftp://ftp.deninc.com/pub (Den Internet Services - US mirror and ports)
http://www.bestweb.net/~aka/gnu-win32/  (GNU-Win32 Bash Configuration)


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Mikey]

-mwindows given to cpp
get's caught by cc1/plus and dumps you out with
windows no such processor (or something like that I don't remember exactly cause I quit using it immediately ;)

using -mdll would work the same, I'm sure, although I don't see any reason
you would need it for the preprocessor/compiler. (I'm sure someone will find one eventually)

maybe I should just bite the bullet, and replace all the FSF windows headers
with the SDK headers, but you can't redistribute those, so using -windows (and -console)
to toggle -I /path/include/win32 (and the necessary predefines) lets people who don't want to download and
patch the SDK headers use the FSF headers without having to modify their
sources, (except where the FSF headers are incompatible)

Also cygwin.dll won't compile with the SDK headers, because of
the incompatibilities, so if you want to recompile the CDK you need the
FSF headers.

On Wed, 28 Jan 1998 21:53:17 +0000 (WET), you wrote:

>On Wed, 28 Jan 1998, Mikey wrote:
>
>OK, my previous message was filtered though Mumit.
>
>> -mXXX always gets interpreted as a processor
>> specification in the specs file, which makes it impossible
>> to use that switch for -I/dir lines to cpp. (or pass down -D option
>> to cc1/plus)
>> 
>> -mwindows is a perfect example
>> -dll worked fine, why was it changed?
>> 
>
>Why is that?
>
>DLL's, console apps and GUI apps are basically the same: they are all PE
>images, but with a different entry point (amongst others).
>
>So, why does -mwindows qualify, but -(m)dll not?
>
>JanJaap
>---
>With sufficient thrust, pigs fly just fine. However, this is not
>necessarily a good idea. It is hard to be sure where they are going
>to land, and it could be dangerous sitting under them as they fly
>overhead.  -- RFC1925.
>


=====================================================
Linux a platform built by, and for users, standing on
the firm legs of reliability, and speed.

Microsoft Windows, a platform without a leg to stand on.

(jeffdbREMOVETHIS@netzone.com)
delete REMOVETHIS from the above to reply
         Mikey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Mikey]

Well let's get cygnus to change to -windows, -dll that way
you could use

gcc (for mingw32 console)
gcc -windows (for mingw32 GUI exe's)
gcc -dll (for mingw32 console dll's)
gcc -windows -dll (for mingw32 GUI dll's)
gcc -posix (for cygwin32 console)
gcc -posix -dll (for cygwin32 dll's)

Didn't Geoff say that B19 or B20 was going
to be native win32 with a posix extension?

Anyone can do this for themselves obviously,
but it's much easier to upgrade if you can get it into the
FSF sources.

CC="gcc -posix" ./configure --options (for unix software)
( or maybe setup autoconf to do it for us where necessary)
make cc=gcc                                            (for vc++ software)

It's pretty ridiculous ask developers to maintain ~40MB of extra
compiler tools, when you can do the same thing with
a few hundred bytes extra in the specs file ;^)

The first goal of any gcc port is to be able to replace the
native compiler. (in this case nmake/cl/link/lib/rc)
Which egcs-mingw32 is already pretty close to.

I would consider mingw32 a port, as opposed to cygwin32
which is actually an emulation library, able to replace
the posix subsystem on NT and add a posix subsystem
on 9x. (with a MUCH better one ;)

Not I hasten to add that I'm taking anything away from
cygnus, without that, we wouldn't have this ;^)
	Thanks Guys!!!

On Wed, 28 Jan 1998 20:57:10 +0000 (WET), you wrote:

>On Wed, 28 Jan 1998, Mumit Khan wrote:
>
>> jeffdbREMOVETHIS@netzone.com (Mikey) writes:
>> > Jan, Colin, Mumit, Geoff, and all other developers/maintainers
>> > 
>> > using -mXXX is a very BAD idea for a gcc option.
>> > 
>> > -m is reserved for processor specifications
>> 
>> That's what the docs say as well, but Kenner has the final say as 
>> FSF's GCC maintainer. 
>> 
>> JJ: did Kenner say why he wanted it this way?
>
>Kenner himself changed "-windows" to "-mwindows". This was probably for
>the sake of compatibility with cygwin32.
>
>When I couldn't talk him out of that, I argued that "-dll" should be
>renamed to "-mdll" to be consistent . BTW: I have seen *.lreg files
>around  when linking a dll, so the compiler was confused with "-dl"
>(preform a debug dump). I never bothered to make it reproducable.
>
>Most -mXXX options deal with target hardware dependant switches, and
>I agree that neither "-mwindows" nor "-mdll" is one of those.
>
> JanJaap
>
>---
>With sufficient thrust, pigs fly just fine. However, this is not
>necessarily a good idea. It is hard to be sure where they are going
>to land, and it could be dangerous sitting under them as they fly
>overhead.  -- RFC1925.
>


=====================================================
Linux a platform built by, and for users, standing on
the firm legs of reliability, and speed.

Microsoft Windows, a platform without a leg to stand on.

(jeffdbREMOVETHIS@netzone.com)
delete REMOVETHIS from the above to reply
         Mikey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Tomas Fasth]

Mikey wrote:

> Well let's get cygnus to change to -windows, -dll that way
> you could use

I think in general single dash options are supposed to be followed by a
single character indicating which option and eventually some more
characters being the option's argument, possibly preceded by white
space. In order to be more compliant to the command line option style in
other GNU software, I suggest we change that to --windows, --dll, and
--posix. Or similar.

I would have expected though, the use of a more generic double dash
option scheme already in place for such a widely ported tool as gcc. I
mean, windows (mingw32) and it's dynamic link scheme is not the only one
out there. Shouldn't this kind of stuff rather fall under the cross
platform properties (and the usage of the corresponding set of options)
of gcc?

Tomas
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Problems with mingw32 GCC 2.8.0 !!!

[Colin Peters]

From: Fabio Vignoli <bafio@dist.unige.it>
>> 1) Did you preserve the trailing slash in GCC_EXEC_PREFIX ?
>> 2) You did replace all `C:\MINGW32' with your alternative path, right?
>
>1) Yes, I paied attention for that.
>2) I suppose yes, maybe the problem is in the pathname with double
quotes:
>   I installed the packages in the <c:\"Program Files"\mingw32>
directory.

You may be finding either that the quote is simply not being processed
properly (try without it) or that it is being escaped by the backslash in
front of it (try putting the entire path in quotes, i.e. "C:\Program
Files\mingw32"). Just a couple of ideas.

Colin.

-- Colin Peters -- colin at fu.is.saga-u.ac.jp
-- Saga University Dept. of Information Science
-- http://www.fu.is.saga-u.ac.jp/~colin
-- http://www.geocities.com/Tokyo/Towers/6162


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".