From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cross build of newlib-cygwin release tag cygwin-2_11_1-release.
Date: Tue, 30 Oct 2018 21:25:00 -0000 [thread overview]
Message-ID: <dfed87f1-5acf-cc44-60d8-0cb7851a71fd@gmail.com> (raw)
In-Reply-To: <20181030203204.GB3310@calimero.vinschen.de>
On 10/30/2018 4:32 PM, Corinna Vinschen wrote:
> On Oct 30 16:01, Earnest Boyd wrote:
>> On 10/30/2018 3:31 PM, cyg Simple wrote:
>>> On 10/30/2018 11:03 AM, cyg Simple wrote:
>>>> PING... Does no one have an idea?
>>>>
>>>> On 10/29/2018 12:09 PM, cyg Simple wrote:
>>>>> I'm trying to cross build the Cygwin source on a VirtualBox Arch Linux
>>>>> with GCC-7.3.0 and Binutils 2.31. The process I am using clones the
>>>>> master repository and then does a checkout of the release tag. Here is
>>>>> the configure command from the head of the config.log.
>>>>>
>>>>> ```
>>>>> $ head /home/cygsimple/src/sf/build/newlib-cygwin/build/config.log |
>>>>> grep newlib-cygwin-2.11.1/configure
>>>>> $
>>>>> /home/cygsimple/src/sf/build/newlib-cygwin/src/newlib-cygwin-2.11.1/configure
>>>>> --prefix=/usr --host=x86_64-pc-cygwin --build=x86_64-pc-linux-gnu
>>>>> --target=x86_64-pc-cygwin --sysconfdir=/etc --sharedstatedir=/var
>>>>> --localstatedir=/var
>>>>> ```
>>>>>
>>>
>>> I tried this on the master Cygwin and get the same error.
>>>
>>> ```
>>> $ head config.log | grep newlib-cygwin
>>> $
>>> /usr/local/src/cygsimple/sf/build/newlib-cygwin/src/newlib-cygwin-2.11.1/configure
>>> --prefix=/usr --host=x86_64-pc-cygwin --build=x86_64-pc-cygwin
>>> --target=x86_64-pc-cygwin --sysconfdir=/etc --sharedstatedir=/var
>>> --localstatedir=/var
>>> ```
>>>
>>> What configuration item should I add to avoid this?
>>>
>>
>> Patching winsup/cygwin/Makefile.in to remove -Werror allows this to
>> build though the warnings continue. But how does Corinna do this?
>
> No special settings. But this:
>
>>>>> c++wrap -pedantic -fomit-frame-pointer -m64 -O2 -g -fno-rtti
> ^^^^^^^^^ ^^^^
> Looks weird. We don't use neither pedantic nor m64 and from the above
> it seems you didn't specify them explicitely either. So where are they
> coming from? "pedantic" may explain the error. What linux-cygwin cross
> gcc are you using? Looks like you're not using the right one.
It's specified in winsup/cygwin/Makefile.in
The cross is my private build but that doesn't matter, the issue happens
in a native build as well.
--
cyg Simple
--
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:[~2018-10-30 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:09 cyg Simple
2018-10-30 15:03 ` cyg Simple
2018-10-30 19:31 ` cyg Simple
2018-10-30 20:02 ` Earnest Boyd
2018-10-30 20:32 ` Corinna Vinschen
2018-10-30 21:25 ` cyg Simple [this message]
2018-10-30 21:29 ` cyg Simple
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=dfed87f1-5acf-cc44-60d8-0cb7851a71fd@gmail.com \
--to=cygsimple@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).