Re: python support appears broken in the ports trree
On Wed, 11 Dec 2019 06:21:29 +0100 Jan Beich jbe...@freebsd.org said Chris writes: > I struggled all day yesterday with various ports barfing with similar > python messages. So today I blew everything off the disk, and started > from scratch. Which only repeats what happened yesterday. Is python > multiplicity no longer available? Or? See bug 233723 or bug 237795. Build each port separately instead of relying on dependecy chaining should work. For best experience use poudriere. Thank you very much for the insight, Jan! Near as I can figure from the two bugs, I'm going to need to fix Mk/python.mk That should be a fun project. :P Thanks again! --Chris ___ 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: python support appears broken in the ports trree
Chris writes: > I struggled all day yesterday with various ports barfing with similar > python messages. So today I blew everything off the disk, and started > from scratch. Which only repeats what happened yesterday. Is python > multiplicity no longer available? Or? See bug 233723 or bug 237795. Build each port separately instead of relying on dependecy chaining should work. For best experience use poudriere. ___ 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: python support appears broken in the ports trree
On Tue, 10 Dec 2019 16:53:38 -0800 s...@troutmask.apl.washington.edu said Thank you very much for taking the time to reply. On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote: > I struggled all day yesterday with various ports barfing with similar > python messages. So today I blew everything off the disk, and started > from scratch. Which only repeats what happened yesterday. Is python > multiplicity no longer available? Or? > Empirical evidence suggests that answer is "yes". Sigh... It would /seem/ so. Maybe someone(tm) should make an entry in UPDATING? Thanks again! --Chris -- Steve ___ 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" ___ 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: python support appears broken in the ports trree
On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote: > I struggled all day yesterday with various ports barfing with similar > python messages. So today I blew everything off the disk, and started > from scratch. Which only repeats what happened yesterday. Is python > multiplicity no longer available? Or? > Empirical evidence suggests that answer is "yes". -- Steve ___ 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"
python support appears broken in the ports trree
I've spent the past 2 days attempting a fresh build/install of world/kernel && preferred ports/applications. The world/kernel worked to perfection. But I can *not* get the ports to build, and install. All *fatal* errors stem from python. So after booting into a new world/kernel; I proceed to build/install perl5-5.30, python27 && python37. I now feel I have the versions I need/want. So I move to /usr/ports/x11/xorg and perform a make config-recursive until the dialogs will no longer appear. From there (today) make(1) terminates at: ... ===> Staging for xorg-7.7_3 ===> xorg-7.7_3 depends on file: /usr/local/libdata/pkgconfig/dri.pc - not found ===> mesa-dri-18.3.2_9 depends on package: wayland-protocols>=1.8 - found ===> mesa-dri-18.3.2_9 depends on file: /usr/local/libdata/pkgconfig/pthread-stubs.pc - found ===> mesa-dri-18.3.2_9 depends on executable: bison - found ===> mesa-dri-18.3.2_9 depends on executable: msgfmt - found ===> mesa-dri-18.3.2_9 depends on executable: gmake - found ===> mesa-dri-18.3.2_9 depends on package: pkgconf>=1.3.0_1 - found ===> mesa-dri-18.3.2_9 depends on file: /usr/local/bin/python2.7 - found ===> mesa-dri-18.3.2_9 depends on package: llvm80>=3.9.0_4 - not found ===> llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified. *** Error code 1 ... I struggled all day yesterday with various ports barfing with similar python messages. So today I blew everything off the disk, and started from scratch. Which only repeats what happened yesterday. Is python multiplicity no longer available? Or? make.conf(5) DEFAULT_VERSIONS+=tcl=8.7 tk=8.7 FreeBSD eleventhree 11.3-RELEASE-p5 FreeBSD 11.3-RELEASE-p5 #0 r355580: Tue Dec 10 13:22:30 PST 2019 root@eleventhree:/usr/obj/usr/src/sys/ELEVENTHREE amd64 Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/releng/11.3 Relative URL: ^/releng/11.3 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 355580 Node Kind: directory Schedule: normal Last Changed Author: gordon Last Changed Rev: 354654 Last Changed Date: 2019-11-12 10:13:51 -0800 (Tue, 12 Nov 2019) Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 519768 Node Kind: directory Schedule: normal Last Changed Author: pizzamig Last Changed Rev: 519768 Last Changed Date: 2019-12-10 09:39:01 -0800 (Tue, 10 Dec 2019) Thank you for all your time, and consideration. --Chris ___ 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"
