On 10/25/2013 15:23, Daniel Richard G. wrote:
> On Thu, 2013 Oct 24 8:59-0400, Earnie Boyd wrote:
>>
>> Daniel, you can have configure use i686-pc-mingw32 or any other host
>> triplet by specifying it in your environment rather than on the
>> command line. Then config.guess doesn't have to guess.
On 10/25/2013 10:00, Daniel Richard G. wrote:
> On Thu, 2013 Oct 24 18:33+0800, JonY wrote:
>>
>>> I'll gladly submit a patch that allows the Libtool script to detect
>>> the MSYS shell at invocation time using ${BASH_VERSINFO[5]}, if
>>> that's the main objection.
>>
>> That was already tried, lik
On Thu, 2013 Oct 24 8:59-0400, Earnie Boyd wrote:
>
> Daniel, you can have configure use i686-pc-mingw32 or any other host
> triplet by specifying it in your environment rather than on the
> command line. Then config.guess doesn't have to guess.
>
> export ac_cv_host=i686-pc-mingw32 ./configure
(
On Thu, 2013 Oct 24 18:33+0800, JonY wrote:
>
> > I'll gladly submit a patch that allows the Libtool script to detect
> > the MSYS shell at invocation time using ${BASH_VERSINFO[5]}, if
> > that's the main objection.
>
> That was already tried, like this patch, it was messy and of
> little value.
>
On Thu, Oct 24, 2013 at 6:40 AM, JonY wrote:
> On 10/24/2013 14:04, Daniel Richard G. wrote:
>> On Wed, 2013 Oct 23 7:55-0400, Earnie Boyd wrote:
>>>
>>> JonY you forget to mention that what Daniel is trying to do has
>>> already been tried once and long since abandoned in favor of using a
>>> cros
On 10/24/2013 14:04, Daniel Richard G. wrote:
> On Wed, 2013 Oct 23 7:55-0400, Earnie Boyd wrote:
>>
>> JonY you forget to mention that what Daniel is trying to do has
>> already been tried once and long since abandoned in favor of using a
>> cross compiler. Remember the -mno-cygwin conglomeration
On 10/24/2013 13:58, Daniel Richard G. wrote:
> On Wed, 2013 Oct 23 18:05+0800, JonY wrote:
>>>
>>> I never suggested replacing Cygwin-GCC with MinGW-GCC
>>
>> You just did, CC=i686-pc-mingw32-gcc, they are NOT drop-in
>> replacements.
>
> I'm aware that the two compilers produce different kinds o
On Wed, 2013 Oct 23 7:55-0400, Earnie Boyd wrote:
>
> JonY you forget to mention that what Daniel is trying to do has
> already been tried once and long since abandoned in favor of using a
> cross compiler. Remember the -mno-cygwin conglomeration of ugliness?
Well, that's using a single toolchain
On Wed, 2013 Oct 23 18:05+0800, JonY wrote:
> >
> > I never suggested replacing Cygwin-GCC with MinGW-GCC
>
> You just did, CC=i686-pc-mingw32-gcc, they are NOT drop-in
> replacements.
I'm aware that the two compilers produce different kinds of outputs (a
Cygwin binary versus a native Win32 binary
On 10/23/2013 19:55, Earnie Boyd wrote:
> On Wed, Oct 23, 2013 at 6:09 AM, JonY wrote:
>> On 10/23/2013 13:49, Daniel Richard G. wrote:
>>> It's a situation where the two "platforms" are not all that different---
>>> the system can run binaries from both---and avoiding the need to
>>> rigorously cr
On Wed, Oct 23, 2013 at 6:09 AM, JonY wrote:
> On 10/23/2013 13:49, Daniel Richard G. wrote:
>> It's a situation where the two "platforms" are not all that different---
>> the system can run binaries from both---and avoiding the need to
>> rigorously cross-compile from one to the other is a big con
On 10/23/2013 13:49, Daniel Richard G. wrote:
> It's a situation where the two "platforms" are not all that different---
> the system can run binaries from both---and avoiding the need to
> rigorously cross-compile from one to the other is a big convenience.
>
> Obviously, Cygwin vs. MinGW program
On 10/23/2013 13:53, Daniel Richard G. wrote:
> On Tue, 2013 Oct 22 17:38+0800, JonY wrote:
>>
>> This has nothing to do with MSYS vs Cygwin, your whole patch is messed
>> up, it needs to be shot down and burned like the bad idea it is.
>> Cygwin ships a CROSS COMPILER, mingw gcc is not a replaceme
On Tue, 2013 Oct 22 17:38+0800, JonY wrote:
>
> This has nothing to do with MSYS vs Cygwin, your whole patch is messed
> up, it needs to be shot down and burned like the bad idea it is.
> Cygwin ships a CROSS COMPILER, mingw gcc is not a replacement for cygwin-
> gcc like your use case suggests.
I
On Tue, 2013 Oct 22 7:14+0200, Jan Engelhardt wrote:
>
> But “only” on Solaris (and I even question _that_ decision). In
> particular,
>
> CC="gcc -m32" ./config.guess# from sparc64, ppc64(non-IBM)
> CC="gcc -mx32" ./config.guess # from x86_64
>
> run from an sparc64-linux does not produce
- Original Message -
> On Mon, Oct 21, 2013 at 9:19 AM, Kai Tietz wrote:
> > Hello,
> >
> > Once again ... We already discussed this issue some time ago directly,
> > Earnie. And just by repeating and spreading this nonsense over and over
> > again, it doesn't make it right.
> >
>
> I am
On Mon, Oct 21, 2013 at 9:19 AM, Kai Tietz wrote:
> Hello,
>
> Once again ... We already discussed this issue some time ago directly,
> Earnie. And just by repeating and spreading this nonsense over and over
> again, it doesn't make it right.
>
I am not going to debate the issue.
>
> So inste
On 10/22/2013 09:43, Daniel Richard G. wrote:
> On Mon, 2013 Oct 21 18:13+0800, JonY wrote:
>>
>> Do not confuse Cygwin and MSYS, they are not interchangeable.
>
> I know about MSYS; it's a good development environment, but not a
> complete system, and a lot less convenient to install. I'm concern
On Tuesday 2013-10-22 03:43, Daniel Richard G. wrote:
>On Mon, 2013 Oct 21 18:13+0800, JonY wrote:
>
>In the same way that, on a Solaris machine I work with here, I can get
>
>$ ./config.guess
>i386-pc-solaris2.10
>$ CC="cc -xarch=generic64" ./config.guess
>x86_64-pc-solaris2.10
On Mon, 2013 Oct 21 18:13+0800, JonY wrote:
>
> Do not confuse Cygwin and MSYS, they are not interchangeable.
I know about MSYS; it's a good development environment, but not a
complete system, and a lot less convenient to install. I'm concerned
with using MinGW-GCC as shipped by Cygwin (not by the
Hello,
Once again ... We already discussed this issue some time ago directly, Earnie.
And just by repeating and spreading this nonsense over and over again, it
doesn't make it right.
First I have to state that therr is (and was) no target using *mingw64* as
host-part triplet. What should
On Mon, Oct 21, 2013 at 8:01 AM, Earnie Boyd wrote:
> On Mon, Oct 21, 2013 at 6:13 AM, JonY wrote:
>>
>> Moreover, *-*-mingw64 does not exist save for a short experimentation
>> period. It should really be removed. The __MINGW64__ macro on the other
>> hand is unrelated to any of this.
>>
>
> No,
On Mon, Oct 21, 2013 at 6:13 AM, JonY wrote:
>
> Moreover, *-*-mingw64 does not exist save for a short experimentation
> period. It should really be removed. The __MINGW64__ macro on the other
> hand is unrelated to any of this.
>
No, it exists because I created it. It should not be removed.
--
On 10/21/2013 09:50, Daniel Richard G. wrote:
> Hello,
>
> Among the many packages Cygwin provides are MinGW builds of GCC and the
> associated libraries and tools, making this a convenient alternative to
> MSYS and the packages provided directly by the MinGW project.
>
> When one is using the Mi
Hello,
Among the many packages Cygwin provides are MinGW builds of GCC and the
associated libraries and tools, making this a convenient alternative to
MSYS and the packages provided directly by the MinGW project.
When one is using the MinGW compiler in this environment, however,
config.guess stil
25 matches
Mail list logo
