I must not abbreviate this time...
On 170228-20:07-0500, Harry Putnam wrote:
> Miroslav Rovis writes:
>
> > On 170226-09:42-0500, Harry Putnam wrote:
> >> Stroller writes:
> > ...
> >>
> >> > Example at the beginning: [32;01m *
> >> > Example from the end: *
> >> >
> >> > Output to the te
Peter Humphrey writes:
> On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
Harry wrote:
>> I guess I'll try this once more... Its still a big log but I cleaned
>> up the escapes ... it is a fresh try at building
>> xf86-video-virtualbox-5.1.14
[...]
Peter replied:
> /lib/modules/4.9.10-gent
Miroslav Rovis writes:
> On 170226-09:42-0500, Harry Putnam wrote:
>> Stroller writes:
> ...
>>
>> > Example at the beginning: [32;01m *
>> > Example from the end: *
>> >
>> > Output to the terminal these would show the text in different colours,
>> > but the output was redirected to a tex
Stroller writes:
[...]
> I would be looking primarily at the next point the word "error" comes up
> properly, which is here:
>
> from
> /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/src/VBox/Runtime/common/alloc/alloc.cpp:34:
> /lib/modules/4.
On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
> I guess I'll try this once more... Its still a big log but I cleaned
> up the escapes ... it is a fresh try at building
> xf86-video-virtualbox-5.1.14
>
> Still failing in the same way and still not seeing clues in the
> log... probably my ow
On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
> I guess I'll try this once more... Its still a big log but I cleaned
> up the escapes ... it is a fresh try at building
> xf86-video-virtualbox-5.1.14
>
> Still failing in the same way and still not seeing clues in the
> log... probably my ow
Stroller writes:
>> On 25 Feb 2017, at 14:19, Harry Putnam wrote:
>>
>> I've attached a hefty log of some 4000 lines and hope someone will be
>> patient enough to try to identify what is causing the problem.
>
> I took a look at this, but the broken colour codes throughout the log make it
>
Dale writes:
> Harry Putnam wrote:
>>
>> Just so you know... I did try that. [--color n] The resulting log
>> looked exactly the same. I posted that fact in an earlier request for
>> help a week or so ago in which I remarked how using the no-color
>> emerge option didn't seem to make a bit of di
On 170226-09:42-0500, Harry Putnam wrote:
> Stroller writes:
...
>
> > Example at the beginning: [32;01m *
> > Example from the end: *
> >
> > Output to the terminal these would show the text in different colours,
> > but the output was redirected to a textfile or mishandled in a
> > copy-pa
Harry Putnam wrote:
>
> Just so you know... I did try that. [--color n] The resulting log
> looked exactly the same. I posted that fact in an earlier request for
> help a week or so ago in which I remarked how using the no-color
> emerge option didn't seem to make a bit of difference. I don't expe
Miroslav Rovis writes:
> On 170225-09:19-0500, Harry Putnam wrote:
>> Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
>> Hardware: HP xw8600 - 2x Xeon CPU X5450 @ 3.00GHz - 32 GB ram
>>
> [ some cca. 80k text cut here ]
>
> Go for the guides, in which you will find that se
Stroller writes:
>> On 25 Feb 2017, at 14:19, Harry Putnam wrote:
>>
>> I've attached a hefty log of some 4000 lines and hope someone will be
>> patient enough to try to identify what is causing the problem.
>
> I took a look at this, but the broken colour codes throughout the
> log make it qu
12 matches
Mail list logo