teway to incorporate
the delivery of the packages to intended targets :)
Mostly asking to make sure if this is something to be expected, glitch in
some
ports or possibly a bug.
-Reko
_______
freebsd-ports@freebsd.org mailing list
https://lists.freeb
==
===
===
===
. . .
So I diff'd the logs and found the following (selective extraction):
(- for amd64 -> armv7; + for armv7)
bin/csh
> -UNAME_p=armv7
> -UNAME_m=arm
> -ABI_FILE=/usr/lib/crt1.o
> +SHELL=/bin/sh
>
> The SHELL's I expected but the other 3 lines I did not.
> But the 3 lines may only occur under qemu-user-static
> style use.
>
> -QEMU_EMULATING=1
>
> Expected
version: 3.2.99.20181024
>>
>> This is was expected but may mean that I need to wait
>> until the armv7 has 3.2.99.20181024 and I try via
>> it.
>>
>> -SHELL=/bin/csh
>> -UNAME_p=armv7
>> -UNAME_m=arm
>> -ABI_FILE=/usr/lib/crt1.o
>>
for armv6 or armv7 in MACHINE_ARCH .]
>
> r319861 doesn't look related here.
I think that you are right.
The fallout logs do show the -O2 for armv6 and armv7
use though, not the -O use.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
E_ARCH] :C to "amd64"
Modifier pattern: "arm(v[67])?(eb)?"
Modifier pattern: "arm"
Result[MACHINE_ARCH] of :C is "amd64"
Applying[MACHINE_ARCH] :C to "amd64"
Modifier pattern: "powerpc(64|spe)"
Modifier pattern: "powerpc"
Result[MACHI
ch.inc.mk:.include "Makefile.${MACHINE_ARCH}"
/usr/src/share/mk/local.meta.sys.mk:.if empty(MACHINE_ARCH)
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "sparc64"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "powerpc"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "powerpcspe"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "powerpc64"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "sparc64"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "powerpc"
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH} == "sparc64"
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Mmips*el*} != ""
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Mmips64*} != ""
/usr/src/share/mk/bsd.cpu.mk:. elif ${MACHINE_ARCH:Mmipsn32*} != ""
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Mmips*hf}
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Marmv6*} != ""
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Marmv7*} != ""
/usr/src/share/mk/bsd.cpu.mk:. if ${MACHINE_ARCH:Marmv[67]*} == ""
/usr/src/share/mk/bsd.cpu.mk:.if ${MACHINE_ARCH:Marmv[67]*} && defined(CPUTYPE)
&& ${CPUTYPE:M*soft*} != ""
/usr/src/share/mk/bsd.cpu.mk:.if ${MACHINE_ARCH} == "powerpcspe"
/usr/src/share/mk/bsd.cpu.mk:.if ${MACHINE_ARCH:Mriscv*sf}
/usr/src/share/mk/bsd.endian.mk:.if ${MACHINE_ARCH} == "aarch64" || \
/usr/src/share/mk/bsd.endian.mk:.elif ${MACHINE_ARCH} == "powerpc" || \
/usr/ports/Mk/Uses/gnustep.mk:.if ${MACHINE_ARCH} == "i386"
(I have not tried to figure out which have a chance of
executing before the MACHINE_ARCH explicit assignment.)
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
way in early 2018-Mar)
___________
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"
ss-build that
> had worked.)
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
rmv7 cross build structure have been using
-O2 for a long time. This may challenge the use of
-O by default in CFLAGS for armv6 and armv7, in that -O2
has been under an implicit test for as long as the
cross build structure has been used with share/mk/sys.mk
having the MACHINE_ARCH based selection
.libs/libpixman-
arm-simd.a ./.libs/libpixman-arm-neon.a -Wl,--no-whole-archive -lm -O
-mcpu=cortex-a7 -g -pthread -pthread -Wl,-soname -Wl,libpixman-1.so.0 -o
.libs/libpixman-1.so.0.34.0
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
X*ABS*
a7b0 R_ARM_V4BX*ABS*
a8cc R_ARM_V4BX *ABS*
000105a0 R_ARM_V4BX*ABS*
00010db8 R_ARM_V4BX*ABS*
00011274 R_ARM_V4BX *ABS*
00011808 R_ARM_V4BX *ABS*
>From this one I show the end of a routine that does not get the
R_ARM_V4BX *ABS* relocation record:
04e8 vst1.16
{d28[1]}, [r2]!
04ec mov r0, r7
04f0 add r2, r2, r3, lsl
#1
04f4 add r4, r4, r5, lsl
#2
04f8 sub r2, r2, r0, lsl
#1
04fc sub r4, r4, r0, lsl
#2
0500 subs r1, r1, #1, 0
0504 mov r6, r2
0508 bge 03ac
050c pop {r4, r5, r6,
r7, r8, r9, sl, fp, ip, pc}
0510 push {r4, r5, r6, r7, r8,
r9, sl, fp, ip, lr}
No "bx lr" involved.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
some installs etc, I'm
just going to blacklist the unnecessary ports which aren't used or linked,
in order to make the Poudriere build process meaner and leaner.
-Reko
_______
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/m
F .text .hidden
> pixman_composite_out_reverse_8_0565_asm_neon
> d528 g F .text .hidden
> pixman_composite_out_reverse_8__asm_neon
> d980 g F .text .hidden
> pixman_scaled_nearest_scanline_8888__OVER_asm_neon
> e008 g
native build vs. cross building. So far
the effort has just eliminated various ideas for
possibilities.
(It also lead to the poudriere/nxb-bin/ discovery of the
-O2 vs. -O sys.mk code not picking the intended -O for arm*,
including armv6 and armv7.)
===
Mark Millard
marklmi at yahoo.com
( dsl-on
x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such file
or directory'
access("/usr/local/sbin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No
such file or directory'
access("/usr/local/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such
file or directory'
access("/usr/home/markmi/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2
'No such file or directory'
(Note: It actually explicitly tries to use the x86_64 assembler if it
does not find an armv7 or a generically pathed one. The generically
pathed ones would normally also be x86_64 ones.)
Another thing of note (using aarch64 as an example):
/usr/local/aarch64-unknown-freebsd13.0/bin/as
does not appear to be someplace that clang would find as
but is a place devel/aarch64-binutils puts one.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
cal/sbin/as",X_OK|R_OK) ERR#2 'No such file or
> directory'
> access("/usr/local/bin/as",X_OK|R_OK) ERR#2 'No such file or
> directory'
> access("/usr/home/markmi/bin/as",X_OK|R_OK)ERR#2 'No such file or
> dir
.0-gnueabihf-as",X_OK|R_OK)
>> ERR#2 'No such file or directory'
>> access("/usr/home/markmi/bin/armv7-unknown-freebsd13.0-gnueabihf-as",X_OK|R_OK)
>> ERR#2 'No such file or directory'
>> access("/sbin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/bin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/usr/sbin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/usr/bin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/usr/local/sbin/as",X_OK|R_OK)ERR#2 'No such file or
>> directory'
>> access("/usr/local/bin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/usr/home/markmi/bin/as",X_OK|R_OK) ERR#2 'No such file or
>> directory'
>> access("/sbin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such file
>> or directory'
>> access("/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such file
>> or directory'
>> access("/usr/sbin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such
>> file or directory'
>> access("/usr/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No such
>> file or directory'
>> access("/usr/local/sbin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No
>> such file or directory'
>> access("/usr/local/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2 'No
>> such file or directory'
>> access("/usr/home/markmi/bin/x86_64-unknown-freebsd13.0-as",X_OK|R_OK) ERR#2
>> 'No such file or directory'
>>
>> (Note: It actually explicitly tries to use the x86_64 assembler if it
>> does not find an armv7 or a generically pathed one. The generically
>> pathed ones would normally also be x86_64 ones.)
>>
>>
>> Another thing of note (using aarch64 as an example):
>>
>> /usr/local/aarch64-unknown-freebsd13.0/bin/as
>>
>> does not appear to be someplace that clang would find as
>> but is a place devel/aarch64-binutils puts one.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ompiler/linker
> is producing something bad from well-defined code.)
>
>
> Bryan Drewery is now aware of the odd -O2 vs. -O
> behavior under poudriere-devel/qemu-arm-static/nxb-bin/
> amd64 -> armv7 cross builds and likely it will be
> fixed at some point.
>
> But the
"/usr/local/bin/as",X_OK|R_OK)ERR#2 'No such file or
>>> directory'
>>> access("/usr/home/markmi/bin/as",X_OK|R_OK) ERR#2 'No such file or
>>> directory'
>>> access("/sbin/x86_64-unknown-freebsd13.0-a
1.1.1.a [poudriere-php56-openssl111]
Number of packages to be downgraded: 1
Proceed with this action? [Y/n]:
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-p
porters handbook and
changing DIST to PORT.
-Reko
[1]
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html
-Original Message-
From: Reko Turja via freebsd-ports
Sent: Wednesday, November 21, 2018 9:17 PM
To: po...@freebsd.org
Subject: Re: Upgrade of
i Nov 9
19:30:13 PST 2018
markmi@FBSDFSSD:/usr/obj/powerpc64vtsc_xtoolchain-gcc/powerpc.powerpc64/usr/src/powerpc.powerpc64/sys/GENERIC64vtsc-NODBG
powerpc powerpc64 133 133
Right now it looks like the poudriere run still has 3+ hours to
go for the rest of the ports to build.
=
r *c[]) = filter_sobel;
The error reported is:
Assertion failed: (isSimple() && "Expected a SimpleValueType!"), function
getSimpleVT, file /usr/src/contrib/llvm/include/llvm/CodeGen/ValueTypes.h, line
254.
Abort trap (core dumped)
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Can someone commit PR#233390
___
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"
an provide those changes/patches if
you'd like to upgrade to PHP7 before the upstream code is ready.
I would also love the preliminary patches for getting Maia to work on PHP7+
Thank you in advance,
Reko
_______
freebsd-ports@freebsd.org mai
go !
___
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"
ilable for testing.
Sounds good, thank you for your work on ports!
-Reko
_______
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"
.00pm
___
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"
gt; > https://download.FreeBSD.org/ftp/snapshots/amd64/amd64/12.0-STABLE/base.txz
> > [00:00:02] Error while creating jail, cleaning up.
> > [00:00:02] Removing 12amd64 jail... done
> > [00:00:04] Cleaning 12amd64 data... done
>
> What did I wrong ?
Try
poudriere jail -
reebsd.org/bugzilla/
Start your bug report summary with "lang/vala: " so that the port maintainer
automatically gets notification of the report and anyone can find your PR
easily.
Lorenzo Salvadore.
_______
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"
ints as the default gcc* is changed. (I sometimes experiment with
more modern tools for targeting powerpc families.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-ports@freebsd.org mailing list
https://lists.fre
itory UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 484783
Last Changed Rev: 484783
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ch64-static wc //dev/null
is hanging-up (again).
Given that these are hangups I'll note that this is a Ryzen
Threadripper 1950X context and is running under Hyper-V from
Windows 10's 1809 update. I gave it 28 logical processors and
have it to have the virtual NUMA topology match the topo
x601d2ec0 in _thr_umtx_timedwait_uint (mtx=0x861027008,
id=, clockid=, abstime=,
shared=)
at /usr/src/lib/libthr/thread/thr_umtx.c:236
#2 0x601dc6f8 in cond_wait_user (cvp=, mp=0x860515b00,
abstime=0x0, cancel=1) at /usr/src/lib/libthr/thread/thr_cond.c:307
#3 cond_wait_common (cond=, mutex=, abstime=0x0,
cancel=1) at /usr/src/lib/libthr/thread/thr_cond.c:367
#4 0x601438bc in qemu_futex_wait (ev=, val=4294967295)
at util/qemu-thread-posix.c:350
#5 qemu_event_wait (ev=0x62735d10 ) at
util/qemu-thread-posix.c:445
#6 0x6014a92a in call_rcu_thread (opaque=) at
util/rcu.c:255
#7 0x601dc376 in thread_start (curthread=0x860518e00) at
/usr/src/lib/libthr/thread/thr_create.c:291
#8 0x in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffdfdfc000
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
96 0 IJ 11:43 0:00.07 | |
`-- /usr/local/bin/qemu-arm-static ninja -j28 -v all
root 415850.0 0.0 102848 25056 0 IJ 11:43 0:00.10 | |
|-- /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E
cmake_autogen /wrkdirs/usr/ports/multimedia/g
root 415860.0 0.0 102852 25072 0 IJ 11:43 0:00.11 | |
`-- /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E
cmake_autogen /wrkdirs/usr/ports/multimedia/g
or as top showed it:
41552 root 1 52010M 1744K0 wait15 0:00 0.00%
/usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt FLAVOR=qt5 build
41566 root 1 52010M 1796K0 wait 1 0:00 0.00%
/bin/sh -e -c (cd /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build;
if ! /usr/bin/env QT_SELECT=qt5 QMAKEMODULES
41567 root 2 52088M13M0 select 4 0:00 0.00%
/usr/local/bin/qemu-arm-static ninja -j28 -v all
41585 root 2 520 100M24M0 kqread 8 0:00 0.00%
/usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E cmake_autogen
/wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.
41586 root 2 520 100M24M0 kqread 22 0:00 0.00%
/usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E cmake_autogen
/wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.
So: waiting in kqread. Repeated tries have gotten the same result
so far.
If this keeps up, later I may be able to try a native FreeBSD boot
instead of Hyper-V use on the same machine.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
mi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___________
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"
-up at the same point.
Building anything that requires multimedia/gstreamer1-qt@qt5 seems to be
solidly blocked in my environment.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-ports@freebsd.org mailing list
18-Mar)
___
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"
ven the prior ports have been built already, building just
> multimedia/gstreamer1-qt@qt5 still gets the hang-up at the same point.
>
> Building anything that requires multimedia/gstreamer1-qt@qt5 seems to be
> solidly blocked in my environment.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
d cross-buiding an
amd64->armv7 ports head -r484783 of my usual ports and the problem
repeated. I also found evidence that originally in the old time frame
I'd disabled part of my originally-intended port builds because of
other problems so multimedia/gstreamer1-qt 's build was not bein
similar (I don't like them): I wrote my own
utility, but it has still some issues, such as this one. I guess having
all the qt* ports in the same category would help.
Lorenzo Salvadore.
_______
freebsd-ports@freebsd.org mailing list
https://lists.freebs
ter ones, starting with:
FreeBSD -r332632 ports -r467547
Interestingly qemu-sbruno (the master port for qemu-user-static)
was not updated in that ports range, being from -r463452 .
There was a cmake change at -r467437 but the more modern
native result suggests cmake is not currently contributing
(a
> Hi Christian,
>
> Thanks for this! Can you please add this to /usr/ports/UPDATING?
>
> # Adam
>
>
I can test a patch for Inn CURRENT and STABLE if you like
> --
> Adam Weinberger
> ad...@adamw.org
> https://www.adamw.org
> _____
0.x and before
are no longer supported for 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/mailman/listinfo/freebsd-ports
To unsubscribe, send
() from /lib/libc.so.7
(gdb) bt
#0 0xf4e5e0dc in _ppoll () from /lib/libc.so.7
#1 0x00033bf0 in SubprocessSet::DoWork (this=) at
src/subprocess-posix.cc:237
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in earl
en when using
head. (The kernel does have symbols.)
===
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/freebsd-ports
To unsubscribe, send
e apparently-odd 2nd entry in the struct
kevent[] .
> 82400 write(1,0xf495,41)ninja: build stopped: subcommand failed.
> = 41
>
> So it was hung at the kevent until the kill -6 .
>
>
> Via another experiment ninja was at the time waiting
> in ppoll:
>
> Reading symbols from ninja...done.
> [New LWP 73023]
> Core was generated by `ninja'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0xf4e5e0dc in _ppoll () from /lib/libc.so.7
> (gdb) bt
> #0 0xf4e5e0dc in _ppoll () from /lib/libc.so.7
> #1 0x00033bf0 in SubprocessSet::DoWork (this=) at
> src/subprocess-posix.cc:237
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
rk].) So it is for the close-down of the thread that was in
nanosleep.
There were no PSIG's and no sigreturn's prior to the kill according to the
kdump output.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
.
> (Such might not have been appropriate to all targets.)
>
> armv6 would have the same problem as I understand things.
Using commented out __packed in:
struct target_freebsd11_kevent {
abi_ulong ident;
int16_tfilter;
uint16_t flags;
uint32_t fflags;
abi_long data;
abi_ulong udata;
} ; // __packed;
struct target_freebsd_kevent {
abi_ulong ident;
int16_tfilter;
uint16_t flags;
uint32_t fflags;
int64_t data;
abi_ulong udata;
uint64_t ext[4];
} ; // __packed;
in
/wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/bsd-user/syscall_defs.h
was sufficient to allow the multimedia/gstreamer1-qt@qt5 build to complete: no
more hang-up.
So this is likely what is wrong for the packages-builders as well.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
r
amd64-native targeting armv7 and see if that is sufficient to avoid the
problem in my context. Previously removing the __packed was enough to
make the structure the same size with the same offsets as for armv7.
(Such might not have been appropriate to all targets.)
armv6 would have the same
On 2018-Dec-30, at 21:01, Jonathan Chen wrote:
> On Mon, 31 Dec 2018 at 14:34, Mark Millard via freebsd-ports
> wrote:
>>
>> [Removing __packed did make the size and offsets match armv7
>> and the build worked based on the reconstructed qemu-arm-static.]
>
> Than
on
i386 and amd64.
Thanks.
Lorenzo Salvadore.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "fr
> with poudriere on 11.2-RELEASE, 12.0-RELEASE, both on
> > i386 and amd64.
>
> Committed, just in time for 2019Q1 8-}
Great! Thank you very much.
Lorenzo Salvadore.
_______
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mai
in build times in
the contexts I described.
Any idea what is going on and what could I do to speed up things?
Thanks.
Lorenzo Salvadore.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
___
freebsd-ports@freebsd.org mailing list
https
-RELEASE and 12.0-RELEASE.
Thanks.
Lorenzo Salvadore.
___
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 also failing for libvpx if
I remember right.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> On 31.12.18 21:03, Lorenzo Salvadore via freebsd-ports wrote:
>
> > > Hi!
> > >
> > > > Am I the only poudriere user that notices very long build times on an
> > > > amd64 machine in i386 jails? This does not happen always, but
> > >
Laundry, 2084M Wired, 187M Free
ARC: 1122M Total, 649M MFU, 323M MRU, 1371K Anon, 16M Header, 133M Other
401M Compressed, 1064M Uncompressed, 2.65:1 Ratio
Swap: 2048M Total, 210M Used, 1838M Free, 10% Inuse
Lorenzo Salvadore.
_______
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"
builds were also failing for libvpx if
> I remember right.
Looks like more recently libvpx builds on the package builders. So next time
that I update the ports tree I'll get to see the next problem (if any).
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
away in early 2018-Mar)
_______
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"
roblematic):
> > CPU: 32.8% user, 4.8% nice, 8.3% system, 0.5% interrupt, 53.5% idle
> > Mem: 1200M Active, 332M Inact, 32M Laundry, 2084M Wired, 187M Free
> > ARC: 1122M Total, 649M MFU, 323M MRU, 1371K Anon, 16M Header, 133M Other
> > 401M Compressed, 1064M Uncompressed, 2
gt;
I have found the real cause of most of the problems: it's ccache configuration.
I used the same cache of 15 Gb for the host (amd64) and for all jails (both
amd64 and i386):
the i386 jails disliked it very much. Creating a new cache only for the i386
jails
fixed the problems. May
rnight.
>
> "indefinite wait..." warnings on the console have returned in abundance with
> the use
> of USB flash swap, even though swap usage is still less than 200MB.
You might want to report the types/models of the USB flash devices that
were in used. Also relevan
536870912
rdi0xf4dede80 4108246656
(gdb) x 0xf4dede80
0xf4dede80: 0x4001
0x000060051c20 <+80>:mov%ecx,%eax
=> 0x60051c22 <+82>:lock cmpxchg %esi,(%rdi)
0x60051c26 <+86>:sete %bl
0x60051c29 <+89>:test %bl,%bl
0x60051c2b <+91>:je 0x60051c20
At this point I do not have interpretation of the details, not even
a comparison to the source code.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
In the source code there is:
1261} else if (TARGET_URWLOCK_READER_COUNT(state) != 0) {
1262/* decrement reader count */
1263for (;;) {
1264if (!tcmpset_32(&target_urwlock->rw_state, state, (state -
1))) {
1265if (
060051c7a <+170>: test $0x4000,%ecx
>> 0x60051c80 <+176>: je 0x60051c50
>> 0x60051c82 <+178>: mov$0x1,%edx
>> 0x60051c87 <+183>: jmp0x60051c8e
>> 0x60051c89 <+185>: mov$0x7fff,%
te) == 0) {
> 1266 unlock_user_struct(target_urwlock,
> 1267 target_addr, 1);
> 1268 return -TARGET_EPERM;
> (gdb)
> 1269 }
> 1270 } else {
> 1271 break;
> 1272
On 2019-Jan-2, at 17:41, Kyle Evans wrote:
> On Wed, Jan 2, 2019 at 3:38 AM Mark Millard via freebsd-ports
> wrote:
>>
>>> . . .
>>
>> So (without old line numbers):
>>
>>} else if (TARGET_URWLOCK_READER_COUNT(state) != 0) {
>>
hitectures instead of tracking the 64-bit vs. 32-bit
status for the architecture.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
d or zero for local */
};
with no potential __packed.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
/* type of l_start */
int l_sysid;/* remote system id or zero for local */
};
with no potential __packed.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gnal.h
has:
struct target_sigframe {
target_siginfo_tsf_si; /* saved siginfo */
target_ucontext_t sf_uc; /* saved ucontext */
};
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-ports@freebsd.org mailing list
htt
ts + NULL (1) */
} target_prpsinfo_t;
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
field
offsets as things are now.
===
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/freebsd-ports
To unsubscribe, send any mail to &qu
e the wrong
size for armv7: arm uses 64-bit time_t. As of 12+ only i386
uses 32-bit time_t if I understand right. In 11.x 32-bit powerpc
also uses 32-bit time_t.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
understand right. In 11.x 32-bit powerpc
also uses 32-bit time_t.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
x27;s for shm_atime, shm_dtime, and shm_ctime are the wrong
size for armv7: arm uses 64-bit time_t. As of 12+ only i386
uses 32-bit time_t if I understand right. In 11.x 32-bit powerpc
also uses 32-bit time_t.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
target_freebsd_timespec));
unsigned int:(8 / 2) * (16 - (int)sizeof(struct target_freebsd_timespec));
} __packed;
There are multiple issues here, for example: __uint32_t (native nstat) vs.
int16_t
(target_nstat) for st_mode. Similarly for st_nlink. And there is __packed
changing
the padding for another example.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
net
• lang/ldc
• math/libpgmath
Collapse this list.
===
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/freebsd-ports
To unsubscr
On 14.01.19 10:09, Jochen Neumeister wrote:
>
> On 14.01.19 09:56, Gregory Byshenk wrote:
>> On Sun, Jan 13, 2019 at 08:39:12PM -0500, Charles Sprickman via
>> freebsd-stable wrote:
On Jan 13, 2019, at 3:19 PM, Randy Bush wrote:
> I have a mission critical app server running an old
g an updated toolchain
for powerpc64.
This is the only failure so far in what I normally build for this
context. (I include building lumina.)
For reference:
# svnlite diff /usr/ports/multimedia/gstreamer1-libav/Makefile
#
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away
qemu-user-static
and host-native cross-tools used for cross builds. The self-hosted
poudriere use has not had the oddities but takes longer to build.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-ports@f
attempted might be involved in your context.
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ork with i686, I'll then up i686 and repeat.
>
> In the end, this looks like a "wrong code" issue with
> llvm/clang/clang++.
>
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
-string result.
Same for cortex-a53 (aarch64) and cortex-a7 (armv7). (I do not have
a powerpc* available at the moment.)
Those result from results like:
# clang -v -fsyntax-only -march=native -x c /dev/null 2>&1
FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM
7.0.1)
Target: aarch64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin
clang: error: the clang compiler does not support '-march=native'
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 27/02/2019 12:51, Mark Martinec wrote:
> Now that poudriere has been upgraded from 3.2.8 to 3.3.0,
> when I press ^T during interactive bulk build, I see:
>
> sed: 1: "s,^\[( *[0-9]+%|[0-9]+/ ...": RE error: repetition-operator
> operand invalid
>
> with many (but not all) build jobs. For ex
On 04/03/2019 23:16, Robert Huff wrote:
> I was recently told the reason we need devel/llvm70 is the llvm
> in base has - for reasons above my pay grade, but probably not above
> yours - certain components disabled which are required by various
> ports.
The LLVM ports are still needed for tho
catomic.h:97:5: note: in
expansion of macro 'Q_STATIC_ASSERT_X'
Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template
parameter is an integral of a size not supported on this platform");
^~~~~
*** [.obj/qatomic.o] Error code 1
===
Mark Millard
marklm
are located at:
cc: note: diagnostic msg: /tmp/nir_constant_expressions-be5a21.c
cc: note: diagnostic msg: /tmp/nir_constant_expressions-be5a21.sh
cc: note: diagnostic msg:
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 07/03/2019 01:55, Craig Leres wrote:
> I'm working on a port for mailman 3. I want to use django 2.1 because
> that's what I'm using on the systems I'm currently running mailman 2 on
> you can't really run different version of django on the same system).
> But it turns out a lot of ports have RU
[Re-sending, because my original reply made it to the mailing list but
not to leres@'s real mailbox due to some brokenness in SPF, but also to
add a quip missing originally. Turns out that quip slightly relates to
what matthew@ mentioned.]
On 07/03/2019 02:32, Charlie Li wrote:
> On 07/03/2019 01:
ay in early 2018-Mar)
_______
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"
0-7ecd-e111-bb59-0022644237b5
Revision: 495006
Last Changed Rev: 495006
===
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/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
: ^/head
Repository Root: svn://svn0.us-west.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 495006
Last Changed Rev: 495006
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___________
freebsd-ports
Just FYI . . .
Adriaan de Groot adridg at freebsd.org wrote on
Mon Mar 11 14:22:10 UTC 2019 :
> On Monday, 11 March 2019 13:01:43 CET freebsd-ports-request at freebsd.org
> wrote:
> > ../qbearerengine_impl.h:48:1: error: expected class-name before '{' token
>
>
_to_seq(value):
^
SyntaxError: invalid syntax
removing /tmp/tmpn6f3Nq.py
running install_egg_info
Copying Jinja2.egg-info to
/usr/ports/devel/py-Jinja2/work-py27/stage/usr/local/lib/python2.7/site-packages/Jinja2-2.10-py2.7.egg-info
running install_scripts
writing list of installed files to
'/usr/ports/devel/py-Jinja2/work-py27/.PLIST.pymodtmp'
> Compressing man pages (compress-man)
real 0m1.288s
user 0m0.630s
sys 0m0.658s
Restoring the git files restores the hang.
What's up with that? Should I CC @python?
Thanks in advance,
Anthony Jenkins
___
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"
ng ports before the src/ports split.
>
> thanks,
>
> -Alfred
>
> Forwarded Message
> Subject: FreeBSD ports you maintain which are out of date
> Date: Thu, 14 Mar 2019 11:27:00 +
> From: portsc...@freebsd.org
> To: alf...@freebsd.org
>
> D
On Sunday 17 March 2019 10:48, Lorenzo Salvadore via freebsd-ports
wrote:
> ‐‐‐ Original Message ‐‐‐
> On Saturday 16 March 2019 22:08, Alfred Perlstein alf...@freebsd.org wrote:
>
> > How do I stop these emails?
> > I just retired my commit bit and stopped comm
--
> rollingbits — 📧 rollingb...@gmail.com 📧 rollingb...@terra.com.br 📧
> rollingb...@yahoo.com 📧 rollingb...@globo.com 📧 rollingb...@icloud.com
> _______
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-
401 - 500 of 1143 matches
Mail list logo