[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
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
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"
::IsSupported, "template
parameter is an integral of a size not supported on this platform");
^
*** [.obj/qatomic.o] Error code 1
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-port
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
find library -lX11
c++: error: linker command failed with exit code 1 (use -v to see
invocation) *** [lib/libFreeCADGui.so] Error code 1
--
by ajtiM
--
FreeBSD 12.0-Release
___
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
On Sun, 24 Feb 2019 22:12:21 +0100
Christoph Moench-Tegeder wrote:
> ## ajtiM via freebsd-ports (freebsd-ports@freebsd.org):
>
> > Subject: freecad cannot build
>
> Oh, it can, e.g.:
> http://beefy6.nyi.freebsd.org/data/120amd64-default/493629/logs/FreeCAD-0.17.13541_6.log
; make build failed for cad/freecad
===>>> Aborting update
--
by ajtiM
--
FreeBSD 12.0-Release
___________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any m
On Fri, 15 Feb 2019 18:51:04 +0100
Christoph Moench-Tegeder wrote:
> ## ajtiM via freebsd-ports (freebsd-ports@freebsd.org):
>
> > Reading
> > /usr/ports/accessibility/qt5-speech/work/qtspeech-everywhere-src-5.12.1/src/plugins/tts/speechdispatcher/speechdispatcher.pro
>
oost_python
-lpython2.7
--
by ajtiM
------
FreeBSD 12.0-Release
___
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"
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"
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@freebsd.org mailing l
erpc64.
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 in early 2018-Mar)
__
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
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
/ 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"
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)
___
d 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"
g
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"
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 "fr
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"
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
https
/* 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"
ead 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"
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
t(target_urwlock,
> 1267 target_addr, 1);
> 1268 return -TARGET_EPERM;
> (gdb)
> 1269 }
> 1270 } else {
> 1271 break;
> 1272 }
> 1273 }
The lack of the update to 'state' is why it was valid for the
compiler to eliminate the code for:
> 1265 if (TARGET_URWLOCK_READER_COUNT(state) == 0) {
> 1266 unlock_user_struct(target_urwlock,
> 1267 target_addr, 1);
> 1268 return -TARGET_EPERM;
> (gdb)
> 1269 }
So (without old line numbers):
} else if (TARGET_URWLOCK_READER_COUNT(state) != 0) {
/* decrement reader count */
for (;;) {
if (!tcmpset_32(_urwlock->rw_state, state, (state - 1))) {
__get_user(state, _urwlock->rw_state);
if (TARGET_URWLOCK_READER_COUNT(state) == 0) {
unlock_user_struct(target_urwlock,
target_addr, 1);
return -TARGET_EPERM;
}
} else {
break;
}
}
This follows the structure of other tcmpset_32 use in the source file.
With this change poudriere-devel's bulk worked for graphics/poppler-qt5
as a amd64->armv7 cross-build (FreeBSD head -r341836 based, under Hyper-V,
with 28 logical-processors assigned):
[00:00:13] [01] [00:00:00] Building graphics/poppler-qt5 | poppler-qt5-0.72.0
[00:08:03] [01] [00:07:50] Finished graphics/poppler-qt5 | poppler-qt5-0.72.0:
Success
===
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"
: test $0x4000,%ecx
>> 0x60051c80 <+176>: je 0x60051c50
>> 0x60051c82 <+178>: mov$0x1,%edx
>> 0x60051c87 <+183>: jmp0x60051c8e
>> 0x60051c89 <+185>: mov $0x7fff,%edx
>> 0x0
s:
1261} else if (TARGET_URWLOCK_READER_COUNT(state) != 0) {
1262/* decrement reader count */
1263for (;;) {
1264if (!tcmpset_32(_urwlock->rw_state, state, (state -
1))) {
1265 if (TARGET_URWLOCK_READER_COUNT(state) == 0) {
12
er dump.
For just before the "lock cmpxchg %esi,(%rdi)" in the loop:
rax0x2001 536870913
rbx0xf4dede00 4108246528
rcx0x2001 536870913
rdx0x2 2
rsi0x2000 536870912
rdi
uot;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 relevant is the past usage patte
und 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. Maybe I will have to make th
):
> > 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.65:1 Rati
arly 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"
e 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"
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"
> 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
> > >
iling 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"
ASE 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"
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
> 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
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
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
t for
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 p
7.
> (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_l
he 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"
ident=6, filter=EVFILT_READ,
flags=0x1, fflags=0, data=0, udata=0x0 }
{ ident=0x0, filter=, flags=0, fflags=0x8,
data=0x1, udata=0x0 } }
Note the 0x2 kevent argument and the apparently-odd 2nd entry in the struct
kevent[] .
> 82400 write(1,0xf495,41)ninja: build stopped: su
ead. (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 any mail to &q
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"
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
> 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
> _____
ing 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
(and, so, likely
lar (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.freebsd.org/mail
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 being
tried.
Given 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"
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"
ang-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
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"
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"
_thr_umtx_timedwait_uint (mtx=0x861027008,
id=, clockid=, abstime=,
shared=)
at /usr/src/lib/libthr/thread/thr_umtx.c:236
#2 0x0000601dc6f8 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"
c 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 topology of
the physical
: 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"
nts 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.freebsd.
illa/
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"
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 -
___
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"
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"
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"
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 mailing list
https
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"
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"
vtsc_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.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
aw
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
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-ports-
uch 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'
>&g
mething 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 existing behavior means that off
t;/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"
("/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
>
sd13.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"
uilding. 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-only.net went
away in ea
posite_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___OVER_asm_neon
> e008 g F .text 0000 .hidden
> pixman_sc
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/mailman/listinfo
*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"
-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"
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 of -O2
ild 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"
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"
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"
ern: "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[MACHINE_ARCH] of :C is "amd64"
Applying[
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)
il 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
>> +SHELL=/bin/sh
>>
>> The SHELL's I expected but the other 3 lines I did not.
>> But the 3 l
e 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.
>
> In CONFIGURE_ENV:
>
> amd64 -> armv7: CCASFLAGS having -O2
> armv7: CCASFLAGS
=
===
. . .
So I diff'd the logs and found the following (selective extraction):
(- for amd64 -> armv7; + for armv7)
-Poudriere version: 3.2.99.20180601
+Poudriere version: 3.2.99.20181024
This is was expected but may mean tha
rporate
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.freebsd.org/mailman/li
-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
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
Error code 1
make[3]: stopped in /wrkdirs/usr/ports/x11/pixman/work/pixman-0.34.0/pixman
1 error
make[3]: stopped in /wrkdirs/usr/ports/x11/pixman/work/pixman-0.34.0/pixman
*** [all-recursive] Error code 1
FreeBSD context details:
# uname -apKU
FreeBSD OPiP2E 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r340287M: Sat Nov 10
22:40:25 PST 2018
markmi@FBSDFSSD:/usr/obj/armv7_clang/arm.armv7/usr/src/arm.armv7/sys/GENERIC-NODBG
arm armv7 133 133
===
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"
etc. and
started the build. For some reason poudriere wants to build a ton of extra
baggage (360+ ports instead of 240.)
Is this expected and will the packages once built be without any extra
cruft?
-Reko
___
freebsd-ports@freebsd.org mailing list
.o bhnd_bus_if.o bhnd_erom.o bhnd_erom_if
64846 root 1 52010M 1768K0 wait22 0:00 0.00% sh
-e
46319 root 1 20011M 2420K0 select 8 0:00 0.00%
/nxb-bin/usr/bin/make all DIRPRFX=bhnd/
Again: not repeatable for when/where --but has a thread
f
t; split off from arm.arm and we use a check like the one in the above
> PR. CC'ing imp for a wisdom drop.
Looks like poudriere-devel is defining UNAME_p and UNAME_m to cause
the right results for its port builds.
===
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"
501 - 600 of 1130 matches
Mail list logo
