FreeBSD_HEAD-tests - Build #1151 - Unstable:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1151/ to view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
FreeBSD_HEAD-tests - Build #1150 - Fixed:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1150/ to view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To uns
On 30/06/2015 17:32, Simon J. Gerraty wrote:
> Jeffrey Bouquet wrote:
>
>> If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
>> where it otherwise may succeed in /usr/src. Any CLI parameters or> the
>> build system is hardcoded enough so that there will always be
>> problems?
>
On Wed, February 4, 2015 15:04, Jakob Alvermark wrote:
>
> On 31 dec 2014, at 16:24, Jakob Alvermark wrote:
>
>
>> On Tue, December 30, 2014 17:00, Nathan Whitehorn wrote:
>>
>>>
>>
>>> On 12/30/14 06:40, Jakob Alvermark wrote:
>>>
>>>
Hi,
Have been playing with this machi
Jeffrey Bouquet wrote:
> If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
> where it otherwise may succeed in /usr/src. Any CLI parameters or> the
> build system is hardcoded enough so that there will always be
> problems?
The only thing hard coded is the default MAKEOBJDIRPR
Justin Hibbits wrote:
> > Yeah, crossbuilds work fine. It's the actual run-on-real-hardware bit
> > that doesn't.
> >
> > (powerpc64 runs fine in qemu-devel; people should try it!)
>
> r284345 (introduction of metamode) is the problem. I bisected it on
> the power8 and it reliably fails this way
On Tue, Jun 30, 2015 at 8:48 AM, Simon J. Gerraty wrote:
> Justin Hibbits wrote:
>> > Yeah, crossbuilds work fine. It's the actual run-on-real-hardware bit
>> > that doesn't.
>> >
>> > (powerpc64 runs fine in qemu-devel; people should try it!)
>>
>> r284345 (introduction of metamode) is the probl
On Jun 30, 2015 1:11 AM, "Perry Hutchison" wrote:
>
> Konstantin Belousov wrote:
>
> > I think trying to understand why the hack was added is not
> > possible.
>
> In an ideal world, "svn blame" would identify the commit in which
> it was added, and that commit's log entry would explain why :)
T
FreeBSD_HEAD-tests - Build #1149 - Unstable:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1149/ to view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On Tue, 30 Jun 2015, John-Mark Gurney wrote:
> Jeffrey Bouquet wrote this message on Mon, Jun 29, 2015 at 04:10 -0700:
> > If I've a spare /mnt/usr/src , it seems buildworld quite
> > soon fails, where it otherwise may succeed in /usr/src. Any CLI parameters
> > or
> > the build system is hardcod
Konstantin Belousov wrote:
> I think trying to understand why the hack was added is not
> possible.
In an ideal world, "svn blame" would identify the commit in which
it was added, and that commit's log entry would explain why :)
___
freebsd-current@fre
11 matches
Mail list logo