I am trying to build stable/{9,8} GENERIC kernels on a recent-ish head system
(cc is clang).
To be sure I first try to build the respective tool-chains using the following
process:
1. make make
2. /usr/obj/path/to/make toolchain WITHOUT_CLANG=1 NO_WERROR=yes WERROR=
WERROR stuff is to increase ch
Hi,
I'm running iperf on Emulex's OCE network adapter in Freebsd-10-current. At
heavy traffic (iperf with ~10 connections), iperf is hanging. The same driver
is working on all other Freebsd versions.
top -HS shows the below information.
PID USERNAME PRI NICE SIZERES STATE C TIME
I have a patch that I intend to commit before the 10.0 code slush that removes
GCC and libstdc++ from the default build on platforms where clang is the system
compiler. We definitely don't want to be supporting our 6-year-old versions of
these for the lifetime of the 10.x branch.
David
On 2
on 23/08/2013 12:16 David Chisnall said the following:
> I have a patch that I intend to commit before the 10.0 code slush that
> removes GCC and libstdc++ from the default build on platforms where clang
> is the system compiler. We definitely don't want to be supporting our
> 6-year-old versions
I don't know if you are aware that IF you really do that we will have serious
problems to ship packages for 10. USE_GCC=any is the fallback in the
portstree for all ports that are unable to build with clang which was introduced
when HEAD switched to clang as default cc. Right now there are 150 port
On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote:
> I don't know if you are aware that IF you really do that we will have serious
> problems to ship packages for 10. USE_GCC=any is the fallback in the
> portstree for all ports that are unable to build with clang which was
> introduced
> when HE
On 8/23/13 6:35 PM, David Chisnall wrote:
On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote:
I don't know if you are aware that IF you really do that we will have serious
problems to ship packages for 10. USE_GCC=any is the fallback in the
portstree for all ports that are unable to build with
23.08.2013 13:16, David Chisnall пишет:
> I have a patch that I intend to commit before the 10.0 code slush that
> removes GCC and libstdc++ from the default build on platforms where clang is
> the system compiler. We definitely don't want to be supporting our
> 6-year-old versions of these fo
On 23 Aug 2013, at 11:42, Julian Elischer wrote:
> no, I believe we have said that 10 would ship with clang by default. NO
> mention was made about gcc being absent, and I am uncomfortable with taking
> that step yet. Having gcc just present, will not hurt you.. even after it is
> gone we wil
On 08/23/13 02:18, Hans Petter Selasky wrote:
On 08/23/13 02:29, George Mitchell wrote:
On 08/22/13 07:34, Hans Petter Selasky wrote:
Here's the result:
[...]
(at which point if I type control-c to stop usbdump, the system gets a
fatal kernel mode translation fault, but that's another story.)
Hi!
> > I have a patch that I intend to commit before the 10.0 code
> > slush that removes GCC and libstdc++ from the default build on
> > platforms where clang is the system compiler. We definitely don't
> > want to be supporting our 6-year-old versions of these for the
> > lifetime of the 10.x
On Fri, Aug 23, 2013 at 12:35 PM, David Chisnall wrote:
> On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote:
>
>> I don't know if you are aware that IF you really do that we will have serious
>> problems to ship packages for 10. USE_GCC=any is the fallback in the
>> portstree for all ports that a
23.08.2013 15:16, Kurt Jaeger пишет:
> Hi!
>
>>> I have a patch that I intend to commit before the 10.0 code
>>> slush that removes GCC and libstdc++ from the default build on
>>> platforms where clang is the system compiler. We definitely don't
>>> want to be supporting our 6-year-old versions o
2013/8/22 John Baldwin :
> On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
>> 2013/8/21 John Baldwin :
>> > On Monday, August 19, 2013 11:13:02 pm Daniel Eischen wrote:
>> >> On Mon, 19 Aug 2013, Adrian Chadd wrote:
>> >>
>> >> > Yes! Please file a PR!
>> >>
>> >> This sorta implies t
On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote:
> On 8/23/13 6:35 PM, David Chisnall wrote:
> > On 23 Aug 2013, at 10:58, Bernhard Fr?hlich wrote:
> >
> >> I don't know if you are aware that IF you really do that we will have
> >> serious
> >> problems to ship packages for 10. U
On 23.08.13 14:16, Kurt Jaeger wrote:
Hi!
I have a patch that I intend to commit before the 10.0 code
slush that removes GCC and libstdc++ from the default build on
platforms where clang is the system compiler. We definitely don't
want to be supporting our 6-year-old versions of these for the
In message <52174d51.2050...@digsys.bg>, Daniel Kalchev writes:
>> - 9.x gcc default and clang in base;
>> - 10.x clang default and gcc in ports;
>
>I believe this is the best idea so far. As long as these ports work with
>gcc in ports, that is.
+1
--
Poul-Henning Kamp | UNIX since Zilog
23.08.2013 12:58, Bernhard Fröhlich wrote:
I don't know if you are aware that IF you really do that we will have serious
problems to ship packages for 10. USE_GCC=any is the fallback in the
portstree for all ports that are unable to build with clang which was introduced
when HEAD switched to clan
$ /usr/obj/usr/devel/svn/base/stable/8/make.amd64/make kernel-toolchain
WITHOUT_CLANG=1 __MAKE_CONF=/dev/null SRCCONF=/dev/null
...
cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H
-DPREFIX=\"/usr/obj/usr/devel/svn/base/stable/8/tmp/usr\"
-I/usr/obj/usr/devel/svn/base/stable/8/tmp/usr/devel/svn/base/stable
on 23/08/2013 14:06 David Chisnall said the following:
> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its
> atomic generation so you can't use it sensibly without lots of inline
> assembly (which it doesn't support for newer architectures) for
> multithreaded things.
>
>
On Fri, Aug 23, 2013 at 2:12 PM, Volodymyr Kostyrko wrote:
> 23.08.2013 12:58, Bernhard Fröhlich wrote:
>>
>> I don't know if you are aware that IF you really do that we will have
>> serious
>> problems to ship packages for 10. USE_GCC=any is the fallback in the
>> portstree for all ports that are
On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote:
> On 23 Aug 2013, at 11:42, Julian Elischer wrote:
>
> > no, I believe we have said that 10 would ship with clang by default. NO
> > mention was made about gcc being absent, and I am uncomfortable with taking
> > that step yet. Having gcc
On 08/23/13 07:26, Andriy Gapon wrote:
on 23/08/2013 14:06 David Chisnall said the following:
Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its
atomic generation so you can't use it sensibly without lots of inline
assembly (which it doesn't support for newer architectur
On 23 Aug 2013, at 13:26, Andriy Gapon wrote:
> On the other hand these tools are perfect for building FreeBSD kernel and
> base.
> Extrapolating my experience with base GCC I am very confident in it as a
> FreeBSD development tool.
> Extrapolating my experience with Clang I am not yet confident
on 23/08/2013 15:34 Nathan Whitehorn said the following:
> On 08/23/13 07:26, Andriy Gapon wrote:
>> on 23/08/2013 14:06 David Chisnall said the following:
>>> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its
>>> atomic generation so you can't use it sensibly without lots
on 23/08/2013 15:56 David Chisnall said the following:
> So you don't want a working debugger? Our gdb doesn't work at all on MIPS
> and barely works with code compiled with clang or a recent gcc.
I am capable of using devel/gdb. Or do you mean kernel debugger?
> We are
> planning on importing
On Aug 23, 2013, at 14:16, Andriy Gapon wrote:
> $ /usr/obj/usr/devel/svn/base/stable/8/make.amd64/make kernel-toolchain
> WITHOUT_CLANG=1 __MAKE_CONF=/dev/null SRCCONF=/dev/null
...
> It seems that the problem is specific to stable/8 and is caused by missing
> -std=gnu89. And that seems to be ca
Slawa Olhovchenkov wrote:
> Its posible use currentle FreeBSD on NFS_V4 root?
>
> Explain:
>
> pxeboot do NFS_v3 (not NFS_v4) mount and pass fd to kernel.
> In this setup kernel can use only configured (established) nfs fh.
> This is not allowed to switch version or some options.
>
> When pxeboo
On 08/23/13 07:30, Ian Lepore wrote:
On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote:
On 23 Aug 2013, at 11:42, Julian Elischer wrote:
no, I believe we have said that 10 would ship with clang by default. NO mention
was made about gcc being absent, and I am uncomfortable with taking t
On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
> 2013/8/22 John Baldwin :
> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
> >> 2013/8/21 John Baldwin :
> >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eischen wrote:
> >> >> On Mon, 19 Aug 2013, Adrian Chadd wrote:
On Aug 23, 2013, at 5:06 AM, David Chisnall wrote:
> On 23 Aug 2013, at 11:42, Julian Elischer wrote:
>
>> no, I believe we have said that 10 would ship with clang by default. NO
>> mention was made about gcc being absent, and I am uncomfortable with taking
>> that step yet. Having gcc just p
On Aug 23, 2013, at 5:16 AM, Kurt Jaeger wrote:
> Hi!
>
>>> I have a patch that I intend to commit before the 10.0 code
>>> slush that removes GCC and libstdc++ from the default build on
>>> platforms where clang is the system compiler. We definitely don't
>>> want to be supporting our 6-year-o
On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote:
> On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
>> 2013/8/22 John Baldwin :
>> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
>> >> 2013/8/21 John Baldwin :
>> >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eisc
On 23 Aug 2013, at 14:52, Warner Losh wrote:
> No. That breaks non x86 architecutres. gcc must remain in base for now, or
> there's no bootstrap ability. Nobody has done the lifting to cleanly
> integrate gcc as a port into buildworld, althogh Brooks' work gets us most of
> the way there.
We'
Hi!
If firewire code doesn't build on clang correctly, have you filed a bug so
it gets looked at before 10.0 is released? that's pretty broken
code/behaviour.
-adrian
On 23 August 2013 04:46, Slawa Olhovchenkov wrote:
> On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote:
>
> >
On Aug 23, 2013, at 6:30 AM, Ian Lepore wrote:
> On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote:
>> On 23 Aug 2013, at 11:42, Julian Elischer wrote:
>>
>>> no, I believe we have said that 10 would ship with clang by default. NO
>>> mention was made about gcc being absent, and I am unc
On Aug 23, 2013, at 7:54 AM, David Chisnall wrote:
> On 23 Aug 2013, at 14:52, Warner Losh wrote:
>> No. That breaks non x86 architecutres. gcc must remain in base for now, or
>> there's no bootstrap ability. Nobody has done the lifting to cleanly
>> integrate gcc as a port into buildworld, alt
According to John-Mark Gurney on Thu, Aug 22, 2013 at 01:20:27PM -0700:
> I have developed a patch to improve AES-NI performance. If you took the
> AES-XTS algorithm into userland (no cryptodev or geli usage), these
> changes improve the performance over 10x in my tests (from ~150MB/sec to
> over
On Fri, Aug 23, 2013 at 03:02:18PM +0400, Boris Samorodov wrote:
> 23.08.2013 13:16, David Chisnall ??:
>
>> I have a patch that I intend to commit before the 10.0 code
>> slush that removes GCC and libstdc++ from the default build
>> on platforms where clang is the system compiler. We de
2013/8/23 Davide Italiano :
> On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote:
>> On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
>>> 2013/8/22 John Baldwin :
>>> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
>>> >> 2013/8/21 John Baldwin :
>>> >> > On Monday, Augu
Hi current,
I have FreeBSD 10.0-CURRENT #5 r254404 on my laptop. During reboot,
I get the following LOR. Could someone please fix this?
Thanks!
Ke Sun
Syncing disks, vnodes remaining...0 0 0 0 0 0 done
All buffers synced.
lock order reversal:
1st 0xfe00094bd5f0 zfs (zfs) @ /usr/src/sys/kern
On Friday, August 23, 2013 9:53:12 am Davide Italiano wrote:
> On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote:
> > On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
> >> 2013/8/22 John Baldwin :
> >> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
> >> >> 2013/8/21 Jo
On 8/23/2013 11:16 AM, Ollivier Robert wrote:
> According to John-Mark Gurney on Thu, Aug 22, 2013 at 01:20:27PM -0700:
>> I have developed a patch to improve AES-NI performance. If you took the
>> AES-XTS algorithm into userland (no cryptodev or geli usage), these
>> changes improve the performan
> As for me I expect something like this:
> . 9.x gcc default and clang in base;
> . 10.x clang default and gcc in base;
> . 11.x gcc withdraw.
There is also the concern whether clang in base will reliably build gcc
required for some ports, and then there are those CPU architectures for which
cl
Ollivier Robert wrote this message on Fri, Aug 23, 2013 at 17:16 +0200:
> According to John-Mark Gurney on Thu, Aug 22, 2013 at 01:20:27PM -0700:
> > I have developed a patch to improve AES-NI performance. If you took the
> > AES-XTS algorithm into userland (no cryptodev or geli usage), these
> >
Mike Tancsa wrote this message on Fri, Aug 23, 2013 at 11:26 -0400:
> On 8/23/2013 11:16 AM, Ollivier Robert wrote:
> > According to John-Mark Gurney on Thu, Aug 22, 2013 at 01:20:27PM -0700:
> >> I have developed a patch to improve AES-NI performance. If you took the
> >> AES-XTS algorithm into u
On 8/23/13 8:26 PM, Andriy Gapon wrote:
on 23/08/2013 14:06 David Chisnall said the following:
Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its
atomic generation so you can't use it sensibly without lots of inline
assembly (which it doesn't support for newer architectu
On 8/23/2013 2:05 PM, John-Mark Gurney wrote:
>> Speeding up userland AES is very interesting to me for a couple of apps.
>> If there is a proper way I should test on RELENG_9, please let me know
>> as I am few boxes that I would be happy to test/deploy on.
>
> My patch would only effect userland
On 8/23/13 7:55 PM, Poul-Henning Kamp wrote:
In message <52174d51.2050...@digsys.bg>, Daniel Kalchev writes:
- 9.x gcc default and clang in base;
- 10.x clang default and gcc in ports;
I believe this is the best idea so far. As long as these ports work with
gcc in ports, that is.
+1
well as
According to John-Mark Gurney:
pjd did not merge (as he said at the time of commit) r226839 & r226839. Is
there any objection to merge these two (and possibly 247061 as well --
copyright update)?
>
> You repeated r226839 twice. What is the correct second revision?
You are right, I wanted to s
Mike Tancsa wrote this message on Fri, Aug 23, 2013 at 14:19 -0400:
> On 8/23/2013 2:05 PM, John-Mark Gurney wrote:
> >> Speeding up userland AES is very interesting to me for a couple of apps.
> >> If there is a proper way I should test on RELENG_9, please let me know
> >> as I am few boxes that
On Friday, August 23, 2013 4:55:06 am Venkata Duvvuru wrote:
> Hi,
>
> I'm running iperf on Emulex's OCE network adapter in Freebsd-10-current. At
> heavy traffic (iperf with ~10 connections), iperf is hanging. The same
> driver is working on all other Freebsd versions.
>
> top -HS shows the belo
On Wednesday, August 21, 2013 8:30:05 pm Yuri wrote:
> On 08/21/2013 17:10, Mateusz Guzik wrote:
> > Short answer is provide epollops with your own fo_close and the rest as
> > it is currently in kqueueops. All function are static, but this is not a
> > real problem since you have to modify kern_ev
On Fri, Aug 23, 2013, at 13:20, Julian Elischer wrote:
> On 8/23/13 7:55 PM, Poul-Henning Kamp wrote:
> > In message <52174d51.2050...@digsys.bg>, Daniel Kalchev writes:
> >
> >>> - 9.x gcc default and clang in base;
> >>> - 10.x clang default and gcc in ports;
> >> I believe this is the best idea
John-Mark Gurney writes:
> Mike Tancsa writes:
> > John-Mark Gurney writes:
> > > My patch would only effect userland applications that use /dev/crypto...
> > For me its ssh which I think does, no ?
> It looks like it uses OpenSSL for it's crypto, not /dev/crypto...
It uses OpenSSL engines, whi
On 08/23/2013 10:02, John Baldwin wrote:
There is something similar: see devfs_ops_f in sys/fs/devfs/devfs_vnops.c.
devfs_ops_f is a local static fileops object for devfs. I don't see how
is this similar to our situation. devfs doesn't overload any other file
system, they are a file system on
On Fri, 2013-08-23 at 13:06 -0700, Yuri wrote:
> On 08/23/2013 10:02, John Baldwin wrote:
> > There is something similar: see devfs_ops_f in sys/fs/devfs/devfs_vnops.c.
>
> devfs_ops_f is a local static fileops object for devfs. I don't see how
> is this similar to our situation. devfs doesn't ov
Dag-Erling Smrgrav wrote this message on Fri, Aug 23, 2013 at 21:30 +0200:
> John-Mark Gurney writes:
> > Mike Tancsa writes:
> > > John-Mark Gurney writes:
> > > > My patch would only effect userland applications that use /dev/crypto...
> > > For me its ssh which I think does, no ?
> > It looks
Hi,
I'd like to commit this to -10. It migrates the if_lagg locking from a rw
lock to a rm lock. We see a bit of contention between the transmit and
receive sides of lagg during traffic loads (10+ gigabit per second.) Using
rmlocks eliminate this.
http://people.freebsd.org/~adrian/netflix/2013081
On Fri, Aug 23, 2013 at 09:32:35AM -0400, Rick Macklem wrote:
> Slawa Olhovchenkov wrote:
> > Its posible use currentle FreeBSD on NFS_V4 root?
> >
> > Explain:
> >
> > pxeboot do NFS_v3 (not NFS_v4) mount and pass fd to kernel.
> > In this setup kernel can use only configured (established) nfs
On Fri, Aug 23, 2013 at 06:54:44AM -0700, Adrian Chadd wrote:
> Hi!
>
> If firewire code doesn't build on clang correctly, have you filed a bug so
> it gets looked at before 10.0 is released? that's pretty broken
> code/behaviour.
How I can do it correctly?
Currently in src.conf:
WITHOUT_CLANG=
Hello.
I have:
FreeBSD 10.0-CURRENT #0 r254719
and
and jail for i386 environment
when building the port devel/gettext I get the following error:
http://privatepaste.com/46f9477022
who can tell me what could be the cause of the error and how to fix it?
still about a month ago, I successfully comp
On 8/23/13 3:35 AM, David Chisnall wrote:
On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote:
I don't know if you are aware that IF you really do that we will have serious
problems to ship packages for 10. USE_GCC=any is the fallback in the
portstree for all ports that are unable to build with
On 08/23/2013 13:36, Ian Lepore wrote:
I think the point is that devfs_ops_f provides several devfs-specific
methods and then "inherits" the rest by referencing the standard
vn_whatever functions. Since John recommended that you expose the
fo_whatever methods, I think he's suggesting you build y
On Aug 23, 2013, at 4:01 PM, Alfred Perlstein wrote:
> On 8/23/13 3:35 AM, David Chisnall wrote:
>> On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote:
>>
>>> I don't know if you are aware that IF you really do that we will have
>>> serious
>>> problems to ship packages for 10. USE_GCC=any is t
On 08/23/13 07:11, George Mitchell wrote:
On 08/23/13 02:18, Hans Petter Selasky wrote:
On 08/23/13 02:29, George Mitchell wrote:
On 08/22/13 07:34, Hans Petter Selasky wrote:
Here's the result:
[...]
(at which point if I type control-c to stop usbdump, the system gets a
fatal kernel mode tr
On 8/24/13 3:23 AM, Mark Felder wrote:
On Fri, Aug 23, 2013, at 13:20, Julian Elischer wrote:
On 8/23/13 7:55 PM, Poul-Henning Kamp wrote:
In message <52174d51.2050...@digsys.bg>, Daniel Kalchev writes:
- 9.x gcc default and clang in base;
- 10.x clang default and gcc in ports;
I believe thi
Hi,
As I moved from old pkg_xxx to pkg2ng.
But I cannot install any new packages as follows:
# rm -f/var/db/pkg*
# pkg2ng
# pkg install gs
freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32,
freebsd:9:x86:32, freebsd:9:x86:32, freebsd:9:x86:32
-
-
-
-
freebsd:9:x86:32, freebs
Hi,
I solved my problem by myself.
I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with
the information in another expert web site.
---
2013/8/24 Hideki Yamamoto
>
> Hi,
>
> As I moved from old pkg_xxx to pkg2ng.
> But I cannot install any new packages as follows:
>
> # rm -f
On 08/24/13 02:44, George Mitchell wrote:
On 08/23/13 07:11, George Mitchell wrote:
On 08/23/13 02:18, Hans Petter Selasky wrote:
On 08/23/13 02:29, George Mitchell wrote:
On 08/22/13 07:34, Hans Petter Selasky wrote:
Give that the printer works fine with the same code on my amd64
machine
70 matches
Mail list logo
