On Sat, 21 Oct 2017 16:17:13, cyg Simple wrote:
5 sec * 2300 packages = 11,500 sec
11,500 sec is 3.19 hours
> Which in a build like FFmpeg or similar, is statistically 0.
>
1 package once in a while doesn't matter.
> So perhaps you have some data to show a non-trivial amount of time saved
>
On 10/21/2017 3:26 PM, Steven Penny wrote:
> On Sat, 21 Oct 2017 13:29:43, cyg Simple wrote:
>> Changing the default does improve the speed of configure because
>> configure no longer needs to execute GCC to figure out where the build
>> files are. Yes the time saved is small but time is expensive
On Sat, 21 Oct 2017 13:29:43, cyg Simple wrote:
Changing the default does improve the speed of configure because
configure no longer needs to execute GCC to figure out where the build
files are. Yes the time saved is small but time is expensive so any
saving is a big deal, especially with such a
On 10/20/2017 6:47 PM, Steven Penny wrote:
> On Fri, 20 Oct 2017 15:53:28, cyg Simple wrote:
>> I appreciate what Yaakov does but I bet these are not built in native
>> Cygwin mode so a host must be supplied. In native mode the default is
>> typically used and currently it doesn't match the expect
On Fri, 20 Oct 2017 15:53:28, cyg Simple wrote:
I appreciate what Yaakov does but I bet these are not built in native
Cygwin mode so a host must be supplied. In native mode the default is
typically used and currently it doesn't match the expected host environment.
Really this discussion boils
On 2017-10-20 14:53, cyg Simple wrote:
> I appreciate what Yaakov does but I bet these are not built in native
> Cygwin mode so a host must be supplied. In native mode the default is
> typically used and currently it doesn't match the expected host environment.
You lose the bet. Every single pac
On 10/20/2017 1:41 PM, Marco Atzeri wrote:
> On 20/10/2017 17:44, cyg Simple wrote:
>> On 10/20/2017 11:24 AM,
>
>> Why is it different? Give a reason not just
>> some lame excuse.
>
> This is extremely rude, in my opinion.
>
Thanks for your opinion. I reworded most of my original text in th
On 10/20/2017 2:44 PM, Brian Inglis wrote:
> On 2017-10-20 11:41, Marco Atzeri wrote:
>> On 20/10/2017 17:44, cyg Simple wrote:
>>> On 10/20/2017 11:24 AM,
>>> Why is it different? Give a reason not just some lame excuse.
>> This is extremely rude, in my opinion.
>
> He's not asking the question
On 10/20/2017 2:34 PM, Eric Blake wrote:
> On 10/20/2017 11:11 AM, cyg Simple wrote:
>
> I may regret joining this thread, but here goes.
>
But thanks for doing so anyway.
>>> Your assumption is that the default and chosen triplets must/should be
>>> one and the same.
>>
>> No, I assume no su
On 2017-10-20 11:41, Marco Atzeri wrote:
> On 20/10/2017 17:44, cyg Simple wrote:
>> On 10/20/2017 11:24 AM,
>> Why is it different? Give a reason not just some lame excuse.
> This is extremely rude, in my opinion.
He's not asking the question he needs answered and is getting exasperated.
> You
On 10/20/2017 11:11 AM, cyg Simple wrote:
I may regret joining this thread, but here goes.
>> Your assumption is that the default and chosen triplets must/should be
>> one and the same.
>
> No, I assume no such thing.
>
>> They are not, they need not be, and we are far from
>> being alone in
On 20/10/2017 17:44, cyg Simple wrote:
On 10/20/2017 11:24 AM,
Why is it different? Give a reason not just
some lame excuse.
This is extremely rude, in my opinion.
Yaakov has been extremely patient with you but you are always
disregarding our point of view, that only shows us that
you have
On 10/20/2017 12:11 PM, cyg Simple wrote:
> On 10/20/2017 11:54 AM, Yaakov Selkowitz wrote:
>> On 2017-10-20 10:44, cyg Simple wrote:
>>> On 10/20/2017 11:24 AM, Yaakov Selkowitz wrote:
On 2017-10-20 08:28, cyg Simple wrote:
> On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
>> 2) the ou
On 10/20/2017 11:54 AM, Yaakov Selkowitz wrote:
> On 2017-10-20 10:44, cyg Simple wrote:
>> On 10/20/2017 11:24 AM, Yaakov Selkowitz wrote:
>>> On 2017-10-20 08:28, cyg Simple wrote:
On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
> 2) the output of config.guess is a default and does NOT re
On 2017-10-20 10:44, cyg Simple wrote:
> On 10/20/2017 11:24 AM, Yaakov Selkowitz wrote:
>> On 2017-10-20 08:28, cyg Simple wrote:
>>> On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
2) the output of config.guess is a default and does NOT reflect, or need
to match, our chosen triplet. The
On 10/20/2017 11:24 AM, Yaakov Selkowitz wrote:
> On 2017-10-20 08:28, cyg Simple wrote:
>> On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
>>> 2) the output of config.guess is a default and does NOT reflect, or need
>>> to match, our chosen triplet. There is nothing to fix in config.guess.
>>
>> F
On 2017-10-20 08:28, cyg Simple wrote:
> On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
>> 2) the output of config.guess is a default and does NOT reflect, or need
>> to match, our chosen triplet. There is nothing to fix in config.guess.
>
> Fine, it doesn't have to match, why don't you want it t
On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote:
> 2) the output of config.guess is a default and does NOT reflect, or need
> to match, our chosen triplet. There is nothing to fix in config.guess.
Fine, it doesn't have to match, why don't you want it to? Don't give me
the historical reasons idea.
On 2017-10-19 19:11, Yaakov Selkowitz wrote:
> On 2017-10-19 18:49, Steven Penny wrote:
>> On Thu, 19 Oct 2017 17:00:12, cyg Simple wrote:
>>> So says you! The vendor portion has been agreed to be -pc- and it isn't
>>> -unknown-, a patch then should be created for config.guess to match the
>>> agr
On 2017-10-19 18:49, Steven Penny wrote:
> On Thu, 19 Oct 2017 17:00:12, cyg Simple wrote:
>> So says you! The vendor portion has been agreed to be -pc- and it isn't
>> -unknown-, a patch then should be created for config.guess to match the
>> agreed upon vendor. The config.guess script supplies
On Thu, 19 Oct 2017 17:00:12, cyg Simple wrote:
So says you! The vendor portion has been agreed to be -pc- and it isn't
-unknown-, a patch then should be created for config.guess to match the
agreed upon vendor. The config.guess script supplies the default to
configure for the build and host.
On 2017-10-19 18:21, Brian Inglis wrote:
> I think the OP's problem is he knows no way to override the default and use
> only
> the standard ./configure && make build approach.
Which works just fine btw, so there's no need to override it.
> The OP could take a build config.cache and save it in /
On 2017-10-19 15:14, Yaakov Selkowitz wrote:
> On 2017-10-19 16:00, cyg Simple wrote:
>> On 10/19/2017 4:35 PM, Yaakov Selkowitz wrote:
>>> On 2017-10-19 15:02, cyg Simple wrote:
On 10/19/2017 3:54 PM, Brian Inglis wrote:
> On 2017-10-19 12:59, Yaakov Selkowitz wrote:
>> On 2017-10-19
On 10/19/2017 04:18 PM, cyg Simple wrote:
> On 10/19/2017 10:18 AM, Ken Brown wrote:
>> On 10/19/2017 9:19 AM, cyg Simple wrote:
>>> On 10/18/2017 6:58 PM, JonY wrote:
I agree with Yaakov, why does it need to change?
>>>
>>> See my response to Yaakov. If you supply explicit host and buil
On 2017-10-19 16:00, cyg Simple wrote:
> On 10/19/2017 4:35 PM, Yaakov Selkowitz wrote:
>> On 2017-10-19 15:02, cyg Simple wrote:
>>> On 10/19/2017 3:54 PM, Brian Inglis wrote:
On 2017-10-19 12:59, Yaakov Selkowitz wrote:
> On 2017-10-19 13:40, cyg Simple wrote:
>> x86_64-pc-cygwin is
On 10/19/2017 4:35 PM, Yaakov Selkowitz wrote:
> On 2017-10-19 15:02, cyg Simple wrote:
>> On 10/19/2017 3:54 PM, Brian Inglis wrote:
>>> On 2017-10-19 12:59, Yaakov Selkowitz wrote:
On 2017-10-19 13:40, cyg Simple wrote:
> x86_64-pc-cygwin is just not correct regardless of the lack of pas
On 2017-10-19 15:26, cyg Simple wrote:
> My assumption is because of config.guess' default. It isn't incorrect,
> it is a valid assumption. You cannot have both, it is one or the other.
Your assumption that the default provided by config.guess must match the
one we have chosen is incorrect. Onc
On 2017-10-19 15:02, cyg Simple wrote:
> On 10/19/2017 3:54 PM, Brian Inglis wrote:
>> On 2017-10-19 12:59, Yaakov Selkowitz wrote:
>>> On 2017-10-19 13:40, cyg Simple wrote:
x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
>>>
>>> As I have said several times, this
> On Oct 19, 2017, at 3:21 PM, cyg Simple wrote:
>
> On 10/19/2017 4:02 PM, Vince Rice wrote:
>>> On Oct 19, 2017, at 2:08 PM, cyg Simple wrote:
>>>
>>> On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
When you *really* need to use --build and/or --host, then you need to
use x86_6
On 2017-10-19 15:21, cyg Simple wrote:
> I'm not providing the name of the package because I don't need help
> configuring it and I don't want the discussion to become how to do that.
This is *exactly* what this discussion *should* have been about from the
beginning, because that would have been a
On 10/19/2017 4:21 PM, Yaakov Selkowitz wrote:
> On 2017-10-19 14:08, cyg Simple wrote:
>> On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
>>>
>>> When you *really* need to use --build and/or --host, then you need to
>>> use x86_64-pc-cygwin, as that is our chosen name.
>>
>> Then config.guess needs
On 10/19/2017 4:02 PM, Vince Rice wrote:
>> On Oct 19, 2017, at 2:08 PM, cyg Simple wrote:
>>
>> On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
>>>
>>> When you *really* need to use --build and/or --host, then you need to
>>> use x86_64-pc-cygwin, as that is our chosen name.
>>
>> Then config.gues
On 2017-10-19 14:08, cyg Simple wrote:
> On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
>>
>> When you *really* need to use --build and/or --host, then you need to
>> use x86_64-pc-cygwin, as that is our chosen name.
>
> Then config.guess needs to change to match the chosen name!!
No, it doesn't.
On 10/19/2017 3:54 PM, Brian Inglis wrote:
> On 2017-10-19 12:59, Yaakov Selkowitz wrote:
>> On 2017-10-19 13:40, cyg Simple wrote:
>>> x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
>>
>> As I have said several times, this assertion is incorrect. You need to
>> use th
> On Oct 19, 2017, at 2:08 PM, cyg Simple wrote:
>
> On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
>>
>> When you *really* need to use --build and/or --host, then you need to
>> use x86_64-pc-cygwin, as that is our chosen name.
>
> Then config.guess needs to change to match the chosen name!!
>
On 2017-10-19 12:59, Yaakov Selkowitz wrote:
> On 2017-10-19 13:40, cyg Simple wrote:
>> x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
>
> As I have said several times, this assertion is incorrect. You need to
> use the triplet which matches the toolchain with which
On 10/19/2017 2:51 PM, Yaakov Selkowitz wrote:
>
> When you *really* need to use --build and/or --host, then you need to
> use x86_64-pc-cygwin, as that is our chosen name.
Then config.guess needs to change to match the chosen name!!
Why confuse everyone? Make up your mind and choose one. I ca
On 10/19/2017 2:59 PM, Yaakov Selkowitz wrote:
> On 2017-10-19 13:40, cyg Simple wrote:
>> x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
>
> As I have said several times, this assertion is incorrect. You need to
> use the triplet which matches the toolchain with whic
On 2017-10-19 13:40, cyg Simple wrote:
> x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
As I have said several times, this assertion is incorrect. You need to
use the triplet which matches the toolchain with which you are building.
For example, Fedora and RHEL all us
On 2017-10-19 11:44, cyg Simple wrote:
> On 10/19/2017 11:04 AM, Yaakov Selkowitz wrote:
>> We've been building packages for 64-bit Cygwin for years now without a
>> problem. Maybe you could just tell what you're trying to do and the
>> problem you're seeing so that we can assist you, instead of t
On 10/19/2017 2:37 PM, Steven Penny wrote:
> On Thu, 19 Oct 2017 12:47:29, cyg Simple wrote:
>> > may we know which package ?
>> > > If it refuses triplet has a strange way to use Autoconf/Automake
>> > and changing the compiler seems the wrong way to solve the issue
>>
>> No, it doesn't matter. D
On Thu, 19 Oct 2017 12:47:29, cyg Simple wrote:
> may we know which package ?
>
> If it refuses triplet has a strange way to use Autoconf/Automake
> and changing the compiler seems the wrong way to solve the issue
No, it doesn't matter. Delivering x86_64-pc-cygwin anything is wrong
since the
On 10/19/2017 12:41 PM, Marco Atzeri wrote:
> On 19/10/2017 18:21, cyg Simple wrote:
>
./configure --host=x86_64-unknown-cygwin --build=x86_64-unknown-cygwin
>>>
>>>
>>> the correct way is
>>> ./configure
>>>
>>
>> Normally yes, but ...
>>
>>> don't add what you don't need..
>>
>> I wa
On 10/19/2017 11:04 AM, Yaakov Selkowitz wrote:
> On 2017-10-19 08:25, cyg Simple wrote:
>> On 10/18/2017 7:26 PM, Steven Penny wrote:
>>> On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
For a regex pattern you should include both.
I do not bore which one is built and distributed on my
On 19/10/2017 18:21, cyg Simple wrote:
./configure --host=x86_64-unknown-cygwin --build=x86_64-unknown-cygwin
the correct way is
./configure
Normally yes, but ...
don't add what you don't need..
I was trying to help a package refusing the config.guess triplet so I
needed it. Regard
On 10/19/2017 10:41 AM, Marco Atzeri wrote:
> On 19/10/2017 15:17, cyg Simple wrote:
>>
>>
>
So the corrective action is to distribute GCC and friends as
x86_64-unknown-cygwin-*.exe instead of x86_64-pc-cygwin-*.exe.
>>>
>>> Incorrect. GCC is also fine as is.
>>>
>>
>> No it is not
On 10/19/2017 10:18 AM, Ken Brown wrote:
> On 10/19/2017 9:19 AM, cyg Simple wrote:
>> On 10/18/2017 6:58 PM, JonY wrote:
>>> I agree with Yaakov, why does it need to change?
>>>
>>
>> See my response to Yaakov. If you supply explicit host and build to
>> configure it does not work.
>
> So don't
On 2017-10-19 08:25, cyg Simple wrote:
> On 10/18/2017 7:26 PM, Steven Penny wrote:
>> On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
>>> For a regex pattern you should include both.
>>> I do not bore which one is built and distributed on my packages.
>>>
>>> E.G. on octave
>>>
>>> /usr/lib/octa
On 19/10/2017 15:25, cyg Simple wrote:
On 10/18/2017 7:26 PM, Steven Penny wrote:
On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
For a regex pattern you should include both.
I do not bore which one is built and distributed on my packages.
E.G. on octave
/usr/lib/octave/site/oct/i686-pc-cyg
On 19/10/2017 15:17, cyg Simple wrote:
So the corrective action is to distribute GCC and friends as
x86_64-unknown-cygwin-*.exe instead of x86_64-pc-cygwin-*.exe.
Incorrect. GCC is also fine as is.
No it is not! The below example should work out of the box and it doesn't.
./configur
On 10/19/2017 9:19 AM, cyg Simple wrote:
On 10/18/2017 6:58 PM, JonY wrote:
I agree with Yaakov, why does it need to change?
See my response to Yaakov. If you supply explicit host and build to
configure it does not work.
So don't do that. Specifying host is for cross-compilation. Specify
On 10/18/2017 7:26 PM, Steven Penny wrote:
> On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
>> For a regex pattern you should include both.
>> I do not bore which one is built and distributed on my packages.
>>
>> E.G. on octave
>>
>> /usr/lib/octave/site/oct/i686-pc-cygwin
>> /usr/lib/octave/si
On 10/18/2017 6:58 PM, JonY wrote:
> On 10/18/2017 10:41 PM, Yaakov Selkowitz wrote:
>> On 2017-10-18 14:10, cyg Simple wrote:
>>> On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
On 2017-10-18 09:05, cyg Simple wrote:
> Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
>>
On 10/18/2017 6:41 PM, Yaakov Selkowitz wrote:
> On 2017-10-18 14:10, cyg Simple wrote:
>> On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
>>> On 2017-10-18 09:05, cyg Simple wrote:
Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
filter to echo ${UNAME_MACHINE}-unkno
On 2017-10-18 18:26, Steven Penny wrote:
> On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
>> For a regex pattern you should include both.
>> I do not bore which one is built and distributed on my packages.
>>
>> E.G. on octave
>>
>> /usr/lib/octave/site/oct/i686-pc-cygwin
>> /usr/lib/octave/site
On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
For a regex pattern you should include both.
I do not bore which one is built and distributed on my packages.
E.G. on octave
/usr/lib/octave/site/oct/i686-pc-cygwin
/usr/lib/octave/site/oct/x86_64-unknown-cygwin
This is certainly not right. I
On 10/18/2017 10:41 PM, Yaakov Selkowitz wrote:
> On 2017-10-18 14:10, cyg Simple wrote:
>> On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
>>> On 2017-10-18 09:05, cyg Simple wrote:
Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
filter to echo ${UNAME_MACHINE}-unknow
On 2017-10-18 14:10, cyg Simple wrote:
> On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
>> On 2017-10-18 09:05, cyg Simple wrote:
>>> Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
>>> filter to echo ${UNAME_MACHINE}-unknown-cygwin?
>>
>> That would be incorrect. config.guess
On 2017-10-18 13:10, cyg Simple wrote:
> On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
>> On 2017-10-18 09:05, cyg Simple wrote:
>>> Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
>>> filter to echo ${UNAME_MACHINE}-unknown-cygwin?
>>
>> That would be incorrect. config.guess
On 10/18/2017 1:11 PM, Yaakov Selkowitz wrote:
> On 2017-10-18 09:05, cyg Simple wrote:
>> Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
>> filter to echo ${UNAME_MACHINE}-unknown-cygwin?
>
> That would be incorrect. config.guess is fine as it is.
>
So the corrective acti
On 2017-10-18 09:05, cyg Simple wrote:
> Does anyone care if a patch to config.guess changes the i*:CYGWIN*:*
> filter to echo ${UNAME_MACHINE}-unknown-cygwin?
That would be incorrect. config.guess is fine as it is.
--
Yaakov
signature.asc
Description: OpenPGP digital signature
On 10/17/2017 3:16 PM, cyg Simple wrote:
> The config.guess file[1] is confused.
>
> 840i*:CYGWIN*:*)
> 841 echo ${UNAME_MACHINE}-pc-cygwin
> 842 exit ;;
> -
> 870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
> 871 echo x86_64-unknown-cygwin
> 872 exit ;;
>
> The GCC executable is x
On 2017-10-18 00:45, Marco Atzeri wrote:
> On 18/10/2017 05:29, cyg Simple wrote:
>> On 10/17/2017 7:49 PM, Brian Inglis wrote:
>>> On 2017-10-17 13:16, cyg Simple wrote:
>> I'm only concerned with Cygwin at the moment. As I understand it the we
>> should distribute x86[_64]-unknown-cygwin-*.exe a
On 18/10/2017 05:29, cyg Simple wrote:
On 10/17/2017 7:49 PM, Brian Inglis wrote:
On 2017-10-17 13:16, cyg Simple wrote:
I'm only concerned with Cygwin at the moment. As I understand it the we
should distribute x86[_64]-unknown-cygwin-*.exe and not as
x86[_64]-pc-cygwin-*.exe We also need
On 2017-10-17 21:29, cyg Simple wrote:
> On 10/17/2017 7:49 PM, Brian Inglis wrote:
>> On 2017-10-17 13:16, cyg Simple wrote:
>>> The config.guess file[1] is confused.
>>>
>>> 840i*:CYGWIN*:*)
>>> 841 echo ${UNAME_MACHINE}-pc-cygwin
>>> 842 exit ;;
>>> -
>>> 870amd64:CYGWIN*:*:* | x86_6
On 10/17/2017 7:49 PM, Brian Inglis wrote:
> On 2017-10-17 13:16, cyg Simple wrote:
>> The config.guess file[1] is confused.
>>
>> 840i*:CYGWIN*:*)
>> 841 echo ${UNAME_MACHINE}-pc-cygwin
>> 842 exit ;;
>> -
>> 870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
>> 871 echo x86_64-unknown-cygw
On 10/17/2017 7:39 PM, Brian Inglis wrote:
> On 2017-10-17 15:31, cyg Simple wrote:
>> On 10/17/2017 3:45 PM, Brian Inglis wrote:
>>> On 2017-10-17 13:16, cyg Simple wrote:
The config.guess file[1] is confused.
840i*:CYGWIN*:*)
841echo ${UNAME_MACHINE}-pc-cygwin
84
On 2017-10-17 13:16, cyg Simple wrote:
> The config.guess file[1] is confused.
>
> 840i*:CYGWIN*:*)
> 841 echo ${UNAME_MACHINE}-pc-cygwin
> 842 exit ;;
> -
> 870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
> 871 echo x86_64-unknown-cygwin
> 872 exit ;;
>
> The GCC executable is x86
On 2017-10-17 15:31, cyg Simple wrote:
> On 10/17/2017 3:45 PM, Brian Inglis wrote:
>> On 2017-10-17 13:16, cyg Simple wrote:
>>> The config.guess file[1] is confused.
>>> 840i*:CYGWIN*:*)
>>> 841 echo ${UNAME_MACHINE}-pc-cygwin
>>> 842 exit ;;
>>> -
>>> 870amd64:CYGWIN*:*:* | x86_64:CY
On 10/17/2017 3:45 PM, Brian Inglis wrote:
> On 2017-10-17 13:16, cyg Simple wrote:
>> The config.guess file[1] is confused.
>>
>> 840i*:CYGWIN*:*)
>> 841 echo ${UNAME_MACHINE}-pc-cygwin
>> 842 exit ;;
>> -
>> 870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
>> 871 echo x86_64-unknown-cygw
On 2017-10-17 13:16, cyg Simple wrote:
> The config.guess file[1] is confused.
>
> 840i*:CYGWIN*:*)
> 841 echo ${UNAME_MACHINE}-pc-cygwin
> 842 exit ;;
> -
> 870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
> 871 echo x86_64-unknown-cygwin
> 872 exit ;;
>
> The GCC executable is x86
The config.guess file[1] is confused.
840i*:CYGWIN*:*)
841 echo ${UNAME_MACHINE}-pc-cygwin
842 exit ;;
-
870amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
871 echo x86_64-unknown-cygwin
872 exit ;;
The GCC executable is x86_64-pc-cygwin-gcc.exe but config.guess on my
system g
72 matches
Mail list logo