public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: The adventure of building Bedrock in Cygwin: any help would be appreciated
Date: Mon, 20 May 2019 20:23:00 -0000	[thread overview]
Message-ID: <e91027df-9388-543f-cf85-0f60c2459a75@t-online.de> (raw)
In-Reply-To: <DB7PR01MB5386A14A1CF3564C8AB1A2EBDE060@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>

Am 20.05.2019 um 21:12 schrieb Jose Isaias Cabrera:

> There is no configure script on the source directory, 

And that should have been a warning to you.

This is the most portability-ignorant open source package I've seen in a
long time, and by a very wide margin.  They don't even _try_ to
accomodate the notion that there might be anything else but Linux left
under the sun.

> so according to Bedrock [1] this is all I need to build it:

Well, in all fairness, those are just the instructions for one type of
Linux distribution.  There are others, but those would not get you any
further, because they just care about different extra libraries, whereas
the real problems are in how they configure the compiler and its
standard library.

Among the fallacies they evidently subscribe to is the one that one
should force-feed the '--std=c++14' flag into all compilations, to get
support for C++ 14 language features, without bothering about the
effects that will have on the standard library feature selection
process.  At the very least, they should have use '--std=gnu++14'
instead, to keep the libraries full-featured.  Or if they didn't, they
would have to add some feature activation options like '-D_GNU_SOURCE'
to get back what they so wilfully turned off.

In short, this whole source is doomed to fail utterly on any system
whose C standard library is not GLIBC.


--
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:[~2019-05-20 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 19:12 Jose Isaias Cabrera
2019-05-20 20:23 ` Hans-Bernhard Bröker [this message]
2019-05-21 12:51   ` Jose Isaias Cabrera

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=e91027df-9388-543f-cf85-0f60c2459a75@t-online.de \
    --to=hbbroeker@t-online.de \
    --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).