On Thu, Jun 21, 2018 at 10:49 PM Mark Millard wrote:
> Has the range r328278 < PROBLEM_START <= r330304 been narrowed down
> some more?
>
> (I'm just curious were the problem started.)
After several rounds of binary search, I found it might have something
todo with r329625.
The only thing I thin
On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote:
> On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>>
>> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>>
>>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
Li-Wen reported that the build is done in a 11.1-rel jail though, so
the li
On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote:
> On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>>
>> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>>
>>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
Li-Wen reported that the build is done in a 11.1-rel jail though, so
the
On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>
> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>
> > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> >> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> >> the libarchive (or any userland) change shouldn't be responsi
On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
>> Li-Wen reported that the build is done in a 11.1-rel jail though, so
>> the libarchive (or any userland) change shouldn't be responsible.
>>
>> Can we update a canary builder to somewhere betwe
On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> the libarchive (or any userland) change shouldn't be responsible.
>
> Can we update a canary builder to somewhere between r328278 and r88?
butler1.nyi.freebsd.org is runnin
On 2018-Jun-18, at 6:03 PM, Mark Millard wrote:
> On 2018-Jun-18, at 4:08 PM, Bryan Drewery wrote:
>
>> On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
>>> ranlib -D libpcap.a
>>> ranlib: fatal: Failed to open 'libpcap.a'
>>
>> Where is this error even coming from? It's not in the usr.bin/ar code
>> an
On 2018-Jun-18, at 4:08 PM, Bryan Drewery wrote:
> On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
>> ranlib -D libpcap.a
>> ranlib: fatal: Failed to open 'libpcap.a'
>
> Where is this error even coming from? It's not in the usr.bin/ar code
> and ranlib does not cause it.
>
> # ranlib -D uh
> ranlib
On 18 June 2018 at 19:29, Bryan Drewery wrote:
>
> The error is coming from libarchive which had a change between those
> revisions:
>
>>
>> r328332 | mm | 2018-01-24 06:24:17 -0800 (Wed, 24 Jan 2018) | 14 lines
Li-Wen repor
On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 5:04 PM Mark Millard via freebsd-toolchain
> wrote:
>>
>> On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
>>
>>> On 6/15/2018 10:55 PM, Mark Millard wrote:
In watching ci.freebsd.org builds I've seen a notable
number of
On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
> ranlib -D libpcap.a
> ranlib: fatal: Failed to open 'libpcap.a'
Where is this error even coming from? It's not in the usr.bin/ar code
and ranlib does not cause it.
# ranlib -D uh
ranlib: warning: uh: no such file
--
Regards,
Bryan Drewery
signature
On 6/18/2018 3:31 PM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 6:27 PM Bryan Drewery wrote:
>>
>> On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
>>> On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
On 6/15/2018 10:55 PM, Mark Millard wrote:
> In watching ci.freebsd.org
On Mon, Jun 18, 2018 at 5:04 PM Mark Millard via freebsd-toolchain
wrote:
>
> On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
>
> > On 6/15/2018 10:55 PM, Mark Millard wrote:
> >> In watching ci.freebsd.org builds I've seen a notable
> >> number of one time failures, such as (example from
> >>
On Mon, Jun 18, 2018 at 6:27 PM Bryan Drewery wrote:
>
> On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
> > On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
> >> On 6/15/2018 10:55 PM, Mark Millard wrote:
> >>> In watching ci.freebsd.org builds I've seen a notable
> >>> number of o
On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
> On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
>> On 6/15/2018 10:55 PM, Mark Millard wrote:
>>> In watching ci.freebsd.org builds I've seen a notable
>>> number of one time failures, such as (example from
>>> powerpc64):
>>>
>>> --
On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
> On 6/15/2018 10:55 PM, Mark Millard wrote:
>> In watching ci.freebsd.org builds I've seen a notable
>> number of one time failures, such as (example from
>> powerpc64):
>>
>> --- all_subdir_lib/libufs ---
>> ranlib -D libufs.a
>> ranlib: fat
On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
> On 6/15/2018 10:55 PM, Mark Millard wrote:
> > In watching ci.freebsd.org builds I've seen a notable
> > number of one time failures, such as (example from
> > powerpc64):
> >
> > --- all_subdir_lib/libufs ---
> > ranlib -D libufs.a
On 6/15/2018 10:55 PM, Mark Millard wrote:
> In watching ci.freebsd.org builds I've seen a notable
> number of one time failures, such as (example from
> powerpc64):
>
> --- all_subdir_lib/libufs ---
> ranlib -D libufs.a
> ranlib: fatal: Failed to open 'libufs.a'
> *** [libufs.a] Error code 70
>
In watching ci.freebsd.org builds I've seen a notable
number of one time failures, such as (example from
powerpc64):
--- all_subdir_lib/libufs ---
ranlib -D libufs.a
ranlib: fatal: Failed to open 'libufs.a'
*** [libufs.a] Error code 70
where the next build works despite the change being
irrelevan
I've had reason to be experimenting with libkvm recently
and have repeatedly run into the following when doing
buildworld with -j16. (I tend to run full buildworlds even
for well-localized changes.) The context is having run
buildworld to completion before so the update is
incremental.
--- kvm_get
On 5/9/2017 11:10 AM, Mark Millard wrote:
> I've had reason to be experimenting with libkvm recently
> and have repeatedly run into the following when doing
> buildworld with -j16. (I tend to run full buildworlds even
> for well-localized changes.) The context is having run
> buildworld to completi
On 22.11.11 22:26, Ivan Klymenko wrote:
В Tue, 22 Nov 2011 19:35:22 +0100
Andreas Tobler пишет:
Anyone seen this too?
make: don't know how to make
/usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
*** Error code 2
Happens on amd64 and powerpc64 while doing a make -j4 buildworld.
Con
В Tue, 22 Nov 2011 19:35:22 +0100
Andreas Tobler пишет:
> Anyone seen this too?
>
> make: don't know how to make
> /usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
> *** Error code 2
>
> Happens on amd64 and powerpc64 while doing a make -j4 buildworld.
> Continuing with -DNO_CLEAN -j
On Tue, Nov 22, 2011 at 10:35 AM, Andreas Tobler
wrote:
> Anyone seen this too?
>
Yes, I've been running into this error too.
Navdeep
> make: don't know how to make
> /usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
> *** Error code 2
>
> Happens on amd64 and powerpc64 while doing a m
В Tue, 22 Nov 2011 21:20:10 +0200
Ivan Klymenko пишет:
> В Tue, 22 Nov 2011 19:35:22 +0100
> Andreas Tobler пишет:
>
> > Anyone seen this too?
> >
> > make: don't know how to make
> > /usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
> > *** Error code 2
> >
> > Happens on amd64 and
В Tue, 22 Nov 2011 19:35:22 +0100
Andreas Tobler пишет:
> Anyone seen this too?
>
> make: don't know how to make
> /usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
> *** Error code 2
>
> Happens on amd64 and powerpc64 while doing a make -j4 buildworld.
> Continuing with -DNO_CLEAN -j
Anyone seen this too?
make: don't know how to make
/usr/obj/export/devel/fbsd/src/tmp/usr/lib/libkrb5.a. Stop
*** Error code 2
Happens on amd64 and powerpc64 while doing a make -j4 buildworld.
Continuing with -DNO_CLEAN -j1 completes the build.
Thanks,
Andreas
> Bruce Evans wrote:
> > >"make buildworld" completes without a problem.
> > >
> > >"make -j 4 buildworld" gives:
> >
> > libncurses now has lots of internal utilities. Apparently the
> > dependencies for them are incomplete. The utilities are are also
> > built at the wrong time and break cros
Bruce Evans wrote:
> >"make buildworld" completes without a problem.
> >
> >"make -j 4 buildworld" gives:
>
> libncurses now has lots of internal utilities. Apparently the
> dependencies for them are incomplete. The utilities are are also
> built at the wrong time and break cross compiling. Se
>"make buildworld" completes without a problem.
>
>"make -j 4 buildworld" gives:
libncurses now has lots of internal utilities. Apparently the
dependencies for them are incomplete. The utilities are are also
built at the wrong time and break cross compiling. See the old curses
(libmytinfo part
I'm getting the same with -j 2 here.
-
Chris D. Faulhaber <[EMAIL PROTECTED]> | All the true gurus I've met never
System/Network Administrator,| claimed they were one, and always
Reality Check Information, Inc. | pointed to someone better.
To Unsubscribe: send mail to [EM
cvsup'd -current source at 0840 PST 31 Aug 99
"make buildworld" completes without a problem.
"make -j 4 buildworld" gives:
cc -o make_hash -O2 -pipe -mpentiumpro -I. -I/usr/src/lib/libncurses
-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses
-I/usr/src/lib/libncurses/../../contrib/ncur
32 matches
Mail list logo
