On 18 Jun 2015, at 08:24, Garrett Cooper wrote:
>
> On Jun 17, 2015, at 23:22, Andriy Gapon wrote:
...
>> Looks like my rather innocent manipulations of CFLAGS could be causing the
>> problem.
>> Without my make.conf:
>> mkdep -f .depend -a
>> -I/usr/devel/svn2/head/lib/clang/libllvmsupport/../
On Jun 17, 2015, at 23:22, Andriy Gapon wrote:
> On 18/06/2015 02:26, Simon J. Gerraty wrote:
>> Andriy Gapon wrote:
Seems like there is some problem with 'toolchain' target in the latest
head.
Output of running `make toolchain TARGET=i386` on amd64 system can be found
here:
On 18/06/2015 02:26, Simon J. Gerraty wrote:
> Andriy Gapon wrote:
>>> Seems like there is some problem with 'toolchain' target in the latest head.
>>> Output of running `make toolchain TARGET=i386` on amd64 system can be found
>>> here: http://dpaste.com/3RD3C4V
>>>
>>
>> AFAICS, it still worked
FreeBSD_HEAD-tests - Build #1113 - Failure:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1113/ to view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
Andriy Gapon wrote:
> > Seems like there is some problem with 'toolchain' target in the latest head.
> > Output of running `make toolchain TARGET=i386` on amd64 system can be found
> > here: http://dpaste.com/3RD3C4V
> >
>
> AFAICS, it still worked as of r283188.
There has been a clang update s
On 17/06/2015 23:42, Andriy Gapon wrote:
>
> Seems like there is some problem with 'toolchain' target in the latest head.
> Output of running `make toolchain TARGET=i386` on amd64 system can be found
> here: http://dpaste.com/3RD3C4V
>
AFAICS, it still worked as of r283188.
--
Andriy Gapon
___
Seems like there is some problem with 'toolchain' target in the latest head.
Output of running `make toolchain TARGET=i386` on amd64 system can be found
here: http://dpaste.com/3RD3C4V
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http:/
On 2015-06-17 13:39, Jonathan Anderson wrote:
>> On Jun 17, 2015, at 2:39 PM, Konstantin Belousov wrote:
>>
>> On Wed, Jun 17, 2015 at 02:32:16PM -0230, Jonathan Anderson wrote:
>>> The system boots the 11-CURRENT kernel in "safe mode" (not sure if it???s
>>> the kern.mp.disabled or kern.eventtim
> On Jun 17, 2015, at 2:39 PM, Konstantin Belousov wrote:
>
> On Wed, Jun 17, 2015 at 02:32:16PM -0230, Jonathan Anderson wrote:
>> The system boots the 11-CURRENT kernel in "safe mode" (not sure if it???s
>> the kern.mp.disabled or kern.eventtimer.periodic that???s causing that),
>> after whic
On Wed, Jun 17, 2015 at 02:32:16PM -0230, Jonathan Anderson wrote:
> The system boots the 11-CURRENT kernel in "safe mode" (not sure if it???s the
> kern.mp.disabled or kern.eventtimer.periodic that???s causing that), after
> which `dmesg -a` produces the following output:
>
> https://people.fre
> On Jun 17, 2015, at 2:24 PM, Konstantin Belousov wrote:
>
> On Wed, Jun 17, 2015 at 02:19:14PM -0230, Jonathan Anderson wrote:
>>>
>>> On Jun 17, 2015, at 12:00 PM, Konstantin Belousov
>>> wrote:
>>>
>>> Show bootverbose dmesg.
>>
>> Is that different from the ???Verbose??? option in the
> On Jun 17, 2015, at 9:35 AM, Andrey Chernov wrote:
>
> Signed PGP part
> On 17.06.2015 16:58, Marcel Moolenaar wrote:
> >
> >> On Jun 16, 2015, at 9:53 PM, Andrey Chernov
> >> wrote:
> >
> >> Should be no any %FF, but single char in pre libxo ls or nothing
> >> in post libxo one.
> >>
> >> Us
On Wed, Jun 17, 2015 at 02:19:14PM -0230, Jonathan Anderson wrote:
> >
> > On Jun 17, 2015, at 12:00 PM, Konstantin Belousov
> > wrote:
> >
> > Show bootverbose dmesg.
>
> Is that different from the ???Verbose??? option in the loader menu? When I do
> a loader-menu-driven verbose boot, I see:
>
> On Jun 17, 2015, at 12:00 PM, Konstantin Belousov wrote:
>
> Show bootverbose dmesg.
Is that different from the “Verbose” option in the loader menu? When I do a
loader-menu-driven verbose boot, I see:
https://drive.google.com/file/d/0B2eLORKzuvdOZ1I4SVB0aFNSenM
Jon
--
jonat...@freebsd.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.06.2015 16:58, Marcel Moolenaar wrote:
>
>> On Jun 16, 2015, at 9:53 PM, Andrey Chernov
>> wrote:
>
>> Should be no any %FF, but single char in pre libxo ls or nothing
>> in post libxo one.
>>
>> Use LANG=ru_RU.KOI8-R before touch command.
On Wed, Jun 17, 2015 at 11:07:24AM -0230, Jonathan Anderson wrote:
> Hi all,
>
> I???m trying to upgrade an old Sony VAIO laptop from 10.1 to -CURRENT.
> Everything seemed to work well with 10.1, but on -CURRENT I get no further in
> the boot than:
>
> ```
> ACPI: No DMAR table found
> Event ti
On 17 June 2015 at 15:00, Arseny Nasokin wrote:
> There was some talks back on 2011/2012 about this option, that kernel
> should include it, but there is no such option (you can see at least
> PR#163630 about this).
>
> Also I've not found any commit which adds this option and no code in kernel
>
> On Jun 16, 2015, at 9:53 PM, Andrey Chernov wrote:
> Should be no any %FF, but single char in pre libxo ls or nothing in post
> libxo one.
>
> Use
> LANG=ru_RU.KOI8-R
> before touch command. It looks like you create file with name "%FF" instead.
No difference:
fbsdvm64% env LANG=ru_RU.KOI8
Hi all,
I’m trying to upgrade an old Sony VAIO laptop from 10.1 to -CURRENT. Everything
seemed to work well with 10.1, but on -CURRENT I get no further in the boot
than:
```
ACPI: No DMAR table found
Event timer “LAPIC” quality 600
ACPI APIC Table:
```
If I disable ACPI, I get:
```
APIC: Cou
There was some talks back on 2011/2012 about this option, that kernel
should include it, but there is no such option (you can see at least
PR#163630 about this).
Also I've not found any commit which adds this option and no code in kernel
which depends on it.
Is note about this option should be no
Hi Kevin,
you signed up as tester of urtw(4). I have converted urtw(4)
and uploaded new patch at:
https://reviews.freebsd.org/D2655
Please try, report and update the project page.
https://wiki.freebsd.org/projects/ifnet/net80211
Thanks a lot for your help with the project.
--
Totus tuus,
21 matches
Mail list logo
