> Whenever my mind wonders off thinking about revision control in Plan
> 9, my first thought is how useful "proto" would be as a building block
> for that and other applications. Yet it very seldom gets any mention,
> I really don't think it ought to be forgotten.
proto is how i build 9atom, so i
> mkdir -p ape auth aux bitsy dial disk fossil fs games ip ip/httpd ndb rune
> opc replica upas venti usb
Shouldn't this be in a "proto" file?
bin
ape
auth
aux
bitsy
dial
disk
fossil
fs
games
ip
httpd
On Tue Jan 20 04:10:48 PST 2015, st...@quintile.net wrote:
> there are a few subdirectories that need to be created when you build the
> amd64 code for the first time. maybe it would be nice to have a
> /sys/lib/newobjtype script to help, but if you just:
>
> cd /sys/src
> objtype=amd64 mk inst
there are a few subdirectories that need to be created when you build the amd64
code for the first time. maybe it would be nice to have a /sys/lib/newobjtype
script to help, but if you just:
cd /sys/src
objtype=amd64 mk install
and create the directories as needed you should be ok
-Steve
>
> Yes, some parts of the amd64 user space are missing in
> the Bell Labs distribution. You have you apply these patches:
>
> hget http://9legacy.org/9legacy/patch/amd64.diff | ape/patch -p0
> hget http://9legacy.org/9legacy/patch/amd64-fix.diff | ape/patch -p0
>
> Also, you have to create the sub
> I followed this one and it solves the runebase problem, but libc build still
> fails as there is no amd64 subdir in libc. Looks like the labs version does
> not have amd64 code for libc. Is that correct? And is libc the only missing
> part?
Yes, some parts of the amd64 user space are missing in
Hi 9fans,
I also attempted to build amd64 version some time ago, and it failed in
libc. I gave up then, but since someone brought this up, let me ask my
question here.
Bell Labs doesn't distribute amd64 binaries. It seems
> you are running a compiler built before the long rune
> change (before Ma
> 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.
Bell Labs doesn
On Sun Jan 18 21:36:26 PST 2015, don.bai...@gmail.com wrote:
> 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.
On Sun, 18 Jan 2015 22:09:02 MST Don Bailey wrote:
> So this issue is clearly documented somewhere that people can catch up
> quickly?
>From an old message by David du Colombier:
1. remove runebase from /sys/src/libc/port/mkfile
2. cd /sys/src/libc && mk install && mk clean
3. for(i in /sys/src
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
On Sun Jan 18 21:05:02 PST 2015, don.bai...@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.bai...@gmail.com wrote:
> >> The build sc
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.bai...@gmail.com wrote:
>> The build scripts should probably address this so people that haven't
>> updated in a while
On Sun Jan 18 20:10:38 PST 2015, don.bai...@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.
- erik
The build scripts should probably address this so people that haven't updated
in a while aren't spinning wheels.
Thanks.
> On Jan 18, 2015, at 9:01 PM, erik quanstrom wrote:
>
>> On Sun Jan 18 15:19:46 PST 2015, don.bai...@gmail.com wrote:
>>
>> Hi All,
>>
>> Looks like a change in libc/p
On Sun Jan 18 15:19:46 PST 2015, don.bai...@gmail.com wrote:
> Hi All,
>
> Looks like a change in libc/port/runebase.c is breaking builds. Does anyone
> have a quick fix? Looks like the issue isn't specific to a particular
> compiler, but illegal runes in the runebase.c file.
>
> runebase.c:1255
Hi All,
Looks like a change in libc/port/runebase.c is breaking builds. Does anyone
have a quick fix? Looks like the issue isn't specific to a particular
compiler, but illegal runes in the runebase.c file.
runebase.c:1255 illegal rune in string
...
Thanks,
D
17 matches
Mail list logo
