public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.11
Date: Tue, 05 Apr 2016 17:07:00 -0000	[thread overview]
Message-ID: <5703F0B5.8020500@maxrnd.com> (raw)
In-Reply-To: <20160405095714.GA2879@calimero.vinschen.de>

Corinna Vinschen wrote:
> On Apr  5 00:18, Mark Geisert wrote:
>> Mark Geisert wrote:
>>> Yaakov Selkowitz wrote:
>>>> On 2016-04-05 00:54, Mark Geisert wrote:
>>>>> When building in winsup/utils, I hit this:
>>>> [snip]
>>>>> I found that the generated winsup/utils/Makefile has
>>>>> MINGW_CXX      := i686-w64-mingw32-g++
>>>>> even though I am building on 64-bit.
>>>>
>>>> I can't reproduce this with git master.  Are you sure you have both a clean
>>>> clone and a clean build directory?
>>>
>>> I'm obtaining the source via setup-x86_64.exe, not git clone.  Then going to the
>>> download directory under /usr/src and doing 'cygport cygwin.cygport prep'.  Then
>>> setting up /oss tree like the FAQ suggests, with /oss/src symlinked to the right
>>> level of the download tree.  cd to /oss/build, configure and make like the FAQ
>>> demonstrates.
>>>
>>> I'll try it with a git clone and report back.
>>
>> I'm getting the same error.  FYI this is with /oss tree per the FAQ with
>> /oss/src symlinked to root of the cloned tree, then building in /oss/build.
>>
>> Do you have both i686-w64-mingw32-g++ and x86_64-w64-mingw32-g++ installed?
>
> I can't reproduce this either.  I built in two variations, with
> i686-w64-mingw32-g++ installed and not installed, and in both cases
> MINGW_CXX was set to x86_64-w64-mingw32-g++
>
> I built manually from git master in a parallel build dir using this
> simple script:
>
> #!/bin/sh
> SRCDIR=../cygwin-newlib
> PREFIX=/usr
> SYSCONFDIR=/etc
> ${SRCDIR}/configure \
>          --prefix=${PREFIX} \
>          --sysconfdir=${SYSCONFDIR} \
>          $@
>
> Care to inspect the config logs to see what happened?

Oh, flock.  As Yaakov suspected, an issue in my build environment.  Stale 
environment vars from the initial 64-bit Cygwin port days, that I had forgotten 
about.  Removed those from my .bashrc and the whole build runs from start to 
completion now.
Sheepishly,

..mark


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

  reply	other threads:[~2016-04-05 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 21:31 Yaakov Selkowitz
2016-04-05  5:54 ` Mark Geisert
2016-04-05  6:24   ` Yaakov Selkowitz
2016-04-05  6:42     ` Mark Geisert
2016-04-05  7:18       ` Mark Geisert
2016-04-05  9:57         ` Corinna Vinschen
2016-04-05 17:07           ` Mark Geisert [this message]
2016-04-05  7:51 ` Ismail Donmez
2016-04-05  8:32   ` Corinna Vinschen
2016-04-05  8:07 ` Thorsten Kampe

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=5703F0B5.8020500@maxrnd.com \
    --to=mark@maxrnd.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).