[SPAM] Re: Official request: Please make GNU grep the default

On 2010-08-20 11:10, Dag-Erling Smørgrav wrote: If you have profiling libraries installed, you can build a profiling version of grep (or any program) like so: % cd /usr/src/usr.bin/grep % make clean % make DEBUG_FLAGS="-pg -g" -DNO_SHARED Do *not" make install, because the result will be dog s

Re: Call for Documentation Contributors

On 2010-09-02 00:46, Gabor PALI wrote: Hello there, I am looking for volunteers who are interested in writing documentation, i.e. working with the FreeBSD Handbook and the documentation set. Many of our great documentation writers have decided to retire from their work over the last years, whic

Re: Error message while updating src for FreeBSD 9 current

On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the following error message when I do a src update. cvsup srcsupfile

[SPAM] Re: Error message while updating src for FreeBSD 9 current

On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the

[SPAM] Re: Error message while updating src for FreeBSD 9 current

On 2010-09-23 14:02, Bartosz Stec wrote: On 2010-09-23 13:36, Niclas Zeising wrote: On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I

Re: Error message while updating src for FreeBSD 9 current

Thanks for all the helpful suggestions. csup worked like a charm and solved the problem. I will be rebuilding my ports gradually, starting with the development ports like Perl, gcc, clang etc. I am also experimenting with a custom kernel where I am eliminating drivers and modules for isa, wireles

[PATCH] update to NTP in base

Hello! The instructions at http://www.freebsd.org/cgi/query-pr.cgi?pr=148836 (Pr bin/148836) contains an update to the base system NTP program suite. Please test it and report successes and failures. Known issues: The html doc distribution is not installed, but it can be found on the internet if

Re: priority of paths to kernel modules?

ne of the reasons we wanted to get rid of the base drivers, as I've stated before). X can't always know which driver to load (when using modesetting for instance), and in my opinion, it should be the kernel/loader that decides which drivers to loa

Re: Problem starting Xorg

On 10/2/18 7:02 PM, Filippo Moretti wrote: I get the following error while attemptong to start xorg,that did work until today,amd64 alpha3drmn0:error:no GEM object associated to handle 0x0400 can't  create framebufferany help appreciatedFilippo Hi! Can you provde your Xorg log, as well as

Re: Dependencies – drm-kmod, drm-stable-kmod and drm-next-kmod

on FreshPorts is probably based on the version of FreeBSD FreshPorts is using to parse the ports tree. gpu-firmware-kmod is a dependency of all drm-*-kmod ports, but it's not a direct dependency of drm-kmod. Regards -- Niclas Zeising ___ freebsd-curren

FreeBSD x11-servers/xorg-server and CVE-2018-14665

x27;t hesitate to contact me or to send a message to the x...@freebsd.org mailing list. Regards - -- Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnic

Re: FreeBSD x11-servers/xorg-server and CVE-2018-14665

On 10/27/18 11:00 PM, Niclas Zeising wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [ cross posted to several FreeBSD lists. Please keep replies to x...@freebsd.org ] Yes, I know the signature is BAD. GPG is as user friendly as always. I'm about to re-send this with a (hope

FreeBSD x11-servers/xorg-server and CVE-2018-14665

x27;t hesitate to contact me or to send a message to the x...@freebsd.org mailing list. Regards Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnica.com/inform

Re: drm changes and updating to 12.0

-video-ati-legacy rather than xf86-video-ati. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: "Oddness" in head since around r343678 or so

On 2019-02-08 10:27, Alexander Leidinger wrote: Hi, I recently noticed some generic slowness myself. I experienced this during replacing disks in a raidz by bigger ones. Long story short, check top -s if you have vnlru running for a long period at high CPU... If yes increase kern.maxvnodes (I

Re: "Oddness" in head since around r343678 or so

On 2019-02-10 16:35, Niclas Zeising wrote: On 2019-02-08 10:27, Alexander Leidinger wrote: Hi, I recently noticed some generic slowness myself. I experienced this during replacing disks in a raidz by bigger ones. Long story short, check top -s if you have vnlru running for a long period at

Re: drm2 removed?

On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? It was r343567. The merg

Re: drm2 removed?

On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? It was r343567. The merg

Re: drm2 removed?

On 2/11/19 6:36 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote: On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I

Re: "Oddness" in head since around r343678 or so

On 2/12/19 1:38 PM, David Wolfskill wrote: On Thu, Feb 07, 2019 at 05:09:40AM -0800, David Wolfskill wrote: ... The laptop is configured to run xdm; while running stable/11 or stable/12, there's a period of about 5 seconds after xdm's login banner shows up before either the mouse or keyboard res

Re: What is evdev and autoloading?

ork much worse. We in the FreeBSD Graphics Team are working very hard to improve the FreeBSD Desktop experience, since it is an avenue to recruit new users, and make current users use FreeBSD more. Evdev and libinput is used by both Wayland and xorg. You are free to use either one. Regar

Re: SVN r345102 breaks drm-current-kmod

(((x) & ((__typeof(x))(a) - 1)) == 0) >> ^ >> --- drm_atomic_helper.o --- >> 1 error generated. >> *** [drm_atomic_helper.o] Error code 1 >> >> make[3]: stopped in >> /usr/ports/graphics/drm-current-kmod/work/kms-drm-78e51d0/drm >> >_

Re: Inability to build FreeBSD-current amd64

On 2019-05-16 03:46, Thomas Mueller wrote: In general, WITH_CLANG_EXTRAS controls the building of extra tools such as a disassembler, and tools for working on clang itself such as bug reporting tools. I don't have a really detailed answer because I've never enabled the option. I've always perce

Re: Inability to build FreeBSD-current amd64

On 2019-05-16 09:36, Thomas Mueller wrote: from Niclas Zeising: I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if that's what you're asking about. This won't take away the need for llvm ports in certain ports builds, however, such as firefox and

Re: Heads up for breaking drm update.

ions. It should also be noted that drm-current now has a new dependency on lindebugfs. It won't load without it :-( Previously, lindebugfs was part of the port, and loaded from the port. With this update, we simply switched to using the debugfs version that was imported into base. Re

Enabling synaptics and elantech touchpads by default

rk in X by default, meaning we get a more user friendly appearance. Is there any reason not to do this? Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, sen

Re: signal 11 for 'conftest' && poudriere jails

On 2019-06-17 07:32, Matthias Apitz wrote: While running poudriere jails on a very recent CURRENT: FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13 CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I see messages about signal 11 for 'conftest'

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 2019-06-23 04:56, Karl Denninger wrote: On 6/22/2019 20:16, Thomas Mueller wrote: I am trying to set up UEFI to boot my FreeBSD and NetBSD installations, and later, Linux. Easy.  Refind should do that and allow selection from a menu. I wrote this as an instruction on how to get FreeBSD

Re: Someone broke USB

ortunately, things have gone left. To update /usr/src to get your change, I pulled in some vm changes, which break the graphics/drm-legacy-kmod port. Can you report this, including the failure you're seeing, to x...@freebsd.org or as an issue on the FreeBSDDesktop github? Thanks! Regards --

Re: Can't buildworld at r350321

On 2019-07-25 12:33, Masachika ISHIZUKA wrote: Hi. I want to update 13-current from r349989 to r350321 as follows. % cd /usr/src % pwd /usr/altlocal/freebsd-current/src % df -h . Filesystem SizeUsed Avail Capacity Mounted on 192.168.1.2:/usr/altlocal2.5T

Re: drm-legacy is broken, again

ual names escaped me. I reproduced the issue and submitted a PR: https://github.com/FreeBSDDesktop/drm-legacy/pull/13 Thanks for that, too. I'm not in a position to submit a PR as my mouse has gone missing under Xorg. Port has been updated: https://svnweb.freebsd.org/changeset/ports

Re: HEADSUP: drm-current-kmod now installs sources

work like this for a while, to shake out any bugs or other unexpected issues, and then look into converting more kmod ports. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd

Re: HEADSUP: drm-current-kmod now installs sources

built for those arches where there is support, and only the modules needed, as an example, i915kms.ko will only be built on amd64 and i386, if that's what you're worried about. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mail

Re: Installing drm-current-kmod from ports

On 2019-08-18 04:08, Clay Daniels Jr. wrote: I've been reading the HEADSUP: drm-current-kmod thread, actually several times, and since my pkg install of plain vanilla drm-kmod was a dud after working for several weekly installs of 13.0-Current, it's clear I probably need to make install from the

ses no longer attaches

Hi! I have an issue where the ses driver no longer attaches. Last known good version was r351188, r351544 is broken. In that interval, something happened. I haven't had time to bisect yet. Thanks! Regards -- Niclas Zeising ___ freebsd-cu

Re: ses no longer attaches

On 2019-08-28 00:38, Alexander Motin wrote: Hi. On 27.08.2019 18:03, Niclas Zeising wrote: I have an issue where the ses driver no longer attaches.  Last known good version was r351188, r351544 is broken.  In that interval, something happened.  I haven't had time to bisect yet. I

Re: ses no longer attaches

On 2019-08-28 01:45, Michael Butler wrote: On 2019-08-27 19:41, Michael Butler wrote: On 2019-08-27 19:15, Niclas Zeising wrote: On 2019-08-28 00:38, Alexander Motin wrote: Hi. On 27.08.2019 18:03, Niclas Zeising wrote: I have an issue where the ses driver no longer attaches.  Last known

Re: ses no longer attaches

On 2019-08-29 00:07, Alexander Motin wrote: On 27.08.2019 19:15, Niclas Zeising wrote: I did some more digging. r351355 is ok, while r351356 is bad.  This is Warner's (CC:d) commit to add RST support to nvme, however, I'm using a ssd drive connected to ahci. What happens is that the

Re: hang up with r352239 and r352386 with i5-7500

top/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d that might solve the issue, can you apply that and recompile drm-current-kmod and see if it works? Thanks! Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https

Re: hang up with r352239 and r352386 with i5-7500

1000 acf mac_ntpd.ko Hi! Can you please use absolute paths to i915kms.ko anyway, just to test? Thanks! Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsu

Re: hang up with r352239 and r352386 with i5-7500

On 2019-09-16 16:06, Masachika ISHIZUKA wrote: Can you please use absolute paths to i915kms.ko anyway, just to test? The same hang up occure with kld_list="/boot/modules/i915kms.ko" in /etc/rc.conf. Even after applying the patch I suggested? Regards -- Nicl

Re: hang up with r352239 and r352386 with i5-7500

t will take some time before it shows up as packages, but there is no problems building drm-current-kmod from ports even if packages are used for the rest of the system. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://li

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a little while, it broke with r353645. https://i.imgur.com/Q5nYZf2.jpg I'm using the same HP Spectre that I used earlier (where it worked and where it panicked). That commit looks unrelated, it touches the wbwd and

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a little while, it broke with r353645. https://i.imgur.com/Q5nYZf2.jpg I'm using the same HP Spectre t

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-20 08:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and mjg@'s earlier patch at https://people.freebsd

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 09:01, Thomas Mueller wrote: from Neel Chauhan: For me, the following code is still necessary for me (HP Spectre x360 2018), which is the remaining parts of the patches not committed if you are using a recent kernel. I don't know about you all ThinkPad users, it should still apply

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 11:08, Yuri Pankov wrote: Niclas Zeising wrote: On 2019-10-20 08:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 10:13, Niclas Zeising wrote: On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-23 21:50, Clay Daniels Jr. wrote: r353709 Looked promising, but failed: Loaded r353709 make install drm-kmod, all 3 installed (drm-devel-kmod, drm-current-kmod, & gpu-firmware-kmod) set /etc/rc.conf & /boot/loader.conf configs as usual rebooted and looked good, video tingling pkg inst

Re: DRM-current-kmod is still a problem at r353339

Hi! On 2019-10-24 01:32, Clay Daniels Jr. wrote: Niclas, my last working install of 13.0 Current was r353072 of Oct 4th. The next week's r353427 of Oct 11th did not work and I reverted to r353072 for a week. Then r353709 of Oct 18th did not work, and when I tried to revert back to r353072 it do

Panic using QLogic NetXtreme II BCM57810 with latest CURRENT snapshot

Hi! I got the following panic with a QLogic NetXtreme II BCM57810 when trying to assign an IP address using dhclient. The network card uses the bxe driver. The machine in question is a HP DL380 Gen9. Kernel page fault with the following non-sleepable locks held: shared rw if_addr_lock (if_addr_l

Re: Bad GPTZFSBOOT?

On 2016-01-27 04:07, Larry Rosenman wrote: > Can someone(tm) look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206659 for me? Just to get the same information here as in the PR. This seems to have broken between r294750 and r294770. There were a series of commits to the boot loaders in

Re: iwn panic with 9.0-BETA3-amd64

0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=38 The only way to restore the firmware is to reboot the computer. Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-cur

Re: /sys/amd64/conf/DEFAULTS

first added 6 years ago, on October 27 2005. Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Heads up: New C++ stack

taking this work. Just a question, is there a wiki page with these instructions, or a wiki page related to this work where these instructions can be added? If they're not on the wiki, I can do the work of getting them there, just point to where they're best suited. Than

[PATCH] make it possible for yp_mkdb to send YPPROC_CLEAR to arbitrary host

jail, there is no localhost. This way YPPROC_CLEAR can be sent to the NIS server in jails as well. The patch is attached and also in bin/169911 [1] Regards -- Niclas Zeising [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/169911 Index: head/usr.sbin/yp_mkdb/yp_mkdb.c

Re: Firefox-15/Thunderbird-15: won't compile on FreeBSD 10.0-CUR: /jsproxy.h:17:7: error: visibility does not match previous declaration

On 2012-09-05 11:11, Dimitry Andric wrote: > On 2012-09-05 10:11, O. Hartmann wrote: >> Udating/reinstalling of both ports www/firefox (15.0) and >> mail/thunderbird (15) fail with an error like showed below. > >> ./jsproxy.h:17:7: error: visibility does not match previous declaration >> class

Re: ZFS on HEAD

On 2012-09-28 21:49, Matthew D. Fuller wrote: > On Fri, Sep 28, 2012 at 09:44:08PM +0200 I heard the voice of > Sami Halabi, and lo! it spake thus: >> >> what count for little, and what count for huge. > > Off the top of my head, I'd say less than 1 gig (maybe 2) or more than > 256. With very lit

Re: HEADS UP: Clang now the default on x86

you have a minimum required memory size to finish a buildworld (amd64). Fabien I have no trouble doing a -j8 build with 2GB memory, so 1GB should work fine, unless you spawn a lot of parallel builds or do a lot of other stuff at the same time. Regards! -- Nicl

Re: lsof vs. clang

op_strategy bp=%p", bp)); ^~ 7 warnings generated. The rest of the warnings are probably follow-up warnings since clang doesn't know the function prototype for KASSERT. Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Traditional cpp

initely. :-) A "C Preprocessor" is clearly meant to > preprocess C, not arbitrary text files. Hear, hear! :) > > You can see the problem of this approach, when you try to use another > traditional preprocessor, like ports/devel/ucpp, for tools like Imake. > Niclas Zei

Re: problem booting to multi-vdev root pool [Was: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot]

irror with striped disks, or a stripe with mirrored disks, which it seems to me the original poster had. Am I correct, and therefore ok to update? Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailma

panic: sbuf_trim makes no sense on sbuf 0xffffff82434d8898 with drain

Hi! I consistently get this panic while trying to boot a kernel build from r243530. It happens when the entropy harvesting rc.d script starts. r243380 worked fine, I haven't tested any revisions in between. Attached is the backtrace from the kernel, as gotten by kgdb. The machine uses zfs as

Re: panic: sbuf_trim makes no sense on sbuf 0xffffff82434d8898 with drain

On 11/25/12 23:48, m...@freebsd.org wrote: On Sun, Nov 25, 2012 at 2:26 PM, Niclas Zeising wrote: Hi! I consistently get this panic while trying to boot a kernel build from r243530. It happens when the entropy harvesting rc.d script starts. r243380 worked fine, I haven't tested any revi

Re: new xorg segfault 11 with KMS

, I cannot > reproduce the crash anymore. Either I forgot to rebuild something (seems > unlikely) or the crash has to do with optimizations or flags not present > in a debug build. This is not unlikely. There are probably places in the

Re: new xorg segfault 11 with KMS

fore we try that, I just need to finish the patch. I'll let you all know when it's ready. Regards -- Niclas -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: new xorg segfault 11 with KMS

Can you please try the attached patch, against x11-servers/xorg-server. Apply it and recompile xorg-server with normal flags (that is, no debugging) and let me and the list know the result when starting X. Regards! -- Niclas Zeising Index: x11-servers/xorg-server/Makefile

Re: new xorg segfault 11 with KMS

On 12/14/12 01:24, Johannes Dieterich wrote: > On Thu, Dec 13, 2012 at 6:51 PM, Artyom Mirgorodskiy > wrote: >> This patch work for me. Thanks. > I can confirm that it also works for me. Thanks a lot! > >> On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: >&

Re: new xorg segfault 11 with KMS

On 12/14/12 00:51, Artyom Mirgorodskiy wrote: > This patch work for me. Thanks. > > On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: >> Can you please try the attached patch, against x11-servers/xorg-server. >> Apply it and recompile xorg-server with norm

Re: 7+ days of dogfood

On 02/10/13 01:07, Steve Kargl wrote: > In a long thread started by Peter Wemm on developers@, he described > the move/upgrade of the FreeBSD.org cluster to using FreeBSD-10. A > part of his description included the need to test top-of-tree under > actual real-world conditions. In his words, Free

Re: 7+ days of dogfood

On 02/10/13 07:33, Ian FREISLICH wrote: > 1. WITHOUT_CLANG_IS_CC=yes >I don't think clang is ready for prime time in FreeBSD, or FreeBSD >isn't ready to use clang in prime time. I got a new laptop (ASUS >UX31A) and found that a lot of the ports I needed to install >didn't compile o

Re: 7+ days of dogfood

On 02/13/13 00:23, Jakub Lach wrote: > This is good moment to bring that around, > > https://wiki.freebsd.org/PortsAndClang > > "Help we don't want: > Submitting ports PR without fixes. We're not yet at the point > where it can help." That should probably be removed... Regards! -- Niclas

Re: Response of *.freebsd.org websites are very slow

On 2013-02-27 20:25, Mehmet Erol Sanliturk wrote: > I have installed snapshot > > FreeBSD-9.1-STABLE-amd64-20130223-r247167-release.iso > > # traceroute ftp.freebsd.org > > 3 failures : traceroute : unknown host ftp.freebsd.org > 2 successes : > > Route is Izmir ( Turkey ) -> Frankfurt -> New Y

Re: Does anyone regularly build HEAD with clang?

On 2012-02-13 17:56, Jordan K. Hubbard wrote: > > On Feb 13, 2012, at 5:59 AM, Dimitry Andric wrote: > >> I build it very regularly, and there are several buildbots that also >> build it continously (though they currently don't spam the mailing >> lists). For me, and the buildbots, head builds j

Re: Mesa 8.0 Info

On 2012-02-13 19:32, Kevin Oberman wrote: > On Mon, Feb 13, 2012 at 10:02 AM, O. Hartmann > wrote: >> On 02/13/12 09:34, vehemens wrote: >> >>> >> >> >> Interesting to read that FreeBSD has now explicitly b

Re: Mesa 8.0 Info

On 2012-02-13 20:29, Ivan Klymenko wrote: > В Mon, 13 Feb 2012 19:57:42 +0100 > Niclas Zeising пишет: > >> On 2012-02-13 19:32, Kevin Oberman wrote: >>> On Mon, Feb 13, 2012 at 10:02 AM, O. Hartmann >>> wrote: >>>> On 02/13/12 09:34, vehemens wrote:

FreeBSD as virtualbox guest not working

Hi! Sometime quite recent a change to FreeBSD CURRENT makes it almost impossible to run it as a virtualbox guest, at least under Windows. If I roll back the vbox machine to a (unfortunately quite old, from January) CURRENT everything seems to be working. The issue is that the virtual machine r

[HEADS UP] xorg version switch in CURRENT

xorg. Please send reports of successes, failures and/or comments to x...@freebsd.org. Remember to include any relevant information, such as xorg logs (Xorg.log.0), dmesg, graphics card model and ports versions with your report. Please test this as much as possible! Regards! -- Niclas Zeising

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

On 2013-03-11 11:58, Hartmann, O. wrote: > Am 03/11/13 11:17, schrieb Dimitry Andric: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.8.0. AFAICT, the

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

On 03/11/13 14:13, Steve Kargl wrote: > On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.

Re: error: unknown warning group '-Wcpp', ignored (#pragma GCC)

On 05/25/13 12:09, O. Hartmann wrote: > With CLANG on FreeBSD 10.0-CURRENT r250968, I get this error message in > a source I try to port. > > I did not find any suitable "official" workaround and I'd like to avoid > patching all files containing those #pragma statements. Is there a > geenral solut

Re: -Qunused-parameter and clang (was Re: GHC Port on 9-CURRENT)

On 2011-06-28 21:19, Pan Tsu wrote: > Niclas Zeising writes: > >> Sorry for hijacking this thread, and cross posting. >> >> On 2011-06-26 03:07, Gabor PALI wrote: >>> >>> >>>> With Clang, an error occurs in one of the configure scrip

Re: FreeBSD 9

On 2011-06-30 17:26, Tim Gustafson wrote: > Hi, > > I've installed FreeBSD 9 on a new server because 8.2 doesn't have support for > the LSI SAS2008 controller. I've also built the system as a ZFS-root box, > and I have to say that I'm quite happy with the disk performance: we're > getting abou

Re: FreeBSD 9

On 2011-06-30 19:40, Tim Gustafson wrote: >> I think you need something along the line of >> ifconfig_bce0_alias0="inet 1.2.3.5 netmask ...", notice the >> 'inet', since aliasN can be used for both inet and inet6. > > Got it, thanks! > > I assume that's also recommended for the primary interface

Re: HEADS UP: BIND 9.8 imported to HEAD

On 2011-07-16 13:55, Doug Barton wrote: > Howdy, > > I wanted to let everyone know that BIND 9.8.0-P4 has just been imported > to 9-current, and will be part of the 9.0-RELEASE. The 9.8 branch has > many nice new features vs. 9.6.x, especially in the area of DNSSEC. You > can read more about the n

Re: em problem in virtualbox since the weekend

or something similar. Rebuilding the kernel with nooptions NEW_PCIB solves the immediate issue (i.e. the machine boots and can find filesystems, etc.). It is probably so, that if there is a bug in vbox bios, the old pci code masks that bug, but the new version is more stringent and therefore dies

Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

On 2011-08-13 12:08, Roland Smith wrote: > On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote: >> On 08/13/11 09:26, Roland Smith wrote: >>> On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: > On Fri, Aug 12, 2011 at 08:44:07PM +

Re: Recent HEAD: buildworld is broken with clang

obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno' > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > > Stop in /usr/src/libexec/atrun. > *** Error code 1 > > Stop in /usr/src

Re: Buildworld failure after update r224806 to r224886

NLS > -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 > -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE > -DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/tzcode/stdtime > -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP > -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING > -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k > -Wno-uninitialized -Wno-pointer-sign -c /usr/src/lib/libc/rpc/svc_vc.c -o > svc_vc.po > ... > > ... > ===> lib/clang/libllvmx86instprinter (all) > ===> lib/clang/libllvmx86utils (all) > ===> lib/clang/include (all) > 6 errors > *** Error code 2 > *** Error code 2 > > Stop in /usr/src. > ... > > > Someone have any idea what is that? > > Thanks! > There was a period when there was a bug in dev/std{in,err,out}, which amongst other things made it impossible to complete a buildworld. Compile a new kernel (past r224842), boot to that kernel and rebuild world, that should work. For details see UPDATING r224875. HTH! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: buildworld has been broken for me since Sunday 20110815 at atrun

On 2011-08-16 15:47, eculp wrote: > Is anyone else seeing this? This is current AMD64. I'm running the > compile from Saturday 20110814 that I have been hammering and it has > been rock solid. > > # uname -a > FreeBSD home.encontacto.net 9.0-BETA1 FreeBSD 9.0-BETA1 #16: Sat Aug 13 > 05:09:17 CDT

Re: howto: enabling journaling on softupdates

n >>> gjournal >>>(async mount)? >> ENOCLUE (because I'm not aware of that with gjournal -- the last time >> I tried setting it up things didn't work too well for me) :). >> >>>Thanks for patience and repson

Re: 8-stable -> 9-current upgrade

On 2011-09-08 02:12, Kevin Oberman wrote: > I've been looking for any information on any special steps required to > update from 8-stable to > 9-current. /usr/src/UPDATING is a bit out of date as it has > instructions for going from 5-stable > to "current", although the instruction may well be the

Re: Call for Testing: UEFI Changes

On 03/22/18 01:45, Kyle Evans wrote: Hello! A number of changes have gone in recently pertaining to UEFI booting and UEFI runtime services. The changes with the most damaging potential are: We now put UEFI runtime services into virtual address mode, fixing runtime services with U-Boot/UEFI as w

Re: Call for Testing: UEFI Changes

On 2018-03-25 14:52, Sheda wrote: >> >> I've tested on two different computers, my ThinkPad x230 and my desktop >> with a Intel DQ77MK motherboard. I've only done light testing such as >> loading efirt.ko and running efibootmgr to check the boot settings, but it >> has worked fine. >> I also haven

Re: Regression Resume Lenovo T450

On 05/08/18 22:09, Manuel Stühn wrote: P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. What issues are you seeing with drm-next-kmod? Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailm

Re: suspend/resume regression

On 05/13/18 09:48, Andriy Gapon wrote: On 13/05/2018 05:25, Pete Wright wrote: hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stable for graphics. during the past week or so i've run into issues with suspend resume...well technically resume

Re: suspend/resume regression

On 05/13/18 21:44, Pete Wright wrote: On 05/13/2018 10:27, Pete Wright wrote: On 05/13/2018 08:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more

Re: suspend/resume regression

On 05/13/18 18:16, Michael Gmelin wrote: On 13. May 2018, at 11:54, Niclas Zeising wrote: On 05/13/18 09:48, Andriy Gapon wrote: On 13/05/2018 05:25, Pete Wright wrote: hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stabl

Re: suspend/resume regression

On 05/13/18 17:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operati

  1   2   >