From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Which is it -pc- or -unknown-
Date: Thu, 19 Oct 2017 14:46:00 -0000 [thread overview]
Message-ID: <d45e7499-fc92-f1a8-5de4-2b43b803e437@gmail.com> (raw)
In-Reply-To: <5e3588d9-d0a6-4181-54aa-56afa5082eab@gmail.com>
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-cygwin
>>> /usr/lib/octave/site/oct/x86_64-unknown-cygwin
>>
>> This is certainly not right. I can understand that we will have some
>> discrepancies across packages, but having a different vendor in the same
>> package
>> is unacceptable. It suggests that x86_64-unknown-cygwin and i686-pc-cygwin
>> differ in more ways that one, which they dont. you let it slide, then
>> people
>> start asking:
>>
>
> I can live with the historical i*-pc-cygwin mishap.
>
>> - where is x86_64-pc-cygwin?
>
> This I cannot live with and the package maintainers need to target
> x86_64-unknown-cygwin instead. GCC has a target build of
> x86_64-pc-cygwin, it needs corrected!
It seems all cygwin package maintainers have no problem.
So are you causing yourself a not-existing problem ?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-10-19 14:46 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 19:16 cyg Simple
2017-10-17 19:46 ` Brian Inglis
2017-10-17 21:31 ` cyg Simple
2017-10-17 23:39 ` Brian Inglis
2017-10-18 3:25 ` cyg Simple
2017-10-17 23:49 ` Brian Inglis
2017-10-18 3:29 ` cyg Simple
2017-10-18 5:26 ` Brian Inglis
2017-10-18 6:45 ` Marco Atzeri
2017-10-18 13:47 ` Brian Inglis
2017-10-18 23:27 ` Steven Penny
2017-10-19 1:16 ` Yaakov Selkowitz
2017-10-19 13:25 ` cyg Simple
2017-10-19 14:46 ` Marco Atzeri [this message]
2017-10-19 15:04 ` Yaakov Selkowitz
2017-10-19 16:44 ` cyg Simple
2017-10-19 18:51 ` Yaakov Selkowitz
2017-10-19 19:08 ` cyg Simple
2017-10-19 20:02 ` Vince Rice
2017-10-19 20:21 ` cyg Simple
2017-10-19 20:33 ` Yaakov Selkowitz
2017-10-20 13:28 ` cyg Simple
2017-10-20 15:24 ` Yaakov Selkowitz
2017-10-20 15:44 ` cyg Simple
2017-10-20 15:54 ` Yaakov Selkowitz
2017-10-20 16:11 ` cyg Simple
2017-10-20 17:24 ` cyg Simple
2017-10-20 18:35 ` Eric Blake
2017-10-20 19:29 ` cyg Simple
2017-10-20 17:41 ` Marco Atzeri
2017-10-20 18:44 ` Brian Inglis
2017-10-20 19:44 ` cyg Simple
2017-10-20 19:53 ` cyg Simple
2017-10-20 20:29 ` Yaakov Selkowitz
2017-10-20 22:47 ` Steven Penny
2017-10-21 17:29 ` cyg Simple
2017-10-21 19:26 ` Steven Penny
2017-10-21 20:17 ` cyg Simple
2017-10-21 23:58 ` Steven Penny
2017-10-19 20:34 ` Vince Rice
2017-10-19 20:21 ` Yaakov Selkowitz
2017-10-19 20:26 ` cyg Simple
2017-10-19 20:49 ` Yaakov Selkowitz
2017-10-18 14:05 ` cyg Simple
2017-10-18 17:11 ` Yaakov Selkowitz
2017-10-18 19:10 ` cyg Simple
2017-10-18 19:28 ` Brian Inglis
2017-10-18 22:41 ` Yaakov Selkowitz
2017-10-18 23:00 ` JonY
2017-10-19 13:20 ` cyg Simple
2017-10-19 14:18 ` Ken Brown
2017-10-19 16:18 ` cyg Simple
2017-10-19 22:38 ` JonY
2017-10-19 13:17 ` cyg Simple
2017-10-19 14:42 ` Marco Atzeri
2017-10-19 16:21 ` cyg Simple
2017-10-19 16:42 ` Marco Atzeri
2017-10-19 16:47 ` cyg Simple
2017-10-19 18:37 ` Steven Penny
2017-10-19 18:40 ` cyg Simple
2017-10-19 18:59 ` Yaakov Selkowitz
2017-10-19 19:04 ` cyg Simple
2017-10-19 19:54 ` Brian Inglis
2017-10-19 20:02 ` cyg Simple
2017-10-19 20:35 ` Yaakov Selkowitz
2017-10-19 21:00 ` cyg Simple
2017-10-19 21:14 ` Yaakov Selkowitz
2017-10-19 23:21 ` Brian Inglis
2017-10-19 23:47 ` Yaakov Selkowitz
2017-10-19 23:49 ` Steven Penny
2017-10-20 1:11 ` Yaakov Selkowitz
2017-10-20 3:19 ` Brian Inglis
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=d45e7499-fc92-f1a8-5de4-2b43b803e437@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.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).