From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Oilshell
Date: Sat, 06 Jul 2019 23:00:56 +0200 [thread overview]
Message-ID: <20190706210056.QSEiKh9kPMjZmyD827EsyqgJfZGPWwSUdBQ8s9VOzWk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12835@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
New comment by Wychmire on void-packages repository
https://github.com/void-linux/void-packages/issues/12835#issuecomment-508953274
Comment:
I added
```
pre_build() {
rm -f ${XBPS_WRAPPERDIR}/strip
}
```
like found in the grub template and it gave me an error about /usr/local being forbidden like you mentioned, so I deleted that chunk and re-ran the build and it works. I installed the package with `sudo xbps-install --repository=hostdir/binpkgs oilshell` and that works too. The issue that caused me to symlink to /usr/local in the first place isn't occurring.
I tried to compile it to i686 with `./xbps-src -a i686 pkg oilshell` but readline-devel never gets installed, so it fails. If I remove `--with-readline` from the configure-args if fails with lots of
```
#error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
```
and then
```
objcopy --only-keep-debug _build/oil/ovm-opt _build/oil/ovm-opt.symbols
objcopy: '_build/oil/ovm-opt': No such file
make: *** [Makefile:150: _build/oil/ovm-opt.symbols] Error 1
=> ERROR: oilshell-0.6.0_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/configure.sh:14
```
So I don't think it supports i686. I attached the whole log regardless
If I add /usr/bin/osh to /etc/shells and chsh to it, I can't log into tty2, though all other ttys work. I can log into it with root, or if I chsh back to /bin/bash
[i686.log](https://github.com/void-linux/void-packages/files/3365023/i686.log)
next prev parent reply other threads:[~2019-07-06 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 13:53 [ISSUE] " voidlinux-github
2019-07-06 14:16 ` voidlinux-github
2019-07-06 14:17 ` voidlinux-github
2019-07-06 15:25 ` voidlinux-github
2019-07-06 16:15 ` voidlinux-github
2019-07-06 16:22 ` voidlinux-github
2019-07-06 20:59 ` voidlinux-github
2019-07-06 21:00 ` voidlinux-github
2019-07-06 21:00 ` voidlinux-github [this message]
2019-07-07 20:10 ` voidlinux-github
2019-07-09 14:31 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190706210056.QSEiKh9kPMjZmyD827EsyqgJfZGPWwSUdBQ8s9VOzWk@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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).