From: Jan-Jaap van der Heijden <janjaap@Wit381304.student.utwente.nl>
To: Fabio Vignoli <bafio@dist.unige.it>
Cc: GNU-Win32 list <gnu-win32@cygnus.com>,
Colin Peters <colin@bird.fu.is.saga-u.ac.jp>
Subject: Re: Problems with mingw32 GCC 2.8.0 !!!
Date: Tue, 27 Jan 1998 16:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980128011515.383C-100000@zoo-station.student.utwente.nl> (raw)
In-Reply-To: <Pine.SOL.3.95.980127111117.5547C-100000@split.com.dist.unige.it>
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".
next prev parent reply other threads:[~1998-01-27 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-18 16:07 [ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available Jan-Jaap van der Heijden
1998-01-20 14:58 ` Paul Garceau
1998-01-24 15:34 ` Jan-Jaap van der Heijden
1998-01-27 2:27 ` Problems with mingw32 GCC 2.8.0 !!! Fabio Vignoli
1998-01-27 8:52 ` Mumit Khan
1998-01-27 16:21 ` Jan-Jaap van der Heijden [this message]
1998-01-28 0:46 ` Mikey
1998-01-28 14:54 ` Fabio Vignoli
1998-01-28 21:10 ` Isaac Kohn
1998-01-29 4:47 ` Benjamin Riefenstahl
1998-01-27 5:51 Earnie Boyd
[not found] <Pine.LNX.3.96.980128215032.3179A-100000@zoo-station.student.utwente.nl>
1998-01-28 14:54 ` Mikey
[not found] <Pine.LNX.3.96.980128204057.2538A-100000@zoo-station.student.utwente.nl>
1998-01-28 15:02 ` Mikey
1998-01-31 5:38 ` Tomas Fasth
1998-01-28 22:17 Colin Peters
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=Pine.LNX.3.96.980128011515.383C-100000@zoo-station.student.utwente.nl \
--to=janjaap@wit381304.student.utwente.nl \
--cc=bafio@dist.unige.it \
--cc=colin@bird.fu.is.saga-u.ac.jp \
--cc=gnu-win32@cygnus.com \
/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).