Re: ltmain.sh not found
Hello, it does have a good man page, as well as a chapter in the official handbook: https://www.freebsd.org/doc/handbook/ports-poudriere.html I assume you build your ports because you have non-standard options, otherwise I'd recommend going with the prebuilt packages, the handling of prebuilt packages has become much more solid now. Best regards Andreas On Thu, Apr 25, 2019 at 3:14 PM Willem Offermans wrote: > Dear FreeBSD friends, > > No, I have not yet considered using poudriere. > > I’m using portmaster for years now and I was too lazy to look for a > better/another tool. > > When I have time, I will dig into poudriere. I assume there is > documentation/tutorial around that will get me going. > The man pages will also be helpful. > > Thank you for your suggestion. > > > > Wiel Offermans > wil...@offermans.rompen.nl > > > > > On 25 Apr 2019, at 14:58, Andreas Nilsson wrote: > > > > On Thu, Apr 25, 2019 at 2:28 AM Kevin Oberman wrote: > >> On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder < >> c...@burggraben.net> >> wrote: >> >> > ## Willem Offermans (wil...@offermans.rompen.nl): >> > >> > > Unfortunately it is probably not gawk in my case, which causes >> trouble. >> > > However, your response indicates that the problem will be solved >> after I >> > > have updated/reinstalled the guilty one. >> > >> > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a >> > tool for checking if any port misses a shared library. It has been >> > rather helpful back when I was using portupgrade... >> > >> > Regards, >> > Christoph >> > >> >> I believe bsdadminscripts has been withdrawn. You should use "pkg check >> -B" >> to check. >> -- >> Kevin Oberman, Part time kid herder and retired Network Engineer >> E-mail: rkober...@gmail.com >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >> >> > Have you considered using poudriere to build your packages? It usually > avoids these types of failures. > > Best regards > Andreas > > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ltmain.sh not found
On Thu, Apr 25, 2019 at 2:28 AM Kevin Oberman wrote: > On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder < > c...@burggraben.net> > wrote: > > > ## Willem Offermans (wil...@offermans.rompen.nl): > > > > > Unfortunately it is probably not gawk in my case, which causes trouble. > > > However, your response indicates that the problem will be solved after > I > > > have updated/reinstalled the guilty one. > > > > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a > > tool for checking if any port misses a shared library. It has been > > rather helpful back when I was using portupgrade... > > > > Regards, > > Christoph > > > > I believe bsdadminscripts has been withdrawn. You should use "pkg check -B" > to check. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > Have you considered using poudriere to build your packages? It usually avoids these types of failures. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using drm-next in 11.2
On Tue, Sep 11, 2018, 14:52 Pete French wrote: > So, I was trying to switch to using this, as I realise its where things > are heading, and I rather like the look of it. But I cant get it to see my > multiple monitors. I install the port, set 'kld_list="amdgpu"' and it boots > up with the new modules, and appears to find all my displays in dmesg. But > when I start X it only uses the single display port, mirroring it to DVI. > > > When I start X what I am seeing in dmesg is this: > > module_register: cannot register drmn from drm2.ko; already loaded from > drm.ko > Module drmn failed to register: 17 > KLD radeonkms.ko: depends on drmn - not available or version mismatch > linker_load_file: Unsupported file type > > Which make me think theres some clash with the old modules and thats why > its not > working properly. Also xrandr only lists a single screen, as default, > unlike > the list I get using the old drm, which lists all the outpus correctly. > > Anyone got any advice, or can point me to the coorrect place for this ? > > cheers, > > -pete. > I think you have to use kld_list="/boot/modules/amdgpu.ko" to get the new one. Best regards Andreas > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Boot partition size
Well, 100mb might be relevant if you ever want to dual-boot. The relevant efi file seems to be < 100k It may go up in size, but I doubt we will see a 100x increase. /A On Tue, Jan 31, 2017 at 1:03 PM, kradwrote: > Its worth noting you should also go for GPT layout and have a 100meg or so > partition provisioned as well so you can do a uefi boot. Even if you arent > going to use it right now. > > > On 30 January 2017 at 03:41, Aristedes Maniatis wrote: > > > On 30/1/17 2:20pm, Freddie Cash wrote: > > > And, you may be able to do that on the existing disks, as ZFS now > leaves > > a MB or two of "slack space" at the end of the device used in the vdev. > > This allows for using drives/partitions that are the same size in MB but > > have different numbers of sectors. This was an issue on the early ZFS > days. > > > > > > So, you may be able to resize the freebsd-zfs partition by a handful of > > KB without actually changing the size of the vdev. > > > > > > Brilliant, thank you. That worked a treat with a new boot size of 256k. > > > > > > Note that this page: https://wiki.freebsd.org/ > RootOnZFS/GPTZFSBoot/Mirror > > needs to be adjusted. This line: > > > > gpart add -b 34 -s 128k -t freebsd-boot ad0 > > > > needs to instead be > > > > gpart add -a 4k -s 512k -t freebsd-boot ad0 > > > > > > I don't have edit rights. Probably someone needs to clean up and merge > > many of these pages: https://wiki.freebsd.org/RootOnZFS/ > > > > > > Ari > > > > > > > > -- > > --> > > Aristedes Maniatis > > CEO, ish > > https://www.ish.com.au > > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A > > > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: suspend/resume on Skylake (Lenovo T460s) with FreeBSD11 stable
On Mon, Dec 19, 2016 at 11:02 AM, Christian Schwarzwrote: > On Mon, Dec 19, 2016 at 08:00:19AM +0100, Chris Ernst wrote: > > it never worked. > > I tried using the FreeBSD 11-STABLE (Revision 310008). > > As i pointed out in my first post. Suspend is working but i am unable to > > resume again. > > Same experience that I had ;) > > One idea that just came across my mind: maybe it's the graphics that > don't resume. > > You could start some network service on the laptop, then suspend & > resume, and check if the network service is reachable. > > Hello, my Lenovo X1 yoga exhibits the same traits, it does suspend, but graphics are corrupted after resume. Machine usually is reachable over the network though. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Routing stops working when we create a new vlan
On Fri, Aug 7, 2015 at 4:29 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. []'s Gondim The change to 0 is probably due to not having gateway_enable=YES in rc.conf Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: gptzfsboot: error 4 lba 30
On Mon, Mar 25, 2013 at 12:52 PM, Kai Gallasch galla...@free.de wrote: Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 (Not shortened, exactly those lines) The server then manages to boot from a mirrored zpool. What is the cause of error 4 lba 30/31 ? - controller is a hp/compaq p400 (ciss) - da0 - da7 are raid0 volumes (controller not jbod capable) - freebsd 9.1 REL (same error message with 9-STABLE from 2013-03-24) - server is zfs-only *snip* Normally one gets ( there were some mails about this just the other day ) gptzfsboot: error 1 lba 32 gptzfsboot: error 1 lba 1 on hp-machines with p410i disk controller. I think there is work ongoing to fix it, and for at least the p410i adding a simple printf in the right place in zfsboot.c allows it to boot. --- sys/boot/i386/zfsboot/zfsboot.c (revision 245604) +++ sys/boot/i386/zfsboot/zfsboot.c (working copy) @@ -453,6 +453,7 @@ heap_end = (char *) PTOV(bios_basemem); } +printf(\n); dsk = malloc(sizeof(struct dsk)); dsk-drive = *(uint8_t *)PTOV(ARGS); dsk-type = dsk-drive DRV_HARD ? TYPE_AD : TYPE_FD; works fine on a dl360g7, as well as a dl360g5. Best regards Andreas Nilsson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is the Right Way(™) to run X?
On Sun, Mar 17, 2013 at 1:07 PM, Daniel O'Connor dar...@dons.net.au wrote: Hi, I recently updated my 9.1-PRE system's ports and my previous X config now results in no mouse (but the keyboard does work). I found that I needed to add the following.. Section ServerFlags Option AllowEmptyInput False EndSection I am pretty sure this used to be necessary, then wasn't, but now seems required again.. From what I can see this means a 'startx' with no config is broken which is a bit of a step backwards. BTW I have dbus hald running. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C On my intel-based systems there is no xorg.conf and on my nVidia-systems there is one, but it contains only: Section Device Identifier nvidia Driver nvidia Option NoLogo true EndSection Section Screen Identifier default screen Device nvidia EndSection so I think your setup is somehow broken. You didn't mention which version of xorg you are using. Does lshal show any inputdevices? Have you tried to do the build from a clean environment? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is the Right Way(™) to run X?
On Sun, Mar 17, 2013 at 1:17 PM, Daniel O'Connor dar...@dons.net.au wrote: On 17/03/2013, at 22:44, Andreas Nilsson andrn...@gmail.com wrote: so I think your setup is somehow broken. You didn't mention which version of xorg you are using. Very possibly :) I have xorg-server 1.7.7_6,1 Does lshal show any inputdevices? I see the following.. udi = '/org/freedesktop/Hal/devices/atkbdc_0' freebsd.driver = 'atkbdc' (string) freebsd.unit = 0 (0x0) (int) info.parent = '/org/freedesktop/Hal/devices/computer' (string) info.product = 'Keyboard controller (i8042)' (string) info.subsystem = 'platform' (string) info.udi = '/org/freedesktop/Hal/devices/atkbdc_0' (string) platform.id = 'atkbdc.0' (string) pnp.description = 'IBM Enhanced (101/102-key, PS/2 mouse support)' (string) pnp.id = 'PNP0303' (string) udi = '/org/freedesktop/Hal/devices/atkbd_0' freebsd.device_file = '/dev/atkbd0' (string) freebsd.driver = 'atkbd' (string) freebsd.unit = 0 (0x0) (int) info.addons.singleton = {'hald-addon-input'} (string list) info.capabilities = {'input', 'input.keyboard', 'input.keys', 'button'} (string list) info.category = 'input' (string) info.parent = '/org/freedesktop/Hal/devices/atkbdc_0' (string) info.product = 'AT Keyboard' (string) info.subsystem = 'platform' (string) info.udi = '/org/freedesktop/Hal/devices/atkbd_0' (string) input.device = '' (string) input.x11_driver = 'kbd' (string) platform.id = 'atkbd.0' (string) Looks promising. Just to make sure, have you verified that hald is still running? Things can crash... Have you tried to do the build from a clean environment? Not really, I can't just nuke the existing packages and do an install (I suppose I could do it in a chroot). That is a problem yes. Have you considered using poudriere to build packages? It is rather nice, it can build old-school and new-school packages, and is very configurable. It does require zfs though ;) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is the Right Way(™) to run X?
On Sun, Mar 17, 2013 at 1:58 PM, Daniel O'Connor dar...@dons.net.au wrote: On 17/03/2013, at 23:08, Matthew D. Fuller fulle...@over-yonder.net wrote: However, some time back, X _did_ start being all stupid about finding the mouse for me. Un/re-plugging it (USB) after starting X made it show up working, but that's annoying and stupid (and not an option on other systems with e.g. PS/2 meece). I wound up sticking the other half of that oft-cargo-culted incantation: Section ServerFlags Option AutoAddDevices off EndSection in my config, and it's worked OK since. 's probably worth a try... Yeah, that does work too. It's just annoying it's necessary :) Sure is. One thing that also comes to mind is moused. Do you have it running? I seem to remember having weird troubles when moused wasn't running. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: rc.d/sysctl fails to parse sysctl.conf
On Thu, Feb 28, 2013 at 9:13 AM, Jeremy Chadwick j...@koitsu.org wrote: On Thu, Feb 28, 2013 at 08:45:11AM +0100, Andreas Nilsson wrote: On Wed, Feb 27, 2013 at 10:39 PM, Chris Rees cr...@freebsd.org wrote: On 27 February 2013 21:19, Andreas Nilsson andrn...@gmail.com wrote: Hello, I tried to get my sound working, and long story short: rc.d/sysctl parses sysctl.conf wrongly if there are sysctls of the form mib=val1=val2 which is what you need for sound. For reference I needed/wanted dev.hdaa.4.nid25_config=as=1,seq=15 dev.hdaa.4.nid31_config=as=1 I believe the following patch would address the incorrect parsing: --- /etc/rc.d/sysctl.old2013-02-27 22:00:00.0 +0100 +++ /etc/rc.d/sysctl2013-02-27 22:05:24.0 +0100 @@ -26,7 +26,7 @@ \#*|'') ;; *) - mib=${var%=*} + mib=${var%%=*} val=${var#*=} if current_value=`${SYSCTL} -n ${mib} 2/dev/null`; then I think that this is the right thing to do here. Chris As a follow-up question: is sysctl.conf supposed to handle all valid input one can give sysctl on the command line? Using the above example would normally be typed: sysctl dev.hdaa.4.nid25_config=as=1 seq=15 which works, but fails to work from sysctl.conf This has to do with how your shell parses things (quotes, etc.) versus how shell scripts like /etc/rc.d/sysctl do. Assuming you read/speak sh: read /etc/rc.d/sysctl. It's not very long, and fairly easy to follow, barring the %, %%, and # pattern modifier parts (read sh man page for how those work). /etc/rc.d/sysctl is not a file parser -- instead it relies on sh to do the work. Once you read the script, you'll understand how/why apostrophes, double quotes, and spaces in /etc/sysctl.conf are a problem. Solving this dilemma in sh is a pain in the ass and often involves utter nonsense like escaping (\) every character and making exceptions; folks who have written extensive shell scripts will know what I mean when I use the term quoting hell. That said, here's the general guideline: your /etc/sysctl.conf should not contain quotes or double-quotes or spaces after the assignment (=), generally speaking. If there is a sysctl MIB that actually ***requires*** spaces in its value, then whoever coded their driver/bit that way should be taken out back and flogged. Hard. This is why you probably see Andreas using a comma-delimited model (and if that works, fantastic+great!). That said: you can get spaces to work in /etc/sysctl.conf by escaping them, i.e.: some.mib=foo\ bar You might be able to escape some types of quotes, but this gets into quoting hell like I said above. Don't bother. As I said, apostrophes (') and double-quotes () and spaces ( ), will cause problems, and if you read the script it'll become apparent why. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | Yes, the parsing hell is not a nice place to be in. I found that easiest solution was to split the config into separate lines like dev.hdaa.4.nid25_config=as=1 dev.hdaa.4.nid25_config=seq=15 dev.hdaa.4.nid31_config=as=1 Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
rc.d/sysctl fails to parse sysctl.conf
Hello, I tried to get my sound working, and long story short: rc.d/sysctl parses sysctl.conf wrongly if there are sysctls of the form mib=val1=val2 which is what you need for sound. For reference I needed/wanted dev.hdaa.4.nid25_config=as=1,seq=15 dev.hdaa.4.nid31_config=as=1 I believe the following patch would address the incorrect parsing: --- /etc/rc.d/sysctl.old2013-02-27 22:00:00.0 +0100 +++ /etc/rc.d/sysctl2013-02-27 22:05:24.0 +0100 @@ -26,7 +26,7 @@ \#*|'') ;; *) - mib=${var%=*} + mib=${var%%=*} val=${var#*=} if current_value=`${SYSCTL} -n ${mib} 2/dev/null`; then Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: rc.d/sysctl fails to parse sysctl.conf
On Wed, Feb 27, 2013 at 10:39 PM, Chris Rees cr...@freebsd.org wrote: On 27 February 2013 21:19, Andreas Nilsson andrn...@gmail.com wrote: Hello, I tried to get my sound working, and long story short: rc.d/sysctl parses sysctl.conf wrongly if there are sysctls of the form mib=val1=val2 which is what you need for sound. For reference I needed/wanted dev.hdaa.4.nid25_config=as=1,seq=15 dev.hdaa.4.nid31_config=as=1 I believe the following patch would address the incorrect parsing: --- /etc/rc.d/sysctl.old2013-02-27 22:00:00.0 +0100 +++ /etc/rc.d/sysctl2013-02-27 22:05:24.0 +0100 @@ -26,7 +26,7 @@ \#*|'') ;; *) - mib=${var%=*} + mib=${var%%=*} val=${var#*=} if current_value=`${SYSCTL} -n ${mib} 2/dev/null`; then I think that this is the right thing to do here. Chris As a follow-up question: is sysctl.conf supposed to handle all valid input one can give sysctl on the command line? Using the above example would normally be typed: sysctl dev.hdaa.4.nid25_config=as=1 seq=15 which works, but fails to work from sysctl.conf Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Mon, Feb 4, 2013 at 2:40 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 03.02.2013 15:28, Dimitry Andric: Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS snip -- Sphinx of black quartz, judge my vow. Could you clarify where you have these settings? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Tue, Feb 5, 2013 at 1:06 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 05.02.2013 13:59, Andreas Nilsson: Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS snip Could you clarify where you have these settings? This is my desktops that I use @home and @work. I'm not going that experimental on any production machine. -- Sphinx of black quartz, judge my vow. Ah, sorry for being unclear. I meant which config files :) Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Tue, Feb 5, 2013 at 3:54 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 05.02.2013 15:06, Andreas Nilsson: Ah, sorry for being unclear. I meant which config files :) I'm using ports-mgmt/portconf to keep track of all knobs. -- Sphinx of black quartz, judge my vow. Thanks. I'll look into that, and how it will fit in with poudriere. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric d...@freebsd.org wrote: On 2013-02-03 11:39, Andreas Nilsson wrote: I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in libmap.conf ), and started to build my normal set of packages ( see desktop.list ). Please note that I also have WITH_NEW_XORG=yes and WITH_KMS=yes, as well as using the devel xorg repo. First Great work for moving FreeBSD towards a more modern c++ world! Results: Some stuff works, some don't ;) Some may be due to clang and not just libc++. Here is a list of packages that fails: audio/libofa databases/akonadi devel/binutils devel/kBuild devel/libftdi devel/libplist devel/qca devel/qt4-qdbusviewer devel/qt4-script emulators/qemu-devel graphics/cairo graphics/graphite2 graphics/libfpx graphics/opencv-core graphics/podofo graphics/vigra lang/sbcl math/cln net-im/libmsn net-p2p/libtorrent net/hupnp net/ns3 net/xmlrpc-c-devel science/openbabel security/pinentry sysutils/fusefs-kmod sysutils/synergy textproc/clucene x11/nvidia-driver Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I didn't save the output for successful packages, but looking through just the files gives libcpp.built at same URL. I expect there will be quite a few ports that are very difficult to get building and running properly with libc++. Some programs rely on undocumented (or half-documented) libstdc++ internals, or on behaviour specific to libstdc++. Also, it would not suprise me if there are programs that even depend on a very specific version of libstdc++, and its accompanying version of gcc. In short, we need some sort of system to specify the general C++ library to use by default (e.g. in make.conf or ports.conf), and for ports that only work with a very specific version, a variable similar to USE_GCC, for example: USE_LIBSTDCXX=4.6+ Sounds good :) Perhaps something like if (( CLANG_IS_CC || CC==clang ) WITH_LIBCPLUSPLUS ) CXXFLAGS+=-stdlib=libc++ endif could be added to correct mk-file where at least ns3 can be ignored ( I created that port myself ). I think nvidia-driver and fusefs-kmod now fails due to -stdlib=libc++ in LDFLAGS, normally fusefs-kmod just fails install-phase due to missing pkg-message file. I saved the workdirs for poudriere, and they are available at http://benriach.widell.net/~**andrnils/libc++/http://benriach.widell.net/~andrnils/libc++/, both as individual tarballs and one tarball that includes all the others. There is also the lists of packages I try to build, as well as the ones that fails. One general question: How am I supposed to include -stdlib=libc++ in LDFLAGS just for c++? Having -stdlib=libc++ in LDFLAGS causes c compiles to fail linking with ld: unrecognized option '-stdlib=libc++' This is as yet an unsolved problem, as LDFLAGS is the same for both C and C++ link jobs. I think the easiest way would be to set your CXX variable to: CXX=cc -stdlib=libc++ Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and CC for c++, or have that convention gone away? The -std=c++11 flag should only have to be specified in CXXFLAGS. I don't think it has any influence on linking. My adding them to LDFLAGS comes from https://wiki.freebsd.org/NewC++Stackwhere it says Add -stdlib=libc++ to your compile and link flags... It actually made a bunch of the qt4- packages build, they wouldn't without it. I guess a wiki page tracking the failing packages would be good, but I couldn't get the hang of creating a page there :( Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Sun, Feb 3, 2013 at 3:25 PM, Dimitry Andric d...@freebsd.org wrote: On 2013-02-03 14:56, Andreas Nilsson wrote: On Sun, Feb 3, 2013 at 2:28 PM, Dimitry Andric d...@freebsd.org wrote: ... This is as yet an unsolved problem, as LDFLAGS is the same for both C and C++ link jobs. I think the easiest way would be to set your CXX variable to: CXX=cc -stdlib=libc++ Wouldn't CXX=CC -stdlib=libc++ be more appropriate, as cc is for c and CC for c++, or have that convention gone away? Sorry, I should have taken one more cup of coffee. :-) 'CC' is not really recommended anymore, just use: CXX=c++ -stdlib=libc++ Ah, yes. To little coffee here as well. My adding them to LDFLAGS comes from https://wiki.freebsd.org/NewC+**+Stackwherehttps://wiki.freebsd.org/NewC++Stackwhereit says Add -stdlib=libc++ to your compile and link flags... Yes, that advice is just fine, but in some cases you cannot influence the link flags used only for C++ linking. In those cases, you will have to trick the build system into doing so. In most cases (but probably not all), this can be done by adding the required flags to ${CXX}. Good point. It actually made a bunch of the qt4- packages build, they wouldn't without it. I guess a wiki page tracking the failing packages would be good, but I couldn't get the hang of creating a page there :( This would better be done by a normal exp-run procedure, but those are offline for the time being. On a side note: I forget the actual logs. They are now available as logs.tgz at same base URL. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pkgng and updated packages
I just wanted to add that when I today went about upgrading a computer I had a very similar thing happen (with pkg-1.0.6 on 9.1-RELEASE): The new version of the package reported conflicts with the old one. Best regards Andreas On Mon, Jan 28, 2013 at 7:59 PM, Rainer Duffner rai...@ultra-secure.dewrote: Am 28.01.2013 um 18:31 schrieb Glen Barber g...@freebsd.org: On Mon, Jan 28, 2013 at 06:28:02PM +0100, Rainer Duffner wrote: I go from PERL 5.10 to PERL 5.16, for example and it complains that perl5.16 conflicts with perl5.10... This I needed, too: pkg set -o long/perl5.10:lang/perl5.16 pkg remove perl pkg set -o devel/pkg-config:devel/pkgconf pkg remove -f pkg-config Hmm, you should not have needed to remove perl or pkg-config. They should have been upgraded as any other package. I tried it without and it said it conflicted. It wanted to install perl5.16, without doing anything to 5.10. Maybe it is because I already had PERL_VERSION=5.16.2 in /etc/make.conf? I still have a couple of those to upgrade. I can send pkg_info etc. and the commands I ran from the next server on Wednesday night. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How do I circumvent the use of clang during build?
Wouldn't this be a case where man src.conf on his system actually wouldn't tell the OP what he wanted, as clang was not available as option in 8? Of course the online version of that man page from RELENG_9* would. Best regards Andreas On Mon, Dec 17, 2012 at 9:54 PM, Beeblebrox zap...@berentweb.com wrote: have a look at /etc/src.conf and $ man src.cof you can set many buildworld options there. -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-do-I-circumvent-the-use-of-clang-during-build-tp5769907p5770203.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Where do I purchace an unlock code to build a custom kernel?
I full-heartedly agree that include-statement is good, but still $ wc -l /usr/src/sys/amd64/conf/MINI 174 /usr/src/sys/amd64/conf/MINI And this is just after removing network cards ( (usb)ethernet, (usb)wlan, raid drivers and firewire) for my pretty standard lenovo t510. There is so much in GENERIC today that seems to work just as well as modules. I guess one thread on a mailing list this summer tried to achieve a more modular config, which would make the include statement even more useful. Best regards Andreas On Sat, Nov 24, 2012 at 6:50 PM, Chris H chris#@1command.com wrote: On Sat, 24 Nov 2012, Chris H wrote: Hi Chris, Friday, November 23, 2012, 11:50:16 PM, you wrote: Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8) would throw me a bone if it were wrong. Greetings, and thank you for your reply. Anyway, I'll take your advice. There are some architecture specific settings there, so it is best to actually do this and fail it early (well if you would do buildkernel it would be earlier :) than getting some strange errors. If you were thinking to just copy it to i386 directory, to save you future issues, I would recommend you to redo the config based on GENERIC in i386 directory. Understood. That's what I did (i386/GENERIC -- CUSTOM). I _knew_ there would be issue(s) otherwise. Thank you again for the advice. Looks to be working as expected. :) Rather than copy and modify, a custom config can include the GENERIC config and override settings. That generally makes the custom config file smaller and easier to maintain: http://www.wonkity.com/~wblock/docs/html/kernelconfig.html Excellent advice. In fact I now feel fairly embarrassed, as your suggestion seems so _obvious_. :P Thanks, that will _definitely_ be my course of action, going forward (as will cross-compiling on my 6 core AMD64 for this k7) :) Best wishes. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: natd in a jail
On Fri, Nov 23, 2012 at 7:22 AM, Morgan Reed morgan.s.r...@gmail.comwrote: On Fri, Nov 23, 2012 at 5:16 PM, Morgan Reed morgan.s.r...@gmail.com wrote: So it turns out I'd not bought bpf into the jails, however even with that and raw_sockets enabled I'm still having no joy with natd. I've been looking at ipfw a bit today but I've run into an issue, loading ipfw_nat causes my kernel to instantly panic, I need to recompile with KDB and DDB turned on so I can actually catch the trace though... Might look at netgraph before going too far down that path. Scratch that, netgtaph isn't in the GENERIC kernel, so I'll have to rebuild anyway. Why not just load the module? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Hangs with nvidia-driver.
On Mon, Nov 5, 2012 at 9:03 AM, arrowdodger 6year...@gmail.com wrote: I've started experiencing hangs after 9.1-RC2 update. These hangs are caused by indefinitly looping somewhere inside nvidia_drv.so. As time passes, X server figures it out somehow and escapes from loop, but after short time everything hangs again. I've tried downgrading to RC1 and upgrading to RC3, downgrading NVIDIA driver to 295 and upgrading to the latest, downgrading Xorg and friends to 1.7.7 and upgrading to the latest with WITHOUT_NOUVEAU set. Nothing helped. Interesting lines from dmesg: NVRM: Xid (:01:00): 8, Channel NVRM: Xid (:01:00): 8, Channel NVRM: Xid (:01:00): 8, Channel NVRM: Xid (:01:00): 13, e0014a00 004a 0100 0010 NVRM: Xid (:01:00): 12, COCOD e0013900 0039 0300 0006 Xorg.0.log: (WW) Nov 05 10:54:18 NVIDIA(0): WAIT (1, 6, 0x8000, 0xf7a0, 0xfb54) (WW) Nov 05 10:54:26 NVIDIA(0): WAIT (0, 6, 0x8000, 0x06e8, 0x06e8) (WW) Nov 05 10:54:29 NVIDIA(0): WAIT (2, 6, 0x8000, 0x06e8, 0x0814) (WW) Nov 05 10:54:37 NVIDIA(0): WAIT (2, 6, 0x8000, 0xbc38, 0xc520) (WW) Nov 05 10:55:10 NVIDIA(0): WAIT (0, 7, 0x8000, 0x5c30, 0x5c30) (WW) Nov 05 10:55:13 NVIDIA(0): WAIT (0, 7, 0x8000, 0x5c54, 0x5c54) (WW) Nov 05 10:55:16 NVIDIA(0): WAIT (0, 7, 0x8000, 0x5c78, 0x5c78) [mi] EQ overflowing. The server is probably stuck in an infinite loop. (WW) Nov 05 10:55:41 NVIDIA(0): WAIT (2, 6, 0x8000, 0xd100, 0xe444) (WW) Nov 05 10:55:48 NVIDIA(0): WAIT (1, 6, 0x8000, 0xd100, 0xe444) (WW) Nov 05 10:55:51 NVIDIA(0): WAIT (2, 6, 0x8000, 0xd100, 0xf8c0) (WW) Nov 05 10:56:04 NVIDIA(0): WAIT (2, 6, 0x8000, 0xc340, 0xd534) (WW) Nov 05 10:56:18 NVIDIA(0): WAIT (2, 6, 0x8000, 0xeb10, 0xeee4) [mi] EQ overflowing. The server is probably stuck in an infinite loop. uname -a: FreeBSD alore 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 03:56:40 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 My video card is GeForce 6600. Please CC me, since i'm not subscribed to the list. I have similar experience, but for me it only happens after a suspend-to-ram cycle, and more often then with external screen connected. I use WITH_NEW_XORG and the xorg-dev repo. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: buildworld fails on recent stable
On Mon, Nov 5, 2012 at 12:41 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: Hi all. When CLANG_IS_CC build fails at sys/boot/i386/boot2: ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/**i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/**i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 -5 bytes available *** [boot2] Error code 1 The relevant output before r242562 looked like: ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/**i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/**i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1569 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1df9 text=200 data=1bf9 org=0 entry=0 7 bytes available dd if=boot2.ld of=boot2 obs=7680 conv=osync -- Sphinx of black quartz, judge my vow. I can confirm, for at least revisions 242602 and 242605. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Wed, Oct 31, 2012 at 3:12 PM, Glen Barber g...@freebsd.org wrote: On Wed, Oct 31, 2012 at 08:30:29AM +0100, Andreas Nilsson wrote: On a more whislist topic: I'd really appreciate if .zfs dirs would be excluded from the tarballs. Hmm, I didn't realize this was happening. So I can verify my change works for all environments, are you using any local zfs dataset properties, specifically unhiding the snapshot directory? Glen Yes, I have the following: tank/cvs/9.1/src snapdir visibleinherited from tank/cvs Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Wed, Oct 31, 2012 at 4:07 AM, Glen Barber g...@freebsd.org wrote: On Tue, Oct 30, 2012 at 08:11:15PM -0400, Glen Barber wrote: Oops, my bad. Yes exact same behavior; make -C release cdrom fails with ... find //tank/cvs/9.1/src/release/dist/doc -empty -delete find //tank/cvs/9.1/src/release/dist/games -empty -delete find: -delete: //tank/cvs/9.1/src/release/dist/games: relative path potentially not safe *** [distributeworld] Error code 1 on 9.1-RC3. I can try with 9-stable as well (tomorrow). Ok, thanks. I do not want to assume anything more at this point. I am still waiting for my build machine to finish a few queued things. Once it frees up, I will roll a release using sudo (just for my own sanity), and without sudo, with your src.conf and make.conf. Anyway, thanks for all of the details you have provided. It is all helpful, and hopefully this will finally be tracked down. Ugh... Ok, so this is my fault. I do not remember why, specifically, but the change in question was not merged to the releng/9.1 branch. Please try the following, in the top-level directory of your releng/9.1 source checkout: svn merge -c240077 ^/head/Makefile.inc1 Makefile.inc1 It worked for me fine. Unfortunately, it is far too late in the release cycle for that change to make it into 9.1-RELEASE. Great that you found the bug! Unfortunately, this does not have anything to do with the recursing in the usr/src tarball. Please let me know if you continue to see that happen, as this is the _single_ most reported issue that I have had zero luck reproducing... With just the merge above now 9.1-RC3 ends up recursing. ( Just tried them one at a time ). Thanks. Glen PS: Sorry about being the cause of your release build failure... No problem really :) Thanks for hunting this down now. /A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Wed, Oct 31, 2012 at 4:35 AM, Glen Barber g...@freebsd.org wrote: On Tue, Oct 30, 2012 at 11:19:12PM -0400, Glen Barber wrote: So, please also do: svn merge -c241451 ^/head/release release You'll want to merge one more revision: svn merge -c241596 ^/head/release release Same as before - I _think_ this should work. :-) Glen Excelent :) That did the trick, ie no recursion :) Thank you very much for finding the bugs. Will this be merge to 9-stable? On a more whislist topic: I'd really appreciate if .zfs dirs would be excluded from the tarballs. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
First, late me state status more clearly: solved :) Big thanks for fixing it. On a side note, how has re-team not run into this? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
make release fails on find
I'm trying to build some images for 9-stable ( r242349 ) and 9.1-RC3, but using the release tools doesn't really work. 9.1-RC3 fails with: ... cd /tank/cvs/9.1/src/libexec/rtld-elf; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf32.so.1 /tmp/newdist/lib32/libexec /tmp/newdist/lib32/usr/libexec/ld-elf32.so.1 - /libexec/ld-elf32.so.1 cd /tank/cvs/9.1/src/usr.bin/ldd; PROG=ldd32 MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 _SHLIBDIRPREFIX=/usr/obj/tank/cvs/9.1/src/lib32 VERSION=FreeBSD 9.1-PRERELEASE amd64 901501 PATH=/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/tmp/install.SgiYOaRS CC=cc -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 CXX=c++ -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 LIBDIR=/usr/lib32 SHLIBDIR=/usr/lib32 make -DNO_CPU_CFLAGS -DCOMPAT_32BIT -DWITHOUT_BIND -DWITHOUT_MAN -DWITHOUT_INFO -DWITHOUT_HTML -DNO_CTF -DNO_LINT -ECC -ECXX -EAS -ELD -DNO_INCS distribute cd /tank/cvs/9.1/src/usr.bin/ldd; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 ldd32 /tmp/newdist/lib32/usr/bin find //tmp/newdist/doc -empty -delete find //tmp/newdist/games -empty -delete find: -delete: //tmp/newdist/games: relative path potentially not safe *** [distributeworld] Error code 1 Stop in /tank/cvs/9.1/src. *** [distributeworld] Error code 1 And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. Is anyone having the same problems? Build machine is amd64 9.1-PRERELASE. Source trees are in separate zfs datasets (tank/cvs/9/src and tank/cvs/9.1/src). Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Tue, Oct 30, 2012 at 5:08 PM, Glen Barber g...@freebsd.org wrote: On Tue, Oct 30, 2012 at 04:58:52PM +0100, Andreas Nilsson wrote: I'm trying to build some images for 9-stable ( r242349 ) and 9.1-RC3, but using the release tools doesn't really work. 9.1-RC3 fails with: ... cd /tank/cvs/9.1/src/libexec/rtld-elf; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf32.so.1 /tmp/newdist/lib32/libexec /tmp/newdist/lib32/usr/libexec/ld-elf32.so.1 - /libexec/ld-elf32.so.1 cd /tank/cvs/9.1/src/usr.bin/ldd; PROG=ldd32 MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 _SHLIBDIRPREFIX=/usr/obj/tank/cvs/9.1/src/lib32 VERSION=FreeBSD 9.1-PRERELEASE amd64 901501 PATH=/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/tmp/install.SgiYOaRS CC=cc -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 CXX=c++ -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 LIBDIR=/usr/lib32 SHLIBDIR=/usr/lib32 make -DNO_CPU_CFLAGS -DCOMPAT_32BIT -DWITHOUT_BIND -DWITHOUT_MAN -DWITHOUT_INFO -DWITHOUT_HTML -DNO_CTF -DNO_LINT -ECC -ECXX -EAS -ELD -DNO_INCS distribute cd /tank/cvs/9.1/src/usr.bin/ldd; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 ldd32 /tmp/newdist/lib32/usr/bin find //tmp/newdist/doc -empty -delete find //tmp/newdist/games -empty -delete find: -delete: //tmp/newdist/games: relative path potentially not safe *** [distributeworld] Error code 1 Stop in /tank/cvs/9.1/src. *** [distributeworld] Error code 1 Are you defining WITH*_GAMES in src.conf or make.conf? If this looks like what I think it looks like, I fixed this a few months ago. Used same command for building both, see below. And yes, WITHOUT_GAMES is set in src.conf And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. I have seen many reports on this, and cannot reproduce it. How exactly are you running the release build? What specific make(1) targets are you using, and what is your make.conf/src.conf contents? Glen I did the following steps: zfs create tank/cvs/9 zfs create tank/cvs/9/src zfs create tank/cvs/9.1 zfs create tank/cvs/9.1/src cd /tank/cvs/9/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9 . cd /tank/cvs/9.1/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9.1 . cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom /relng/files/src.conf contains: $ cat /relng/files/src.conf WITHOUT_X11=true WITHOUT_BLUETOOTH=true WITHOUT_CLANG=true WITHOUT_ATM=true WITHOUT_CTM=true WITHOUT_CDDL=true WITHOUT_DICT=true WITHOUT_HTML=true WITHOUT_IPFILTER=true WITHOUT_IPX=true WITHOUT_IPX_SUPPORT=true WITHOUT_LOCALES=true WITHOUT_LPR=true WITHOUT_NCP=true WITHOUT_NIS=true WITHOUT_OBJC=true WITHOUT_RCMDS=true WITHOUT_RCS=true WITHOUT_SENDMAIL=true WITHOUT_SSP=true WITHOUT_ZFS=true WITHOUT_BIND_DNSSEC=true WITHOUT_GAMES=true WITHOUT_IPX=true WITHOUT_NIS=true WITHOUT_PF=true WITHOUT_SENDMAIL=true WITHOUT_WIRELESS=true make.conf contains: $ cat /etc/make.conf CPUTYPE?=core2 CFLAGS=-pipe -O2 BUILD_JOBS=8 WITHOUT_SENDMAIL=true WITHOUT_X11=true DISTDIR=/tank/distfiles WRKDIRPREFIX?=/tmp/ports PACKAGES?=/tmp/ports/packages # WITH_KMS=yes WITH_NEW_XORG=yes # added by use.perl 2012-10-15 17:24:41 PERL_VERSION=5.14.2 Some of the stuff there could be removed I guess... Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Tue, Oct 30, 2012 at 6:09 PM, Glen Barber g...@freebsd.org wrote: On Tue, Oct 30, 2012 at 05:32:20PM +0100, Andreas Nilsson wrote: Are you defining WITH*_GAMES in src.conf or make.conf? If this looks like what I think it looks like, I fixed this a few months ago. Used same command for building both, see below. And yes, WITHOUT_GAMES is set in src.conf And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. I have seen many reports on this, and cannot reproduce it. How exactly are you running the release build? What specific make(1) targets are you using, and what is your make.conf/src.conf contents? Glen I did the following steps: zfs create tank/cvs/9 zfs create tank/cvs/9/src zfs create tank/cvs/9.1 zfs create tank/cvs/9.1/src cd /tank/cvs/9/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9 . cd /tank/cvs/9.1/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9.1 . cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom /relng/files/src.conf contains: $ cat /relng/files/src.conf WITHOUT_X11=true WITHOUT_BLUETOOTH=true WITHOUT_CLANG=true WITHOUT_ATM=true WITHOUT_CTM=true WITHOUT_CDDL=true WITHOUT_DICT=true WITHOUT_HTML=true WITHOUT_IPFILTER=true WITHOUT_IPX=true WITHOUT_IPX_SUPPORT=true WITHOUT_LOCALES=true WITHOUT_LPR=true WITHOUT_NCP=true WITHOUT_NIS=true WITHOUT_OBJC=true WITHOUT_RCMDS=true WITHOUT_RCS=true WITHOUT_SENDMAIL=true WITHOUT_SSP=true WITHOUT_ZFS=true WITHOUT_BIND_DNSSEC=true WITHOUT_GAMES=true WITHOUT_IPX=true WITHOUT_NIS=true WITHOUT_PF=true WITHOUT_SENDMAIL=true WITHOUT_WIRELESS=true make.conf contains: $ cat /etc/make.conf CPUTYPE?=core2 CFLAGS=-pipe -O2 BUILD_JOBS=8 WITHOUT_SENDMAIL=true WITHOUT_X11=true DISTDIR=/tank/distfiles WRKDIRPREFIX?=/tmp/ports PACKAGES?=/tmp/ports/packages # WITH_KMS=yes WITH_NEW_XORG=yes # added by use.perl 2012-10-15 17:24:41 PERL_VERSION=5.14.2 I don't really see any reason this should not work. However, I have not tested with sudo. Maybe that is the piece of the puzzle I am missing... Glen Hmm, interesting idea, would be pretty bad if sudo caused that. I gave it run without direct sudo call ( ie sudo bash, then make ... ) and no go. Doing just su - and cd'ing to proper dir and the make ... is still not working. Overnight I'll try to build world and kernel without src.conf ( ie SRCCONF=/dev/null ) and same for make release. I'll posts results in the morning. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Tue, Oct 30, 2012 at 11:29 PM, Andreas Nilsson andrn...@gmail.comwrote: On Tue, Oct 30, 2012 at 6:09 PM, Glen Barber g...@freebsd.org wrote: On Tue, Oct 30, 2012 at 05:32:20PM +0100, Andreas Nilsson wrote: Are you defining WITH*_GAMES in src.conf or make.conf? If this looks like what I think it looks like, I fixed this a few months ago. Used same command for building both, see below. And yes, WITHOUT_GAMES is set in src.conf And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. I have seen many reports on this, and cannot reproduce it. How exactly are you running the release build? What specific make(1) targets are you using, and what is your make.conf/src.conf contents? Glen I did the following steps: zfs create tank/cvs/9 zfs create tank/cvs/9/src zfs create tank/cvs/9.1 zfs create tank/cvs/9.1/src cd /tank/cvs/9/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9 . cd /tank/cvs/9.1/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9.1 . cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom /relng/files/src.conf contains: $ cat /relng/files/src.conf WITHOUT_X11=true WITHOUT_BLUETOOTH=true WITHOUT_CLANG=true WITHOUT_ATM=true WITHOUT_CTM=true WITHOUT_CDDL=true WITHOUT_DICT=true WITHOUT_HTML=true WITHOUT_IPFILTER=true WITHOUT_IPX=true WITHOUT_IPX_SUPPORT=true WITHOUT_LOCALES=true WITHOUT_LPR=true WITHOUT_NCP=true WITHOUT_NIS=true WITHOUT_OBJC=true WITHOUT_RCMDS=true WITHOUT_RCS=true WITHOUT_SENDMAIL=true WITHOUT_SSP=true WITHOUT_ZFS=true WITHOUT_BIND_DNSSEC=true WITHOUT_GAMES=true WITHOUT_IPX=true WITHOUT_NIS=true WITHOUT_PF=true WITHOUT_SENDMAIL=true WITHOUT_WIRELESS=true make.conf contains: $ cat /etc/make.conf CPUTYPE?=core2 CFLAGS=-pipe -O2 BUILD_JOBS=8 WITHOUT_SENDMAIL=true WITHOUT_X11=true DISTDIR=/tank/distfiles WRKDIRPREFIX?=/tmp/ports PACKAGES?=/tmp/ports/packages # WITH_KMS=yes WITH_NEW_XORG=yes # added by use.perl 2012-10-15 17:24:41 PERL_VERSION=5.14.2 I don't really see any reason this should not work. However, I have not tested with sudo. Maybe that is the piece of the puzzle I am missing... Glen Hmm, interesting idea, would be pretty bad if sudo caused that. I gave it run without direct sudo call ( ie sudo bash, then make ... ) and no go. Doing just su - and cd'ing to proper dir and the make ... is still not working. Overnight I'll try to build world and kernel without src.conf ( ie SRCCONF=/dev/null ) and same for make release. I'll posts results in the morning. Best regards Andreas Just a quick update; running a new buildworld+buildkernel and then make release from su - does not work :( Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make release fails on find
On Wed, Oct 31, 2012 at 12:14 AM, Glen Barber g...@freebsd.org wrote: On Wed, Oct 31, 2012 at 12:11:22AM +0100, Andreas Nilsson wrote: interesting idea, would be pretty bad if sudo caused that. Indeed, but sudo only keeps certain environment variables, so it's not entirely unexpected if this is the case. I gave it run without direct sudo call ( ie sudo bash, then make ... ) and no go. Doing just su - and cd'ing to proper dir and the make ... is still not working. Overnight I'll try to build world and kernel without src.conf ( ie SRCCONF=/dev/null ) and same for make release. I'll posts results in the morning. Best regards Andreas Just a quick update; running a new buildworld+buildkernel and then make release from su - does not work :( You've said 'does not work' twice. Can you elaborate more? What specifically isn't working? Same behavior as before, or...? Glen Oops, my bad. Yes exact same behavior; make -C release cdrom fails with ... find //tank/cvs/9.1/src/release/dist/doc -empty -delete find //tank/cvs/9.1/src/release/dist/games -empty -delete find: -delete: //tank/cvs/9.1/src/release/dist/games: relative path potentially not safe *** [distributeworld] Error code 1 on 9.1-RC3. I can try with 9-stable as well (tomorrow). Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern.maxswzone is gone... what next?
On Thu, Oct 11, 2012 at 3:38 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 11.10.2012 18:37, Sergey Kandaurov wrote: On 11 October 2012 19:32, Volodymyr Kostyrko c.kw...@gmail.com wrote: Hi all. I prefer to build all ports in /tmp, which is actually a tmpfs filesystem. I have 8G partition. But when I tried to compile Apache OpenOffice system starts shooting processes when I was near 6G of swap. Oct 11 18:12:32 ar1l0u kernel: swap zone exhausted, increase kern.maxswzone Oct 11 18:12:32 ar1l0u kernel: pid 1334 (java), uid 818, was killed: out of swap space Oct 11 18:12:32 ar1l0u kernel: pid 74518 (thunderbird), uid 1001, was killed: out of swap space Oct 11 18:12:32 ar1l0u kernel: swap zone ok How much RAM (avail memory) do you have? 2G I can chime in with the exact same error. I was using poudriere to build some ports, and on apache-oo the machine actually had a kernel panic. Machine has 16gb of ram and 16gb swap. I had top running (update every 1 sec) and there was 10gb of swap free when panic happened. The OS is fbsd 9.1-PRERELEASE, from before problematic changes with nullfs/zfs interaction. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: how to update ports while using pkgng?
On Sat, Sep 15, 2012 at 6:41 AM, Mike Manilone crtm...@gmx.us wrote: Hi, I'm using ports with pkgng enabled. But I found that portmaster won't work. Is there any way to update ports? Thanks! Since no one asked: Why would you want to do it this way? If you are using pkgng updating is as easy as: pkg upgrade. If you have some programs installed not available from official pkgng repositories you are on thin ice and should consider using something like ports-mgmt/poudriere to build pkgng packages of those ports and host your own repo from which you can then install them. As others already said: pkgng is drastically different from previous package management, so they do should not be used in parallel. Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clang as default compiler
in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? It probably is. However, WITHOUT_GCC is not supported yet. On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm l#i386-and-x86_002d64-Options Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in the FreeBSD source directory for supported march switches. There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. Is there a time frame for this requirement? And for the know broken ports, how are the users supposed to deal with them until the ports is fixed? Modifying the port by hand in the local ports tree? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Clang as default compiler
Today I decided to take the plunge and make clang the default compiler, ie I set WITH_CLANG=yes WITH_CLANG_IS_CC=yes WITH_CLANG_EXTRAS=yes in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options After successful install I went on to upgrade some ports. Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 6:50 AM, Ken Smith kensm...@buffalo.edu wrote: The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 9.0-RELEASE can upgrade as follows: # freebsd-update upgrade -r 9.1-RC1 This has not been working for me on i386 for the last few days. It fails with: [root@mist /usr/home/andrnils]# freebsd-update upgrade -r 9.1-RC1 Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. Best regards Andreas ... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: battery state
On Wed, Aug 15, 2012 at 10:36 AM, Dominic Fandrey kamik...@bsdforen.dewrote: For a while now acpiconf -i0 always shows the battery state that was correct when booting the system. It's never updated. snip It wont solve the problem, but does the sysctl hw.acpi.battery.time update correctly? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: battery state
On Wed, Aug 15, 2012 at 10:45 AM, Dominic Fandrey kamik...@bsdforen.dewrote: On 15/08/2012 10:40, Andreas Nilsson wrote: On Wed, Aug 15, 2012 at 10:36 AM, Dominic Fandrey kamik...@bsdforen.de wrote: For a while now acpiconf -i0 always shows the battery state that was correct when booting the system. It's never updated. snip It wont solve the problem, but does the sysctl hw.acpi.battery.time update correctly? Thanks for the fast reply, right now it shows -1 (the system was plugged in during boot). I just unplugged it and it still shows -1: sysctl hw.acpi.battery hw.acpi.battery.life: 99 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Sounds like there is some acpi-problem then. On my thinkpad it takes maybe five seconds for it to go from -1 to an estimate. Also hw.acpi.battery.state=0 for me equals AC plugged in and battery full. I have this in my .xinitrc to monitor my battery ( in a loop which then uses xsetroot to show the info ): case `sysctl -n hw.acpi.battery.state` in 0) batstate=AC full ;; 1) batstate=`sysctl -n hw.acpi.battery.time` m ;; 2) batstate=AC charing ;; Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: new desktop box
On Wed, Jun 27, 2012 at 6:37 PM, Zoran Kolic zko...@sbb.rs wrote: Dear list! This evening my 7 years old node powers down for it's own sake. After a bit of panic, I made a decision to get new box. Regarding fast development of hardware, I cannot choose what is the correct way to go. For long time I use AMD and would like to have another one, but would listen to advice, if proves better to have intel. What are features I'd like: - to be silent and cold - to stay on not-expensive side Finally, questions. Phenom II 1100 or something else? Mobo for said cpu with eth, well working with freebsd? Graphical card, silent, that would work with amd64, branch 9? No games, nothing fancy. To last next few years. I plan to com- pile kernel or two. Half of usage is in console, startx then. I will give additional information for my taste, if needed. Best regards Zoran You did not specify what expensive is to you, nor if you want prebuilt or if you want to assemble it yourself. I'd go with Intel today. We just got Dell Vostro 460 desktops, with Intel core i5-2400 cpu with integrated graphics. Works really good, almost quiet. You would need to go with 9-stable and use new xorg though, so once X is started, you would lose console. The only bad thing is perhaps the ethernet, it's some lousy RTL8111/8168B PCI Express Gigabit Ethernet controller If you want a few hdds the chassi is not that good. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ULE Scheduler
On Fri, Jun 8, 2012 at 2:29 AM, Momchil Ivanov momc...@xaxo.eu wrote: At Fri, 8 Jun 2012 00:54:15 +0200, Martin Sugioarto wrote: [1 text/plain; UTF-8 (quoted-printable)] Am Thu, 07 Jun 2012 03:01:07 +0200 schrieb Момчил Иванов momc...@xaxo.eu: Is there some remedy? Hi, I remember this series, I've had a T60p and when I compiled world, I placed a fan in front of it to cool it down from 100°C. The difference with T60p was that it simply shut off reaching 101°C. The problem is the hardware, not FreeBSD. T60p and obviously T60, too, was made by some crazy people who had the idea to cool the CPU und the GPU under the same heat sink. The funny thing is that the GPU is running at 70°C all the time, because FreeBSD does not implement voltage regulation for the VGA chipset. The result is that the GPU warms up the CPU to at least 55°C while idle. If you want to have a cooler CPU implement power saving for the Radeon chipset there. Martin [2 signature.asc application/pgp-signature (7bit)] Hi, well, that is not true, I have been using the laptop since more than 4 years without any problems. The thing is that yesterday I had it docked and that seems to raise the idle temperature by about 10°C, so I get docked somewhere about 42°C when doing nothing computationally intensive: hw.acpi.thermal.tz0.temperature: 50.0C hw.acpi.thermal.tz1.temperature: 42.0C dev.cpu.0.temperature: 42.0C dev.cpu.1.temperature: 42.0C So I probably have to shift things around to give the dock a bit more room. However, the dust, the thermal liquid and the screws seem to have contributed to the temperature increase too. The GPU (Nvidia Quadro NVS 140M) might be an issue, nvidia-settings says 58°C (I am not running any fancy graphics) and I've seen it getting over 100-120°C before, when I am doing some opengl stuff. With the latter I mean, that I know how to intentionally kill it. Anyway, I have solved my problem and that seems to not be related to ULE at all. However, it was still surprising for me to find out how ULE schedules computationally intensive tasks. Regards, Momchil My t61p also had overheating problems with fbsd, but never in linux. For me the fan control was somewhat broken: I had to turn off auto-mode and set max myself to get any heavy usage out of it. You might want to check that as well. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD9 and the sheer number of problem reports
On Fri, Feb 24, 2012 at 7:46 AM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, On Friday 24 February 2012 04:21:12 Peter Maloney wrote: Am 23.02.2012 21:15, schrieb Mark Felder: On Thu, 23 Feb 2012 12:25:01 -0600, Damien Fleuriot m...@my.gd wrote: Now, I find the number of problem reports regarding 9.0-RELEASE alarming and I'm growing more and more fearful towards it. I suggest these concepts should be tested: I can tell you what in practical terms stops me from testing very often. The switch back to the running version. Let me suggest this. Currently, we have on the disk normally two kernels. The current one and the last one. Why not add a third one called testing? Add then an entry into the boot menu that users can switch between the current kernel and a kernel they just installed for testing. Well, as you would want to test both kernel + userland its get a bit tricky on ufs based system, as you have to setup several slices/partitions. For ZFS its easier, as the only thing required would be a snapshot of clean install, which the user then can just zfs recv, modify vfs.root.mountfrom and so on. Just my thoughts. Andreas I know that I can do this manually. But this is the point where it becomes difficult for the majority of people. As FreeBSD needs a large amount of testing on unknown hardware, this could increase the number of actual testers without much effort. Ok, the developers must then be ready to deal with reports which miss many things. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: nmbclusters: how do we want to fix this for 8.3 ?
On Thu, Feb 23, 2012 at 9:19 AM, Fabien Thomas fabien.tho...@netasq.comwrote: Le 22 févr. 2012 à 22:51, Jack Vogel a écrit : On Wed, Feb 22, 2012 at 1:44 PM, Luigi Rizzo ri...@iet.unipi.it wrote: On Wed, Feb 22, 2012 at 09:09:46PM +, Ben Hutchings wrote: On Wed, 2012-02-22 at 21:52 +0100, Luigi Rizzo wrote: ... I have hit this problem recently, too. Maybe the issue mostly/only exists on 32-bit systems. No, we kept hitting mbuf pool limits on 64-bit systems when we started working on FreeBSD support. ok never mind then, the mechanism would be the same, though the limits (especially VM_LIMIT) would be different. Here is a possible approach: 1. nmbclusters consume the kernel virtual address space so there must be some upper limit, say VM_LIMIT = 256000 (translates to 512MB of address space) 2. also you don't want the clusters to take up too much of the available memory. This one would only trigger for minimal-memory systems, or virtual machines, but still... MEM_LIMIT = (physical_ram / 2) / 2048 3. one may try to set a suitably large, desirable number of buffers TARGET_CLUSTERS = 128000 4. and finally we could use the current default as the absolute minimum MIN_CLUSTERS = 1024 + maxusers*64 Then at boot the system could say nmbclusters = min(TARGET_CLUSTERS, VM_LIMIT, MEM_LIMIT) nmbclusters = max(nmbclusters, MIN_CLUSTERS) In turn, i believe interfaces should do their part and by default never try to allocate more than a fraction of the total number of buffers, Well what fraction should that be? It surely depends on how many interfaces are in the system and how many queues the other interfaces have. if necessary reducing the number of active queues. So now I have too few queues on my interface even after I increase the limit. There ought to be a standard way to configure numbers of queues and default queue lengths. Jack raised the problem that there is a poorly chosen default for nmbclusters, causing one interface to consume all the buffers. If the user explicitly overrides the value then the number of cluster should be what the user asks (memory permitting). The next step is on devices: if there are no overrides, the default for a driver is to be lean. I would say that topping the request between 1/4 and 1/8 of the total buffers is surely better than the current situation. Of course if there is an explicit override, then use it whatever happens to the others. cheers luigi Hmmm, well, I could make the default use only 1 queue or something like that, was thinking more of what actual users of the hardware would want. I think this is more reasonable to setup interface with one queue. Even if the cluster does not hit the max you will end up with unbalanced setting that let very low mbuf count for other uses. If interfaces have the possibility to use more queues, they should, imo so I'm all for rasing the default size. For those systems with very limited memory it's easily changed. After the installed kernel is booted and the admin would do whatever post install modifications they wish it could be changed, along with nmbclusters. This was why i sought opinions, of the algorithm itself, but also anyone using ixgbe and igb in heavy use, what would you find most convenient? Jack ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New BSD Installer
On Mon, Feb 13, 2012 at 3:58 PM, George Kontostanos gkontos.m...@gmail.comwrote: I don't think that reverting is either an option or a solution at this point. You can consider filing PRs. How compatible is bsdinstaller with pc-sysinstaller? Are there any notes on why a new installer was created over reusing pc-sysinstall? Regards Andreas Nilsson -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New BSD Installer
On 13 feb 2012, at 17:08, Bruce Cran br...@cran.org.uk wrote: pc-sysinstall doesn't work (well?) on non-x86 platforms so bsdinstall was created as an interim solution. I'll take your word for it, but as far as I know the backend is shell-based as well. /Andreas -- Bruce Cran Sent from my iPhone On 13 Feb 2012, at 15:44, Andreas Nilsson andrn...@gmail.com wrote: On Mon, Feb 13, 2012 at 3:58 PM, George Kontostanos gkontos.m...@gmail.comwrote: I don't think that reverting is either an option or a solution at this point. You can consider filing PRs. How compatible is bsdinstaller with pc-sysinstaller? Are there any notes on why a new installer was created over reusing pc-sysinstall? Regards Andreas Nilsson -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Reducing the need to compile a custom kernel
2012/2/10 Marek 'Buki' Kozlovský free...@dev.null.cz On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote: Hi, during some big discussions in the last monts on various lists, one of the problems was that some people would like to use freebsd-update but can't as they are using a custom kernel. With all the kernel modules we provide, the need for a custom kernel should be small, but on the other hand, we do not provide a small kernel-skeleton where you can load just the modules you need. This should be easy to change. As a first step I took the generic kernel and removed all devices which are available as modules, e.g. the USB section consists now only of the USB_DEBUG option (so that the module is build like with the current generic kernel). I also removed some storage drivers which are not available as a module. The rationale is, that I can not remove CAM from the kernel config if I let those drivers inside (if those drivers are important enough, someone will probably fix the problem and add the missing pieces to generate a module). Such a kernel would cover situations where people compile their own kernel because they want to get rid of some unused kernel code (and maybe even need the memory this frees up). The question is, is this enough? Or asked differently, why are you compiling a custom kernel in a production environment (so I rule out debug options zhich are not enabled in GENERIC)? Are there options which you add which you can not add as a module (SW_WATCHDOG comes to my mind)? If yes, which ones and how important are they for you? I need (not on every machine, granted) IPSEC and MROUTING Bye, Alexander. -- Cheit's Lament: If you help a friend in need, he is sure to remember you-- the next time he's in need. http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Buki IPFIREWALL_DEFAULT_TO_ACCEPT, DEVICE_POLLING and HZ=1000. /Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SVN checkout
On 01/13/2012 09:51 PM, Garrett Cooper wrote: On Jan 13, 2012, at 5:53 AM, Julian Kennedy wrote: Hi All Im just joined the list. Im not sure if this is the right place to ask svn questions. I want to checkout the freebsd code to play with it a bit. What should I do and which part of the repo should I checkout? I want the 9.0 code. $ cd /usr/src $ svn co http://svn.freebsd.org/base/release/9.0.0 . Can I just ask a for a clarification then: would .../release/8.2.5 get me what after buildworld+buildkernel results in 8.2-RELEASE-p5? I ask because I have some interest in having a tree from which i easily can check out a given patch-version. Cheers, -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Regards Andreas Nilsson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SVN checkout
On Fri, Jan 13, 2012 at 11:00 PM, Garrett Cooper yaneg...@gmail.com wrote: On Jan 13, 2012, at 1:55 PM, John Baldwin wrote: On Friday, January 13, 2012 4:40:08 pm Andreas Nilsson wrote: On 01/13/2012 09:51 PM, Garrett Cooper wrote: On Jan 13, 2012, at 5:53 AM, Julian Kennedy wrote: Hi All Im just joined the list. Im not sure if this is the right place to ask svn questions. I want to checkout the freebsd code to play with it a bit. What should I do and which part of the repo should I checkout? I want the 9.0 code. $ cd /usr/src $ svn co http://svn.freebsd.org/base/release/9.0.0 . Can I just ask a for a clarification then: would .../release/8.2.5 get me what after buildworld+buildkernel results in 8.2-RELEASE-p5? I ask because I have some interest in having a tree from which i easily can check out a given patch-version. I don't think we tag the patches, I think they are just committed to releng/8.2 directly. However, you could look at the logs for a given branch (e.g. svn log --stop-on-copy releng/8.2) and figure out the svn revision that would correspond to 8.2-p5. Thanks. That would be my recommendation too. Things aren't always consistent between CVS and SVN because they're two separate systems, but it should be more consistent with 9.0.0+ (or at least it appeared to have been that way because now releng is using SVN primarily for release from what I saw and not CVS, which was the way things were in the past). Thanks, -Garrett Thanks. I had some inkling of this :) Shame on my for not keeping checkouts in a more consistent way. /Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
On 19 dec 2011, at 12:50, Samuel J. Greear s...@evilcode.net wrote: 2011/12/19 Lev Serebryakov l...@freebsd.org: Hello, Samuel. You wrote 15 декабря 2011 г., 16:32:47: Other benchmarks in the Phoronix suite and their representations are similarly flawed, _ALL_ of these results should be ignored and no time should be wasted by any FreeBSD committer further evaluating this garbage. (Yes, I have been down this rabbit hole). Here is one problem: we have choice from three items: (1) Make FreeBSD looks good on benchmarks by fixing FreeBSD (2) Make FreeBSD looks good on benchmarks by fixing Phoronix (communication with them, convincing, that they benchamrks are unfare / meaningless, ets) (3) Lose [potential] userbase. You know, that these benchmarks are bad. I know. But potential (and even some current!) user doesn't. And it seems, that these benchmarks become popular over Internet. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org Here is where you completely derail the train, let me paste again what I said before. ... Take the first test as an example, Blogbench read. This doesn't raise any red flags, right? At least not until you realize that Blogbench isn't a read test, it's a read/write test. So what they have done here is run a read/write test and then thrown away the write results for both platforms and reported only the read results. If you dig down into the actual results, http://openbenchmarking.org/result/1112113-AR-ORACLELIN37 -- you will see two Blogbench numbers, one for read and another for write. These were both taken from the same Blogbench run, so FreeBSD optimizes writes over reads, that's probably a good thing for your data but a bad thing when someone totally misrepresents benchmark results. ... FreeBSD actually does _BETTER_ (subjectively) in this test than the Linux system when you look at what is really going on. FreeBSD is favoring writes, which is _GOOD_. FreeBSD does not need to be fixed, the benchmarks need to be fixed to represent reality rather than throwing half of the results in the trash. To be quite frank, fixing FreeBSD to look good on this benchmark will make it a worse real-world OS. But you guys go ahead and foot-shoot over these ridiculous benchmarks all you want. Sam I seem to remember that before ULE people were fleeing to Linux as the os to run apache on since 4BSD didn't scale all too well. That may have changed over time though. However ULE could perhaps be made aware technologies like turbo-boost, ie with few threads higher performance might be gained by utilizing all virtual cores on a physical core before spreading tasks to too different cores. Just my speculations though :) Regards Andreas Nilsson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org