9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: bug: ape/psh is broken
Date: Wed, 12 Sep 2018 09:28:15 -0700	[thread overview]
Message-ID: <CAH_zEu62q60JjNx7fuBLW0_DJOwwsu0beMJJ==Veqyj7BE9nLw@mail.gmail.com> (raw)
In-Reply-To: <CAH_zEu7j50-YbwQ+3cA2X6txzXx+Fo_FOt53=s4Qt5SwNDb3dA@mail.gmail.com>

correction: the subject of this mail should be "ape pax is broken".

apologies for any confusion.
On Wed, Sep 12, 2018 at 9:21 AM Nick Owens <mischief@offblast.org> wrote:
>
> see below.
>
> cpu% pwd
> /sys/src/ape/cmd/pax
> cpu% ape/psh
> $ make
> cc -O  -c pax.c
> /sys/src/ape/cmd/pax/./pax.h:268[stdin:1872] name not declared: PATH_MAX
> /sys/src/ape/cmd/pax/./pax.h:268[stdin:1872] array size must be a
> positive constant
> cc: cpp: 6c 2661303: error
> *** Error code 1
>
> Stop.
> $  cpu% mk
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 pax.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 append.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 buffer.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 cpio.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 create.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 extract.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 fileio.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 link.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 list.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 mem.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 namelist.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 names.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 pass.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 pathname.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 port.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 regexp.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 replace.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 tar.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 ttyio.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 warn.c
> pcc -c -D_POSIX_SOURCE -B -DPATH_MAX=1024 wildmat.c
> pcc  -o 6.out pax.6 append.6 buffer.6 cpio.6 create.6 extract.6
> fileio.6 link.6 list.6 mem.6 namelist.6 names.6 pass.6 pathname.6
> port.6 regexp.6 replace.6 tar.6 ttyio.6 warn.6 wildmat.6 -lv
> name_next: undefined: seekdir in name_next
> name_next: undefined: telldir in name_next
> pcc: 6l: 6l 2661619: error
> mk: pcc  -o ...  : exit status=rc 2661616: pcc 2661618: 6l: 6l 2661619: error


      reply	other threads:[~2018-09-12 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 16:21 Nick Owens
2018-09-12 16:28 ` Nick Owens [this message]

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='CAH_zEu62q60JjNx7fuBLW0_DJOwwsu0beMJJ==Veqyj7BE9nLw@mail.gmail.com' \
    --to=mischief@offblast.org \
    --cc=9front@9front.org \
    /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).