From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <38792ced13d4ed51db1573cf42bb7249@brasstown.quanstro.net> <91e3601b39c9e4cb04e86c26f171e94d@brasstown.quanstro.net> Date: Sun, 18 Jan 2015 22:40:54 -0700 Message-ID: From: Don Bailey To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113dfb780d09a4050cfac49f Subject: Re: [9fans] runebase breaking libs build Topicbox-Message-UUID: 3a2ec54a-ead9-11e9-9d60-3106f5b1d025 --001a113dfb780d09a4050cfac49f Content-Type: text/plain; charset=UTF-8 This will be the last email I send regarding this issue as I have no interest in getting into a long drawn-out 9fans-style discussion. I upgraded via pull, then `{cd /sys/src/; mk objtype='amd64' install}; which broke at libc. If the issue is the compilers not being built first, maybe it could be documented on the wiki that they need to be built first, otherwise odd errors would occur during a world-build. Thanks. On Sun, Jan 18, 2015 at 10:16 PM, erik quanstrom wrote: > 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 > 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 > > --001a113dfb780d09a4050cfac49f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This will be the last email I send regarding this issue as= I have no interest in getting into a long drawn-out 9fans-style discussion= .=C2=A0

I upgraded via pull, then `{cd /sys/src/; mk obj= type=3D'amd64' install}; which broke at libc. If the issue is the c= ompilers not being built first, maybe it could be documented on the wiki th= at they need to be built first, otherwise odd errors would occur during a w= orld-build.=C2=A0

Thanks.=C2=A0

On Sun, Jan 18, 2015 at = 10:16 PM, erik quanstrom <quanstro@quanstro.net> wrote:<= br>
O= n 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.=C2=A0 pull from sources doesn't compile= anything.=C2=A0 did you update by hand?
if so, why would hand-update be well-documented.=C2=A0 by definition, one w= ould think that
it couldn't be.=C2=A0 (since every hand update is different.)

- erik


--001a113dfb780d09a4050cfac49f--