On 2021-Jul-3, at 21:32, Mark Millard wrote:
> [Just correcting a bad placement of some of the new text.]
>
> On 2021-Jul-3, at 21:25, Mark Millard wrote:
>
>> On 2021-Jul-3, at 21:15, Mark Millard wrote:
>>
>>> Summary: You need to update /usr/local/poudriere/poudriere-system
>>>
>>> Upda
[Just correcting a bad placement of some of the new text.]
On 2021-Jul-3, at 21:25, Mark Millard wrote:
> On 2021-Jul-3, at 21:15, Mark Millard wrote:
>
>> Summary: You need to update /usr/local/poudriere/poudriere-system
>>
>> Updating your HOST environment does not automatically update tha
On 2021-Jul-3, at 21:15, Mark Millard wrote:
> Summary: You need to update /usr/local/poudriere/poudriere-system
>
> Updating your HOST environment does not automatically update that
> area.
>
> One possibility for an update procedure is:
>
> # cd /usr/src
> # make installworld DESTDIR=/usr
Summary: You need to update /usr/local/poudriere/poudriere-system
Updating your HOST environment does not automatically update that
area.
One possibility for an update procedure is:
# cd /usr/src
# make installworld DESTDIR=/usr/local/poudriere/poudriere-system DB_FROM_SRC=1
# make distrib-dirs
On 2021-Jul-3, at 14:54, bob prohaska wrote:
> On Sat, Jul 03, 2021 at 01:15:19PM -0700, Mark Millard wrote:
>>
>>
>>
>> So you still have not tried an artifacts or snapshot kernel+world?
>>
> Not yet.
>
>>> Eventually I resorted to running make in devel/llvm10, to my surprise it
>>> ran
On 2021-Jul-3, at 14:54, bob prohaska wrote:
> On Sat, Jul 03, 2021 at 01:15:19PM -0700, Mark Millard wrote:
>>
>>
>>
>> So you still have not tried an artifacts or snapshot kernel+world?
>>
> Not yet.
>
>>> Eventually I resorted to running make in devel/llvm10, to my surprise it
>>> ran to
On Sat, Jul 03, 2021 at 01:15:19PM -0700, Mark Millard wrote:
>
>
>
> So you still have not tried an artifacts or snapshot kernel+world?
>
Not yet.
> > Eventually I resorted to running make in devel/llvm10, to my surprise it
> > ran to completion.
>
> Interesting.
>
> Was this -j4? -j1? -j2
On 2021-Jul-3, at 13:15, Mark Millard wrote:
> On 2021-Jul-3, at 11:25, bob prohaska wrote:
>
> On 2021-Jul-2, at 19:23, Mark Millard wrote:
>> Side note:
>>
>> It llooks like http://www.zefox.org/~bob/swaplogs/poudrierellvm10.log
>> shows that you tried with:
>>
On 2021-Jul-3, at 11:25, bob prohaska wrote:
On 2021-Jul-2, at 19:23, Mark Millard wrote:
>>>
> Side note:
>
> It llooks like http://www.zefox.org/~bob/swaplogs/poudrierellvm10.log
> shows that you tried with:
>
> Device 1K-blocks UsedAvail Cap
> >> On 2021-Jul-2, at 19:23, Mark Millard wrote:
> >
> >>> Side note:
> >>>
> >>> It llooks like http://www.zefox.org/~bob/swaplogs/poudrierellvm10.log
> >>> shows that you tried with:
> >>>
> >>> Device 1K-blocks UsedAvail Capacity
> >>> /dev/da0s2b 104857625784 10
On 2021-Jul-3, at 01:45, Mark Millard wrote:
> On 2021-Jul-2, at 21:47, Mark Millard wrote:
>
>> On 2021-Jul-2, at 19:23, Mark Millard wrote:
>>>
>>> I just noticed that in several prior messasges I quoted the llvm-tblgen
>>> command that generates the *.inc files with the odd contents ins
On 2021-Jul-2, at 21:47, Mark Millard wrote:
> On 2021-Jul-2, at 19:23, Mark Millard wrote:
>>
>> I just noticed that in several prior messasges I quoted the llvm-tblgen
>> command that generates the *.inc files with the odd contents instead
>> of the later compile that tried to use the output
On 2021-Jul-2, at 19:23, Mark Millard wrote:
>
> I just noticed that in several prior messasges I quoted the llvm-tblgen
> command that generates the *.inc files with the odd contents instead
> of the later compile that tried to use the output files in question.
>
> This leaves open the possi
http://www.zefox.org/~bob/poudriere/bulk.log shows that you had
the RPi3b (whatever variant) with the following builders (jobs)
going in parallel as of whe llvm10 reported the failure:
. . .
[00:03:20] Building 81 packages using 4 builders
. . .
[00:07:07] [04] [00:00:00] Building lang/rust | rust
I just noticed that in several prior messasges I quoted the llvm-tblgen
command that generates the *.inc files with the odd contents instead
of the later compile that tried to use the output files in question.
This leaves open the possibility that I had incorrectly checked on if
the build had fail
On 2021-Jun-25, at 21:41, Mark Millard wrote:
>> . . .
>
> Note that system-clang just got updates for stable/11 stable/12
> stable/13 and main for a defect that prevents building
> www/chromium with a clang that has assertions enabled (a form
> of debug build contribution):
>
> The branch ma
On 2021-Jun-26, at 15:29, Mark Millard wrote:
>
> [freebsd-arm+owner at FreeBSD.org sent a notice of rejection
> of the original of the below because, according to it, I was
> not a subscriber to freebsd-arm. So this is a resend after
> (re-)subscribing. We will see if it is again rejected.]
>
>
[freebsd-arm+owner at FreeBSD.org sent a notice of rejection
of the original of the below because, according to it, I was
not a subscriber to freebsd-arm. So this is a resend after
(re-)subscribing. We will see if it is again rejected.]
On 2021-Jun-25, at 22:14, Mark Millard wrote:
> On 2021-Jun
On 2021-Jun-25, at 22:14, Mark Millard wrote:
> On 2021-Jun-25, at 20:52, bob prohaska wrote:
>
>> If you replicate the problem I'll be very pleased.
>> And just slightly relieved.
>
>
> No luck on the 1st try:
>
> [ 28% 1315/4575] cd /wrkdirs/usr/ports/devel/llvm10/work/.build &&
> /wrk
On 2021-Jun-25, at 20:52, bob prohaska wrote:
> If you replicate the problem I'll be very pleased.
> And just slightly relieved.
No luck on the 1st try:
[ 28% 1315/4575] cd /wrkdirs/usr/ports/devel/llvm10/work/.build &&
/wrkdirs/usr/ports/devel/llvm10/work/.build/bin/llvm-tblgen -gen-global-i
On 2021-Jun-25, at 20:52, bob prohaska wrote:
> On Fri, Jun 25, 2021 at 07:52:32PM -0700, Mark Millard wrote:
> [huge snip, hope the quotes are still correct]
>>> So I'm going to suggest using an official kernel build
>>> as built by the ci.freebsd.org systems, one that is not
>>> GENERIC-MMCCAM.
On Fri, Jun 25, 2021 at 07:52:32PM -0700, Mark Millard wrote:
[huge snip, hope the quotes are still correct]
> > So I'm going to suggest using an official kernel build
> > as built by the ci.freebsd.org systems, one that is not
> > GENERIC-MMCCAM. In:
> >
World and kernel are updating now to -cur
On 2021-Jun-24, at 17:54, Mark Millard wrote:
> On 2021-Jun-24, at 17:16, bob prohaska wrote:
>
>> On Thu, Jun 24, 2021 at 10:41:38AM -0700, Mark Millard wrote:
>> [huge snip]
>>>
>>> So: Even going back to June 9 may messed up nfs
>>> use. (I've no clue what services you depend on
>>> or in w
On 2021-Jun-24, at 17:16, bob prohaska wrote:
> On Thu, Jun 24, 2021 at 10:41:38AM -0700, Mark Millard wrote:
> [huge snip]
>>
>> So: Even going back to June 9 may messed up nfs
>> use. (I've no clue what services you depend on
>> or in what contexts.) You might need to disable
>> nfs even tr
On Thu, Jun 24, 2021 at 10:41:38AM -0700, Mark Millard wrote:
[huge snip]
>
> So: Even going back to June 9 may messed up nfs
> use. (I've no clue what services you depend on
> or in what contexts.) You might need to disable
> nfs even trying to start at the next boot before
> booting into such an
On 2021-Jun-24, at 09:01, bob prohaska wrote:
> [What about trying a new kernel? details at end]
> On Wed, Jun 23, 2021 at 11:02:02PM -0700, Mark Millard wrote:
>> On 2021-Jun-23, at 21:30, bob prohaska wrote:
>>
>>> On Wed, Jun 23, 2021 at 04:22:35PM -0700, Mark Millard wrote:
On 2021-Jun
[What about trying a new kernel? details at end]
On Wed, Jun 23, 2021 at 11:02:02PM -0700, Mark Millard wrote:
> On 2021-Jun-23, at 21:30, bob prohaska wrote:
>
> > On Wed, Jun 23, 2021 at 04:22:35PM -0700, Mark Millard wrote:
> >> On 2021-Jun-23, at 15:28, bob prohaska wrote:
> >> . . .
> >
>
On 2021-Jun-23, at 21:30, bob prohaska wrote:
> On Wed, Jun 23, 2021 at 04:22:35PM -0700, Mark Millard wrote:
>> On 2021-Jun-23, at 15:28, bob prohaska wrote:
>> . . .
>
>>
> [snipped for brevity]
>>
For example, 0xA5u byte values might be the value that newly
allocated memory is in
On Wed, Jun 23, 2021 at 04:22:35PM -0700, Mark Millard wrote:
> On 2021-Jun-23, at 15:28, bob prohaska wrote:
>
> > On Wed, Jun 23, 2021 at 02:03:42PM -0700, Mark Millard wrote:
> >> On 2021-Jun-23, at 10:43, bob prohaska wrote:
> >>
> >>> On Wed, Jun 23, 2021 at 01:34:55AM -0700, Mark Millard
On 2021-Jun-23, at 18:15, Mark Millard wrote:
> On 2021-Jun-23, at 17:58, Mark Millard wrote:
>
>> Misc notes . . .
>>
>> Looking at your logs, I expect trying to build both
>> llvm10 and rust in parallel is likely to run into
>> resource issues on teh RPi3B+. For builds in that
>> context, it
On 2021-Jun-23, at 17:58, Mark Millard wrote:
> Misc notes . . .
>
> Looking at your logs, I expect trying to build both
> llvm10 and rust in parallel is likely to run into
> resource issues on teh RPi3B+. For builds in that
> context, it may be better to do something like:
>
> # poudriere buld
Misc notes . . .
Looking at your logs, I expect trying to build both
llvm10 and rust in parallel is likely to run into
resource issues on teh RPi3B+. For builds in that
context, it may be better to do something like:
# poudriere buld -j main devel/llvm10
# poudriere buld -j main lang/rust
# poudr
On 2021-Jun-23, at 15:28, bob prohaska wrote:
> On Wed, Jun 23, 2021 at 02:03:42PM -0700, Mark Millard wrote:
>> On 2021-Jun-23, at 10:43, bob prohaska wrote:
>>
>>> On Wed, Jun 23, 2021 at 01:34:55AM -0700, Mark Millard wrote:
Not that it helps much, but: 2779096485 == 0xA5A5A5A5
>>
On Wed, Jun 23, 2021 at 02:03:42PM -0700, Mark Millard wrote:
> On 2021-Jun-23, at 10:43, bob prohaska wrote:
>
> > On Wed, Jun 23, 2021 at 01:34:55AM -0700, Mark Millard wrote:
> >>
> >> Not that it helps much, but: 2779096485 == 0xA5A5A5A5
> >>
> >> It appears that such somehow was involved-i
On 2021-Jun-23, at 10:43, bob prohaska wrote:
> On Wed, Jun 23, 2021 at 01:34:55AM -0700, Mark Millard wrote:
>>
>> Not that it helps much, but: 2779096485 == 0xA5A5A5A5
>>
>> It appears that such somehow was involved-in/generated by:
>>
>> [ 24% 1326/5364] cd /wrkdirs/usr/ports/devel/llvm10/w
On Wed, Jun 23, 2021 at 01:34:55AM -0700, Mark Millard wrote:
>
> Not that it helps much, but: 2779096485 == 0xA5A5A5A5
>
> It appears that such somehow was involved-in/generated by:
>
> [ 24% 1326/5364] cd /wrkdirs/usr/ports/devel/llvm10/work/.build &&
> /wrkdirs/usr/ports/devel/llvm10/work/.b
On 2021-Jun-22, at 22:09, bob prohaska wrote:
> Attempts to compile devel/llvm10 on a RPi3 under poudriere using
> poudriere bulk -J 2 -j main devel/llvm10 > bulk.log &
> are failing with:
>
> In file included from
> /wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target/AMDGPU/AMDGPUI
Attempts to compile devel/llvm10 on a RPi3 under poudriere using
poudriere bulk -J 2 -j main devel/llvm10 > bulk.log &
are failing with:
In file included from
/wrkdirs/usr/ports/devel/llvm10/work/llvm-10.0.1.src/lib/Target/AMDGPU/AMDGPUInstructionSelector.cpp:45:
lib/Target/AMDGPU/AMDGPUGenGlobal
38 matches
Mail list logo
