On 2009-01-29 05:08Z, Charles Wilson wrote:
Greg Chicares wrote:
On 2009-01-28 05:28Z, Charles Wilson wrote:
Forgive my delay in thanking you for taking so much time to
point out the many issues with what I'm doing. Perhaps the
worst problem was this:
An incidental oddity is that the
At:
http://www.cygwin.com/ml/cygwin/2009-01/msg00848.html
Charles Wilson said:
Greg said
I use '--build=i686-pc-mingw32 --host=i686-pc-mingw32'. Here:
http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00193.html
you say that's lying to 'configure', but you also observe that
I'm in
Danny Smith wrote:
The reasons I use --build=mingw32 --host=mingw32 --target=mingw32
when building gcc are
1) I have, perhaps mistakenly, assumed that --build= referred to the OS of
the compiler,
not the ethnicity of the shell.
I've assumed it was describing the entire build environment:
Charles Wilson wrote:
[describe old libtool behavior; what I called current gcc libtool]
1) creates both a wrapper script foo and wrapper exe foo.exe in the
build directory, and also (?) a copy of the wrapper script in .libs/
2) the wrapper exe execs the wrapper script via $SHELL
3) the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Right, if I'm building a compiler. I'm not -- although that wasn't very
clear, since the only examply I gave was Danny's incantation for
building gcc, a compiler. Oops.
I'm talking about building, say, ncurses so that
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler. That is, incantations like this:
snip
I find myself bouncing around between cygwin and mingw because
On Wed, 28 Jan 2009 09:38:47 -0500, Ralph Hempel rhem...@bmts.com wrote:
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler. That is, incantations like
On Wed, Jan 28, 2009 at 12:14:40AM -0600, Yaakov (Cygwin/X) wrote:
Charles Wilson wrote:
This led to a suggestion that --build=cygwin --host=mingw32 should
always be interpreted as: mingw32-gcc is a cygwin-hosted cross
compiler, NOT the native MinGW-project supported gcc (and if it IS the
native
On Wed, Jan 28, 2009 at 04:05:55PM +0100, Vincent R. wrote:
Actually I am using cygwin because there are many packages, adn a good
installer but I will
switch completely to mingw if I could get the same.
Couldn't be possible to share more things between the two projects ?
I mean for instance
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler. That is, incantations like this:
1a)
cygwin$ some-src-pkg/configure \
--build=i686-pc-cygwin
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler.
- I currently use Cygwin for cross-platform development of software and
firmware.
- I use
Charles Wilson schrieb:
I just want to get an idea of how many people are currently,
actually, successfully, doing something like 1a) or 1b) above.
I never do serious cross-compiling from or to mingw in a cygwin shell.
When testing mingw I do it from cmd.exe and the mingw toolkit and no
On 2009-01-28 05:28Z, Charles Wilson wrote:
Greg Chicares wrote:
On 2009-01-28 02:21Z, Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler.
I use the
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler. That is, incantations like this:
[snip]
I hope this is considered on-topic here, because I'm
Greg Chicares wrote:
On 2009-01-28 05:28Z, Charles Wilson wrote:
First, thanks for your detailed response. It was very helpful.
Do you use gnu-style configured projects (autoconf, automake, libtool,
all that?) -- or some other build framework?
Yes. I use autotools to build native versions
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler. That is, incantations like this:
1a)
cygwin$ some-src-pkg/configure \
--build=i686-pc-cygwin --host=mingw32 \
On Tue, Jan 27, 2009 at 09:21:59PM -0500, Charles Wilson wrote:
I hope this is considered on-topic here, because I'm interested in the
uses of the cygwin environment itself.
It's certainly on-topic. I'd be interested in the responses too.
cgf
--
Unsubscribe info:
Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler.
I do half of what you're asking: use Cygwin's bash shell as an
environment to drive mingw32-make on
On 2009-01-28 02:21Z, Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler.
I use the native MinGW compiler in a Cygwin environment,
successfully, many
Greg Chicares wrote:
On 2009-01-28 02:21Z, Charles Wilson wrote:
Pursuant to a discussion on the libtool list, I'm trying to get a feel
for how many cygwin users rely on the cygwin environment to drive the
*native* MinGW gcc compiler.
I use the native MinGW compiler in a Cygwin environment,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
This led to a suggestion that --build=cygwin --host=mingw32 should
always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler,
NOT the native MinGW-project supported gcc (and if it IS the native
MinGW one,
Yaakov (Cygwin/X) wrote:
Charles Wilson wrote:
This led to a suggestion that --build=cygwin --host=mingw32 should
always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler,
NOT the native MinGW-project supported gcc (and if it IS the native
MinGW one, expect breakage). I'm not
22 matches
Mail list logo
