Re: 11.0-RC1 unsupported by ports?

2017-01-25 Thread Mark Millard
ted. Currently outdated are OSVERSION < 1003000 (pre 10.3-RELEASE) and 110 <= OSVERSION < 1100122 (from 11-CURRENT'2013 to 11.0-PRERELEASE) I expect these to be kept up to date with base system lifetimes, be updated BEFORE removing any support for outdated release from the tree and

buzilla 214400: is is ports/head/base/binutils that is being reported on, freebsd-powe...@freebsd.org assignee is wrong

2017-03-07 Thread Mark Millard
t back the port version number in the summary. But I can not fix the assignee: it should not be freebsd-powe...@freebsd.org Can you put back the correct assignee for a port problem? === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org ma

FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-12 Thread Mark Millard
completely non-functional for powerpc64 (program crashes via signals reporting problems). === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any m

I had to revert /usr/local/aarch64-freebsd from 2.28 for its bin/ld to work for -r315870 buildworld (adm64 -> arm64 cross build)

2017-03-23 Thread Mark Millard
B${CROSS_BINUTILS_PREFIX} XCXXFLAGS+= -B${CROSS_BINUTILS_PREFIX} # There is no XCPPFLAGS but XCPP gets XCFLAGS content. # XCFLAGS+= -mcpu=cortex-a53 XCXXFLAGS+= -mcpu=cortex-a53 # There is no XCPPFLAGS but XCPP gets XCFLAGS content. # more ~/src.configs/make.conf CFLAGS.gc

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-26 Thread Mark Millard
[I add some what-it-take-for-an-upgrade information.] On 2017-Mar-12, at 6:53 PM, Mark Millard wrote: > Summary: RAM+(peak swap) was about 26 GiBytes. > Also: about 118 GiByte /usr/obj/. . ./llvm40/ area. > (2 processors, 2 cores each, all in use; > WITH

Re: I had to revert /usr/local/aarch64-freebsd from 2.28 for its bin/ld to work for -r315870 buildworld (adm64 -> arm64 cross build)

2017-03-26 Thread Mark Millard
On 2017-Mar-26, at 5:07 AM, Li-Wen Hsu wrote: On Fri, Mar 24, 2017 at 11:31 AM, Mark Millard wrote: > Building /usr/obj/pine64_clang/arm64.aarch64/usr/src/lib/libc/libc.so.7.full > --- libc.so.7.full --- > building shared library libc.so.7 > /usr/local/aarch64-freebsd/bin/ld: ge

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-27 Thread Mark Millard
On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: > On 26 Mar 2017, at 23:36, Mark Millard wrote: >> >> I upgraded from llvm40 r4 to final. An interesting result was >> its creation of a backup package for llvm40-4.0.0.r4: >> >> about 13 cpu-core-hours ru

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-27 Thread Mark Millard
On 2017-Mar-27, at 3:25 AM, Mark Millard wrote: > On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: > >> On 26 Mar 2017, at 23:36, Mark Millard wrote: >>> >>> I upgraded from llvm40 r4 to final. An interesting result was >>> its creation

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-27 Thread Mark Millard
On 2017-Mar-27, at 5:53 AM, Dimitry Andric wrote: > On 27 Mar 2017, at 12:25, Mark Millard wrote: >> >> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >>> On 26 Mar 2017, at 23:36, Mark Millard wrote: > ... >>>> Installed packages to be REMOVED: &g

RE: disk space needs for source based system and ports?

2017-03-29 Thread Mark Millard
m the proper thread topic, feel free to change > the > subject line and respond to freebsd-ports if that is more appropriate, so I > won't be accused of hijacking this thread. Done. === Mark Millard markmi at dsl-only.net ___ freebsd-port

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-30 Thread Mark Millard
On 2017-Mar-29, at 8:53 AM, Brooks Davis wrote: > On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: >> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >> >>> On 26 Mar 2017, at 23:36, Mark Millard wrote: >>>> >>>> I upgraded fr

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-30 Thread Mark Millard
did have a native-clang cross-compiler involved.) [I do not have access to server-class thread counts or RAM either. And the non-multithread stages contribute even in those contexts as well.] So I'm not looking forward to the issue from that point of view. ===

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-30 Thread Mark Millard
On 2017-Mar-30, at 1:22 PM, Mark Millard wrote: > On 2017-Mar-29, at 8:53 AM, Brooks Davis wrote: > >> On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: >>> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >>> >>>> On 26 Mar 2017, at

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-03-31 Thread Mark Millard
On 2017-Mar-30, at 7:51 PM, Mark Millard wrote: > On 2017-Mar-30, at 1:22 PM, Mark Millard wrote: > >> Sounds like the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG technique >> would not change the "WITNESS and INVARIANTS"-like part of the >> issue. In fact if WITH_D

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-04-01 Thread Mark Millard
On 2017-Mar-31, at 4:51 PM, Mark Millard wrote: > On 2017-Mar-30, at 7:51 PM, Mark Millard wrote: > >> On 2017-Mar-30, at 1:22 PM, Mark Millard wrote: >> >>> Sounds like the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG technique >>> would not change the "

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-04-03 Thread Mark Millard
On 2017-Apr-1, at 3:51 AM, Mark Millard wrote: > On 2017-Mar-31, at 4:51 PM, Mark Millard wrote: > >> On 2017-Mar-30, at 7:51 PM, Mark Millard wrote: >> >>> On 2017-Mar-30, at 1:22 PM, Mark Millard wrote: >>> >>>> Sounds like the ALLOW_OPTIM

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-04-05 Thread Mark Millard
o report for installed-size for the no-WITH_DEBUG variant's scale for installed-size. === Mark Millard markmi at dsl-only.net ___ 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"

lang/gcc6-aux build error due to internal Makefile/sh syntax: $${PWDCMD-pwd} is missing a ":"

2017-04-10 Thread Mark Millard
2 stable/11 is supposed to get an MFC for -r316679 in a couple of weeks. -r313772 was from February and has yet to be MFC'd but is needed. No explicit MFC schedule has been set. === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd

Re: lang/gcc6-aux build error due to internal Makefile/sh syntax: $${PWDCMD-pwd} is missing a ":"

2017-04-10 Thread Mark Millard
On 2017-Apr-10, at 12:12 PM, Mark Millard wrote: > Context (on a BPI-M3 arm64 board): I had been thinking of the BPI-M3 for other reasons and typed that instead of the correct: pine64+ 2GB. (True elsewhere as well.) I do really mean arm64 here. > # svnlite info /usr/ports/ | grep &

Re: lang/gcc6-aux build error due to internal Makefile/sh syntax: $${PWDCMD-pwd} is missing a ":" [misidentified problem]

2017-04-10 Thread Mark Millard
On 2017-Apr-10, at 1:21 PM, John Marino wrote: > On 4/10/2017 15:12, Mark Millard wrote: >> On 2017-Apr-10, at 12:12 PM, Mark Millard wrote: >>> with line 875 being the one with: @r=`${PWD_COMMAND}` >>> >>> It appears to me that the notation $${PWDCMD-p

Re: lang/gcc6-aux build error due to internal Makefile/sh syntax: $${PWDCMD-pwd} is missing a ":" [misidentified problem]

2017-04-10 Thread Mark Millard
On 2017-Apr-10, at 5:52 PM, Mark Millard wrote: > On 2017-Apr-10, at 1:21 PM, John Marino wrote: > >> On 4/10/2017 15:12, Mark Millard wrote: >>> On 2017-Apr-10, at 12:12 PM, Mark Millard wrote: >>>> with line 875 being the one with: @r=`${PWD_COMMAND}` >

Re: [Bug 214864] [exp-run] test build with lld as /usr/bin/ld [vs. gcc6-aux but avoiding further polluting the bug with side issues]

2017-04-12 Thread Mark Millard
/show_bug.cgi?id=214864 > > ... > > --- Comment #16 from Pedro F. Giffuni --- > (In reply to Mark Millard from comment #15) > GCC has the nasty habit of "fixing" the system headers according to outdated > expectations. > There is a way to regenerate the headers but

lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-13 Thread Mark Millard
trapping has more problems than just __nonnull and __nonnull_all issues, at least for aarch64 head. lang/gcc6-aux might not be the only thing with such issues. I stopped with this. There could be more issues for lang/gcc6-aux . === Mark Millard markmi at dsl-only.net ___

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-13 Thread Mark Millard
update claiming native aarch64 support for synth and tried to build it. I've no direct interest in lang/gcc6-aux . I just ended up with FYI information about lang/gcc6-aux .] === Mark Millard markmi at dsl-only.net (I've added a missing "n" in the first "__nonnull_all&q

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-14 Thread Mark Millard
o prevent the fixincludes script from running: sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in (End quote) So seems that disabling fixinc.sh's use is fairly common when the headers are known to "not require fixing" (i.e., are known to already be gcc compliant). === M

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-14 Thread Mark Millard
t wrote = write (descriptor, buffer, size); ^ The implicit-declaration warnings for read and write may well also not be expected/desirable. It may be that more than a script run is needed to make things be appropriate. === Mark Millard markmi at dsl-only.net __

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-14 Thread Mark Millard
On 2017-Apr-14, at 6:54 PM, Mark Millard wrote: > Alexander Kabaev kabaev at gmail.com on Sat Apr 15 00:20:40 UTC 2017 > wrote: > . . . > >> it was suggested multiple times that the whole fixinc step is >> ultimately harmful and serves no useful purpose and probably

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-14 Thread Mark Millard
I wanted to explore. I've seen material quoted from a exp-run that reported that about 54(?) ports were then blocked by lang/gcc6-aux not building. (So some problems might not be aarch64 specific despite my example context: the "54" material was likely not for an aarch64 contex

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-15 Thread Mark Millard
On 2017-Apr-15, at 2:30 AM, Mark Linimon wrote: > On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: >> I've seen material quoted from a exp-run that reported >> that about 54(?) ports were then blocked by lang/gcc6-aux >> not building. > > Althoug

FYI: amd64 built with WITH_LLD_IS_LD= vs. devel/libunwind : cannot preempt symbol (for various symbols)

2017-04-16 Thread Mark Millard
${CFLAGS} ${DEBUG_FLAGS} +.else CFLAGS:= ${CFLAGS:N-O*:N-fno-strict*} ${DEBUG_FLAGS} +.endif .if defined(INSTALL_TARGET) INSTALL_TARGET:= ${INSTALL_TARGET:S/^install-strip$/install/g} .endif and use ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG= and WITH_DEBUG= : # more /etc/make.conf WANT_Q

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) [amd64 system ld being lld vs. binutils based]

2017-04-16 Thread Mark Millard
On 2017-Apr-15, at 11:30 PM, Mark Millard wrote: > On 2017-Apr-15, at 2:30 AM, Mark Linimon wrote: > >> On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: >>> I've seen material quoted from a exp-run that reported >>> that about 54(?) ports were th

Re: FYI: amd64 built with WITH_LLD_IS_LD= vs. devel/libunwind : cannot preempt symbol (for various symbols)

2017-04-16 Thread Mark Millard
On 2017-Apr-16, at 1:10 AM, Mark Millard wrote: > Context: amd64 FreeBSD -r316952 as a VirtualBox guest > that was built using WITH_LLD_IS_LD= . ports -r438577. > > x11/xorg-minimal indirectly gets to devel/libunwind and > devel/libunwind fails to build from source: > >

amd64 head -r317015 system clang 4.0 crashes during qt5-widgets "checking" activity: "Wrong prefetch hint in intrinsic: should be 0 or 1" (avx512.cpp)

2017-04-16 Thread Mark Millard
x: /usr/ports/Mk/bsd.port.mk === --- /usr/ports/Mk/bsd.port.mk (revision 436747) +++ /usr/ports/Mk/bsd.port.mk (working copy) @@ -1646,7 +1646,11 @@ STRIP_CMD= ${TRUE} .endif DEBUG_FLAG

amd64 head -r317015 system ports -r438577 : qt5-widgets vs. libQt5Core.so "multiple definition of" for: __bss_start@Qt_5 _edata@Qt_5 _end@Qt_5

2017-04-16 Thread Mark Millard
5697150-7ecd-e111-bb59-0022644237b5 Revision: 436731 Node Kind: directory Schedule: normal Last Changed Author: bdrewery Last Changed Rev: 434651 Last Changed Date: 2017-02-22 15:33:44 -0800 (Wed, 22 Feb 2017) === Mark Millard markmi at dsl-only.net ___

Re: FYI: amd64 built with WITH_LLD_IS_LD= vs. devel/libunwind : cannot preempt symbol (for various symbols)

2017-04-16 Thread Mark Millard
On 2017-Apr-16, at 7:01 PM, Ed Maste wrote: > On 16 April 2017 at 04:10, Mark Millard wrote: >> Context: amd64 FreeBSD -r316952 as a VirtualBox guest >> that was built using WITH_LLD_IS_LD= . ports -r438577. >> >> x11/xorg-minimal indirectly gets to devel/libunwind a

Re: RPI2, www/firefox, error: "NEON support not enabled"

2017-05-05 Thread Mark Millard
3D graphics or gaming. NEON can also accelerate signal processing algorithms and functions to speed up applications such as audio and video processing, voice and facial recognition, computer vision and deep learning. === Mark Millard markmi at dsl-only.net __

Re: RPI2, www/firefox, error: "NEON support not enabled"

2017-05-05 Thread Mark Millard
On 2017-May-5, at 11:28 AM, bob prohaska wrote: > On Fri, May 05, 2017 at 09:30:39AM -0700, Mark Millard wrote: >> >> Wrong neon. >> >> > Ahh, what I feared 8-) > > >> https://developer.arm.com/technologies/neon says: >> > > I di

Re: RPI2, www/firefox, error: "NEON support not enabled"

2017-05-05 Thread Mark Millard
On 2017-May-5, at 4:01 PM, bob prohaska wrote: > On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote: >> >> An rpi2 has Cortex-A7 (armv7-A) cores that have NEON >> but armv6 does not. >> >> There is some possibility that with something like >&g

Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

2017-05-06 Thread Mark Millard
rget"); . . . It appears that there is no kernel debugging supported for TARGET_ARCH=powerpc currently. (The system no longer has its own gdb related materials.) === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list h

Re: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

2017-05-06 Thread Mark Millard
On 2017-May-6, at 5:21 PM, Mark Millard wrote: > On: > > # uname -apKU > FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc powerpc > 1200030 1200030 > > When I attempt to use: > > # which kgdb > /usr/local/bin/kgdb > > that was from bu

Re: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

2017-05-07 Thread Mark Millard
[This update just notes that it appears that combination ${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes is not intended to be used, effectively eliminating "THING #1" of 0-2.] On 2017-May-6, at 10:03 PM, Mark Millard wrote: > On 2017-May-6, at 5:21 PM, Mark Millard wrote: >

Re: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

2017-05-08 Thread Mark Millard
[Mostly: Why THING #2 fails: checks for ET_EXEC but the actual vmcore.* 's have ET_DYN instead.] On 2017-May-8, at 11:30 AM, John Baldwin wrote: > On Saturday, May 06, 2017 10:03:57 PM Mark Millard wrote: >> THING #0: >> >> It appears that usr.sbin/crashinfo/crashin

Re: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

2017-05-08 Thread Mark Millard
[I've submitted bugzilla 219153 for this libvm issue of not handling powerpc's/powerp64's ET_DYN vmcore.* 's and such.] On 2017-May-8, at 1:18 PM, Mark Millard wrote: > [Mostly: Why THING #2 fails: checks for ET_EXEC > but the actual vmcore.* 's have ET_DYN inst

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-10 Thread Mark Millard
looking at some vintage of config/rules.mk on the web): $(SOBJS): $(REPORT_BUILD) $(AS) -o $@ $(DEFINES) $(ASFLAGS) $($(notdir $<)_FLAGS) $(LOCAL_INCLUDES) -c $< then the -mcpu=cortex-a7 is likely not involved. Instead such a context would suggest needing to supply some o

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-11 Thread Mark Millard
On 2017-May-10, at 10:31 PM, Mark Millard wrote: > On 2017-May-10, at 8:37 PM, bob prohaska wrote: > >> With freebsd at >> FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #50 r318138: Wed May >> 10 10:30:51 PDT 2017 b...@www.zefox.com:/usr/obj/usr/src/sy

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-11 Thread Mark Millard
On 2017-May-11, at 6:44 PM, bob prohaska wrote: > On Thu, May 11, 2017 at 01:53:33PM -0700, Mark Millard wrote: >> >> It would help others help you if the assembler or >> compiler command that specifically generated this >> error message was also included in the text

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-11 Thread Mark Millard
On 2017-May-11, at 7:16 PM, Mark Millard wrote: > On 2017-May-11, at 6:44 PM, bob prohaska wrote: > >> On Thu, May 11, 2017 at 01:53:33PM -0700, Mark Millard wrote: >>> >>> It would help others help you if the assembler or >>> compiler command tha

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread Mark Millard
On 2017-May-12, at 12:31 PM, bob prohaska wrote: > On Thu, May 11, 2017 at 08:14:14PM -0700, Mark Millard wrote: >> Having -mcpu=cortex-a7 in ASFLAGS would contribute to >> both of the examples. >> > > Restarting the make with > root@www:/usr/ports/www/firefox

Re: www/firefox on RPI2: error: instruction requires: armv6t2

2017-05-12 Thread Mark Millard
On 2017-May-12, at 5:34 PM, bob prohaska wrote: > On Fri, May 12, 2017 at 02:36:48PM -0700, Mark Millard wrote: >> >> My guess from the above is that the problem will >> repeat in this rebuild. >> >> >> > That'

RE: The future of portmaster [and of ports-mgmt/synth]

2017-05-30 Thread Mark Millard
out progressing to the ino64 changes in FreeBSD's head (12-CURRENT). Unfortunately ports-mgmt/synth suffers from build prerequisites that do not have a wide range of contributing maintainers or otherwise broad support. This looks like it will make ports-mgmt/synth problematical as things are

Re: The future of portmaster [and of ports-mgmt/synth]

2017-05-30 Thread Mark Millard
On 2017-May-30, at 1:06 PM, Mark Linimon wrote: > On Tue, May 30, 2017 at 12:00:14PM -0700, Mark Millard wrote: >> Kevin Oberman rkoberman at gmail.com wrote on Tue May 30 16:52:19 UTC 2017 >> >>> I really suggest that you look at synth. > > synth is curren

Re: bapt@ back on portmgr

2017-06-09 Thread Mark Millard
builds for DragonFly BSD. (DragonFly forked from FreeBSD back in FreeBSD-4.x time frames.) So updates appropriate to FreeBSD's head driven by just upstream activity would not seem likely. === Mark Millard markmi at dsl-only.net ___ freebsd-ports@f

lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-24 Thread Mark Millard
area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-26 Thread Mark Millard
ng which specific handling needs to be made. But the vm_ooffset_t and vm_pindex_t changes did not even make the UPDATING notes. Right now things look to have the worst combination for lang/gcc* when release/11.1.0/ becomes official: lang/gcc* 's break without notification or suggestion of a workaro

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-28 Thread Mark Millard
l need whatever technique is used. Some, such as lang/gcc6-aux, need more done because of binary bootstrap materials being downloaded and used and so the build of lang/gcc6-aux gets the problem and fails before staging happens: the binary-bootstrap materials need to avoid the adjusted headers th

/usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi)

2017-06-28 Thread Mark Millard
81000 0x1000>, <0x01C82000 0x2000>, <0x01C84000 0x2000>, <0x01C86000 0x2000>; interrupts = ; }; I'll be trying 3 other u-boot-*'s so I may have more to report later. === Mark Millard mar...@d

Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi)

2017-06-28 Thread Mark Millard
On 2017-Jun-28, at 7:44 PM, Mark Millard wrote: > Is the below a BSDL vs. GPL DTS issue? > > In my attempt to build sysutils/u-boot-pine64 I got: > > OBJCOPY u-boot.srec > OBJCOPY u-boot-nodtb.bin > start=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-29 Thread Mark Millard
On 2017-Jun-29, at 3:10 AM, Gerald Pfeifer wrote: > Am 28. Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard dsl-only.net>: >> A primary test is building lang/gcc5-devel under release/11.0.1 >> and then using it under stable/11 or some draft of release/11.1.0 . > >

It looks like USE_GCC=any is broken and leads to system-clang use

2017-07-02 Thread Mark Millard
[It looks like USE_GCC=any is broken and leads to system-clang use.] On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote: > Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard > : >> I'm not currently set up to run more than head on >> any of amd64, powerpc64, power

Re: It looks like USE_GCC=any is broken and leads to system-clang use

2017-07-02 Thread Mark Millard
[Looks like output from "make test-gcc" is appropriate, so I'm adding such.] On 2017-Jul-2, at 7:53 PM, Mark Millard wrote: > [It looks like USE_GCC=any is broken and leads to system-clang use.] > > On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote: > >> Am

Re: It looks like USE_GCC=any is broken and leads to system-clang use

2017-07-02 Thread Mark Millard
[More on the behavior: it is more complicated than previously shown.] On 2017-Jul-2, at 8:12 PM, Mark Millard wrote: > [Looks like output from "make test-gcc" is appropriate, > so I'm adding such.] > > On 2017-Jul-2, at 7:53 PM, Mark Millard wrote: > >>

Re: head -r320192 vs. devel/aarch64-xtoolchain-gcc and devel/aarch64-binutils (/usr/ports -r443557): "liblto_plugin.so: error loading plugin: Service unavailable" for .pico link

2017-08-10 Thread Mark Millard
: libc.so.7 => /lib/libc.so.7 (0x800825000) # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 447082 Last Changed Rev: 447082 === Mark Millard markmi at

head -r322287 buildworld vs. devel/aarch64-xtoolchain-gcc devel/aarch64-binutils devel/aarch64-gcc: Error: selected processor does not support

2017-08-10 Thread Mark Millard
o/openssl/crypto/ecdsa /usr/src/crypto/openssl/crypto/engine /usr/src/crypto/openssl/crypto/err /usr/src/crypto/openssl/crypto/evp /usr/src/crypto/openssl/crypto/hmac /usr/src/crypto/openssl/crypto/idea /usr/src/crypto/openssl/crypto/kr b5 /usr/src/crypto/openssl/crypto/lhash /usr/src/crypto/openssl/crypto/md4 /usr/src/crypto/openssl/crypto/md5 /usr/src/crypto/openssl/crypto/mdc2 /usr/src/crypto/openssl/crypto/modes /usr/src/crypto/openssl/crypto/objects /usr/src/crypto/openssl/crypto/ocsp /usr/src/crypto/openssl/crypto/pem /usr/src/crypto/openssl/crypto/pkcs12 /usr/src/crypto/openssl/crypto/pkcs7 /usr/src/crypto/openssl/crypto/pqueue /usr/src/crypto/openssl/crypto/rand /usr/src/crypto/openssl/crypto/rc2 /usr/src/crypto/openssl/crypto/rc4 /usr/src/crypto/openssl/crypto/rc5 /usr/src/crypto/openssl/crypto/ripemd /usr/src/crypto/openssl/crypto/rsa /usr/src/crypto/openssl/crypto/seed /usr/src/crypto/openssl/crypto/sha /usr/src/crypto/openssl/crypto/srp /usr/src/crypto/openssl/crypto/stack /usr/src/crypto/openssl/crypto/ts /usr/src/crypto/openssl/crypto/txt_db /usr/src/crypto/openssl/crypto/ui /usr/src/crypto/openssl/crypto/whrlpool /usr/src/crypto/openssl/crypto/x509 /usr/src/crypto/openssl/crypto/x509v3 /usr/src/secur e/lib/libcrypto/man' *** [secure/lib/libcrypto__L] Error code 2 === Mark Millard markmi at dsl-only.net ___ 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"

FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-30 Thread Mark Millard
mu-user-static are broken. === Mark Millard markmi at dsl-only.net ___ 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: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-30 Thread Mark Millard
On 2017-Aug-30, at 4:00 AM, Mark Linimon wrote: > On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: >> It appears that qemu-ppc64-static and qemu-ppc-static from >> emulators/qemu-user-static are broken. > > Correct, and known for some time. (fwiw sparc64 h

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-30 Thread Mark Millard
On 2017-Aug-30, at 4:32 PM, Don Lewis wrote: > On 30 Aug, Mark Millard wrote: >> On 2017-Aug-30, at 4:00 AM, Mark Linimon wrote: >> >>> On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: >>>> It appears that qemu-ppc64-static and qemu-ppc-static

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-31 Thread Mark Millard
[Turns out that the emulated program counter is not progressing for syscall emulation, at least for syscall falure cases.] On 2017-Aug-30, at 8:43 PM, Mark Millard wrote: > On 2017-Aug-30, at 4:32 PM, Don Lewis wrote: > >> On 30 Aug, Mark Millard wrote: >>> On 2017-Aug

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-31 Thread Mark Millard
e PC is not being adjusted now but needs to be adjusted. === Mark Millard markmi at dsl-only.net On 2017-Aug-31, at 12:13 PM, Mark Millard wrote: [Turns out that the emulated program counter is not progressing for syscall emulation, at least for [some] syscall [failure] cases.] On 2017-Aug-30

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

2017-08-31 Thread Mark Millard
[I show some of the target/ppc/translate.c source code and related material this time. Not that I know enough to patch it correctly.] On 2017-Aug-31, at 12:13 PM, Mark Millard wrote: > [Turns out that the emulated program counter is not progressing > for syscall emulation, at least for

x11/pixman vs. clang 5 arm assembler handling: "error: unknown directive" and the like

2017-09-05 Thread Mark Millard
ORTED_VARS+= OPSYS .if !defined(_OSRELEASE) -_OSRELEASE!= ${UNAME} -r +_OSRELEASE!= echo 12.0-CURRENT .endif _EXPORTED_VARS+= _OSRELEASE === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list https://li

Re: x11/pixman vs. clang 5 arm assembler handling: "error: unknown directive" and the like

2017-09-05 Thread Mark Millard
On 2017-Sep-5, at 1:13 PM, Jan Beich wrote: > Mark Millard writes: > >> In an experiment with building some arm ports via poudriere >> cross building on amd64 I got the following. It appears that >> clang does not handle all the assembler notation and a >> differ

Re: x11/pixman vs. clang 5 arm assembler handling: "error: unknown directive" and the like

2017-09-05 Thread Mark Millard
On 2017-Sep-5, at 1:33 PM, Mark Millard wrote: > On 2017-Sep-5, at 1:13 PM, Jan Beich wrote: > >> Mark Millard writes: >> >>> In an experiment with building some arm ports via poudriere >>> cross building on amd64 I got the following. It appears th

x11-toolkits/qt5-gui vs. arm.armv6 build via poudriere cross build: fails (undefined references) and odd mix of "clang++" vs. "/nxb-bin/usr/bin/c++"

2017-09-05 Thread Mark Millard
f the places: # Get the operating system type .if !defined(OPSYS) -OPSYS!=${UNAME} -s +OPSYS!=echo FreeBSD .endif _EXPORTED_VARS+=OPSYS .if !defined(_OSRELEASE) -_OSRELEASE!= ${UNAME} -r +_OSRELEASE!= echo 12.0-CURRENT .endif _EXPORTED_VARS+=_OSRELEASE =

Could someone see about possibly applying the patch(s) from bugzilla 216816 so arm qt5 builds can work? (includes patching bsd.qt.mk)

2017-09-06 Thread Mark Millard
ports of the problem(s), noted as duplicates of the bugzilla that has the patches at this point. === Mark Millard markmi at dsl-only.net ___ 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"

kernel-toolchain did not create stdint.h for amd64 -> arm64.aarch64 head -r323246 cross build so buildkernel failed

2017-09-08 Thread Mark Millard
/usr/src/sys/modules/armv8crypto/../Makefile.inc /usr/src/share/mk/bsd.own.mk /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.linker.mk /usr/src/sys/conf/kern.opts.mk /usr/src/sys/conf/config.mk /usr/src/share/mk/bsd.links.mk /usr/src/share/mk/bsd.dep.mk /usr/src/share/mk/bs

Re: head -r324071 system clang 5 based powerpc64 building ports: lang/gcc7 messed up by a matching name vec_step? [vec_step macro name in gcc7's altivec.h]

2017-09-29 Thread Mark Millard
[Looks like gcc7 might be causing its own problem via a vec_step macro name in its altivec.h .] On 2017-Sep-29, at 1:14 AM, Mark Millard wrote: > I attempted a poudriere based build of some > ports and the gcc7 build involved failed > with the following sorts of notices: > >

Re: head -r324071 system clang 5 based powerpc64 building ports: lang/gcc7 messed up by a matching name vec_step? [vec_step macro name in gcc7's altivec.h]

2017-09-29 Thread Mark Millard
Summary of later additions: devel/powerpc64-gcc has the same problem as gcc7 in this clang-based powerpc64. My note about using gcc 4.2.1 for the kernel build was wrong. (My 32-bit powerpc builds are that way, not the powerpc64 ones.) On 2017-Sep-29, at 1:51 AM, Mark Millard wrote: > [Lo

head -r324071 system clang 5 based powerpc64 building ports: x11-toolkit/qt5-gui gets "clang++: error: unknown argument: '-mminimal-toc'"

2017-09-29 Thread Mark Millard
ARGET:= ${INSTALL_TARGET:S/^install-strip$/install/g} .endif (Note: I've had problems with some ${UNAME} use returning empty strings, which is why I've used echo as a replacement in places. The real point for the above is the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG use.) === Mar

Re: head -r324071 system clang 5 based powerpc64 building ports: lang/gcc7 messed up by a matching name vec_step? [renaming in tree-vect-loop.c avoids the issue]

2017-10-01 Thread Mark Millard
2017-Sep-29, at 12:14 PM, Mark Millard wrote: > Summary of later additions: > > devel/powerpc64-gcc has the same problem as gcc7 > in this clang-based powerpc64. > > My note about using gcc 4.2.1 for the kernel > build was wrong. (My 32-bit powerpc builds > are that way

lang/pdflib: I've submitted bugzilla 222722 with a patch for allowing lang/pdflib to build under __POWERPC__

2017-10-01 Thread Mark Millard
*/ > > +#if 0 > #if (defined macintosh || defined __POWERPC__ || defined __CFM68K__) && \ > !defined MAC && !defined MACOSX && !defined __BEOS__ > #define MAC > +#endif > #endif > > /* === Mark Millard markmi at dsl-only.net _

devel/llvm40 and llvm50 builds vs. powerpc (32-bit) FreeBSD: "Host compiler appears to require libatomic, but cannot find it."

2017-10-02 Thread Mark Millard
THOUT_GCC_IS_CC= WITHOUT_GNUCXX= # NO_WERROR= # # Use WERROR to avoid stopping at the likes of: # error: implicit conversion from 'int' to 'int8_t' (aka 'signed char') changes value from 128 to -128 [-Werror,-Wconstant-conversion] WERROR= MALLOC_PRODUCT

Re: Cross compiling GCC for aarch64

2017-10-09 Thread Mark Millard
correctly you are looking more for (B) and (C) not being distinct. Or am I wrong and you want(?): (A) to be a amd64 (i386?) FreeBSD 11.1 context (B) to be amd64(?) FreeBSD 12 for cross compiling to aarch64 FreeBSD 12 and used to produce an aarch64 compiler for use on aarch64 FreeBSD 12

Re: Cross compiling GCC for aarch64

2017-10-10 Thread Mark Millard
On 2017-Oct-9, at 11:22 PM, Tarjei Jensen wrote: >> On Mon, Oct 9, 2017 at 11:26 PM, Mark Millard wrote: >> Tarjei Jensen tarjei99 at gmail.com wrote on >> Mon Oct 9 17:16:41 UTC 2017 : >> >> > This does NOT concern making a cross compiler. It is about cross

Re: ports: pkg-static: "x86_64-unknown-freebsd" versus "x86_64-portbld-freebsd"

2017-10-15 Thread Mark Millard
6 2017 /usr/local/bin/powerpc64-unknown-freebsd12.0-gcov-tool Something like this might be involved in your context? === Mark Millard markmi at dsl-only.net ___ 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"

armv7 perl5.24 build gets dt_modtrace:/. . ./dt_link.c(814): DOODAD and prepare_elf32:/. . ./dt_link.c(235): DOODAD notices; Context: head -r324743

2017-10-24 Thread Mark Millard
-mcpu=cortex-a7 (buildworld, buildkernel, and ports builds). === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-uns

Re: SF mastersites

2017-10-28 Thread Mark Millard
s for "make" can disagree. The one in the environment in question needs to be consulted unless one knows an alternate name as used in an alternate environment. So many standards to choose from. . . === Mark Millard markmi at dsl-only.net _

Re: [Bug 223383] pathconf querying for posix_falloc not supported on freebsd [devel/llvm*'s lld's are also broken by this for zfs and need updating]

2017-11-09 Thread Mark Millard
rns EINVAL to > indicate that the operation is not supported. (I think this is a strange > choice of errno on the part of POSIX.) > > PR: 223383, 223440 > Reported by: Mark Millard > Sponsored by: The FreeBSD Foundation > > Changes: > _U stable/11/ >

building ports (well, pkg) and make -j (even -j1 ) on a fast and64 machine: builds fail (head -r325997 context)

2017-11-22 Thread Mark Millard
T r325997M amd64 amd64 1200054 1200054 # more /etc/make.conf WANT_QT_VERBOSE_CONFIGURE=1 # DEFAULT_VERSIONS+=perl5=5.24 gcc=7 WRKDIRPREFIX?=/wrkdirs # # From a local /usr/ports/Mk/bsd.port.mk extension: ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG= # .if ${.CURDIR:M*/devel/llvm*} #WITH_DEBUG= .elif ${.CURDI

poudriere-devel -S SRCPATH : no longer supported? (/usr/ports/ -r454407 vintage example)

2017-11-22 Thread Mark Millard
usr/src/.cpignore ]; then cpdup -i0 ${cpignore_flag} ${SRC_BASE} ${JAILMNT}/usr/src SRC_BASE="${JAILMNT}/usr/src" It leaves me wondering if some notation like: ${SRCPATH:-${JAILMNT}}/usr/src should be in use in some places where ${JAILMNT}/usr/src is now in use. I&#x

Re: poudriere-devel -S SRCPATH : no longer supported? (/usr/ports/ -r454407 vintage example)

2017-11-22 Thread Mark Millard
[Dumb typo in my } placements.] On 2017-Nov-22, at 8:36 PM, Mark Millard wrote: > As evidence only two lines of jail.sh reference SRCPATH > other than where -S assigns to it: > > # grep "SRCPATH" /usr/local/share/poudriere/jail.sh > [ -z "${SRCP

Re: Welcome flavors! portmaster now dead? synth?

2017-12-02 Thread Mark Millard
ut copies of such world builds on the target device and used it with poudriere on that device as well. Thus the BPI-M3 did not have to do its own buildworld for poudriere use in its jail when I tried local port builds via poudriere. === Mark Millard markmi at dsl-only.net ___

Re: Welcome flavors! portmaster now dead? synth?

2017-12-03 Thread Mark Millard
.9 and later • FreeBSD/amd64 Release 11 and later • Linux/x86-64 (glib 2.6.32-based) (I listed the contents of the 3 boxes in right-box to left-box order.) === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing

poudriere jail -c -j JNAME -m null -M PREBUILT-WORLD-PATH -S /usr/src -v 12.0-CURRENT complains about "DIrectory not empty" for PREBUILT-WORLD-PATH

2017-12-03 Thread Mark Millard
err 1 "Cannot use / for -M" fi . . . SRC_BASE="${JAILMNT}/usr/src" case ${METHOD} in . . . null) JAILFS=none FCT= ;; esac

Re: poudriere jail -c -j JNAME -m null -M PREBUILT-WORLD-PATH -S /usr/src -v 12.0-CURRENT complains about "DIrectory not empty" for PREBUILT-WORLD-PATH

2017-12-04 Thread Mark Millard
On 2017-Dec-4, at 3:54 PM, Bryan Drewery wrote: > On 12/3/2017 8:29 PM, Mark Millard wrote: >> Note: /usr/ports/ (and so poudriere-devel) as of -r425204 >> (poudriere-devel-3.2.99.20171129). >> >> I expect that the below is from ports-mgmt/poudriere-=devel >>

32-bit powerpc system-clang based builds of devel/llvm40 and devel/llvm50: fails via "Host compiler appears to require libatomic, but cannot find it"

2017-12-05 Thread Mark Millard
lite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 455204 Last Changed Rev: 455204 === Mark Millard markmi at dsl-only.net ___

32-bit powerpc lang/ruby23 build fails: [BUG] Segmentation fault

2017-12-05 Thread Mark Millard
src/sys/modules/dtb/allwinner/Makefile M /usr/src/sys/powerpc/aim/mmu_oea64.c M /usr/src/sys/powerpc/ofw/ofw_machdep.c M /usr/src/sys/powerpc/powerpc/interrupt.c M /usr/src/sys/powerpc/powerpc/mp_machdep.c M /usr/src/sys/powerpc/powerpc/trap.c

Re: 32-bit powerpc system-clang based builds of devel/llvm40 and devel/llvm50: fails via "Host compiler appears to require libatomic, but cannot find it"

2017-12-05 Thread Mark Millard
r/lib/crtend.o /usr/lib/crtn.o /tmp/cpp_atomic_64_test-1fa999.o: In function `main': cpp_atomic_64_test.cpp:(.text+0xa8): undefined reference to `__atomic_load_8' clang++: error: linker command failed with exit code 1 (use -v to see invocation) > On Tue, Dec 05, 2017 at 10:42:49AM -080

powerpc64 & system-clang vs. building the likes of lang/gcc7 (at least): vec_step name pollution causes compile failures, should gcc7 source code avoid the name?

2017-12-05 Thread Mark Millard
e of some other lang/gcc*'s: I just happen to build lang/gcc7 but not the others (generally). Context details: # uname -apKU FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r326192M powerpc powerpc64 1200054 1200054 # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head R

For armv7 (cross build target): multimedia/libvpx depends on the GNU C library function getauxval and so fails to build; so, disable its expectation?

2017-12-06 Thread Mark Millard
sl/crypto/armcap.c:if (getauxval != NULL) { /usr/src/crypto/openssl/crypto/armcap.c:if (getauxval(HWCAP) & HWCAP_NEON) { /usr/src/crypto/openssl/crypto/armcap.c:unsigned long hwcap = getauxval(HWCAP_CE); === Mark Millard markmi at dsl-only.net ___

rpi2 V1.1 vs. hard coded max_execution_time figures in /usr/local/share/poudriere/common.sh (package; also: extract, install, deinstall)

2017-12-19 Thread Mark Millard
0 0 0 100%/dev (/dev/da0p1 has a UFS file system.) # swapinfo Device 1K-blocks UsedAvail Capacity /dev/da0p2157286416876 1555988 1% === Mark Millard markmi at dsl-only.net ___ freebsd-ports@fre

<    1   2   3   4   5   6   >