From: jimerickso@gmail.com
To: 9front@9front.org
Subject: [9front] build errors when building treason
Date: Wed, 08 Feb 2023 12:07:37 -0600 [thread overview]
Message-ID: <CA562C350774203C3951794E76F310A8@gmail.com> (raw)
i am attempting to build treason but i get several errors. they are as follows:
/fd/0:1: /sys/src/cmd/audio/libogg/libogg.a6: '/sys/src/cmd/audio/libogg/libogg.a6' access permission denied
pcc -o 6.opusdec opusdec.6 wav_io.6 wave_out.6 diag_range.6 opus_header.6 resample.6 getopt.6 getopt1.6 /amd64/lib/ape/libopusfile.a /amd64/lib/ape/libopusenc.a /amd64/lib/ape/libopus.a /sys/src/cmd/audio/libogg/libogg.a6
cp 6.opusdec /amd64/bin/audio/opusdec
/fd/0:1: /sys/src/cmd/audio/libogg/libogg.a6: '/sys/src/cmd/audio/libogg/libogg.a6' access permission denied
pcc -o 6.opusenc opusenc.6 audio-in.6 diag_range.6 flac.6 picture.6 opus_header.6 resample.6 getopt.6 getopt1.6 /amd64/lib/ape/libopusfile.a /amd64/lib/ape/libopusenc.a /amd64/lib/ape/libopus.a /sys/src/cmd/audio/libogg/libogg.a6
cp 6.opusenc /amd64/bin/audio/opusenc
/fd/0:1: /sys/src/cmd/audio/libogg/libogg.a6: '/sys/src/cmd/audio/libogg/libogg.a6' access permission denied
pcc -o 6.opusinfo opusinfo.6 info_opus.6 picture.6 tagcompare.6 opus_header.6 resample.6 getopt.6 getopt1.6 /amd64/lib/ape/libopusfile.a /amd64/lib/ape/libopusenc.a /amd64/lib/ape/libopus.a /sys/src/cmd/audio/libogg/libogg.a6
cp 6.opusinfo /amd64/bin/audio/opusinfo
committing treason
6c -FTVw -D__plan9__ -p -D__amd64__ -I../dav1d/include/dav1d -I../dav1d/src/plan9 -I../libvpx/vpx -I../openh264/codec -I../openh264/codec/api/svc -I../openh264/codec/common/inc -I../openh264/codec/decoder/core/inc decoder_vpx.c
cpp: decoder_vpx.c:1 Could not find include file <vpx_codec.h>
mk: 6c -FTVw -D__plan9__ ... : exit status=rc 670323: 6c 670325: error
can anyone help out with this? i have been playing around with it for a while now and all the dependencies build except opus-tools, which is the permission denied error. is there a tutorial i am over looking? i have googled for quite some time now and come up with nothing. thank you for your time.
next reply other threads:[~2023-02-08 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:07 jimerickso [this message]
2023-02-08 18:19 ` Sigrid Solveig Haflínudóttir
2023-02-08 18:20 ` Sigrid Solveig Haflínudóttir
2023-02-08 18:42 ` jimerickso
2023-02-08 19:07 ` Sigrid Solveig Haflínudóttir
2023-02-08 19:28 ` jimerickso
2023-02-08 19:33 ` Sigrid Solveig Haflínudóttir
2023-02-09 15:36 ` mkf9
2023-02-09 14:14 ` Jim Erickson
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=CA562C350774203C3951794E76F310A8@gmail.com \
--to=jimerickso@gmail.com \
--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).