From: Kai Ruottu <kai.ruottu@wippies.com>
To: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@laposte.net>,
gcc-help@gcc.gnu.org
Subject: Re: w32api: configure: error: C compiler cannot create executables
Date: Thu, 07 Aug 2014 21:07:00 -0000 [thread overview]
Message-ID: <53E3EA99.1000005@wippies.com> (raw)
In-Reply-To: <20140807215948.2cf3fc8f03a40eb8c0e1c537@laposte.net>
7.8.2014, 22:59, YuGiOhJCJ Mailing-List kirjoitti:
> Hello,
>
> I am building a cross compiler (linux 32 bits -> windows 32 bits).
> I have compiled and installed:
> - binutils-2.24.51
> - gcc-4.9.1 (with mingwrt-4.0.3.1 and w32api-4.0.3.1 headers)
I understand this as the creation of the (bare) gcc-4.9.1 succeeding
with only
the MinGW headers... But I don't understand why you didn't install the full
prebuilt 4.0.3.1 runtime and w32api stuff...
> But when I try to configure the w32api library, I got an error:
This I don't understand... Why you are trying to reinvent the wheel and
recreate
the w32api headers and import libraries for the MS DLLs?
I myself have done this last when making a variation of the w32api for
the Win32s
subset used with the Win3.1/Win32s 16/32-bit hybrid opsys in the 1990's...
> Do you have any idea why I am unable to compile this w32api please?
Probably it wasn't thought that someone wants to reinvent the wheel with the
import libraries, if not being one of the MinGW-maintainers. Are you one
of them
but don't know how they will be recreated after some fixes?
prev parent reply other threads:[~2014-08-07 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:59 YuGiOhJCJ Mailing-List
2014-08-07 20:05 ` Jonathan Wakely
2014-08-07 21:06 ` YuGiOhJCJ Mailing-List
2014-08-07 22:07 ` Jonathan Wakely
2014-08-07 23:38 ` YuGiOhJCJ Mailing-List
2014-08-07 21:07 ` Kai Ruottu [this message]
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=53E3EA99.1000005@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.org \
--cc=yugiohjcj-mailinglist@laposte.net \
/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).