Re: [gentoo-user] pcre build failure
On Mon, Oct 05, 2020 at 09:56:03PM -0400, Jude DaShiell wrote:
> When the failure happened on the computer I neglected to braille the
> commands that would have only produced a single copy of the text. In
> order to get the content from the second file, I needed to run the emerge
> update world command again then locate the command for the second file
> then cat that command. Braille paper is available here so I won't make
> that mistake again.
OK, don't worry. Although, try not to add any valuable information after a
signature-marker ("-- ") in an e-mail, as some mail clients will hide any
further text, and some (such as Mutt) may show it in a different colour, causing
confusion.
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
Re: [gentoo-user] pcre build failure
On Tue, 6 Oct 2020, Ashley Dixon wrote: > Date: Mon, 5 Oct 2020 19:55:50 > From: Ashley Dixon > Reply-To: gentoo-user@lists.gentoo.org > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] pcre build failure > > This is confusing me to no end, partly because you seem to have included > the > same text twice? The information posted seems to contradict itself, > particularly > with the USE-flags. For example, here you have the `static-libs` flag > disabled: > > On Mon, Oct 05, 2020 at 02:40:47PM -0400, Jude DaShiell wrote: > > [ebuild R] dev-libs/libpcre-8.44:3::gentoo USE="bzip2 cxx jit > > readline recursion-limit (split-usr) (unicode) zlib -libedit -pcre16 > > -pcre32 -static-libs*" ABI_X86="(64) -32 (-x32)" 0 KiB > > ... which is supported by the output of the configure script: > > > checking whether to build static libraries... no > [...] > > Build static libs ... : no > > ... but then in the output of `emerge --info`, which displays the flags of the > currently installed version, the `static-libs` flag is enabled: > > > dev-libs/libpcre-8.44::gentoo was built with the following: > > USE="bzip2 cxx jit readline recursion-limit (split-usr) static-libs > > (unicode) zlib -libedit -pcre16 -pcre32" ABI_X86="(64) -32 (-x32)" > > As the asterisk in the first emerge output would suggest, the flag is only > now > being disabled for the package. Such a change is very dangerous, and > although I > can't imagine why PCRE was built to use static libraries in the first place, > I > can assume this might be the cause of the error. I am still unable to > reproduce > this behaviour on my own system. > > PCRE depends on the following packages, so you will want to make sure that > all > of these agree on the nature of the libraries: static or dynamic? > > $ equery g libpcre > * Searching for libpcre ... > * dependency graph for dev-libs/libpcre-8.44 > `-- dev-libs/libpcre-8.44 amd64 >`-- app-arch/bzip2-1.0.6-r11 (app-arch/bzip2) amd64 >`-- sys-libs/zlib-1.2.11-r2 (sys-libs/zlib) amd64 >`-- dev-libs/libedit-20191211.3.1 (dev-libs/libedit) amd64 >`-- sys-libs/readline-8.0_p4 (sys-libs/readline) amd64 >`-- virtual/pkgconfig-2 (virtual/pkgconfig) amd64 >`-- app-portage/elt-patches-20170815 > (>=app-portage/elt-patches-20170815) amd64 > [ dev-libs/libpcre-8.44 stats: packages (7), max depth (1) ] > > > Irrelevant aside: you see these annoying ANSI colour codes captured by > `script`? > You can strip them out with the `ansifilter` program, provided by the > `app-text/ > ansifilter` package in gentoo.git. It takes standard input or a file name, > and > without any arguments, will erase all ANSI escape sequences. > > > [01;31mlivecd[01;34m / #[00m exit > > $ ansifilter <<< "[01;31mlivecd[01;34m / #[00m exit" # bash syntax > livecd / # exit > > In future, if you just want to capture the output of a (possibly > interactive) > command, `tee` is better than `script`. It usually strips escape sequences > and > such. However, it does not capture standard error to the output file, so > you'll > want to redirect it into standard output, like so: > > $ ./prog 2>&1 | tee prog-log > > -- When the failure happened on the computer I neglected to braille the commands that would have only produced a single copy of the text. In order to get the content from the second file, I needed to run the emerge update world command again then locate the command for the second file then cat that command. Braille paper is available here so I won't make that mistake again.
Re: [gentoo-user] pcre build failure
This is confusing me to no end, partly because you seem to have included the same text twice? The information posted seems to contradict itself, particularly with the USE-flags. For example, here you have the `static-libs` flag disabled: On Mon, Oct 05, 2020 at 02:40:47PM -0400, Jude DaShiell wrote: > [ebuild R] dev-libs/libpcre-8.44:3::gentoo USE="bzip2 cxx jit readline > recursion-limit (split-usr) (unicode) zlib -libedit -pcre16 -pcre32 > -static-libs*" ABI_X86="(64) -32 (-x32)" 0 KiB ... which is supported by the output of the configure script: > checking whether to build static libraries... no [...] > Build static libs ... : no ... but then in the output of `emerge --info`, which displays the flags of the currently installed version, the `static-libs` flag is enabled: > dev-libs/libpcre-8.44::gentoo was built with the following: > USE="bzip2 cxx jit readline recursion-limit (split-usr) static-libs (unicode) > zlib -libedit -pcre16 -pcre32" ABI_X86="(64) -32 (-x32)" As the asterisk in the first emerge output would suggest, the flag is only now being disabled for the package. Such a change is very dangerous, and although I can't imagine why PCRE was built to use static libraries in the first place, I can assume this might be the cause of the error. I am still unable to reproduce this behaviour on my own system. PCRE depends on the following packages, so you will want to make sure that all of these agree on the nature of the libraries: static or dynamic? $ equery g libpcre * Searching for libpcre ... * dependency graph for dev-libs/libpcre-8.44 `-- dev-libs/libpcre-8.44 amd64 `-- app-arch/bzip2-1.0.6-r11 (app-arch/bzip2) amd64 `-- sys-libs/zlib-1.2.11-r2 (sys-libs/zlib) amd64 `-- dev-libs/libedit-20191211.3.1 (dev-libs/libedit) amd64 `-- sys-libs/readline-8.0_p4 (sys-libs/readline) amd64 `-- virtual/pkgconfig-2 (virtual/pkgconfig) amd64 `-- app-portage/elt-patches-20170815 (>=app-portage/elt-patches-20170815) amd64 [ dev-libs/libpcre-8.44 stats: packages (7), max depth (1) ] Irrelevant aside: you see these annoying ANSI colour codes captured by `script`? You can strip them out with the `ansifilter` program, provided by the `app-text/ ansifilter` package in gentoo.git. It takes standard input or a file name, and without any arguments, will erase all ANSI escape sequences. > [01;31mlivecd[01;34m / #[00m exit $ ansifilter <<< "[01;31mlivecd[01;34m / #[00m exit" # bash syntax livecd / # exit In future, if you just want to capture the output of a (possibly interactive) command, `tee` is better than `script`. It usually strips escape sequences and such. However, it does not capture standard error to the output file, so you'll want to redirect it into standard output, like so: $ ./prog 2>&1 | tee prog-log -- Ashley Dixon suugaku.co.uk 2A9A 4117 DA96 D18A 8A7B B0D2 A30E BF25 F290 A8AA signature.asc Description: PGP signature
Re: [gentoo-user] pcre build failure
On Mon, Oct 05, 2020 at 04:14:07PM -0400, John Covici wrote:
> Also, you might want to go to the ~ tre -- I have no trouble compiling, but I
> have version 10.35 which is much newer than what you are trying to compile.
This concerns `dev-libs/libpcre`, not `dev-libs/pcre2`. As far as Portage is
concerned, these are two completely different packages. For the package in
question, the version Jude is attempting to install is the only one in the tree.
It's a bit tricky to triage the error from the assembler, because the compiler
is piping in its output, hence the assembler only reporting "{standard input}".
With that said, it looks like the assembler is encountering a syntax error,
which is very peculiar indeed. Furthermore, I'm unable the replicate this error
with the USE-flags given in Jude's `emerge --info` output, including the
notorious `static-libs` flag.
Can anyone else replicate this error?
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
Re: [gentoo-user] pcre build failure
On Mon, 05 Oct 2020 14:40:47 -0400,
Jude DaShiell wrote:
>
> Script started on 2020-10-05 09:53:20-04:00 [TERM="linux" TTY="/dev/tty2"
> COLUMNS="80" LINES="25"]
> [01;31mlivecd[01;34m / #[00m emerge --ask --verbose --ud[Kpdate --deep
> --newuse @world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies .. ... done!
> [ebuild R] dev-libs/libpcre-8.44:3::gentoo USE="bzip2 cxx jit readline
> recursion-limit (split-usr) (unicode) zlib -libedit -pcre16 -pcre32
> -static-libs*" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] app-arch/zstd-1.4.5:0/1::gentoo [1.4.4-r4:0/1::gentoo]
> USE="threads -lz4 -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] sys-apps/sandbox-2.20::gentoo [2.18::gentoo] ABI_X86="(32)
> (64) (-x32)" 0 KiB
> [ebuild U ] sys-apps/less-563::gentoo [551::gentoo] USE="pcre unicode" 0
> KiB
> [ebuild U ] sys-apps/debianutils-4.11.2::gentoo [4.11.1::gentoo]
> USE="installkernel -static" 0 KiB
> [ebuild U ] dev-lang/python-exec-2.4.6-r2:2::gentoo [2.4.6-r1:2::gentoo]
> PYTHON_TARGETS="(pypy3) (python2_7) (python3_6) (python3_7) (python3_8)
> (python3_9)" 0 KiB
> [uninstall ] dev-lang/python-2.7.18-r2:2.7::gentoo USE="gdbm ipv6
> ncurses readline ssl (threads) (wide-unicode) xml (-berkdb) -bluetooth -build
> -examples -hardened -libressl -sqlite -tk -wininst"
> [blocks b ] <=dev-lang/python-2.7.18-r3:2.7
> ("<=dev-lang/python-2.7.18-r3:2.7" is blocking dev-lang/python-exec-2.4.6-r2)
> [ebuild U ] sys-apps/busybox-1.32.0::gentoo [1.31.1-r2::gentoo]
> USE="ipv6 static systemd* -debug -livecd -make-symlinks -math -mdev -pam
> -savedconfig (-selinux) -sep-usr -syslog" 0 KiB
> [ebuild U ] app-admin/perl-cleaner-2.28::gentoo [2.27::gentoo] 0 KiB
> [ebuild NS] app-text/docbook-xml-dtd-4.2-r3:4.2::gentoo
> [4.1.2-r7:4.1.2::gentoo, 4.3-r2:4.3::gentoo, 4.4-r3:4.4::gentoo,
> 4.5-r2:4.5::gentoo] 0 KiB
> [ebuild U ] sys-fs/udev-init-scripts-34::gentoo [33::gentoo] 0 KiB
> [ebuild U ] sys-apps/hwids-20200813.1::gentoo [20200204::gentoo]
> USE="net pci udev usb" 0 KiB
> [ebuild U ] sys-apps/man-pages-5.08::gentoo [5.07::gentoo] L10N="-de -fr
> -it -ja -nl -pl -ru -zh-CN" 0 KiB
> [ebuild U ] sys-apps/attr-2.4.48-r4::gentoo [2.4.48-r3::gentoo] USE="nls
> (split-usr) -debug -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild NS] sys-devel/binutils-2.35.1:2.35::gentoo
> [2.34-r2:2.34::gentoo] USE="gold nls plugins -default-gold -doc -multitarget
> -static-libs -test -vanilla%" 0 KiB
> [ebuild U ] sys-apps/acl-2.2.53-r1::gentoo [2.2.53::gentoo] USE="nls
> (split-usr) -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] sys-devel/make-4.3::gentoo [4.2.1-r4::gentoo] USE="nls
> -guile -static" 0 KiB
> [ebuild U ] sys-devel/bison-3.7.2::gentoo [3.7.1-r1::gentoo] USE="nls
> -examples -static -test" 0 KiB
> [ebuild NS] sys-devel/gcc-10.2.0-r2:10::gentoo [9.3.0-r1:9.3.0::gentoo]
> USE="(cxx) fortran (multilib) nls nptl openmp pch (pie) sanitize ssp vtv
> (-ada) -d -debug -doc (-fixed-point) -go -graphite (-hardened) -jit (-libssp)
> -lto -objc -objc++ -objc-gc -pgo -systemtap -test -vanilla -zstd%
> (-altivec%)" 0 KiB
> [ebuild U ] dev-libs/popt-1.18::gentoo [1.16-r2::gentoo] USE="nls
> -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] sys-apps/grep-3.5::gentoo [3.4::gentoo] USE="nls pcre
> -static" 0 KiB
> [ebuild U ] dev-libs/elfutils-0.181::gentoo [0.180::gentoo] USE="bzip2
> nls utils -lzma -static-libs -test (-threads) -valgrind" ABI_X86="(64) -32
> (-x32)" 0 KiB
> [ebuild U ] app-editors/nano-5.2::gentoo [4.9.3::gentoo] USE="magic
> ncurses nls spell (split-usr) unicode -debug -justify -minimal -slang
> -static" 0 KiB
> [ebuild U ] dev-python/certifi-10001-r1::gentoo [10001::gentoo]
> USE="-test" PYTHON_TARGETS="python3_7 -pypy3 -python3_6 -python3_8 -python3_9
> (-python2_7%*)" 0 KiB
> [ebuild U ] dev-util/meson-0.55.3::gentoo [0.54.3::gentoo] USE="(-test)"
> PYTHON_TARGETS="python3_7 -python3_6 -python3_8 -python3_9%" 0 KiB
> [ebuild N ] sys-libs/libcap-2.43::gentoo USE="pam (split-usr)
> -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] sys-apps/shadow-4.8.1-r3::gentoo [4.8-r5::gentoo] USE="acl
> nls pam (split-usr) su xattr -audit -bcrypt -cracklib (-selinux) -skey" 0 KiB
> [ebuild U ] sys-libs/pam-1.4.0_p20200829::gentoo
> [1.3.1_p20200128-r1::gentoo] USE="berkdb filecaps* pie (split-usr) -audit
> -debug -nis (-selinux) (-cracklib%*) (-static-libs%)" ABI_X86="(64) -32
> (-x32)" 0 KiB
> [ebuild NS] sys-libs/db-6.0.35-r2:6.0::gentoo [5.3.28-r2:5.3::gentoo]
> USE="-cxx -doc -examples -java -tcl -test" ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild N ] sys-auth/passwdqc-1.4.0-r1::gentoo 0 KiB
> [ebuild U ] sys-apps/iproute2-5.8.0::gentoo [5.7.0::gentoo] USE="berkdb
> iptables ipv6 -atm -caps -elf -minimal (-selinux)" 0 KiB
>
