Re: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" (RPI/arm64)
Hello, I'm on FreeBSD 12.0-STABLE #0 r344261 amd64. I've rebuilt all ports after clang 7 import to 12-STABLE. Now I get with mplayer ld-elf.so.1: /lib/libc.so.7: Undefined symbol "__progname" -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: [CFT] AMD cpu microcode update port sysutils/devcpu-data D13832
How far it's supposed to support legacy CPUs on FreeBSD? x86info Found 2 identical CPUs Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 10 Type: 0 (Original OEM) CPU Model (x86info's best guess): Unknown model. Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo CPU P9700 @ 2.80GHz from README "Features: - SMP support. - Recognition of all Intel/AMD/Centaur/Cyrix/VIA CPUs." -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: Newbie q [repost]
I can't help noticing your signature, so clean installation is always a good start. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: src.conf: setting WITHOUT_DEBUG_FILES has no effect
I saw this few weeks ago with -STABLE. It's only recently that make delete-old delete debug files, so it might started a lot earlier that we think. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: should MINIMAL boot?
The definition of a MINIMAL used is a specific one- it does not contain anything which can be loaded by modules. It could be a starting point to something else, but then, it still contains other things you probably not need. If I get the point, I would probably try to boot MINIMAL on a new hardware, build all modules by default, see which modules get loaded and work from there. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: questions re updating to -CURRENT
> Maybe ... but this is one of those things that (in my > experience) either Just Work or Go Horribly Wrong. That's why I would go at least (latest) -RELEASE to -STABLE before going -STABLE to -CURRENT, if you must. Why trying your luck with big jumps? -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: questions re updating to -CURRENT
I use 11-STABLE with Intel. Some time ago, there was a switch to drm2 here. Iirc I had to add kld_list="i915kms.ko to rc.conf and ensure that drm2/drm2 and drm2/i915kms are built (which should be default). Are you sure you are not using drm2 already? I would check with kldstat. The message in UPDATING is about removing old code from the tree. In any case, RELEASE to STABLE to CURRENT could be a less bumpy ride. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ 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: OptionalObsoleteFiles.inc completeness improvement, try 2
In other words, if a user has some WITHOUT_* set in src.conf, specific files are not installed by installworld, but not removed by remove-old, which I try to fix. Please carry on, I saw quite a few times that this behaviour was assumed by new users, only it is not (yet), to their surprise :) -- View this message in context: http://freebsd.1045724.n5.nabble.com/OptionalObsoleteFiles-inc-completeness-improvement-try-2-tp5983192p5983627.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
Are there any problems with MFC? -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5916170.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
Hello, as of FreeBSD 10.0-STABLE #0 r266216 I still have a mute console in X (which isn't surprising, as there was no MFC) -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5913086.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
By choppy I've also meant it's noticeably slower than syscons, but I think it's already known. The shell was a shells/mksh. I think I may switch to newcons permanently after a merge of bell patch thing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908275.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
newcons beeping in X and no localised font in system console is why I've dropped newcons. Thanks for submission. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907856.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
I think that newcons used somehow my terminus font from X (?) and there were no polish characters. I had/have in rc.conf font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 but it made no difference. It was on 10-STABLE, somewhat early after merge. I may try it again later today. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907951.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
As far as I can tell, the situation is the same on FreeBSD 10.0-STABLE #0 r265185 amd64. newcons uses my X font (terminus), albeit it produces no polish letters (some random glyphs are produced), bell is working but initila terminal offset is wrong- I can overwrite my terminal prompt, X is mute but correctly localized. I've added: device vt device vt_vga #device sc #device vga I have in rc.conf font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 keymap=pl_PL.ISO8859-2 but it makes no difference on newcons iirc from last time. newcons work similarly to xterm those few times I've unsuccessfully tried to switch to UTF-8 (I've distinctly remember prompt offset problem and indexed 3 in place of ł). -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908019.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
Thanks for reply, that helped me somehow. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908076.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: newcons and beeping X
I've used attached script for making usable kbd. I'm aware of another problem though (and can clarify it now). If I use any other character than a basic latin set, my prompt is not preserved. e. g. Kuba@Thinkpad:/usr/home/Kuba $ abcdefghi deleting Kuba@Thinkpad:/usr/home/Kuba $ prompt is right here Kuba@Thinkpad:/usr/home/Kuba $ ąćęłóźż deleting Kuba@Thinkpad:/usr/ho prompt somewhere here Apart form that, newcons works, albeit kind of choppy, do I have any control of it's resolution? Can I make it more seamless with both X and bootloader? (now I have bootloader for a splitsecond, abrupt video reset, newcons spawned with the same resolution but with different font, after starting X and going back to newcons it preserves X resolution) -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908080.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: OpenSSL vs. LibreSSL (OpenBSD)
There is info feed also http://opensslrampage.org/ Too early to say what will come out of it, but has some promising qualities certainly. -- View this message in context: http://freebsd.1045724.n5.nabble.com/OpenSSL-vs-LibreSSL-OpenBSD-tp5906272p5906317.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Leaving the Desktop Market
You got me for a moment :) On a serious note... OpenBSD is reportedly having some success on a desktop- is using -CURRENT on dev's desktop religiously (so I've heard) something related? (e.g. working sound out of the box) I have sound with www/firefox without pulseaudio, albeit firefox 28 segfaults from time to time (see gecko@ if really interested). My desktop experience from few years on -CURRENT/STABLE- with stable/sane configuration that's working it's a bliss, however when something goes awry... Few hours of frustration almost guaranteed. And sometimes it goes that way due to some update unfortunately. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Leaving-the-Desktop-Market-tp5899597p5899727.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Newcons with Nvidia
Hello. I've tried to use vt on 10-STABLE, but had my own problems and abandoned it. From what I've heard, no support for vidcontrol(*) is expected at this point. * https://wiki.freebsd.org/Newcons -- View this message in context: http://freebsd.1045724.n5.nabble.com/Newcons-with-Nvidia-tp5895287p5895400.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
base unzip on 10-STABLE/ 11-HEAD unzip: skipping non-regular entry
Hello, Unfortunately, this is the case with *zips from Dropbox (Download as .zip) directory option. $ /usr/bin/unzip file.zip Archive: file.zip unzip: skipping non-regular entry '' unzip: skipping non-regular entry 'A B C D.pdf' archivers/unzip manages this case though... $ /usr/local/bin/unzip file.zip Archive: file.zip warning: stripped absolute path spec from / mapname: conversion of failed inflating: A B C D.pdf Tested on 10-STABLE, but should be the same on HEAD. -- View this message in context: http://freebsd.1045724.n5.nabble.com/base-unzip-on-10-STABLE-11-HEAD-unzip-skipping-non-regular-entry-tp5887996.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Could you elaborate? Are those ntfs pendrives? ntfs support by ntfs.ko and mount_ntfs was removed in 10 tree. There is fuse kernel module and a port for ntfs in place of it (haven't tested but I'm told it works). Regarding fat (msdosfs) pendrives, I've just mounted one created under 8-CURRENT. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5881032.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Regarding ports, since I've converted to pkng earlier, for most part I've just removed /usr/local/* and hit portmaster -af -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5881033.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: (no subject)
I'm using a T400 with exact same GM45 and besides error: [drm:pid861:intel_lvds_enable] *ERROR* timed out waiting for panel to power off I don't experience errors with FreeBSD 10.0-STABLE #0 r261219 amd64, xorg trunk. -- View this message in context: http://freebsd.1045724.n5.nabble.com/no-subject-tp5881101p5881165.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Fuse is now the only way to mount ntfs. That's all. Regarding Gnome, Avahi or hald, I use none of it so really I have nothing to compare. Speaking of ports, did you really cleanly rebuild all of them? When you are speaking of ports linked against port libconv, I'm suspicious (old libtool?). -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5881337.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
I've made a switch early. What gave me some bumps: - removal of ntfs module - vorbis-tools-1.4.0_6,3 with ogg123 missing (??) - ports built on db42 - malloc.conf - gcc48 entries in libmap.conf (my fault) - subversion-static looks broken a bit, nls problems e.g. $ sudo svn up Password: Service unavailableService unavailableService unavailableUpdating '.': -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5879448.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Unfortunately, I think there is measurable penalty going to BSD licensed tools, same system: http://pastebin.com/BNfhevBa -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5879565.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
I plan to stay some time on 9.2-STABLE (already pkgng and clangfied) waiting maybe till next release from 10-STABLE tree, however 10-STABLE will be where I will be eventually heading, so notes in this spirit are valuable reminders at least, I appreciate it. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5879039.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: PACKAGESITE spam
I was surprised initially, but haven't thought about it much since. -- View this message in context: http://freebsd.1045724.n5.nabble.com/PACKAGESITE-spam-tp5870583p5870666.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Plugins support in pkgng
That's very nice, but I still prefer pkg_cleanup as you don't have to go one by one. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Plugins-support-in-pkgng-tp5739664p5858340.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: rcs
I have similar views. There is abundance of be-everything-for-everybody Linuxes and not enough lean and mean Unix-style kits... -- View this message in context: http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Can't compile lxpanel
Sorry for being so sparse, but I was just talking about general impression from few tries I gave it. /proc wasn't main problem, usually I didn;t have any use for it. Basically it wasn't for me what it aimed to be- a frugal replacement for DE. Half of things didn't work, other half worked erratically. Starting from bare panel/openbox looked more viable. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Can-t-compile-lxpanel-tp5817985p5818453.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Can't compile lxpanel
Last time I've checked lxde was unfortunately not worth hassle. e.g. it depends on /proc -- View this message in context: http://freebsd.1045724.n5.nabble.com/Can-t-compile-lxpanel-tp5817985p5818153.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: [PATCH] USB power usage reporting
Nifty thing, waiting for MFC! -- View this message in context: http://freebsd.1045724.n5.nabble.com/PATCH-USB-power-usage-reporting-tp5786928p5786988.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 7+ days of dogfood
Hi Anton, I recognize you from your usual struggle with ia64 :) Hope your work/environment really have a good justification for keeping them around... I would actually set only -march= because it should set mtune to the same value by default too. Moreover, I suspect mckinley is an alias for itanium2, as it was it's codename... Strangely, current gcc documentation for ia64 is missing references of march and mtune for ia64. http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/IA_002d64-Options.html -- View this message in context: http://freebsd.1045724.n5.nabble.com/7-days-of-dogfood-tp5785452p5786248.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 7+ days of dogfood
Actually there _is_ reference to mtune in doc, so probably only your first choice of mtune itanium2 would work, sorry for the noise. -- View this message in context: http://freebsd.1045724.n5.nabble.com/7-days-of-dogfood-tp5785452p5786250.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: sysctl -a causes kernel trap 12
If you were thinking about the same as me, is there some switch to curb hw.dri.0.info.i915_gem_hws output? -- View this message in context: http://freebsd.1045724.n5.nabble.com/sysctl-a-causes-kernel-trap-12-tp5775646p5786336.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: sysctl -a causes kernel trap 12
or rather hw.dri.0.info.i915_ringbuffer_data -- View this message in context: http://freebsd.1045724.n5.nabble.com/sysctl-a-causes-kernel-trap-12-tp5775646p5786337.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 7+ days of dogfood
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. Is not exactly encouraging. -- View this message in context: http://freebsd.1045724.n5.nabble.com/7-days-of-dogfood-tp5785452p5786468.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 7+ days of dogfood
I've ran 8-CURRENT amd64 desktop which evolved to 8-STABLE and 9-STABLE now, without real deal breakers. All rougher edges I reckon from -CURRENT days gradually went away, but system was very usable then too. -- View this message in context: http://freebsd.1045724.n5.nabble.com/7-days-of-dogfood-tp5785452p5785794.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: CLANG and -fstack-protector
Closest would be http://www.freebsd.org/news/status/report-2008-01-2008-03.html#ProPolice-support-for-FreeBSD but port part it was not committed. -- View this message in context: http://freebsd.1045724.n5.nabble.com/CLANG-and-fstack-protector-tp5784739p5784992.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: LLVM 3.2: official stable port is still LLVM 3.1. Basesystem missing important LLVM pieces!
While it is only remotely related, it looks like MFC of 3.2 for STABLE should be around the corner? -- View this message in context: http://freebsd.1045724.n5.nabble.com/LLVM-3-2-official-stable-port-is-still-LLVM-3-1-Basesystem-missing-important-LLVM-pieces-tp5775141p5775300.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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] Imported llvm/clang 3.2 RC2 into head
It looks clang/libreoffice has been broken a bit earlier (before import). Currently building libreoffice on -STABLE with gcc47. -- View this message in context: http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5771689.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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] Imported llvm/clang 3.2 RC2 into head
To clear up confusion, I'm very well aware that that 3.2 is not yet in -STABLE at this time, that's why I'm reporting that it could be not import that broke LibreOffice. Currently, after icu bump people on -STABLE were recompiling libreoffice, and it turned out, this is no longer possible with base clang. (bapt@ has already reproduced this error, see -office for details, I have some local problems with searching mailing list archive now, sorry.) With (WITH_GCC) gcc47 I've successfully built and I'm running libreoffice after icu bump. -- View this message in context: http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5771721.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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] Imported llvm/clang 3.2 RC2 into head
I'm on -STABLE, I was referring to editors/libreoffice and I've just used already available option in Makefile, just commenting out testcase. Accidentally, I'm forcing gcc47 for ports usually, but that's different story, handled here by ports.conf inclusion in make.conf. I've heard there is some new knob (USE_GCC=4.6+) but haven't used it. I suppose you could force it globally but weight your choices as it could be not what you really want. -- View this message in context: http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5771725.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Request for merge into 9.x
Have you tested 9-STABLE? I see there some 2860 bits- http://svnweb.freebsd.org/base/stable/9/sys/dev/ral/ There are some updates in head, they should go to -STABLE after a usual while (TM). FYI, current wifi development and discussion takes place in freebsd-wireless too. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Request-for-merge-into-9-x-tp5768802p5768897.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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] Imported llvm/clang 3.2 RC2 into head
If there is indeed some problem with libreoffice, I will report back after MFC :) -- View this message in context: http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5766507.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: UTF-8 console
True, but info about state of project is correct, yes? -- View this message in context: http://freebsd.1045724.n5.nabble.com/UTF-8-console-tp5761405p5761662.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: cvsup/csup servers stale?
Good luck with employing full discombobulation! I think this is the main requirement for _cloud computing_. -- View this message in context: http://freebsd.1045724.n5.nabble.com/cvsup-csup-servers-stale-tp5761290p5761389.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: UTF-8 console
http://wiki.freebsd.org/SysconsUnicodeProject -- View this message in context: http://freebsd.1045724.n5.nabble.com/UTF-8-console-tp5761405p5761407.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Simple check if current is broken
What about cases when something is broken, but not for everybody? If only GENERIC build, how does that differ from existing tinderboxing? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Simple-check-if-current-is-broken-tp5760481p5760700.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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 DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1
Thanks for replies. * Finally, default values for many things on 64-bit machines have been adjusted upward significantly to make proper use of available resources Well that one should be fast to test, if it really makes so much difference. * Scheduler rewrite They threw out old scheduler and have instant gains? That's too good to be true, seeing as still some loathe ULE in FreeBSD after all this time. etc. I would like to see some independent benchmarks and not only Postgres too. If they are really onto something, that's good and I'm happy for them, as they were supposedly performance oriented projected, but it haven't show up in past benches. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-new-DragonFly-3-2-scheduler-and-PostgreSQL-comparision-with-FreeBSD-9-1-RC1-tp5751589p5751862.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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 DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1
I do not loathe ULE, but I also do not use ULE. Maybe my wording wasn't exactly suitable, but that was the point I was trying to make. ULE is default for quite some time (and boasted impressive benchmarks upon introduction too), yet in reality 4BSD is far from being superseded for many. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-new-DragonFly-3-2-scheduler-and-PostgreSQL-comparision-with-FreeBSD-9-1-RC1-tp5751589p5751929.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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 DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1
I'm not at all up to date with DragonFly, so does anybody know what did they change so spectacularly between 3.0/3.2? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-new-DragonFly-3-2-scheduler-and-PostgreSQL-comparision-with-FreeBSD-9-1-RC1-tp5751589p5751733.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: FreeBSD 10.0-CURRENT: CLANG and port/clang weirdness!
The LibreOffice package doesn't compile with the system's CLANG, so it
is installed whenever LibreOffice is installed.
FWIW, it's using base clang and it does compile if ${OSVERSION} = 900014
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-10-0-CURRENT-CLANG-and-port-clang-weirdness-tp5741455p5741777.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
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: UFS journal error on 10.0-CURRENT
That's normally the case, yes, but not here. Are you saying that if using journal, inconsistencies in 'clean' fs are expected? Basically I'm saying that apparently here journal does nothing after enabling it. Usually after really hard power dip, I need to manually fsck as all symptoms of unclean fs are apparent. Maybe disabling; fsck; removing journal file; and reenabling it could fix it too? Yes, I'm afraid of it... -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739669.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: UFS journal error on 10.0-CURRENT
If I were you, I would try regular fsck, as here (9-STABLE) using journal has left me with fs inconsistencies. -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739274.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: UFS journal error on 10.0-CURRENT
Yes, if I would answer 'yes' to using journal, there would be unexpected free inodes (?) or something like that in syslog and inconsistencies if full fsck would be performed. Basically if I have answered 'yes' to using journal, fs would always be marked 'clean' regardless of state. -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739408.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD ?
Sometimes it would be enough just to test if the port compiles before committing it (I'm talking about libreoffice here which is broken) Yeah right... Like updating libreoffice without testing would be actually possible at all... Are you familiar with http://redports.org/ ? Just a example what is used for WIP. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714183p5717150.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD ?
I just have successfully (*) build LibreOffice by just typing # make build in editors/libreoffice... * Without any manually removed hiccups. Dependencies build with clang fine too, as graphics/vigra is updated. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714183p5716905.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD ?
The same one I had problems earlier. I heard that you shouldn't have boost* ports installed prior, but when I had problems I didn't. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714183p5716943.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD?
I'm not (only) pointing finger and whining, but maybe PC-BSD could relegate someone permanently to help you with libreoffice, if indeed desktop is so important to them? I'm not sure how exactly PC-BSD and iXsystems are related (I know that iXystems provided you with build system at some point), but from my point of view *office port should be at least as important to PC-BSD as KDE infrastructure. Apart from that other idea, that I brought up on -office and nobody responded (libreoffice volunteer fund). -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714951.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD?
I saw LibreOffice as cleaning-up *office effort, maybe my hopes were displaced, maybe not. I personally do not care if it will be LibreOffice or Apache OpenOffice as long as it's working and not pulling in KDE4/QT4/GTK (most people/linux distros are abandoning OO for Libre though it appears), but if human resources are scarce, shouldn't we (who?) decide that one big editor (tm) is plenty? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714969.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD?
*misplaced :) -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714978.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD?
just the base system is the only part that needs to be unified, everything else can be installed from source. You really don't know what you are talking about, do you? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714654.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Why Are You NOT Using FreeBSD?
Hmm... Speaking of libreoffice ERROR: error 65280 occurred while making /usr/obj/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj ? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714383.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: OptionalObsoleteFiles.inc completeness
I'm pro improving completeness, as most people are really surprised when after setting WITHOUT* they are left with old cruft from first install, what's more important- it's getting left as is with all possible (security) bugs. Just be careful, as after recent expansion it looked here like setting WITHOUT_GCC= was breaking gcc47 from ports also, but couldn't really reproduce it reliably. -- View this message in context: http://freebsd.1045724.n5.nabble.com/OptionalObsoleteFiles-inc-completeness-tp5712560p5712976.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: As of r233419, head should compile cleanly with clang
Nice! Is 9-STABLE also planned to be cleaned up? -- View this message in context: http://freebsd.1045724.n5.nabble.com/HEADS-UP-As-of-r233419-head-should-compile-cleanly-with-clang-tp5591742p5592266.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: bsdinstall kbdmap
As I said before, it's not related, because your problem is X/ hal related, and I was speaking of syscons. Can you set language in X by x11/setxkbmap? You are using hald, and xorg.conf is probably ignored. If you insist on keeping hal, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html should give you some pointers on setting keyboard language. I don't know why you previously had localized keyboard in X. Was that first reboot of system? -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5122813.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
bsdinstall kbdmap
Is it working correctly? e.g. Choosing Polish ISO-8859-2 results in just keymap=pl_PL.ISO8859-2.kbd added to rc.conf, while to have fully working polish fonts you need font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 keymap=pl_PL.ISO8859-2 -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5119535.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: bsdinstall kbdmap
Is vidfont invoked during installation at all? -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5119548.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: bsdinstall kbdmap
That's not related at all. For X you need something like Option XkbLayout es in xorg.conf, and I complained about syscons settings after installation. -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5120710.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: bsdinstall kbdmap
Or you could use x11/setxkbmap each time you login. -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5120743.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 9RC2 amd64 Can't work out which disk we are booting from
But I have not found what it was, and switched to build i386 images only yet. Indeed, only amd64 has this problem. -- View this message in context: http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5011412.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
9RC2 amd64 Can't work out which disk we are booting from
Hello. I'm almost positive it's probably my fault, but anyway, I have installed FreeBSD on laptop from source (9-STABLE), on the same machine I can't boot RC2 usb.img due to Can't work out which disk we are booting.. and after installing RC2 on usbstick and trying to boot it, same problem occurs. (well, surprise). I have used default layout on usbdrive. Any ideas? ls show files structure, but boot /boot/kernel doesn't work. On the side note, Verbatim STORE N GO 2.66 8GB gave me nothing but problems, not recommended. (it's actually Blaze Drive but it's recognised as store 'n go) best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5006547.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 9RC2 amd64 Can't work out which disk we are booting from
...and booting dvd rc2 iso works. I actually installed from it to the usbdisk, just booting usb is broken. On the side note, bsdinstall is OK, missing maybe space/enter mapped action reminder, and certainly back button. -- View this message in context: http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5007183.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
WITHOUT_GCC for build target / system without base gcc (9RC1)
Hello. When one can expect being able to have system without base gcc installed? Since I enabled clang, and I'm using gcc46 for ports, having base gcc is largely pointless for me, but couldn't build system with clang only, because of: === usr.bin/xlint/llib (all) lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix llib-lposix: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory *** Error code 1 best regards, - Jakub Lach PS. If I'm doing something retarded, feel free to point out. I'm just feeling that 3 compilers on one system is a bit much, and most ports are developed with newest gcc in mind, while for FreeBSD clang is obviously way to go. FWIW, right now I would need base gcc only for compiling libreoffice, and I hope it will change sometime in future. -- View this message in context: http://freebsd.1045724.n5.nabble.com/WITHOUT-GCC-for-build-target-system-without-base-gcc-9RC1-tp4951986p4951986.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: WITHOUT_GCC for build target / system without base gcc (9RC1)
Hi, thanks for reply. But seriously, building ports which have not explicitly been marked as being gcc 4.5 or 4.6 compatible is taking a chance. It might work, or break in various interesting ways. Yes, I know. I'm just using small subset of ports as well. Will probably try clang for ports too, when feeling suitably adventurous :) While totally unscientific, clang 3.0 (-O2 -march=native) surprised me with getting more MIPS from p7zip than gcc46. Clang built kernel is smaller here too. Libreoffice is not problem per se, considering it's nature, I'm happy it's working at all for me. best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/WITHOUT-GCC-for-build-target-system-without-base-gcc-9RC1-tp4951986p4952372.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
It would be nice, If somebody would write updated manual documenting whole process of setting up hplip. In past, I could only get it to the point of printing test pages (sigh...) Before release preferably? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-USB-HPLIP-what-s-the-new-right-way-to-manage-hplip-usb-plugged-printers-running-Free9-tp4948737p4949780.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Or just extend hplip section in handbook. http://www.freebsd.org/doc/handbook/printing-lpd-alternatives.html It could be roughly based upon this: http://freebsd.kde.org/howtos/hplip.php -- View this message in context: http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-USB-HPLIP-what-s-the-new-right-way-to-manage-hplip-usb-plugged-printers-running-Free9-tp4948737p4949796.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: 9-stable: My AR5B95 not reconized anymore.
20110331: ath(4) has been split into bus- and device- modules. if_ath contains the HAL, the TX rate control and the network device code. if_ath_pci contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb contains the AHB glue. Users need to load both if_ath_pci and if_ath in order to use ath on everything else. TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only need to load if_ath and if_ath_pci for ath(4) operation. -- View this message in context: http://freebsd.1045724.n5.nabble.com/9-stable-My-AR5B95-not-reconized-anymore-tp4838772p4839491.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: bsdgrep: does anyone see this?
FreeBSD 9.0-BETA2 #0 r225641 amd64 $ echo |grep -q '^'; echo $? 0 $ echo |grep -qv '^'; echo $? 1 $ echo |bsdgrep -q '^'; echo $? 1 $ echo |bsdgrep -qv '^'; echo $? 0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/bsdgrep-does-anyone-see-this-tp4815133p4815764.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: kldload uhci, system grinds to halt
After filling sticks with zeros, and writing data again on them, cannot replicate. Maybe usb sticks were to blame. One was brand new, possibly loaded with some helpful software, and other contained broken OpenBSD install. Thanks for attention. best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/kldload-uhci-system-grinds-to-halt-tp4723962p4727173.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
kldload uhci, system grinds to halt
Hello. Anybody is experiencing something similar? There was no such problem on 8-STABLE, this is now FreeBSD 9.0-BETA1 #0 r225063 amd64, kernel is semi-heavily stripped (usb is not compiled in). I could post system details, but for now I think it could be unnecessary distraction. When this system was 8-STABLE, this configuration worked fine. regards, -Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/kldload-uhci-system-grinds-to-halt-tp4723962p4723962.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: kldload uhci, system grinds to halt
Hi, thanks for reply. ahci and pci is compiled in. I doubt I will be able to get vmstat, single xterm bell is continuous sound. I usually brought up usb by something like: # kldload usb umass uhci ehci and was only able to isolate cause to uhci module. Speaking of hardware, it's common Intel 82801I (ICH9 Family). As I think of it, maybe I don't need uhci after all, but I suspected I used it with usb/ums mouse. regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/kldload-uhci-system-grinds-to-halt-tp4723962p4724430.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
libdialog strangeness after source upgrade to head/9.0BETA1
Hello. I svn-switched my 8-STABLE to head, and upgrade went reasonable well. (9-STABLE will be my preferred/final destination, but test boots with BETA1 img stick looked problem free enough to start messing early.) While recreating ports, only real glitch was that apparently pkg_cleanup is not yet 9 ready, but I commented BROKEN line and it seemed to work normally anyway. After all ports were recreated, I booted to X, and tried to run pkg_cleanup again, only this time pressing return ended dialog, so I couldn't check/ uncheck any boxes. At first I thought this is why it's marked BROKEN on 9, but apparently make config has the same symptoms. that is, - pressing return ends dialog Any ideas what I have screwed up (starting from scratch not counting) ? best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/libdialog-strangeness-after-source-upgrade-to-head-9-0BETA1-tp4677182p4677182.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: FreeBSD Compiler Benchmark: gcc-base vs. gcc-ports vs. clang
Vinícius Zavam wrote: i'm still curious about things like CPUTYPE= and -march= configured as native, gentlemen. is it the golden egg to use with our system or not? why natives aren't in the benchs? /me feels confused. -- Vinícius Zavam profiles.google.com/egypcio Apparently -march=native would equal -march=core2 with 65nm generation Core2s, this is not the case with Penryns.. But there are none in the test? However, I agree that testing with -march=native would be simpler and more straightforward. regards, - Jakub Lach -- View this message in context: http://old.nabble.com/FreeBSD-Compiler-Benchmark%3A-gcc-base-vs.-gcc-ports-vs.-clang-tp31119986p31138978.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: FreeBSD Compiler Benchmark: gcc-base vs. gcc-ports vs. clang
Thanks for starting this interesting comparison. Maybe using -march=native would be simpler and more meaningful? I'm thinking about penryns especially. regards, - Jakub Lach -- View this message in context: http://old.nabble.com/FreeBSD-Compiler-Benchmark%3A-gcc-base-vs.-gcc-ports-vs.-clang-tp31119986p31131269.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: FreeBSD Compiler Benchmark: gcc-base vs. gcc-ports vs. clang
Core i7 based procesors run slower with -march=core2 (new option) on the system compiler than with -march=nocona Sorry for double mail, isn't CPUTYPE=core2 just alias to nocona with base compiler? -- View this message in context: http://old.nabble.com/FreeBSD-Compiler-Benchmark%3A-gcc-base-vs.-gcc-ports-vs.-clang-tp31119986p31131280.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Sense fetching [Was: cdrtools /devel ...]
In spirit of Brandon Gooch's mail (although I have lurked whole time) , I'm currently on FreeBSD 8.1-STABLE #0 r215179 amd64, and I'm also willing to test any relevant patches, preferably after consensus is reached. regards, - Jakub Lach -- View this message in context: http://old.nabble.com/Sense-fetching--Was%3A-cdrtools--devel-...--tp30144086p30205790.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Sense fetching [Was: cdrtools /devel ...]
Hello. scgcheck after applying all patches: Ready to start test for second SCSI open? Enter CR to continue: First SCSI open OK - device usable ** Checking for second SCSI open. Second SCSI open for same device succeeded, 1 additional file descriptor(s) used. Second SCSI open is usable Closing second SCSI. Checking first SCSI. First SCSI open is still usable -- Second SCSI open test PASSED. First SCSI open is still usable Ready to start test for succeeded command? Enter CR to continue: ** Checking for succeeded SCSI command. Executing 'inquiry' command on Bus 1 Target 0, Lun 0 timeout 40s CDB: 12 00 00 00 24 00 cmd finished after 0.002s timeout 40s Inquiry Data : 05 80 00 32 5B 00 00 00 48 4C 2D 44 54 2D 53 54 44 56 44 52 41 4D 20 47 53 41 2D 55 32 30 4E 20 48 58 31 31 -- SCSI succeeded command test PASSED Ready to start test for failing command? Enter CR to continue: ** Testing for failed SCSI command. scgcheck: Input/output error. inquiry: scsi sendcmd: retryable error CDB: 12 00 00 FF 24 00 status: 0x0 (GOOD STATUS) resid: 36 cmd finished after 0.038s timeout 40s -- SCSI Transport return != SCG_NO_ERROR (1) -- SCSI status byte set to 0 (0x0) -- SCSI failed command test FAILED Ready to start test for sense data count? Enter CR to continue: ** Testing for SCSI sense data count. ** Testing if at least CCS_SENSE_LEN (18) is supported... Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0x00: expected: 18 reported: 18 max found: 0 Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0xFF: expected: 18 reported: 18 max found: 18 -- Wanted 18 sense bytes, got it. ** Testing for 32 bytes of sense data... Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0x00: expected: 32 reported: 32 max found: 0 Sense Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- Method 0xFF: expected: 32 reported: 32 max found: 32 -- Wanted 32 sense bytes, got it. -- Got a maximum of 32 sense bytes -- SCSI sense count test PASSED -- SCSI status byte test NOT YET READY Ready to start test for working DMA residual count? Enter CR to continue: ** Testing for working DMA residual count. ** Testing for working DMA residual count == 0. CDB cnt: 36 DMA cnt: 36 got really: 36 (System says: RDMA cnt: 36 resid 0) CDB cnt: 36 DMA cnt: 36 got really: 36 (System says: RDMA cnt: 36 resid 0) -- Wanted 36 bytes, got it. -- SCSI DMA residual count == 0 test PASSED Ready to start test for working DMA residual count == DMA count? Enter CR to continue: resid: 36 CDB cnt: 0 DMA cnt: 36 got really: 0 (System says: RDMA cnt: 0 resid 36) resid: 36 CDB cnt: 0 DMA cnt: 36 got really: 0 (System says: RDMA cnt: 0 resid 36) -- Wanted 0 bytes, got it. -- SCSI DMA residual count == DMA count test PASSED Ready to start test for working DMA residual count == 1? Enter CR to continue: ** Testing for working DMA residual count == 1. resid: 1 CDB cnt: 36 DMA cnt: 37 got really: 36 (System says: RDMA cnt: 36 resid 1) resid: 1 CDB cnt: 36 DMA cnt: 37 got really: 36 (System says: RDMA cnt: 36 resid 1) -- Wanted 36 bytes, got it. -- SCSI DMA residual count == 1 test PASSED Ready to start test for working DMA overrun detection? Enter CR to continue: ** Testing for working DMA overrun detection. DMA overrun, resid: -1 CDB cnt: 36 DMA cnt: 35 got really: 36 (System says: RDMA cnt: 36 resid -1) DMA overrun, resid: -1 CDB cnt: 36 DMA cnt: 35 got really: 36 (System says: RDMA cnt: 36 resid -1) -- Wanted 36 bytes, got it - DMA overrun not blocked. -- Wanted 35 bytes, got (36) -- Libscg says 35 bytes but got (36) -- SCSI DMA overrun test FAILED -- SCSI transport code test NOT YET READY What is more important, writing CD-Rs and DVD-Rs works. Thanks for help, - Jakub Lach -- View this message in context: http://old.nabble.com/Sense-fetching--Was%3A-cdrtools--devel-...--tp30144086p30206153.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: regarding pciids
Alexander Best-4 wrote: any thoughts on using http://pciids.sourceforge.net/ for pciids instead of the Hart and Boemler lists. the SF site seems to be updated more regularly and would get rid of the need to decide for each entry, whether to take the Hart or Boemler one. right now tools/tools/pciid/mk_pci_vendors.pl favours long descriptions over short ones which means that something like: 'Intel(R) ICH9 Family SMBus Controller (8086)' will get discarded in favor of 'Intel(R) ICH9 Family SMBus Controller working fine with http://download.cnet.com/Chipset-Driver-Inte (8086)' +1, since I'm the one[1] with (well, not the only one, ICH9 should be quite popular) http://download.cnet.com/Chipset-Driver-Inte; device. best regards, - Jakub Lach [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=748866+0+archive/2010/freebsd-stable/20100912.freebsd-stable -- View this message in context: http://old.nabble.com/regarding-pciids-tp29704378p29707595.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
wpa_supplicant update? CTRL-EVENT-SCAN-RESULTS
Hello. Is update of wpa_supplicant planned? Current version in STABLE as well as CURRENT (v0.6.8) is suffering from CTRL-EVENT-SCAN-RESULTS log spam. If it's the same problem, looks like it's fixed in v0.6.10 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539915 best regards, Jakub Lach -- View this message in context: http://old.nabble.com/wpa_supplicant-update--CTRL-EVENT-SCAN-RESULTS-tp28870665p28870665.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: wpa_supplicant update? CTRL-EVENT-SCAN-RESULTS
Rui Paulo-3 wrote: On 13 Jun 2010, at 04:23, Jakub Lach wrote: Hello. Is update of wpa_supplicant planned? I'll likely work on this soon. -- Rui Paulo That's splendid, thanks for fast reply. Is MFC to 8 feasible? regards, - Jakub Lach -- View this message in context: http://old.nabble.com/wpa_supplicant-update--CTRL-EVENT-SCAN-RESULTS-tp28870665p28873483.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: wpa_supplicant update? CTRL-EVENT-SCAN-RESULTS
Rui Paulo-3 wrote: On 13 Jun 2010, at 12:40, Jakub Lach wrote: Rui Paulo-3 wrote: On 13 Jun 2010, at 04:23, Jakub Lach wrote: Hello. Is update of wpa_supplicant planned? I'll likely work on this soon. -- Rui Paulo That's splendid, thanks for fast reply. Is MFC to 8 feasible? Possibly, but it won't make it in time for 8.1. That's understandable, I track STABLE anyway (since 8 became STABLE as a matter of fact). regards, - Jakub Lach -- View this message in context: http://old.nabble.com/wpa_supplicant-update--CTRL-EVENT-SCAN-RESULTS-tp28870665p28873587.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
