From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Sorace <a@9srv.net>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Message-Id: <48AC91DA-BAA7-4419-BCDC-7E1D05D96065@9srv.net>
Date: Wed,  3 Dec 2014 07:51:11 -0500
References: <1417446698.1746961.197334701.394E4D52@webmail.messagingengine.com>
In-Reply-To: <1417446698.1746961.197334701.394E4D52@webmail.messagingengine.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] golang on 9atom
Topicbox-Message-UUID: 32ca60b6-ead9-11e9-9d60-3106f5b1d025

The error is what it says: the file name (rather than the full path) is too l=
ong for your file server. It sounds like you're running kfs, which is the ol=
dest and most restricted of our general purpose options. Long-term, I sugges=
t migrating, although if you're on a single-system setup and already have da=
ta you care about, that can be a pain. In the short-term, check out lnfs(4) t=
o get around this issue.


> On Dec 1, 2014, at 10:11, Ramakrishnan Muthukrishnan <ram@rkrishnan.org> w=
rote:
>=20
> I do not remember getting this error in the Labs version. But on 9atom
> with kfs, I get a build error while compiling golang 1.3.3 from the
> source:
>=20
> go tool dist: create
> /usr/ram/src/go/src/pkg/runtime/zruntime_defs_plan9_amd64.go:
> '/usr/ram/src/.... amd64.go' name too long
>=20
> I remember getting this error on 9atom before too, but had forgotten to
> report it.