From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] runebase breaking libs build
Date: Sun, 18 Jan 2015 21:16:36 -0800 [thread overview]
Message-ID: <c0aa72baaa6456a5b5585ef7a5545141@brasstown.quanstro.net> (raw)
In-Reply-To: <B0016A05-E6CF-423A-8BFD-97762CC3FB2B@gmail.com>
On Sun Jan 18 21:05:02 PST 2015, don.bailey@gmail.com wrote:
> So this issue is clearly documented somewhere that people can catch up quickly?
>
>
>
> > On Jan 18, 2015, at 9:14 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> >
> >> On Sun Jan 18 20:10:38 PST 2015, don.bailey@gmail.com wrote:
> >> The build scripts should probably address this so people that haven't updated in a while aren't spinning wheels.
> >
> > maybe, but libc was changed in 2013, so, even gentoo doesn't handle this case.
i don't follow. pull from sources doesn't compile anything. did you update by hand?
if so, why would hand-update be well-documented. by definition, one would think that
it couldn't be. (since every hand update is different.)
- erik
next prev parent reply other threads:[~2015-01-19 5:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 23:23 Don Bailey
2015-01-19 4:01 ` erik quanstrom
2015-01-19 4:14 ` Don Bailey
2015-01-19 4:14 ` erik quanstrom
2015-01-19 5:09 ` Don Bailey
2015-01-19 5:16 ` erik quanstrom [this message]
2015-01-19 5:40 ` Don Bailey
2015-01-19 5:47 ` erik quanstrom
2015-01-19 7:52 ` David du Colombier
2015-01-20 9:35 ` Zbigniew Radosz
2015-01-20 9:50 ` David du Colombier
2015-01-20 12:08 ` Zbigniew Radosz
2015-01-20 12:14 ` Quintile
2015-01-20 22:26 ` erik quanstrom
2015-01-21 4:10 ` lucio
2015-01-21 14:11 ` erik quanstrom
2015-01-19 5:50 ` Bakul Shah
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=c0aa72baaa6456a5b5585ef7a5545141@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).