From: Jose Isaias Cabrera <jicman@outlook.com>
To: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: The adventure of building Bedrock in Cygwin: any help would be appreciated
Date: Tue, 21 May 2019 12:51:00 -0000 [thread overview]
Message-ID: <DB7PR01MB538677C509A8017E18156A28DE070@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <e91027df-9388-543f-cf85-0f60c2459a75@t-online.de>
Hans-Bernhard Bröker, on Monday, May 20, 2019 04:23 PM, wrote...
>Am 20.05.2019 um 21:12 schrieb Jose Isaias Cabrera:
>
>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.
You said it, but I agreed. :-)
>> 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
True, but I thought it would be the closest "linux flavor" in comparison to Cygwin. There is a set of Mac build steps. I started with that. First built brew in cygwin, but then when tried to do 'brew install gcc@6' got a bunch of errors and I just thought that building gcc6 from scratch without brew would be the best way to go, but it wasn't.
>In short, this whole source is doomed to fail utterly on any system
>whose C standard library is not GLIBC.
Reminiscing way back in the days... Marlon Brando, "You don't understand! I coulda had class. I coulda been a contender. I coulda been somebody instead of a bum, which is what I am."
--
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
prev parent reply other threads:[~2019-05-21 12:51 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
2019-05-21 12:51 ` Jose Isaias Cabrera [this message]
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=DB7PR01MB538677C509A8017E18156A28DE070@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=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).