Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[My wording presumed some context not presented.] On 2018-Nov-14, at 18:21, Mark Millard wrote: > On 2018-Nov-14, at 17:45, Bryan Drewery wrote: > >> I think the real problem here is that Poudriere is setting MACHINE_ARCH >> in make.conf and sys.mk loads make.conf *after* checking MACHINE_CPUA

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
On 2018-Nov-14, at 17:45, Bryan Drewery wrote: > I think the real problem here is that Poudriere is setting MACHINE_ARCH > in make.conf and sys.mk loads make.conf *after* checking MACHINE_CPUARCH > (derived from MACHINE_ARCH) to determine CFLAGS; The .if is expanding > MACHINE_CPUARCH before make

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[Looks like there are 2 stages involved in that 2mmjnk.txt file that I generated. Before MACHINE_ARCH is explicitly assigned and after.] On 2018-Nov-14, at 15:40, Mark Millard wrote: > [Evidence from inside poudriere bulk -j... -i ports-mgmt/pkg . > Use of native /nxb-bin/. . . leads to MACHINE_

Re: japanese/libreoffice build failed (13.0-CURRENT/r339677)

2018-11-14 Thread KIRIYAMA Kazuhiko
At Wed, 14 Nov 2018 21:06:37 +0900, 私 wrote: > > Hi all, > > ja-libreoffice-6.0.7 (japanese/libreoffice) failed to build in > 13.0-CURRENT with port revision r339677 (detail log in [1]): s/339677/484802/ Sorry ;) > > ===> License LGPL3+ MPL20 accepted by the user > ===> ja-libreoffice-6.0.

Re: multimedia/umplayer build failed (13.0-CURRENT/r339677)

2018-11-14 Thread KIRIYAMA Kazuhiko
At Wed, 14 Nov 2018 21:00:20 +0900, 私 wrote: > > Hi all, > > umplayer-0.97_4 (multimedia/umplaye) failed to build in > 13.0-CURRENT with port revision r339677 (detail log in [1]): ~~ s/339677/484802/ Sorry ;) > > ===> License GPLv3 accepted by the user >

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[Evidence from inside poudriere bulk -j... -i ports-mgmt/pkg . Use of native /nxb-bin/. . . leads to MACHINE_ARCH being amd64 instead of armv7 or the like. See later supporting material.] On 2018-Nov-14, at 14:38, Bryan Drewery wrote: > On 11/14/18 2:35 PM, Mark Millard wrote: >> [Looking at pac

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
On 2018-Nov-14, at 14:38, Bryan Drewery wrote: > On 11/14/18 2:35 PM, Mark Millard wrote: >> [Looking at package fallout logs: the official armv6 and armv7 >> builds are using -O2 because of MACHINE_ARCH being defined >> because of qemu-user-static use. (mips too?) The logic in >> share/mk/sys.mk

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[Looking at package fallout logs: the official armv6 and armv7 builds are using -O2 because of MACHINE_ARCH being defined because of qemu-user-static use. (mips too?) The logic in share/mk/sys.mk is not causing -O . An implication is that -O2 for armv6 and armv7 is probably far more tested than peo

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[Tracking down -O2 vs. -O lead to share/mk/sys.mk instead of to my materials. It in turn leads back to poudriere-devel with qemu-user-static in use defining MACHINE_ARCH but without it instead not doing so. share/mk/sys.mk behaves differently for with vs. without the definition, leading to -O2 vs -

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
[Added: The original cross-build via poudriere-devel and qemu-user-static did not get this problem. I give details later. Sumamry: Looks like -O2 was used for the cross build and -O was used for armv7 native. The difference is likely(?) from my materials but not supporting both ways of building is

Re: Poudriere building far more ports than it should

2018-11-14 Thread Reko Turja via freebsd-ports
-Original Message- From: AlexandreC. Guimarães Sent: Wednesday, November 14, 2018 9:26 PM Do you mean the OPTIONS you previously set were not honoured by poudriere? Just in case, poudriere does not `read` OPTIONS and/or other things like make.conf from the default location but from /us

Re: Poudriere building far more ports than it should

2018-11-14 Thread Alexandre C . Guimarães
On Wed, Nov 14, 2018 at 08:57:59PM +0200, Reko Turja via freebsd-ports wrote: > Hello! > > -Original Message- From: Dmytro Bilokha > > On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports > wrote: > > > > I finally took the hurdle and made a poudriere VM for building

Re: Poudriere building far more ports than it should

2018-11-14 Thread Reko Turja via freebsd-ports
-Original Message- From: Matthias Fechner Sent: Wednesday, November 14, 2018 9:10 PM Am 14.11.2018 um 19:57 schrieb Reko Turja via freebsd-ports: I guess one option would be blacklisting in poudriere those unneeded dependencies which shouldn't be linked with my packages, if my options

Re: Poudriere building far more ports than it should

2018-11-14 Thread Matthias Fechner
Am 14.11.2018 um 19:57 schrieb Reko Turja via freebsd-ports: > I guess one option would be blacklisting in poudriere those unneeded > dependencies which shouldn't be linked with my packages, if my options > are honoured by poudriere. have you made your options (maybe they are located on /var/db/p

Re: Poudriere building far more ports than it should

2018-11-14 Thread Reko Turja via freebsd-ports
Hello! -Original Message- From: Dmytro Bilokha On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports wrote: I finally took the hurdle and made a poudriere VM for building my ports instead of building them on target system. At first I did however build every sing

ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

2018-11-14 Thread Mark Millard via freebsd-ports
I'll first note: # /usr/bin/ld -v LLD 6.0.1 (FreeBSD 335540-130) (compatible with GNU linkers) and that I use: CFLAGS.clang+= -mcpu=cortex-a7 CXXFLAGS.clang+= -mcpu=cortex-a7 CPPFLAGS.clang+= -mcpu=cortex-a7 in the src.conf like ~/src.configs/src.conf.armv7-clang-bootstrap.armv7-host file t

Re: Poudriere building far more ports than it should

2018-11-14 Thread Dmytro Bilokha
On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports wrote: Hello list! I finally took the hurdle and made a poudriere VM for building my ports instead of building them on target system. At first I did however build every single port I will need on the VM resulting on 240 or

Re: FreeBSD Port: spamassassin-3.4.2_1

2018-11-14 Thread Niclas Zeising
On 11/14/18 2:42 PM, H. Rouwenhorst wrote: Hello, It might be of no concern since you seem to have rolled back the upgrade, but the pkg version of spamassassin-3.4.2_1 won't install with the following errors: Hi! The change has been reverted, so 3.4.2_2 should not contain this issue. It w

japanese/libreoffice build failed (13.0-CURRENT/r339677)

2018-11-14 Thread KIRIYAMA Kazuhiko
Hi all, ja-libreoffice-6.0.7 (japanese/libreoffice) failed to build in 13.0-CURRENT with port revision r339677 (detail log in [1]): ===> License LGPL3+ MPL20 accepted by the user ===> ja-libreoffice-6.0.7 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by ja-l

multimedia/umplayer build failed (13.0-CURRENT/r339677)

2018-11-14 Thread KIRIYAMA Kazuhiko
Hi all, umplayer-0.97_4 (multimedia/umplaye) failed to build in 13.0-CURRENT with port revision r339677 (detail log in [1]): ===> License GPLv3 accepted by the user ===> umplayer-0.97_4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by umplayer-0.97_4 for bui

Re: BIND update gone bad

2018-11-14 Thread Mathieu Arnold
On Wed, Nov 14, 2018 at 10:44:49AM +0100, Andrea Venturoli wrote: > On 11/14/18 7:35 AM, Matthias Fechner wrote: > > > maybe an OPTION problem. > > Make sure you disable the GOST option (in bind and openssl), I faced a > > similar problem, but I thing this option was removed, but I think it is > >

Re: BIND update gone bad

2018-11-14 Thread Andrea Venturoli
On 11/14/18 7:35 AM, Matthias Fechner wrote: maybe an OPTION problem. Make sure you disable the GOST option (in bind and openssl), I faced a similar problem, but I thing this option was removed, but I think it is a try worth. Hello. Just to say I've been hit by the same problem: fortunately I

Re: BIND update gone bad

2018-11-14 Thread Mathieu Arnold
On Tue, Nov 13, 2018 at 09:15:12PM -0500, Kevin P. Neal wrote: > Before anyone panics on my behalf, I did a zfs rollback to avoid the new > named problem. But something needs to be fixed somewhere. > > I just did an svn update of /usr/ports, ran poudriere and then did pkg > upgrade, which includes

FreeBSD ports you maintain which are out of date

2018-11-14 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you