ZFS sends TIRMs to agressively? (Was: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system)

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 7:58:37 PM, you wrote: >> Can you please narrow the problem down to a specific kernel revision? > I'm still not sure it is software or hardware problem. Looks like Samsung 850 EVO doesn't like TRIMs sent by ZFS (and I've thought it is good SSD,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Mateusz, Saturday, December 8, 2018, 5:27:42 PM, you wrote: >> Looks like each next compiler invocation is slower and more stressful than >> previous one. > Is this a fresh install? Almost fresh. It was installed from some rather fresh 13 snapshot and then upgraded to r341157 and custom

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Mateusz Guzik
On 12/8/18, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > >> Even when build is single-job, system becomes unresponsive. With >> 4-job build running it could takes up to minute to switch screen's >> windows! > And even with 1-job kernel build

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Eugene Grosbein
08.12.2018 18:13, Lev Serebryakov wrote: > I'm completely lost. Is it problem of software? Hardware? If it is > hardware problem what should I blame? Try using different kern.timecounter.hardware and/or kern.eventtimer.timer but first try kern.eventtimer.periodic=1 instead of default 0. If

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Eugene, Saturday, December 8, 2018, 4:27:13 PM, you wrote: >> I'm completely lost. Is it problem of software? Hardware? If it is >> hardware problem what should I blame? > Try using different kern.timecounter.hardware and/or kern.eventtimer.timer > but first try

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Even when build is single-job, system becomes unresponsive. With > 4-job build running it could takes up to minute to switch screen's windows! And even with 1-job kernel build upsmon's connection to remote upsd flickers!

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Another strange thing I noticed: when system is in such state, "top -SH" > shows that sometimes very low-profile processes, like clock software > interrupt (!) could consume large amount of CPU for short periods time. When >

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Waitman Gobble
‐‐‐ Original Message ‐‐‐ On Saturday, December 8, 2018 8:18 AM, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > > Another strange thing I noticed: when system is in such state, "top -SH" > > shows that sometimes very low-profile processes,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > I've checked all "standard" places — CPU is not throttling, SSD looks > perfectly Ok according to SMART and there is no complains from AHCI driver > about timeouts and such, system doesn't start to use swap. ZFS ARC was checked

Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Freebsd-hackers, I'm experiencing very strange situation on my lab system which is E3-1220v2, 8GiB of RAM and 850 EVO SATA SSD (with single ZFS pool). It runs CURRENT r341157. Kernel is built *without* INVARIANTS and other heavy debug aids. Everything works great — but compilation

Re: Compilation failure of the kernel for drm-next

2018-02-27 Thread Mylan Connolly
Thanks for the help, all. Last night I set my computer to compile from the 12-CURRENT head and went to sleep. This morning, I installed the graphics/drm-next-kmod port and after a little troubleshooting (I had to set the compat.linuxkpi.enable_hangcheck=0 bootflag) I got it up and running.

Re: Compilation failure of the kernel for drm-next

2018-02-27 Thread Greg V
On 2/27/2018 5:03 AM, Pete Wright wrote: On 02/26/2018 17:17, Mylan Connolly wrote: Hello all, I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. there may not be much traffic on it recently, but people are def still actively

Re: Compilation failure of the kernel for drm-next

2018-02-26 Thread Pete Wright
On 02/26/2018 17:17, Mylan Connolly wrote: Hello all, I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. there may not be much traffic on it recently, but people are def still actively working on the repository and will see

Compilation failure of the kernel for drm-next

2018-02-26 Thread Mylan Connolly
Hello all, I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. I have been trying to compile it for the past few weeks after downloading the latest code about once a week and it looks like this issue hasn't resolved itself. When I

SVN r323289 breaks i386 kernel compilation

2017-09-07 Thread Michael Butler
On i386, this revision breaks compilation as follows: Building /usr/obj/usr/src/sys/SARAH/mca.o --- mca.o --- /usr/src/sys/x86/x86/mca.c:985:54: error: format specifies type 'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat

Re: SVN r307866 compilation problem

2016-10-24 Thread Konstantin Belousov
On Mon, Oct 24, 2016 at 02:58:43PM -0400, Michael Butler wrote: > It seems that compilation of -current fails in the case that KDB is not > defined. > > I'm assuming that the following diff achieves what was intended: > > imb@vm01:/usr/src/sys/x86/x86> svn diff &

SVN r307866 compilation problem

2016-10-24 Thread Michael Butler
It seems that compilation of -current fails in the case that KDB is not defined. I'm assuming that the following diff achieves what was intended: imb@vm01:/usr/src/sys/x86/x86> svn diff Index: cpu_machdep.c === --- cpu_machde

Re: SVN r303643 breaks non-SMP compilation

2016-08-02 Thread Guido Falsi
On 08/02/16 05:06, Mateusz Guzik wrote: > On Mon, Aug 01, 2016 at 09:49:03PM -0400, Michael Butler wrote: >> In the non-SMP case, ADAPTIVE_MUTEXES is not defined and a subsequent >> reference to mtx_delay causes compilation of kern_mutex.c to fail >> because KDTRACE_HOOKS m

amd64-xtoolchain-gcc: small kernel compilation issue

2016-08-02 Thread Andriy Gapon
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c: In function 'alloc_memseg': /usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c:261:3: error: null argument where non-null required (argument 1) [-Werror=nonnull] error = copystr(VM_MEMSEG_NAME(mseg), name, SPECNAMELEN + 1, 0); This is with

Re: SVN r303643 breaks non-SMP compilation

2016-08-01 Thread Mateusz Guzik
On Mon, Aug 01, 2016 at 09:49:03PM -0400, Michael Butler wrote: > In the non-SMP case, ADAPTIVE_MUTEXES is not defined and a subsequent > reference to mtx_delay causes compilation of kern_mutex.c to fail > because KDTRACE_HOOKS may be, > Indeed, fixed in r303655. Thanks f

SVN r303643 breaks non-SMP compilation

2016-08-01 Thread Michael Butler
In the non-SMP case, ADAPTIVE_MUTEXES is not defined and a subsequent reference to mtx_delay causes compilation of kern_mutex.c to fail because KDTRACE_HOOKS may be, imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-11-01 Thread Simon J. Gerraty
NGie Cooper wrote: > And here’s the real issue — .PATH is completely broken when > TARGET/TARGET_ARCH are specified as explicit values: It would help if you could indicate what you think the right value should be. > $ env MAKEOBJDIRPREFIX=/scratch/tmp/ngie/obj/ make

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-31 Thread NGie Cooper
> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote: > > NGie Cooper wrote: >> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS >> and I ran into this linker issue below. I have no idea (yet) why it’s trying >> to compile an

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-31 Thread NGie Cooper
> On Oct 30, 2015, at 23:51, NGie Cooper wrote: > > >> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote: >> >> NGie Cooper wrote: >>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS >>> and I ran into

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-31 Thread NGie Cooper
> On Oct 31, 2015, at 14:37, NGie Cooper wrote: > > >> On Oct 30, 2015, at 23:51, NGie Cooper wrote: >> >> >>> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote: >>> >>> NGie Cooper wrote: I

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Bryan Drewery
On 10/30/2015 1:57 PM, NGie Cooper wrote: > Hi Bryan/Simon! > I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS > and I ran into this linker issue below. I have no idea (yet) why it’s trying > to compile an x64 object when I specify powerpc/powerpc — and more >

Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread NGie Cooper
Hi Bryan/Simon! I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS and I ran into this linker issue below. I have no idea (yet) why it’s trying to compile an x64 object when I specify powerpc/powerpc — and more importantly, why is the object not being put in

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Bryan Drewery
On 10/30/2015 2:21 PM, Bryan Drewery wrote: > On 10/30/2015 1:57 PM, NGie Cooper wrote: >> Hi Bryan/Simon! >> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS >> and I ran into this linker issue below. I have no idea (yet) why it’s trying >> to compile an x64 object when

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Mark Johnston
On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote: > On 10/30/2015 3:03 PM, NGie Cooper wrote: > > On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote: > >> On 10/30/2015 2:21 PM, Bryan Drewery wrote: > >>> On 10/30/2015 1:57 PM, NGie Cooper wrote: > Hi

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Bryan Drewery
On 10/30/2015 4:08 PM, Mark Johnston wrote: > On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote: >> On 10/30/2015 3:03 PM, NGie Cooper wrote: >>> On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote: On 10/30/2015 2:21 PM, Bryan Drewery wrote: > On

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Simon J. Gerraty
NGie Cooper wrote: > I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS > and I ran into this linker issue below. I have no idea (yet) why it’s trying > to compile an x64 object when I specify powerpc/powerpc — and more > importantly, why is the

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread NGie Cooper
On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote: > On 10/30/2015 2:21 PM, Bryan Drewery wrote: >> On 10/30/2015 1:57 PM, NGie Cooper wrote: >>> Hi Bryan/Simon! >>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS >>> and I ran into this linker

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread Bryan Drewery
On 10/30/2015 3:03 PM, NGie Cooper wrote: > On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote: >> On 10/30/2015 2:21 PM, Bryan Drewery wrote: >>> On 10/30/2015 1:57 PM, NGie Cooper wrote: Hi Bryan/Simon! I tried doing buildworld on powerpc/powerpc with

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-10-30 Thread NGie Cooper
On Fri, Oct 30, 2015 at 4:09 PM, Bryan Drewery wrote: ... > The example output must be a mistake as they are correct on ref11: > > ref11-amd64% find > /scratch/tmp/ngie/obj/*/scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json > -name tst.usdt.o -exec file {} + >

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Matt Smith
On Sep 24 21:52, Kurt Jaeger wrote: Hi! > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > in March, in PR198436: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > Eh, now with an actual patch. :) Thanks, helps to build it. Still fails on 9.3a,

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Kurt Jaeger
Hi! > >> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > This seems to create a run time dependency on GCC. Should it not just be > a build time dependency which allows you to uninstall GCC afterwards? Maybe, I have not looked into that. Can you suggest a patch ? --

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Matt Smith
On Sep 25 09:18, Kurt Jaeger wrote: Hi! >> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 This seems to create a run time dependency on GCC. Should it not just be a build time dependency which allows you to uninstall GCC afterwards? Maybe, I have not looked into that. Can

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Don Lewis
On 25 Sep, Matt Smith wrote: > On Sep 24 21:52, Kurt Jaeger wrote: >>Hi! >> >>> > > Try dropping the attached patch in net/mediatomb/files. I submitted it >>> > > in March, in PR198436: >>> > > >>> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 >>> > >>> > Eh, now with an actual

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Matt Smith
On Sep 25 01:00, Don Lewis wrote: On 25 Sep, Matt Smith wrote: On Sep 24 21:52, Kurt Jaeger wrote: Hi! > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > in March, in PR198436: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > Eh, now with an

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-25 Thread Don Lewis
On 25 Sep, Matt Smith wrote: > On Sep 25 01:00, Don Lewis wrote: >>On 25 Sep, Matt Smith wrote: >>> On Sep 24 21:52, Kurt Jaeger wrote: Hi! > > > Try dropping the attached patch in net/mediatomb/files. I > > > submitted it in March, in PR198436: > > > > > >

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-24 Thread Kurt Jaeger
Hi! > > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > > in March, in PR198436: > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > > > Eh, now with an actual patch. :) > > Thanks, helps to build it. Still fails on 9.3a, but I *have* to go >

Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-23 Thread Kevin Oberman
met/mediatomb fails to compile with clang++36. Works fine with gcc++ and older versions of clang++. /usr/local/bin/clang++36 -DHAVE_CONFIG_H -I. -I.. -I../tombupnp/upnp/inc -I/usr/local/include -DLIBICONV_PLUG -I../src -I../tombupnp/ixml/inc -I../tombupnp/threadutil/inc -I../tombupnp/upnp/inc

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-23 Thread Dimitry Andric
On 23 Sep 2015, at 21:57, Dimitry Andric wrote: > On 23 Sep 2015, at 17:38, Kevin Oberman wrote: >> >> met/mediatomb fails to compile with clang++36. Works fine with gcc++ and >> older versions of clang++. > > Try dropping the attached patch in

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-23 Thread Dimitry Andric
On 23 Sep 2015, at 17:38, Kevin Oberman wrote: > > met/mediatomb fails to compile with clang++36. Works fine with gcc++ and > older versions of clang++. Try dropping the attached patch in net/mediatomb/files. I submitted it in March, in PR198436:

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-23 Thread Kurt Jaeger
Hi! > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > in March, in PR198436: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > Eh, now with an actual patch. :) Thanks, helps to build it. Still fails on 9.3a, but I *have* to go to bed now. --

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

2015-09-23 Thread Kevin Oberman
On Wed, Sep 23, 2015 at 1:39 PM, Kurt Jaeger wrote: > Hi! > > > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > > in March, in PR198436: > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > > > Eh, now with an actual patch. :) > >

Re: Need help reducing compilation warnings in CURRENT

2015-05-30 Thread Craig Rodrigues
On Thu, May 28, 2015 at 9:49 AM, Konstantin Belousov kostik...@gmail.com wrote: On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: I take some time to do a pass over mine code or code I am somewhat knowledgable, to correct some 'assigned but not used variable' warnings. There

Re: Need help reducing compilation warnings in CURRENT

2015-05-30 Thread Garrett Cooper
On May 30, 2015, at 19:15, Craig Rodrigues rodr...@freebsd.org wrote: On Thu, May 28, 2015 at 9:49 AM, Konstantin Belousov kostik...@gmail.com wrote: On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: I take some time to do a pass over mine code or code I am somewhat

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread NGie Cooper
On Thu, May 28, 2015 at 12:18 PM, Baptiste Daroussin b...@freebsd.org wrote: ... If not upstreamed, there is a good chance it get lost during the next update. So in the special case of warning fixes, I would strongly advice to upstream first!! +200 Plus upstream sources generally get

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Dimitry Andric
On 28 May 2015, at 21:09, Craig Rodrigues rodr...@freebsd.org wrote: On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner x...@freebsd.org ... The warnings are almost all in contrib/ areas. Hence, any fix might want to probably be submitted to upstream first. Sure, if we can push fixes

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Craig Rodrigues
On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner x...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Craig, I'll gladly help (good excuse to learn C), but looking at those errors in general, one thing pops out: The warnings are almost all in contrib/ areas.

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Baptiste Daroussin
On Thu, May 28, 2015 at 12:09:35PM -0700, Craig Rodrigues wrote: On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner x...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Craig, I'll gladly help (good excuse to learn C), but looking at those errors in

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Craig Rodrigues
On Thu, May 28, 2015 at 5:45 AM, Muhammad Moinur Rahman b...@freebsd.org wrote: Hi, Can anyone give me any ideas about how can I contribute some of my idle times? Do I need commit bit to submit patches in Jenkins? Or should I submit through CODE Review? Please read this:

Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Craig Rodrigues
Hi, I've configured Jenkins to highlight compiler warnings and generate a table. Jenkins also keeps track of new compiler warnings over time. See: https://jenkins.freebsd.org/job/FreeBSD_HEAD/warnings7 Can anyone help improve the code by periodically looking at this table and submitting

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Marcelo Araujo
Hi Craig, I can give a hand with it. Best, 2015-05-28 14:30 GMT+08:00 Craig Rodrigues rodr...@freebsd.org: Hi, I've configured Jenkins to highlight compiler warnings and generate a table. Jenkins also keeps track of new compiler warnings over time. See:

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Johannes Jost Meixner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Craig, I'll gladly help (good excuse to learn C), but looking at those errors in general, one thing pops out: The warnings are almost all in contrib/ areas. Hence, any fix might want to probably be submitted to upstream first. Correct me if

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Muhammad Moinur Rahman
Hi, Can anyone give me any ideas about how can I contribute some of my idle times? Do I need commit bit to submit patches in Jenkins? Or should I submit through CODE Review? BR, @bofh On Thu, May 28, 2015 at 6:38 PM, Johannes Jost Meixner x...@freebsd.org wrote: -BEGIN PGP SIGNED

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Marcelo Araujo
Hi, You don't need src bit to submit any patch and you can do it via review without any problem. Just try to drive the patch to the right person. Best, 2015-05-28 20:45 GMT+08:00 Muhammad Moinur Rahman b...@freebsd.org: Hi, Can anyone give me any ideas about how can I contribute some of my

Re: Need help reducing compilation warnings in CURRENT

2015-05-28 Thread Konstantin Belousov
On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: Hi, I've configured Jenkins to highlight compiler warnings and generate a table. Jenkins also keeps track of new compiler warnings over time. See: https://jenkins.freebsd.org/job/FreeBSD_HEAD/warnings7 Can anyone help

Re: [Request for Help] Reducing gcc 4.9 compilation warnings

2015-04-20 Thread Craig Rodrigues
On Sun, Apr 19, 2015 at 2:10 AM, Eitan Adler li...@eitanadler.com wrote: Perhaps it would be useful to do a second run of this, but with a modified share/mk to silence the most useless of these warnings? Sure, that's fine. Can you provide a modified share/mk which you think does the right

Re: [Request for Help] Reducing gcc 4.9 compilation warnings

2015-04-20 Thread Benjamin Kaduk
On Sun, 19 Apr 2015, Adrian Chadd wrote: I just got a booting mips32 kernel using gcc-4.9.2, and boy are there a lot of warnings. I'm going to start fixing the ones I find - cleaner code is better code. Mostly. (I'd be happy with -Wall -Werror.) I thought that -Wall was a fixed set of

Re: [Request for Help] Reducing gcc 4.9 compilation warnings

2015-04-19 Thread Eitan Adler
://lists.freebsd.org/pipermail/freebsd-toolchain/2015-April/001658.html The boot2 compilation errors still need to be worked on. However, most other things compile with warnings. If folks are interested in looking at the warnings, you can see them here: https://jenkins.freebsd.org/job

Re: [Request for Help] Reducing gcc 4.9 compilation warnings

2015-04-19 Thread Adrian Chadd
to skip boot2 from building because of errors reported here: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-April/001658.html The boot2 compilation errors still need to be worked on. However, most other things compile with warnings. If folks are interested in looking

[Request for Help] Reducing gcc 4.9 compilation warnings

2015-04-18 Thread Craig Rodrigues
compilation errors still need to be worked on. However, most other things compile with warnings. If folks are interested in looking at the warnings, you can see them here: https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/warnings17 Please look at these warnings, and if you see places

emulators/virtualbox-ose: compilation on CURRENT fails due to: tstVMStructRC: 1: Syntax error: ( unexpected

2014-10-27 Thread O. Hartmann
compilation of port emulators/virtualbox-ose, although I already updated the ports tree and did successfully a portmaster -R -fd /emulators/virtualbox-ose. Since I use some non-standard optimization flags in /etc/src.conf and /etc/make.conf (-O3 and CPUTYPE=native instead of plain -O and outdated

SVN r273734 breaks i386 compilation

2014-10-27 Thread Michael Butler
The updates to dd cause this on an i386 .. === bin/dd (all) cc -O2 -pipe -march=pentium4 -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings

Re: SVN r273734 breaks i386 compilation

2014-10-27 Thread Kurt Jaeger
Hi! The updates to dd cause this on an i386 .. Yes, I'm sorry. Change reverted. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-current@freebsd.org mailing list

i386 compilation errors in head/sys/dev/ixl/if_ixl.c

2014-08-29 Thread David Shao
Compilation errors occur in head/sys/dev/ixl/if_ixl.c on i386 for FreeBSD 11-current for the following: In function ixl_print_debug_info() printf(Queue irqs = %lx\n, que-irqs); printf(AdminQ irqs = %lx\n, pf-admin_irq); ... printf(RX not ready = %lx\n, rxr-not_done

Re: i386 compilation errors in head/sys/dev/ixl/if_ixl.c

2014-08-29 Thread Steven Hartland
Looks like this was already fixed by: http://svnweb.freebsd.org/changeset/base/270799 Regards Steve - Original Message - From: David Shao davs...@gmail.com To: freebsd-current@freebsd.org Sent: Friday, August 29, 2014 6:38 AM Subject: i386 compilation errors in head/sys/dev/ixl

Re: i386 compilation errors in head/sys/dev/ixl/if_ixl.c

2014-08-29 Thread Bjoern A. Zeeb
On 29 Aug 2014, at 12:02 , Steven Hartland kill...@multiplay.co.uk wrote: Looks like this was already fixed by: http://svnweb.freebsd.org/changeset/base/270799 Yes, just before I closed the bugreport. There’s a few more follow-up commits that (if I didn’t screw up) should make things at

Re: i386 compilation errors in head/sys/dev/ixl/if_ixl.c

2014-08-29 Thread David Wolfskill
On Fri, Aug 29, 2014 at 12:55:40PM +, Bjoern A. Zeeb wrote: On 29 Aug 2014, at 12:02 , Steven Hartland kill...@multiplay.co.uk wrote: Looks like this was already fixed by: http://svnweb.freebsd.org/changeset/base/270799 Yes, just before I closed the bugreport. There?s a few more

Re: i386 compilation errors in head/sys/dev/ixl/if_ixl.c

2014-08-29 Thread Bjoern A. Zeeb
On 29 Aug 2014, at 13:33 , David Wolfskill da...@catwhisker.org wrote: On Fri, Aug 29, 2014 at 12:55:40PM +, Bjoern A. Zeeb wrote: On 29 Aug 2014, at 12:02 , Steven Hartland kill...@multiplay.co.uk wrote: Looks like this was already fixed by:

Re: gcc compilation broken with SVN r264042

2014-04-03 Thread David Chisnall
On 3 Apr 2014, at 00:23, Warner Losh i...@bsdimp.com wrote: So less carping and more fixing is needed here. Should be fixed in r264069 - I'm sure Jenkins / Tinderbox will tell me if it isn't... libc now builds for me with gcc and clang. David ___

Re: gcc compilation broken with SVN r264042

2014-04-03 Thread Warner Losh
On Apr 3, 2014, at 2:11 AM, David Chisnall thera...@freebsd.org wrote: On 3 Apr 2014, at 00:23, Warner Losh i...@bsdimp.com wrote: So less carping and more fixing is needed here. Should be fixed in r264069 - I'm sure Jenkins / Tinderbox will tell me if it isn't... libc now builds for

Re: gcc compilation broken with SVN r264042

2014-04-03 Thread David Chisnall
On 3 Apr 2014, at 14:26, Warner Losh i...@bsdimp.com wrote: On Apr 3, 2014, at 2:11 AM, David Chisnall thera...@freebsd.org wrote: On 3 Apr 2014, at 00:23, Warner Losh i...@bsdimp.com wrote: So less carping and more fixing is needed here. Should be fixed in r264069 - I'm sure Jenkins

Re: gcc compilation broken with SVN r264042

2014-04-03 Thread Warner Losh
On Apr 3, 2014, at 7:35 AM, David Chisnall thera...@freebsd.org wrote: On 3 Apr 2014, at 14:26, Warner Losh i...@bsdimp.com wrote: On Apr 3, 2014, at 2:11 AM, David Chisnall thera...@freebsd.org wrote: On 3 Apr 2014, at 00:23, Warner Losh i...@bsdimp.com wrote: So less carping and

gcc compilation broken with SVN r264042

2014-04-02 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Seems that GCC doesn't like/understand the cast .. imb@mail:/usr/src/lib/libc sudo make cc -O2 -pipe -march=pentium4 -I/usr/src/lib/libc/include - -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -DNLS - -D__DBINTERFACE_PRIVATE

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread David Chisnall
Hi, I'm trying to reproduce this, but I don't seem to be able to get the same error as you. I do get a warning with GCC about a cast to an anonymous struct, which the attached patch fixes, but even without this I'm able to build both with the gcc in 9 and the gcc in ports. Can you let me

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread Michael Butler
On 04/02/14 15:30, David Chisnall wrote: I'm trying to reproduce this, but I don't seem to be able to get the same error as you. I do get a warning with GCC about a cast to an anonymous struct, which the attached patch fixes, but even without this I'm able to build both with the gcc in 9 and

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread David Chisnall
On 2 Apr 2014, at 20:53, Michael Butler i...@protected-networks.net wrote: cc (GCC) 4.2.1 20070831 patched [FreeBSD] .. on .. FreeBSD 11.0-CURRENT #22 r263969: Mon Mar 31 10:45:56 EDT 2014 Splitting it like .. - fn.fn_ptr.cxa_func = (void(*)(void*))GET_BLOCK_FUNCTION(func); +

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread Steve Kargl
On Wed, Apr 02, 2014 at 08:58:21PM +0100, David Chisnall wrote: Well, I wouldn't object to that, but it would be good to fix this - we still want to be able to build the base system with gcc (or another compiler), even if we don't encourage it... Who is we in even if we don't encourage

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread David Chisnall
On 2 Apr 2014, at 21:21, Steve Kargl s...@troutmask.apl.washington.edu wrote: Who is we in even if we don't encourage it...? We is the FreeBSD project, collectively. For a larger list of things that we recommend, look at the src.conf man page, which contains a long list of things that we

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread Steve Kargl
On Wed, Apr 02, 2014 at 09:46:19PM +0100, David Chisnall wrote: On 2 Apr 2014, at 21:21, Steve Kargl s...@troutmask.apl.washington.edu wrote: Who is we in even if we don't encourage it...? We is the FreeBSD project, collectively. For a larger list of things that we recommend, There

Re: gcc compilation broken with SVN r264042

2014-04-02 Thread Warner Losh
On Apr 2, 2014, at 1:15 PM, Michael Butler i...@protected-networks.net wrote: /usr/src/lib/libc/stdlib/atexit.c: In function 'atexit_b': /usr/src/lib/libc/stdlib/atexit.c:157: error: cannot convert to a pointer type *** Error code 1 This also breaks mips*, sparc64, armeb and ia64. I’ve seen

Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-11 Thread David O'Brien
On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote: On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney j...@funkthat.com wrote: But, can you tell use how you built your kernel and on what system? COMPILER_TYPE should always be defined... Are you trying to build a HEAD kernel on

Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-11 Thread O. Hartmann
On Wed, 11 Sep 2013 13:06:44 -0700 David O'Brien obr...@freebsd.org wrote: On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote: On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney j...@funkthat.com wrote: But, can you tell use how you built your kernel and on what system?

r255449: kernel compilation fails due to : cc: error: no input files

2013-09-10 Thread O. Hartmann
I get this error when trying to compile a kernel on CURRENT r29: [...] make[2]: Unclosed substitution for COMPILER_TYPE (/ missing) cc -c -O3 -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith

Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-10 Thread John-Mark Gurney
O. Hartmann wrote this message on Tue, Sep 10, 2013 at 15:03 +0200: I get this error when trying to compile a kernel on CURRENT r29: [...] make[2]: Unclosed substitution for COMPILER_TYPE (/ missing) cc -c -O3 -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls

Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-10 Thread O. Hartmann
On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney j...@funkthat.com wrote: O. Hartmann wrote this message on Tue, Sep 10, 2013 at 15:03 +0200: I get this error when trying to compile a kernel on CURRENT r29: [...] make[2]: Unclosed substitution for COMPILER_TYPE (/ missing)

compilation

2013-07-27 Thread gahn
hi all: need your experts' opinions, i tried to compile customized kernel for 8.3 but failed miserably: linking kernel.debug dcons_crom.o(.text+0x388): In function `dcons_crom_post_busreset': /usr/src/sys/dev/dcons/dcons_crom.c:145: undefined reference to `crom_add_chunk'

Re: compilation

2013-07-27 Thread Freddie Cash
umass requires SCSI support. Bert you removed scbus, da, and similar. On 2013-07-27 6:00 PM, gahn ipfr...@yahoo.com wrote: hi all: need your experts' opinions, i tried to compile customized kernel for 8.3 but failed miserably: linking kernel.debug dcons_crom.o(.text+0x388): In function

Re: compilation

2013-07-27 Thread gahn
thank freddie! From: Freddie Cash fjwc...@gmail.com To: gahn ipfr...@yahoo.com Cc: FreeBSD-Current freebsd-current@freebsd.org Sent: Saturday, July 27, 2013 9:23 PM Subject: Re: compilation umass requires SCSI support. Bert you removed scbus, da

Re: SVN r252892: videodev2.h update breaks gcc compilation

2013-07-10 Thread Alexander Leidinger
On Sun, 07 Jul 2013 06:59:59 -0400 Michael Butler i...@protected-networks.net wrote: The recent linux header update triggers the following error: In file included from /usr/src/sys/compat/linux/linux_ioctl.c:91: /usr/src/sys/contrib/v4l/videodev2.h:430: warning: declaration does not declare

Re: SVN r252892: videodev2.h update breaks gcc compilation

2013-07-08 Thread Alexander Leidinger
On Sun, 07 Jul 2013 06:59:59 -0400 Michael Butler i...@protected-networks.net wrote: The recent linux header update triggers the following error: In file included from /usr/src/sys/compat/linux/linux_ioctl.c:91: /usr/src/sys/contrib/v4l/videodev2.h:430: warning: declaration does not declare

SVN r252892: videodev2.h update breaks gcc compilation

2013-07-07 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The recent linux header update triggers the following error: In file included from /usr/src/sys/compat/linux/linux_ioctl.c:91: /usr/src/sys/contrib/v4l/videodev2.h:430: warning: declaration does not declare anything

compilation error regarding __cxa_call_terminate()

2013-06-29 Thread dt71
Using Clang head: /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++/eh_call.cc:44:1: error: conflicting types for '__cxa_call_terminate' __cxa_call_terminate(_Unwind_Exception* ue_header_) ^ /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++/unwind-cxx.h:136:17:

Re: compilation error regarding __cxa_call_terminate()

2013-06-29 Thread Dimitry Andric
On Jun 29, 2013, at 16:14, d...@gmx.com wrote: Using Clang head: /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++/eh_call.cc:44:1: error: conflicting types for '__cxa_call_terminate' __cxa_call_terminate(_Unwind_Exception* ue_header_) ^

Re: Compilation issue due to 251982

2013-06-21 Thread Alie Tan
Hi, Anyone got idea how to fix this compilation issue? Regards, Alie T On Wed, Jun 19, 2013 at 12:08 PM, Alie Tan a...@affle.com wrote: http://freshbsd.org/commit/freebsd/r251982 === usr.bin (cleandir) Makefile, line 370: Malformed conditional (${MK_SVN} == yes || ${MK_SVNLITE} == yes

Compilation issue due to 251982

2013-06-18 Thread Alie Tan
http://freshbsd.org/commit/freebsd/r251982 === usr.bin (cleandir) Makefile, line 370: Malformed conditional (${MK_SVN} == yes || ${MK_SVNLITE} == yes) Makefile, line 373: if-less endif make: fatal errors encountered -- cannot continue *** [usr.bin.cleandir__D] Error code 1 Stop in /usr/src. ***

Re: compilation error with WITHOUT_ED_CRYPTO

2013-03-23 Thread John-Mark Gurney
deeptech71 wrote this message on Fri, Mar 22, 2013 at 15:55 +0100: The obvious fix: widen the scope of ``#ifdef DES'': Thanks, committed in r248656. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not.

  1   2   3   >