On 01/06/12 13:49, Dimitry Andric wrote:
> On 2012-01-06 09:40, O. Hartmann wrote:
> ...
>> Obviously, these lines in make.conf seem to fail recently when building
>> the sources:
>>
>> ###
>> ### CLANG
>> ###
>>
>> .if !defined(NO_CLANG)
>> .if ${.CURDIR:M/usr/src/*} || ${.CURDIR:M/usr/obj/*}
On Fri, Jan 6, 2012 at 6:57 PM, Freek Dijkstra wrote:
> Hi,
>
> I just tried to install FreeBSD 9.0RC3 with a ZFS-only file system. I
> succeeded by doing a manual install. The bsdinstaller failed: it would
> write not write the new filesystem to /mnt as expected (I presume it has
> overwritten th
Hi,
I just tried to install FreeBSD 9.0RC3 with a ZFS-only file system. I
succeeded by doing a manual install. The bsdinstaller failed: it would
write not write the new filesystem to /mnt as expected (I presume it has
overwritten the memstick filesystem at /). I'm relative new to FreeBSD,
so I'm t
TB --- 2012-01-06 21:20:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 21:20:00 - starting HEAD tinderbox run for i386/i386
TB --- 2012-01-06 21:20:00 - cleaning the object tree
TB --- 2012-01-06 21:20:14 - cvsupping the source tree
TB --- 2012-01-06 21:20:14 - /usr/bin/c
On Fri, 2012-01-06 at 07:16 -0700, Peter wrote:
> Not for stable/9 [__FreeBSD_version 900500+:
Sorry for the delay cleaning that up. It should be fixed as of
r229748.
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.ed
Hi,
You need to build the system with:
options AH_SUPPORT_AR5416
.. even if you're not building _with_ the ath device. This is a
byproduct of how the modules are currently built.
I'm sorry for introducing this breakage. I'm going to try and fix the
driver soon but it's going to require a little
Hello,
I receive this error since I reeled in the most recent sources for FBSD
10.0-CURRENT/amd64. I build the system with CLANG.
clang -O2 -pipe -O2 -fno-strict-aliasing -pipe -pipe -O3
-fno-strict-aliasing -march=native -D_KERNEL -DKLD_MODULE -nostdinc -I.
-I/usr/src/sys/modules/ath/../../dev
I'm more worried about the module loading as well as building. So if
you're not using wireless, fine, but I'd hate to see the default
builds produce modules that can't be used. ;)
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.
On 06.01.2012 22:49 (UTC+1), Alexander Yerenkow wrote:
2012/1/6 Adrian Chadd mailto:adr...@freebsd.org>>
On 6 January 2012 10:19, Rainer Hurling mailto:rhur...@gwdg.de>> wrote:
> I commented all wireless network drivers and their options out.
But the
> error remains. Is it nec
On 06.01.2012 22:42 (UTC+1), Adrian Chadd wrote:
On 6 January 2012 10:19, Rainer Hurling wrote:
I commented all wireless network drivers and their options out. But the
error remains. Is it necessary to have this option uncommented even when the
driver ath is commented out?
Yes, because of ho
2012/1/6 Adrian Chadd
> On 6 January 2012 10:19, Rainer Hurling wrote:
>
> > I commented all wireless network drivers and their options out. But the
> > error remains. Is it necessary to have this option uncommented even when
> the
> > driver ath is commented out?
>
> Yes, because of how the wla
On 6 January 2012 10:19, Rainer Hurling wrote:
> I commented all wireless network drivers and their options out. But the
> error remains. Is it necessary to have this option uncommented even when the
> driver ath is commented out?
Yes, because of how the wlan/ath modules are built. You need to h
On 5 January 2012 05:48, John Baldwin wrote:
> [ A bit excessive on the cross-posting? arch@ alone was probably fine ]
I wanted to capture the attention of relevant people, as I don't want
to break some subtle setup that I'm not at all aware of.
> NFS doesn't actually use them curently, only UF
2012/1/5 Dag-Erling Smørgrav :
> Adrian Chadd writes:
>> Since I'm not using NFS or UFS_ACL, I wondered if that code required.
>> It turns out I can just build a kernel with those two disabled.
>>
>> Would it be possible to remove them from "standard" and make them
>> optional? Or is there a reaso
This is on r228936M amd64
(the only modification is 9.9 patch
in /usr/src/sys/conf/newvers.h)
However, I've never used this pccard before.
1. On inserting the card:
# pciconf -lv
bwi0
On Friday 06 January 2012 19:35:31 Sergey Kandaurov wrote:
> On 6 January 2012 21:50, Oliver Pinter wrote:
> > Hi All!
> >
> > When svn installed and the source stored in git, then now the version
> > detection failed. The attached patch fixed this situation.
>
> FWIW, a different version proposed
On Fri, Jan 6, 2012 at 11:02 AM, Oliver Pinter wrote:
> On Friday 06 January 2012 19:35:31 Sergey Kandaurov wrote:
>> On 6 January 2012 21:50, Oliver Pinter wrote:
>> > Hi All!
>> >
>> > When svn installed and the source stored in git, then now the version
>> > detection failed. The attached patc
[-stable@ removed, as there's no need to cross-post this. dhw]
On Fri, Jan 06, 2012 at 06:50:33PM +0100, Oliver Pinter wrote:
> Hi All!
>
> When svn installed and the source stored in git, then now the version
> detection failed. The attached patch fixed this situation.
> ...
Caveat: I don't u
Hi All!
When svn installed and the source stored in git, then now the version
detection failed. The attached patch fixed this situation.
--
Oliver Pinter
(Tresorium)
From a84c998c251a83ba3fa3c734b7fbc6fe1af17c6a Mon Sep 17 00:00:00 2001
From: Oliver Pinter
Date: Tue, 3 Jan 2012 12:17:43 +0100
On 6 January 2012 21:50, Oliver Pinter wrote:
> Hi All!
>
> When svn installed and the source stored in git, then now the version
> detection failed. The attached patch fixed this situation.
>
FWIW, a different version proposed by Maciej Milewski on -current
some time ago. I don't have/use git, s
On 2012-01-05 21:03, kab...@gmail.com wrote:
On Wed, 04 Jan 2012 14:31:55 -0800
wrote:
> Thanks for the comment Arnaud. For comparative benchmarking
> on[1]Phoronix.com, Michael inva configuration 'in the way the
> developers or production'. This is by rule. However, i poo
On 06.01.2012 18:30 (UTC+1), Adrian Chadd wrote:
i thought I had captured these.
just add
options AH_SUPPORT_AR5416
to your kernel.
Ah, I indeed missed the new option in GENERIC, because I build with
modified kernel config file.
I commented all wireless network drivers and their options o
TB --- 2012-01-06 16:10:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 16:10:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2012-01-06 16:10:00 - cleaning the object tree
TB --- 2012-01-06 16:11:13 - cvsupping the source tree
TB --- 2012-01-06 16:11:13 - /usr/bin
TB --- 2012-01-06 16:10:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 16:10:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2012-01-06 16:10:00 - cleaning the object tree
TB --- 2012-01-06 16:10:39 - cvsupping the source tree
TB --- 2012-01-06 16:10:39 - /usr/bin/c
TB --- 2012-01-06 16:10:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 16:10:00 - starting HEAD tinderbox run for i386/i386
TB --- 2012-01-06 16:10:00 - cleaning the object tree
TB --- 2012-01-06 16:11:13 - cvsupping the source tree
TB --- 2012-01-06 16:11:13 - /usr/bin/c
i thought I had captured these.
just add
options AH_SUPPORT_AR5416
to your kernel.
Adrian
On 6 January 2012 09:14, Rainer Hurling wrote:
> I am getting the following error when trying to build recent 10.0-CURRENT
> kernel (amd64)?
>
> [..snip..]
> cc -O2 -pipe -O2 -fno-strict-aliasing -pipe
I am getting the following error when trying to build recent
10.0-CURRENT kernel (amd64)?
[..snip..]
cc -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Werror -D_KERNEL
-DKLD_MODULE -nostdinc -I. -I/usr/src/sys/modules/ath/../../dev/ath
-I/usr/src/sys/modules/ath/../../dev/ath/ath_hal
-DHAV
TB --- 2012-01-06 16:10:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 16:10:00 - starting HEAD tinderbox run for arm/arm
TB --- 2012-01-06 16:10:00 - cleaning the object tree
TB --- 2012-01-06 16:10:39 - cvsupping the source tree
TB --- 2012-01-06 16:10:39 - /usr/bin/csu
TB --- 2012-01-06 14:58:14 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 14:58:14 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2012-01-06 14:58:14 - cleaning the object tree
TB --- 2012-01-06 14:58:30 - cvsupping the source tree
TB --- 2012-01-06 14:58:30 - /usr
TB --- 2012-01-06 14:09:40 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 14:09:40 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2012-01-06 14:09:40 - cleaning the object tree
TB --- 2012-01-06 14:10:00 - cvsupping the source tree
TB --- 2012-01-06 14:10:00 - /u
TB --- 2012-01-06 09:30:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 09:30:00 - starting HEAD tinderbox run for i386/i386
TB --- 2012-01-06 09:30:00 - cleaning the object tree
TB --- 2012-01-06 09:30:55 - cvsupping the source tree
TB --- 2012-01-06 09:30:55 - /usr/bin/c
> On Thu, Jan 5, 2012 at 2:12 PM, Peter wrote:
>> Hello,
>> Installed 9-RELEASE amd64, svn the latest stable/9 sources,
>> built/installed kernel/world and did pkg_add - It is still by default
>> pointing at -current:
>>
>> pkbsdpkg:#uname -a
>> FreeBSD pkbsdpkg 9.0-STABLE FreeBSD 9.0-STABLE #0 r
On 2012-01-06 09:40, O. Hartmann wrote:
...
Obviously, these lines in make.conf seem to fail recently when building
the sources:
###
### CLANG
###
.if !defined(NO_CLANG)
.if ${.CURDIR:M/usr/src/*} || ${.CURDIR:M/usr/obj/*} || ${.CURDIR:M/sys/*}
Hi Oliver,
The problem is that the ${.CURDI
TB --- 2012-01-06 09:30:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-06 09:30:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2012-01-06 09:30:00 - cleaning the object tree
TB --- 2012-01-06 09:30:30 - cvsupping the source tree
TB --- 2012-01-06 09:30:30 - /usr/bin/c
On 01/06/12 08:31, Roman Divacky wrote:
> what makes you think you're using clang?
>
> On Thu, Jan 05, 2012 at 11:20:34PM +0100, O. Hartmann wrote:
>> When compiling most recent CURRENT on amd64 platform, using CLANG and
>> enabled WITH_LIBCPLUSPLUS, I receive the follwing error since two days
>>
35 matches
Mail list logo
