Re: problem installing ports
On 8/26/2016 7:42 AM, Robert Huff wrote: Let me guess, you have (NFSv4) ACLs enabled somewhere. The HEAD was supposedly fixed in r304075, but the change still was not merged to stable/11. Yes, on the filesystem that holds WRKDIRPREFIX. Is it as simple as that? (And is there a PR number?) Apparently, it is. Thanks for the helo. Madly compiling away, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem installing ports
On 8/26/2016 7:33 AM, Konstantin Belousov wrote: ===> Registering installation for dialog4ports-0.1.6 Installing dialog4ports-0.1.6... Child process pid=6648 terminated abnormally: Bus error *** Error code 138 Stop. ... and pkg-static drops a core file. I get this (with different pids) for _every_ port on "make install". Never seen this before. Google offered no possible causes. "Bus error" means a memory violation - and I have no idea how to proceed. The core file has no debugging symbols, making a backtrace useless. Let me guess, you have (NFSv4) ACLs enabled somewhere. The HEAD was supposedly fixed in r304075, but the change still was not merged to stable/11. Yes, on the filesystem that holds WRKDIRPREFIX. Is it as simple as that? (And is there a PR number?) Boggled at the simplicity, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem installing ports
On Fri, Aug 26, 2016 at 07:14:38AM -0400, Robert Huff wrote: > So ... > I replaced my 10.3/i386 system with: > > FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 > r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > and kernel+world are working. > Installing ports is a different matter. > 1) I created /usr/ports and /usr/doc. > 2) I "self-installed" pkg; this brought with it > > apr-1.5.2.1.5.4_1 > db5-5.3.28_4 > expat-2.1.1_2 > gdbm-1.12 > gettext-runtime-0.19.8.1 > indexinfo-0.2.4 > readline-6.3.8 > serf-1.3.8_1 > sqlite3-3.13.0 > > 3) Next: > > root@>> pkg install subversion > > which I used to populate the ports tree. > 4) Now, to install portmaster. That requires dialog4ports: > > root@>> make clean > ===> Cleaning for dialog4ports-0.1.6 > root@>> make > ===> License BSD2CLAUSE accepted by the user > ===> dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by dialog4ports-0.1.6 for building > ===> Extracting for dialog4ports-0.1.6 > => SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz. > ===> Patching for dialog4ports-0.1.6 > ===> Configuring for dialog4ports-0.1.6 > ===> Building for dialog4ports-0.1.6 > --- dialog4ports.o --- > --- mixedlist.o --- > --- dialog4ports.1.gz --- > --- dialog4ports.o --- > cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c > dialog4ports.c -o dialog4ports.o > --- mixedlist.o --- > cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c > mixedlist.c -o mixedlist.o > --- dialog4ports.1.gz --- > gzip -cn dialog4ports.1 > dialog4ports.1.gz > --- dialog4ports --- > cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic > dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog > ===> Staging for dialog4ports-0.1.6 > ===> Generating temporary packing list > install -m 555 dialog4ports > /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin > install -m 0644 dialog4ports.1.gz > /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1 > > Compressing man pages (compress-man) > root@>> make install > ===> Installing for dialog4ports-0.1.6 > ===> Checking if dialog4ports already installed > ===> Registering installation for dialog4ports-0.1.6 > Installing dialog4ports-0.1.6... > Child process pid=6648 terminated abnormally: Bus error > *** Error code 138 > > Stop. > > ... and pkg-static drops a core file. > I get this (with different pids) for _every_ port on "make install". > Never seen this before. Google offered no possible causes. > "Bus error" means a memory violation - and I have no idea how to > proceed. The core file has no debugging symbols, making a backtrace > useless. > Let me guess, you have (NFSv4) ACLs enabled somewhere. The HEAD was supposedly fixed in r304075, but the change still was not merged to stable/11. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
problem installing ports
So ... I replaced my 10.3/i386 system with: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and kernel+world are working. Installing ports is a different matter. 1) I created /usr/ports and /usr/doc. 2) I "self-installed" pkg; this brought with it apr-1.5.2.1.5.4_1 db5-5.3.28_4 expat-2.1.1_2 gdbm-1.12 gettext-runtime-0.19.8.1 indexinfo-0.2.4 readline-6.3.8 serf-1.3.8_1 sqlite3-3.13.0 3) Next: root@>> pkg install subversion which I used to populate the ports tree. 4) Now, to install portmaster. That requires dialog4ports: root@>> make clean ===> Cleaning for dialog4ports-0.1.6 root@>> make ===> License BSD2CLAUSE accepted by the user ===> dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by dialog4ports-0.1.6 for building ===> Extracting for dialog4ports-0.1.6 => SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz. ===> Patching for dialog4ports-0.1.6 ===> Configuring for dialog4ports-0.1.6 ===> Building for dialog4ports-0.1.6 --- dialog4ports.o --- --- mixedlist.o --- --- dialog4ports.1.gz --- --- dialog4ports.o --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c dialog4ports.c -o dialog4ports.o --- mixedlist.o --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c mixedlist.c -o mixedlist.o --- dialog4ports.1.gz --- gzip -cn dialog4ports.1 > dialog4ports.1.gz --- dialog4ports --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog ===> Staging for dialog4ports-0.1.6 ===> Generating temporary packing list install -m 555 dialog4ports /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin install -m 0644 dialog4ports.1.gz /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1 > Compressing man pages (compress-man) root@>> make install ===> Installing for dialog4ports-0.1.6 ===> Checking if dialog4ports already installed ===> Registering installation for dialog4ports-0.1.6 Installing dialog4ports-0.1.6... Child process pid=6648 terminated abnormally: Bus error *** Error code 138 Stop. ... and pkg-static drops a core file. I get this (with different pids) for _every_ port on "make install". Never seen this before. Google offered no possible causes. "Bus error" means a memory violation - and I have no idea how to proceed. The core file has no debugging symbols, making a backtrace useless. Exasperatedly, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
