Re: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h

2019-11-24 Thread Mark Millard via freebsd-ports
On 2019-Nov-24, at 15:11, Ben Woods wrote: > On Sun, 24 Nov 2019 at 1:27 pm, Mark Millard wrote: > My poudiere jail constructions with the likes of -a arm64.aarch64 -x are > all getting: > > awk: can't open file /sys/param.h > source line number 1 > > Hi M

Re: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h

2019-12-07 Thread Mark Millard via freebsd-ports
[In part this note shows that the issue is not specific to cross builds: -a arm64.aarch64 is not essential. But it also shows just where the /sys/param.h comes from.] On 2019-Nov-24, at 15:22, Mark Millard wrote: > On 2019-Nov-24, at 15:11, Ben Woods wrote: > >> On Sun, 24 Nov 201

devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

2019-12-26 Thread Mark Millard via freebsd-ports
932 Dec 25 19:25:10 2019 patch-powerpc32 -rw-r--r-- 1 root wheel 294 Sep 15 13:10:46 2019 pkg-message.in I do not know if other differences in the patch lists might be important to other aspects (in either direction). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 201

Re: devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

2019-12-26 Thread Mark Millard via freebsd-ports
On 2019-Dec-26, at 15:21, Mark Millard wrote: > I tried to build devel/freebsd-gcc9@powerpc on a powerpc64 (in an > ELFv1 clang environment) and it reported (listing just one of the > examples that pointed to vec_step): > > > /wrkdirs/usr/ports/devel/freebsd-gcc9/work-pow

Re: devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

2019-12-26 Thread Mark Millard via freebsd-ports
On 2019-Dec-26, at 20:49, Gerald Pfeifer wrote: > On Thu, 26 Dec 2019, Mark Millard wrote: >> I tried to build devel/freebsd-gcc9@powerpc on a powerpc64 (in an >> ELFv1 clang environment) and it reported (listing just one of the >> examples that pointed to vec_step): >

security/nss failed to build on/for 32-bit powerpc for a -Werror,-Wtautological-constant-out-of-range-compare

2019-12-28 Thread Mark Millard via freebsd-ports
ving directory '/wrkdirs/usr/ports/security/nss/work/nss-3.48/nss' *** Error code 1 Stop. make: stopped in /usr/ports/security/nss =>> Cleaning up wrkdir ===> Cleaning for nss-3.48 build of security/nss | nss-3.48 ended at Sat Dec 28 11:00:18 PST 2019 In essence: unsigned long h

32-bit powerpc graphics/mesa-libs build failed: u_atomic.c:38:1: error: cannot redeclare builtin function '__sync_add_and_fetch_8' (and others)

2019-12-28 Thread Mark Millard via freebsd-ports
1 gmake[2]: Leaving directory '/wrkdirs/usr/ports/graphics/mesa-libs/work/mesa-18.3.2/src/util' gmake[1]: *** [Makefile:996: all] Error 2 The is a clang-based FreeBSD context. The ports are at -r520539 . === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar

x11-toolkits/qt5-gui build on/for Cortex-A7 ( head -r356109 ) failed with: unable to execute command: Executable "as" doesn't exist

2019-12-28 Thread Mark Millard via freebsd-ports
-gnueabihf Thread model: posix InstalledDir: /usr/bin # svnlite info /usr/ports/ 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: 52053

devel/binutils@powerpc64 ( powerpc64-unknown-freebsd13.0-ld ) unbounded loop in bfd/elf64-ppc.c : the source code and values

2019-12-30 Thread Mark Millard via freebsd-ports
/binutils-2.33.1/bfd/elf64-ppc.c The 1st line quoted above was line 7455 according to vi. Ref reference, both of the stuck links (clang.full and lld.full) have: (gdb) print r_type $1 = R_PPC64_REL16_HA (gdb) print/x *rel $3 = {r_offset = 0x2, r_info = 0x1800fc, r_addend = 0x2} === Mar

Re: exFAT is no longer encumbered

2019-12-30 Thread Mark Millard via freebsd-ports
ellectualproperty/iplicensing/default.aspx has a link for "process of obtaining a license". Guess where it goes: http://aka.ms/celaiplicensing The earlier "Contact a licensing executive" link on the page also goes there. Both of those are under the "Learn More about Pa

Re: devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

2019-12-31 Thread Mark Millard via freebsd-ports
On 2019-Dec-31, at 16:41, John Baldwin wrote: > On 12/26/19 11:39 PM, Mark Millard wrote: >>>> is missing the patch-clang-vec_step that is in: >>>> >>>> FBSDG5L2# ls -laT /usr/ports/lang/gcc9/files/ >>> >>> That is a hack that can b

amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
lvm10/lib/libarcher_static.a:No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/devel/llvm10 =>> Cleaning up wrkdir ===> Cleaning for llvm10-10.0.0.r1_1 head -r3577979 based system source; head -r536339 based ports tree. === Mark Millard marklmi at yahoo.com (

Re: amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
On 2020-Feb-17, at 09:53, Mark Millard wrote: > [The native arm64 build worked fine. But the cross builds > got . . .] > > The builds failed with: > > > Compressing man pages (compress-man) > ===> Installing

Re: amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files

2020-02-17 Thread Mark Millard via freebsd-ports
On 2020-Feb-17, at 09:56, Mark Millard wrote: > On 2020-Feb-17, at 09:53, Mark Millard wrote: > >> [The native arm64 build worked fine. But the cross builds >> got . . .] >> >> The builds failed with: >> >> > Compressing man pages

Re: svn commit: r358166 - head

2020-02-21 Thread Mark Millard via freebsd-ports
l/bin/gnuplot libncurses.so.8 /usr/local/bin/FileCheck80 libncurses.so.8 /usr/local/bin/FileCheck10 libncurses.so.8 /usr/local/lib/gettext/cldr-plurals libncurses.so.8 This can be a lot of files to go through (e.g., lib*) and so can take a fair amount of time. === Mark Millard marklmi at yahoo.co

Re: svn commit: r358166 - head

2020-02-21 Thread Mark Millard via freebsd-ports
On 2020-Feb-21, at 08:38, Mark Millard wrote: > Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd > there are commands such as the following that might help: > > . . . > > This can be a lot of files to go through (e.g., lib*) and so > can take a fair

Re: svn commit: r358166 - head

2020-02-21 Thread Mark Millard via freebsd-ports
On 2020-Feb-21, at 15:59, Kevin Oberman wrote: > On Fri, Feb 21, 2020 at 8:38 AM Mark Millard via freebsd-ports > wrote: > Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd > there are commands such as the following that might help: > > . . . > > Th

Re: svn commit: r358166 - head

2020-02-22 Thread Mark Millard via freebsd-ports
On 2020-Feb-22, at 09:29, Stefan Eßer wrote: > Am 22.02.20 um 03:50 schrieb Mark Millard via freebsd-ports: >> >> >> . . . >> >> In the style of my prior examples (including the change that >> found libedit and such), analogous would be: >> >

amd64->armv7 cross-build failure for security/ca_root_nss: It failed in memcpy () from /libexec/ld-elf.so.1

2020-03-16 Thread Mark Millard via freebsd-ports
in my context. Having security/ca_root_nss blocked, blocks cross-building lots of other things, including devel/llvm10 . === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https:/

Re: amd64->armv7 cross-build failure for security/ca_root_nss: It failed in memcpy () from /libexec/ld-elf.so.1

2020-03-23 Thread Mark Millard via freebsd-ports
On 2020-Mar-16, at 21:48, Mark Millard wrote: > Context: head -r358966 attempting to update ports > to -r528535 . Also, 50+ ports built just fine > but the below has been repeatable in my context. > > The original failure was under devel/poudriere-devel (with > nxb-bin/ ma

WITHOUT_BINUTILS= based head -r356427 FreeBSD context: x11-toolkits/qt5-gui build fails in poudriere: unable to execute command: Executable "as" doesn't exist!

2020-04-22 Thread Mark Millard via freebsd-ports
neon_asm.o . . . --- .obj/qdrawhelper_neon_asm.o --- cc: error: unable to execute command: Executable "as" doesn't exist! This suggests that a dependency on a ports binutils is needed and use of it is needed to keep this building when binutils 2.17.50 is absent in head. === Mark Mil

Applying distribution patches for u-boot-rpi4-2020.04 fails during build (poudriere-devel context)

2020-04-25 Thread Mark Millard via freebsd-ports
lls(fdt, nodeoffset, "#address-cells"); +} - return val; +int fdt_size_cells(const void *fdt, int nodeoffset) +{ + return fdt_cells(fdt, nodeoffset, "#size-cells"); } === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _

Re: Applying distribution patches for u-boot-rpi4-2020.04 fails during build (poudriere-devel context)

2020-04-26 Thread Mark Millard via freebsd-ports
On 2020-Apr-25, at 02:00, Emmanuel Vadot wrote: > On Sat, 25 Apr 2020 10:56:47 +0200 > Emmanuel Vadot wrote: > >> On Sat, 25 Apr 2020 00:43:27 -0700 >> Mark Millard via freebsd-uboot wrote: >> >>> From the log file: >>> >>> ===

aarch64 based sysutils/u-boot-rpi[34] (and more?) builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-26 Thread Mark Millard via freebsd-ports
: *** [scripts/Makefile.autoconf:48: include/autoconf.mk.dep] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[1]: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'. Stop. gmake[1]: Leaving directory '/wrkdirs/usr

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-26 Thread Mark Millard via freebsd-ports
On 2020-Apr-26, at 01:14, Mark Millard wrote: > The below where based on poudriere-devel based build attempts. > /usr/ports/ was based on head -r532972 and aarch64 FreeBSD was > based on head -r360311 . amd64 FreeBSD did not have the build > problem for the aaarch64-targeted

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-27 Thread Mark Millard via freebsd-ports
On 2020-Apr-27, at 11:46, Emmanuel Vadot wrote: > On Mon, 27 Apr 2020 12:32:46 +0200 > Emmanuel Vadot wrote: > >> On Sun, 26 Apr 2020 12:13:46 -0700 >> Mark Millard via freebsd-arm wrote: >> >>> >>> >>> On 2020-Apr-26, at 01:14, M

security/nss poudriere amd64->aarch64 cross-build failure: could not find libraries -lplc4 -lplds4 -lnspr4

2020-04-27 Thread Mark Millard via freebsd-ports
ports/security/nss/work/nss-3.51.1/nss/lib' gmake[1]: *** [coreconf/rules.mk:101: libs] Error 2 gmake[1]: Leaving directory '/wrkdirs/usr/ports/security/nss/work/nss-3.51.1/nss' *** Error code 1 === Mark Millard marklmi at yahoo.com

Oddities possibly contributing to lang/gcc9 not building (amd64->aarch64 poudriere based cross build)

2020-04-27 Thread Mark Millard via freebsd-ports
ally stopped the build. It might have been the kinds of things reported above --or it might not. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/m

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-27 Thread Mark Millard via freebsd-ports
On 2020-Apr-27, at 17:15, Mark Millard wrote: > On 2020-Apr-27, at 11:46, Emmanuel Vadot wrote: > >> On Mon, 27 Apr 2020 12:32:46 +0200 >> Emmanuel Vadot wrote: >> >>> On Sun, 26 Apr 2020 12:13:46 -0700 >>> Mark Millard via freebsd-arm wrote: >

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: > On Mon, 27 Apr 2020 20:14:47 -0700 > Mark Millard wrote: > >> On 2020-Apr-27, at 17:15, Mark Millard wrote: >> >>> On 2020-Apr-27, at 11:46, Emmanuel Vadot wrote: >>> >>>> On Mon, 27

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
On 2020-Apr-28, at 09:23, Mark Millard wrote: > On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: > >> On Mon, 27 Apr 2020 20:14:47 -0700 >> Mark Millard wrote: >> >>> On 2020-Apr-27, at 17:15, Mark Millard wrote: >>> >>>> On 2020-Apr-2

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
[Found a cause of the poudiere vs. not distinction.] On 2020-Apr-28, at 13:01, Mark Millard wrote: > > On 2020-Apr-28, at 09:23, Mark Millard wrote: > >> On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: >> >>> On Mon, 27 Apr 2020 20:14:47 -0700 >>> Mar

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
[Looks like more than objdump may be involved for /usr/local/aarch64-none-elf/bin/ use.] On 2020-Apr-28, at 14:00, Mark Millard wrote: > [Found a cause of the poudiere vs. not distinction.] > > On 2020-Apr-28, at 13:01, Mark Millard wrote: >> >> On 2020-Apr-28, at 09:23

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-29 Thread Mark Millard via freebsd-ports
fig FAMILY=allwinner64 +MAKE_JOBS_UNSAFE=yes + .include "${MASTERDIR}/Makefile" based on historical build-race problems specific to pine64's u-boot build. But it makes the qemu-based build take a very long time. === Mark Millard marklmi at yahoo.com ( dsl-only.net

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-29 Thread Mark Millard via freebsd-ports
On 2020-Apr-29, at 10:22, Emmanuel Vadot wrote: > On Wed, 29 Apr 2020 12:50:36 +0200 > Emmanuel Vadot wrote: > >> On Wed, 29 Apr 2020 01:36:01 -0700 >> Mark Millard wrote: >> >>> [Build successes for building via poudriere-devel. >>> Mess

Re: Poudriere - Compile ALL Ports

2020-05-11 Thread Mark Millard via freebsd-ports
an have the same problems with having pre-existing material in an equivalent of my /usr/obj/DESTDIRs/clang-amd64-installworld-poud/usr/local/ area. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-port

Re: Poudriere - Compile ALL Ports

2020-05-11 Thread Mark Millard via freebsd-ports
14 21:07:05 /usr/ports Again a "null" METHOD where I'm supplying my own materials. Again it allows for testing development materials that are not checked into svn. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
because of the textproc/py-sphinx* difference in requirements. The conflict is real and limits what combinations of ports you may have installed at the same time. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebs

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 00:33, Mark Millard wrote: > bob prohaska fbsd at www.zefox.net wrote on > Fri May 15 04:30:07 UTC 2020 : > >> An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B >> resulted in a >> conflict: >> >> ===&g

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 08:19, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports > wrote: >> >> Some building and isntalling had to occur prior to the >> textproc/py-sphinx18 build attempt, possibly from >> prior session

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 11:05, bob prohaska wrote: > On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote: >> On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote: >>> On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports >>> wrote: &

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
[Gack: devel/cmake needs devel/py-sphinx by default and devel/llvm80 needs both devel/cmake and devel/py-pshinx18 by default.] On 2020-May-15, at 11:59, Mark Millard wrote: > > On 2020-May-15, at 11:05, bob prohaska wrote: > >> On Fri, May 15, 2020 at 01:49:21PM -0300, Danil

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 13:03, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:02PM -0700, Mark Millard wrote: >> [Gack: devel/cmake needs devel/py-sphinx by default >> and devel/llvm80 needs both devel/cmake and >> devel/py-pshinx18 by default.] >> >> On 20

Re: Missing /dev/io on rpi3 running 12-stable

2020-05-20 Thread Mark Millard via freebsd-ports
) That is all I have. I'm not so sure any of it will happen to help. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

Re: Missing /dev/io on rpi3 running 12-stable

2020-05-23 Thread Mark Millard via freebsd-ports
uot;Module ABI versions" information. So your failing context is either devd based or still has the environment configured for HAL or is otherwise messed up such that udev is not in use. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)

Re: 'asm/hwcap.h' file not found building chromium on Pi3

2020-05-31 Thread Mark Millard via freebsd-ports
itself so it seems the problem would be considered to be in the port instead. I've no clue what a proper alternative would be for third_party/zlib/cpu_features.c to use in a FreeBSD context. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?

2020-06-16 Thread Mark Millard via freebsd-ports
rpi3 is for use with aarch64 FreeBSD B) sysutils/u-boot-rpi3-32 is for use with armv7 FreeBSD === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailm

Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?

2020-06-16 Thread Mark Millard via freebsd-ports
On 2020-Jun-16, at 22:21, bob prohaska wrote: > On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote: >> >> >> On 2020-Jun-16, at 21:34, bob prohaska wrote: >> >>> Just noticed there are now two u-boot ports for the RPi3, one >>> called u

Re: Jumbled dependencies

2020-06-18 Thread Mark Millard via freebsd-ports
e from FreeBSD's /var/db/ports/*_*/options files. > I once got a royal mess of circular/jumbled dependencies with dialog4ports; > cleaning was a major nuisance, nothing simple like editing /etc/mk.conf or > /etc/make.conf . > > I never used pkgsrc with any

armv7: x11-toolkits/qt5-gui still blocked by 'unable to execute command: Executable "as" doesn't exist!' for .obj/qdrawhelper_neon_asm.o and .obj/pixman-arm-neon-asm.o

2020-07-15 Thread Mark Millard via freebsd-ports
6,10 @@ ${MAKE_ARGS} ${INSTALL_TARGET} .endfor -.include +.include + +.if ${ARCH} == "armv6" || ${ARCH} == "armv7" +BUILD_DEPENDS+= ${LOCALBASE}/bin/as:devel/binutils +.endif + +.include === Mark Millard marklmi

devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-20 Thread Mark Millard via freebsd-ports
"--enable-new-dtags" "-m" "elf32ppc_fbsd" "-o" "a.out" "/usr/lib/crt1.o" "/usr/lib/crti.o" "/usr/lib/crtbegin.o" "-L/usr/lib" "/dev/null" "-lc++" "-lm" "-lgcc" "--a

Re: devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-20 Thread Mark Millard via freebsd-ports
might decay to a pointer in some contexts, unlike what __float128 or __int128 would have done. > On 20-07-20 15:27:01, Mark Millard wrote: >> This resulted in: Failed: 1 Skipped: 181 >> >> # poudriere jail -l >> JAILNAME VERSION ARCH METHOD

Re: Why lang/gcc9 depends native-binutils ?

2020-07-21 Thread Mark Millard via freebsd-ports
sd13.0" but that is not what was reported as involved. I've ignored CROSS_TOOLCHAIN infrastructure as it was not mentioned as being in use. I do not see how devel/binutils/Makefile would generate "native-unknown-freebsd13.0" text on its own. Sorry I've not been able to i

Re: devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-21 Thread Mark Millard via freebsd-ports
-20 16:33:27, Mark Millard wrote: >> >> >> On 2020-Jul-20, at 16:13, Piotr Kubaj wrote: >>> >>> Thanks for your report. I'm currently testing whether powerpc(64) on >>> 12.1 and head can build with this patch >>> https://github.com/li

32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-21 Thread Mark Millard via freebsd-ports
-e111-bb59-0022644237b5 Revision: 542111 Node Kind: directory Schedule: normal Last Changed Author: vanilla Last Changed Rev: 542111 Last Changed Date: 2020-07-12 21:32:18 -0700 (Sun, 12 Jul 2020) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

Re: Why lang/gcc9 depends native-binutils ?

2020-07-22 Thread Mark Millard via freebsd-ports
On 2020-Jul-22, at 00:23, KIRIYAMA Kazuhiko wrote: > Hi, Mark > > On Tue, 21 Jul 2020 17:51:41 +0900, > Mark Millard via freebsd-ports wrote: >> >> KIRIYAMA Kazuhiko kiri at truefc.org wrote on >> Tue Jul 21 02:33:25 UTC 2020 : >> >>> checking

Re: Why lang/gcc9 depends native-binutils ?

2020-07-22 Thread Mark Millard via freebsd-ports
On 2020-Jul-22, at 01:03, Mark Millard wrote: > On 2020-Jul-22, at 00:23, KIRIYAMA Kazuhiko wrote: > >> Hi, Mark >> >> On Tue, 21 Jul 2020 17:51:41 +0900, >> Mark Millard via freebsd-ports wrote: >>> >>> KIRIYAMA Kazuhiko kiri at true

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-22 Thread Mark Millard via freebsd-ports
On 2020-Jul-22, at 14:11, Jan Beich wrote: > Mark Millard via freebsd-ppc writes: > >> ../src/util/u_atomic.c:38:1: error: cannot redeclare builtin function >> '__sync_add_and_fetch_8' >> __sync_add_and_fetch_8(uint64_t *ptr, uint64_t val) >>

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-22 Thread Mark Millard via freebsd-ports
On 2020-Jul-22, at 17:16, Mark Millard wrote: > On 2020-Jul-22, at 14:11, Jan Beich wrote: > >> Mark Millard via freebsd-ppc writes: >> >>> ../src/util/u_atomic.c:38:1: error: cannot redeclare builtin function >>> '__sync_add_and_fetch_8' >

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-23 Thread Mark Millard via freebsd-ports
On 2020-Jul-22, at 21:02, Mark Millard wrote: > On 2020-Jul-22, at 17:16, Mark Millard wrote: > >> On 2020-Jul-22, at 14:11, Jan Beich wrote: >> >>> Mark Millard via freebsd-ppc writes: >>> >>>> ../src/util/u_atomic.

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-23 Thread Mark Millard via freebsd-ports
On 2020-Jul-23, at 09:25, Mark Millard wrote: > > On 2020-Jul-22, at 21:02, Mark Millard wrote: > >> On 2020-Jul-22, at 17:16, Mark Millard wrote: >> >>> On 2020-Jul-22, at 14:11, Jan Beich wrote: >>> >>>> Mark Millard via freebsd-p

security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-29 Thread Mark Millard via freebsd-ports
fail("cannot make symbolic link %s", toname); } . . . The "goto retry" is odd given the "fail" use and: void fail(char *format, ...) { . . . abort(); exit(1); } The poudriere bulk is still going, building other things. So it will be some time

Re: security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-30 Thread Mark Millard via freebsd-ports
nss/work/nss-3.54/nss' > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/security/nss > > > I don't

Re: security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-31 Thread Mark Millard via freebsd-ports
h if MAKE_JOBS_UNSAFE use made a difference would be problematical: failure is rare without MAKE_JOBS_UNSAFE in my context. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https

How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-10 Thread Mark Millard via freebsd-ports
Obin Double Shot --but it is based on using a personal uefi/acpi build that I was given access to. I've no clue how to reproduce it from what source. I've no clue what would be good to build for @macchiatobin use. (It need not match what is good for the RPi3 and RPi4 as far as I can tell,

Re: How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-11 Thread Mark Millard via freebsd-ports
On 2020-Aug-11, at 00:46, Mark Murray wrote: >> On 11 Aug 2020, at 07:44, Mark Millard via freebsd-arm >> wrote: >> >> Unfortunately, I'm not aware of anything for macchiatobin >> that is analogous to https://github.com/pftf/RPi3 and >> https://gith

Re: How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-15 Thread Mark Millard via freebsd-ports
On 2020-Aug-10, at 23:44, Mark Millard wrote: > I noticed the sysutils/edk2 addition. So I've tried to figure > out how to use it to reproduce the pftf RPi4 V1.18 release > (as an example), by, say, adjusting the distinfo file to pick > up the matching source. > > Lookin

Re: DEFAULT_VERSIONS+=llvm=90 ignored?

2020-12-05 Thread Mark Millard via freebsd-ports
for things using the LLVM API. Having all ports using the same LLVM API release is probably not an option (upstream issues). In other words: software that chooses to be in part based on the LLVM API tends to lead to needing various vintages of LLVM to be installed. === Mark Millard marklmi at y

Re: DEFAULT_VERSIONS+=llvm=90 ignored?

2020-12-05 Thread Mark Millard via freebsd-ports
On 2020-Dec-5, at 07:02, Steve Kargl wrote: > On Sat, Dec 05, 2020 at 01:18:34AM -0800, Mark Millard wrote: >> Steve Kargl sgk at troutmask.apl.washington.edu wrote on: >>> >>> Well, I guess that pretty much kills LLVM_DEFAULT for any >>> modern hardware

math/suitesparse from ports head -r557893 fails for armv7 by default: "/usr/local/bin/ld: cannot find -lomp"

2020-12-14 Thread Mark Millard via freebsd-ports
ec 10 03:15:10 PST 2020 root@FBSDFHUGE:/usr/obj/cortexA72_clang/arm64.aarch64/usr/src/arm64.aarch64/sys/GENERIC-NODBG arm64 aarch64 1300131 1300131 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-por

Re: math/suitesparse from ports head -r557893 fails for armv7 by default: "/usr/local/bin/ld: cannot find -lomp"

2020-12-14 Thread Mark Millard via freebsd-ports
On 2020-Dec-14, at 13:34, Mark Millard wrote: > This was on aarch64 doing a build targeting armv7 via poudriere --but might > apply to other platforms that by default do not have LLVM's OpenMP runtime: > >WITHOUT_OPENMP > Set to not build L

Re: Warning: Major OS version upgrade detected

2021-01-30 Thread Mark Millard via freebsd-ports
So it would seem unlikely you could have picked up a pkg that was built for/from stable/13 or main as 14-CURRENT on Jan-22nd or soon after. This leaves me curious about what to avoid at such transitions. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)

"pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
;m trying to update an old PowerMac powerpc64 context to FreeBSD:14 based ABI builds for ports.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/li

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
m/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin . . . --MAKE_ENV-- . . . PATH=/wrkdirs/usr/ports/x11/libXpm/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin . . . > Mark Millard via freebsd-ports wrote on 2021/02/05 07:14: >

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
ng as far as I can tell. If so, it needs to be added. > Mark Millard wrote on 2021/02/05 07:58: >> >> >> On 2021-Feb-4, at 14:44, Tatsuki Makino >> wrote: >> >>> Hello. >>> >>> It's the one that happens when environment variab

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
On 2021-Feb-4, at 15:33, Mark Millard wrote: > On 2021-Feb-4, at 15:11, Tatsuki Makino wrote: > >> In rare cases, a package with missing contents may be created. >> If there is a problem after checking with >> >> tar -t -f >> /usr/local/poudriere/data/p

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
indexes\n\nWWW: https://github.com/bapt/indexinfo","categories":["ports-mgmt","print"],"annotations":{"FreeBSD_version":"143"},"files":{"/usr/local/bin/indexinfo":"1$0231cd46617eb332e640aec15dee7f273a675e8f9669154d821613232de51c20","/usr/local/sh

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
On 2021-Feb-4, at 16:47, Tatsuki Makino wrote: > Mark Millard wrote on 2021/02/05 09:39: >> >> >> On 2021-Feb-4, at 15:54, Tatsuki Makino >> wrote: >> >>> Is there indexinfo in deps in +MANIFEST extracted from your >>> /usr/local/poud

Re: Bind9 security upgrade

2021-02-06 Thread Mark Millard via freebsd-ports
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin Thus the error that it reported. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.fre

Re: Bind9 security upgrade

2021-02-06 Thread Mark Millard via freebsd-ports
some of the features of C, sed, awk and shell. See the manual page for more hype. There are also many books published by O'Reilly & Assoc. See pod/perlbook.pod for more information. WWW: https://www.perl.org/ === Mark Millard marklmi at yahoo.com ( dsl-only.net went a

Re: Bind9 security upgrade

2021-02-07 Thread Mark Millard via freebsd-ports
/libdialog.so.9 (0x403a5000) libc.so.7 => /lib/libc.so.7 (0x40408000) An incorrectly built dialog4ports will show /usr.lib/libdialog.so.8 instead. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
he FreeBSD servers. But, either way, if I understand right, the warning implies the above (presuming you have not forced a definition of ABI). I'm not sure if a definition of ABI can lead to such notices when it mismatches with the architecture/annotations for pkg. === Mark Mi

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
ial to be distributed to various servers. But I do not know how to track down those times.) Did you happen to to do step 6 before the first FreeBSD:14 ports showed up? If yes, then you were still working against FreeBSD:13 ports from pkg install; if no, then you should have gotten FreeBSD:14 po

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
Steve Kargl sgk at troutmask.apl.washington.edu wrote on Tue Feb 16 02:14:06 UTC 2021 : > On Mon, Feb 15, 2021 at 05:10:54PM -0800, Mark Millard via freebsd-ports > wrote: > > Steve Kargl sgk at troutmask.apl.washington.edu wrote on > > Mon Feb 15 20:39:19 UTC 2021 : > >

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
On 2021-Feb-15, at 20:18, Mark Millard wrote: > Steve Kargl sgk at troutmask.apl.washington.edu wrote on > Tue Feb 16 02:14:06 UTC 2021 : > >> On Mon, Feb 15, 2021 at 05:10:54PM -0800, Mark Millard via freebsd-ports >> wrote: >>> Steve Kargl sgk at troutmask.apl.w

Re: When did pkg(8) drop support for 12-STABLE?

2021-02-23 Thread Mark Millard via freebsd-ports
last February. > > I > > am > > not sure what build you mean by "12-STABLE" > It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, > save > building up to 12.2? You might want to report the output of: # uname -apKU if you can still

Re: When did pkg(8) drop support for 12-STABLE?

2021-02-23 Thread Mark Millard via freebsd-ports
nd.) For stable/13/ and releng/13.*/ and relelase/13.*/ and main (14) and later: snv can no longer be used to get source. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list ht

Re: www/joomla3 is no longer in the FreeBSD pkg repo

2021-03-04 Thread Mark Millard via freebsd-ports
tion 6 indicates that: "This license is governed by the laws of Germany, excluding choice of law rules." I make no claim about any validity of depending on any of the content of the PDFlib-Lite-license.pdf referenced. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early

Re: No update for a day on ports?

2021-04-01 Thread Mark Millard via freebsd-ports
-- George Be careful: Git-svn-cheatsheet.pdf is about how to use git with a svn server, not with a git server: "Cheatsheet for Git as an SVN Client" The "as an SVN Client" is what says that the server involved is an SVN server. === Mark Millard marklmi at yahoo.co

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
.git was effectively renamed to /freebsd/freebsd-ports-legacy/ and a new /freebsd/freebsd-ports/ was created that used "main" instead of "master". === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
On 2021-Apr-2, at 17:41, Mark Millard wrote: > The Doctor doctor at doctor.nl2k.ab.ca wrote on > Sat Apr 3 00:27:42 UTC 2021 : > > Results: > >> gitup -v 1 ports >> # Host: github.com >> # Port: 443 >> # Repository: /freebsd/freebsd-por

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
On 2021-Apr-2, at 18:20, The Doctor wrote: > On Fri, Apr 02, 2021 at 05:54:48PM -0700, Mark Millard via freebsd-ports > wrote: >> >> >> On 2021-Apr-2, at 17:41, Mark Millard wrote: >> >>> The Doctor doctor at doctor.nl2k.ab.ca wrote on >>>

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
x27;s/freebsd\/freebsd-//g' /usr/local/etc/gitup.conf >> >> then do `gitup ports` >> >> Kind Regards, >> Moin >> >>> On 3 Apr, 2021, at 07:20, The Doctor via freebsd-ports >>> wrote: >>> >>> On Fri, Apr 02, 2021 at 05:

Re: No update for a day on ports?

2021-04-03 Thread Mark Millard via freebsd-ports
s is not in control of when useful: http://${SERVERNAME}/s/${SNAPSHOTHASH}.tgz files exist. But there is not much point to having /usr/sbin/portsnap in the file systems once useful versions of such files are no longer available to fetch. === Mark Millard marklmi at yahoo.com ( dsl-

Re: No update for a day on ports?

2021-04-03 Thread Mark Millard via freebsd-ports
Felix Palmen felix at palmen-it.de wrote on Sat Apr 3 20:35:46 UTC 2021 : > * Mark Millard via freebsd-ports [20210403 > 10:02]: > > Felix Palmen felix at palmen-it.de wrote on > > > There was an announcement to deprecate it, but it's still built with > >

Re: gitip usage.

2021-04-04 Thread Mark Millard via freebsd-ports
place. Unlike for src, the ports schedule makes no mention of the likes of "Starting pushing to external mirrors (github, gitlab, etc.)". The following *presumes* such will be done but the status of such in unclear. Once github is updated(?) to be tracking the new ports git repository, you may ha

Read-only https://cgit.freebsd.org/ports/ accessible now; push access not reported as available yet

2021-04-05 Thread Mark Millard via freebsd-ports
ch have happened yet. "2021Q2 quarterly branch created" is listed last. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listi

Re: Any plan to fix ports git main history compatibility with old GitHub master?

2021-04-05 Thread Mark Millard via freebsd-ports
___ 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: Any plan to fix ports git main history compatibility with old GitHub master?

2021-04-05 Thread Mark Millard via freebsd-ports
" that was added to the schedule on 2021-04-05 09:12:09 UTC. That might be what you are waiting for. Still not listed as started, last I looked. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@fr

devel/llvm10 (and 11) on aarch64: only BE_AMDGPU registered targets despite OPTIONS_FILE_SET+=BE_NATIVE also being set

2021-04-08 Thread Mark Millard via freebsd-ports
88ec59866cf2878263e7f3b2 merge-base: CommitDate: 2021-03-12 20:29:42 + 7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all XPT_ASYNC ccbs in a dedicated thread n245444 (--first-parent --count for merge-base) === Mark Millard marklmi at

<    1   2   3   4   5   6   >