> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release.
I tried this, and compilation becomes seamless.
However, a new test error occured as:
=
? cmd/nm [no test files]
pack.test 1119: suicide: sys: tr
On Wed Apr 2 01:20:42 EDT 2014, 0in...@gmail.com wrote:
> Two days ago, I've fixed the script mklibc.rc to
> generate the libc_plan9.h file properly on 9atom.
>
> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release
> As I cannot force plan 9 to use my sata disk, I've decided to buy a sata to
> usb convertor.
> After compiling the usb tools on 9atom, I can find my disk under /dev/sdU1.0
> and now is the time to
> prepare the disk partitions in order to install plan 9. Disk which I want to
> use isn't empty
> if you do a pull as glenda, or alternately
>
> mount /srv/boot /n/root &&
> 9fs atom &&
> disk/mkfs -vkU -s /n/atom/plan9^`{pwd} -d . <{echo +}
>
> you can then try "mkusbboot -p `{echo +}". this may actually work.
srv: dial tcp!atom.9atom.org!fs:
On Wed Apr 2 17:49:51 EDT 2014, szymon.olewnic...@rid.pl wrote:
> > if you do a pull as glenda, or alternately
> >
> > mount /srv/boot /n/root &&
> > 9fs atom &&
> > disk/mkfs -vkU -s /n/atom/plan9^`{pwd} -d . <{echo +}
> >
> > you can then try "mkusbboot -p `{echo +
small but potentially deadly
diff -c /n/dump/2014/0402/sys/src/cmd/fossil/9fsys.c 9fsys.c
/n/dump/2014/0402/sys/src/cmd/fossil/9fsys.c:34,40 - 9fsys.c:34,40
char* curfsys;
} sbox;
- static char *_argv0;
+ char *_argv0;
#define argv0 _argv0
static char FsysAll[] = "all";
i should explain further, since this is sneaky. since we're calling
ARGBEGIN lots of times, we hit a special case. the defn is
#define ARGBEGINfor((argv0||(argv0=*argv)),argv++,argc--;\
a subsequent call to ARGBEGIN will not reset argv0, and worse, argv0
can be pointing to bogus memory.
>> https://codereview.appspot.com/82660044/
>>
>> Please give a try and review this change to
>> get it submitted before the Go 1.4 release.
Sorry, David.
I made mistake to copy your patch file to Plan9
system (I've not set abaco yet).
I retried your above patch, and perfectly seamless results
w
> the script itself reminds me of gcc fixincludes.
This is probably not ideal, but the alternative would be
to split libc.h in three parts: libc.h, fmt.h and utf.h
and only include libc.h in Go (because Go has his own
variants of libfmt and libutf).
--
David du Colombier
On Thu Apr 3 01:51:59 EDT 2014, 0in...@gmail.com wrote:
> > the script itself reminds me of gcc fixincludes.
>
> This is probably not ideal, but the alternative would be
> to split libc.h in three parts: libc.h, fmt.h and utf.h
> and only include libc.h in Go (because Go has his own
> variants of
> Sorry, David.
> I made mistake to copy your patch file to Plan9
> system (I've not set abaco yet).
>
> I retried your above patch, and perfectly seamless results
> which are included here.
I don't think the error you encountered was related to
the patch, since it's only related to a compilation
> > ? cmd/nm [no test files]
> > pack.test 1119: suicide: sys: trap: fault read addr=0xeafc
> > pc=0x254b6 *** Test killed: ran too long (3m0s).
> > FAILcmd/pack180.007s
> > ? cmd/yacc[no test files]
>
> It was probably a real error. However, other
On Apr 3, 2014, at 12:58 AM, erik quanstrom wrote:
>
> On Thu Apr 3 01:51:59 EDT 2014, 0in...@gmail.com wrote:
>>> the script itself reminds me of gcc fixincludes.
>>
>> This is probably not ideal, but the alternative would be
>> to split libc.h in three parts: libc.h, fmt.h and utf.h
>> and on
> why is the alternative to modify plan 9, and why can't they
> live with the system fmt/rune routines?
They are incompatible. For example, some Fmt verbs (like %F) does produce
slightly different output. It was an explicit requirement from the Go team
to use their variants of these libraries.
--
> They are incompatible. For example, some Fmt verbs (like %F) does produce
> slightly different output. It was an explicit requirement from the Go team
> to use their variants of these libraries.
do you see why i think that relationship is upside down?
- erik
15 matches
Mail list logo
