Re: Which is it -pc- or -unknown-

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 >>>

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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.

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: No error messages printed out within Windows Command Prompt when shared libraries are not found

Sorry, I have just realized that the issue happens only when I use the "Windows Command Prompt" run by Total Commander (www.ghisler.com), while I correctly get the notification when using the "Windows Command Prompt" run from the Start Menu. This issue is actually related to Total Commander,

Re: [PATCH] Revert "Don't override a Keep selection"

On 10/19/2017 11:05 AM, Ken Brown wrote: On 10/18/2017 11:01 PM, Ken Brown wrote: On 10/17/2017 3:31 PM, Ken Brown wrote: On 10/17/2017 2:43 PM, Jon Turney wrote: On 16/10/2017 20:13, Ken Brown wrote: This reverts (the rest of) commit b43b697.  Part of that commit was already reverted in

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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.

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

> 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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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.

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

> 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

Re: Which is it -pc- or -unknown-

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

Problem with Fossil version

I've been using fossil as my SCM system of choice for some years now, and have been in the habit of synching my repositories under Cygwin with those on a remote Unix (FreeBSD) system. Recently, though, I created a new repository under FreeBSD and found I cannot clone it to Cygwin. Apparently,

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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. 

Re: Which is it -pc- or -unknown-

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

Re: [Attn. Maintainers] Perl 5.26.1 (release is imminent)

Yaakov Selkowitz writes: >> git-svn: Subversion compatibility support for Git version control >> system >> git: Distributed version control system > > Adam, git will break if it doesn't get rebuilt and uploaded together > with the 5.26 upgrade. How soon can you rebuild it

Re: [setup topic/libsolv] Packages contained in multiple repositories

Jon Turney writes: >> Extrapolating from my experience with zypper, libsolv should stick with >> the repo the installed package comes from even if some other repo has a >> newer version. > > Unfortunately, we are limited by the fact that installed.db doesn't > record which repo an installed

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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.

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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

Re: [PATCH] Revert "Don't override a Keep selection"

On 10/18/2017 11:01 PM, Ken Brown wrote: On 10/17/2017 3:31 PM, Ken Brown wrote: On 10/17/2017 2:43 PM, Jon Turney wrote: On 16/10/2017 20:13, Ken Brown wrote: This reverts (the rest of) commit b43b697.  Part of that commit was already reverted in commit ff0bb3d.  The rest is not needed

Re: Which is it -pc- or -unknown-

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 >>> >>>

Re: [Attn. Maintainers] Perl 5.26.1 (release is imminent)

On 2017-10-18 13:20, Achim Gratz wrote: > I've just uploaded the files for the update of Perl to version 5.26 to > sourceware. Unfortunatley only a single other package has been staged > there (znc), so we need to wait for the rest of the maintainers to do > their uploads. My uploads are queued

Re: Which is it -pc- or -unknown-

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

Re: Which is it -pc- or -unknown-

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.

Re: Which is it -pc- or -unknown-

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.

Re: [setup topic/libsolv] Packages contained in multiple repositories

On 18/10/2017 17:41, Achim Gratz wrote: Ken Brown writes: In retrospect, I'm not sure this patch is right, but I'm sending it anyway for the sake of discussion. My hesitation comes from the fact that libsolv might have a good reason for preferring the one it chose, e.g., if we've assigned

Re: git can not access remote repository anymore after cygwin+git update

On Thu, Oct 19, 2017, at 14:28, Marco Atzeri wrote: > On 19/10/2017 13:38, Ronald Fischer wrote: > > I'm using 64 Bit Cygwin on Windows 7. After upgrading Git to version > > 2.14.2 (I think I had 2.13 or 2.12 before), git can not access our > > repository anymore. Commands such as "git pull" or

Re: Which is it -pc- or -unknown-

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 >>

Re: Which is it -pc- or -unknown-

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*:*

Re: Which is it -pc- or -unknown-

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

[PATCH setup] Add bitness to user-agent string

We have no idea about the proportion of 32-bit and 64-bit Cygwin installs. Add a 'Win32', 'WoW64' or 'Win64' token to the user-agent string to report bitness. Future work: it might be useful to report the OS version as well Signed-off-by: Jon Turney --- nio-ie5.cc

Re: git can not access remote repository anymore after cygwin+git update

On 19/10/2017 13:38, Ronald Fischer wrote: I'm using 64 Bit Cygwin on Windows 7. After upgrading Git to version 2.14.2 (I think I had 2.13 or 2.12 before), git can not access our repository anymore. Commands such as "git pull" or "git push" result into the error fatal: Could not read from

[PATCH setup 0/2] Fix gcc 6 warnings

Jon Turney (2): Fix -Werror=unused-const-variable error seen with gcc 6 Fix -Werror=misleading-indentation errors seen with gcc 6 libgetopt++/src/OptionSet.cc | 6 -- sha2.c | 2 ++ 2 files changed, 6 insertions(+), 2 deletions(-) -- 2.14.2

[PATCH setup 1/2] Fix -Werror=unused-const-variable error seen with gcc 6

sha2.c:199:24: error: 'sha224_initial_hash_value' defined but not used [-Werror=unused-const-variable=] --- sha2.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sha2.c b/sha2.c index 4842e42..67251bc 100644 --- a/sha2.c +++ b/sha2.c @@ -195,6 +195,7 @@ static const u_int32_t K256[64] = {

[PATCH setup 2/2] Fix -Werror=misleading-indentation errors seen with gcc 6

This looks like an actual bug which has been lurking here since forever, fortunately not exposed since hardly anything uses Option::Optional... libgetopt++/src/OptionSet.cc: In member function 'void OptionSet::doOption(std::__cxx11::string&, const size_type&)':

git can not access remote repository anymore after cygwin+git update

I'm using 64 Bit Cygwin on Windows 7. After upgrading Git to version 2.14.2 (I think I had 2.13 or 2.12 before), git can not access our repository anymore. Commands such as "git pull" or "git push" result into the error fatal: Could not read from remote repository. Please make sure you have the

Re: [Attn. Maintainers] Perl 5.26.1 (release is imminent)

On 18/10/2017 20:20, Achim Gratz wrote: Please upload your packages to sourceware _without_ the !ready cookies (i.e. don't use cygport upload) and instead place !perl cookies. This way the staged uploads can all be activated at the same time so that no inconsistent intermediate state gets