Re: FreeBSD 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how?
On 10/10/11 03:18, Manfred Antar wrote: At 11:57 AM 10/9/2011, Conrad J. Sabatier wrote: On Sun, 09 Oct 2011 08:48:46 -0700 Manfred Antarn...@pozo.com wrote: Did you rebuild ports/devel/binutils after change to 10.0 current. I was having same problem with gcc45 , then i rebuilt binutils with uname_r 9.0-Current and it went away. Actually, binutils built just fine for me just now without setting UNAME_r under current. -- Conrad J. Sabatier conr...@cox.net Built fine for me too. But when I tried to compile gcc45 no go recompiled binutils with uname_r 9.0-CURRENT, And gcc45 built fine. so my assumption was that something gets messed up with the binutils and gcc45 when built with current. Managed it. Somehow I maneged to build the binutils without setting the UNAME_r kludge. I confused myself and the system. Thanks. I think, watching this is a very good opportunity to learn by doing, how things work. Oliver ___ 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: System headers with clang?
2011/10/9 Larry Rosenman l...@lerctr.org: I had gotten a PR about sysutils/lsof not compiling with clang. That could be mine, ports/160544 ? I had Vic Abell check it out, and the problem is NOT with lsof per se, but with the system headers. Is there a project afoot to update the system headers to make them clang compilable? So I get the same errors as you for 9.0 (also with BETA3) on amd64, but for 9.0 on i386 from 2011-08-19 it builds fine: http://rene-ladan.nl:8080/tb/logs/9-FreeBSD-clang/lsof-4.85D_1,5.log René ___ 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: USB storage corruption/panic when doing file IO and unplugging (another, non-storage) device
On Friday 07 October 2011 08:32:40 Adrian Chadd wrote: On 7 October 2011 13:55, Garrett Cooper yaneg...@gmail.com wrote: Has anyone seen this before? This is _not_ plug/unplug the active storage device, or another storage device. This is when doing IO on a storage device (whether the root device or a media device) whilst plug/unplug a non-storage USB device (wifi chipsets w/ no driver.) Yeah. Ran into it earlier on in the 9.x cycle with twa unplugging a USB keyboard when I was rebooting a machine; the panic was fixed in twa, not ukbd. I suppose my question is: does this only happen with USB, or is firewire affected, and why aren't the devices being properly masked against interrupts [in the same queue??] [by newbus???]? Let's wait for hps to get back to us. This seems like something he can replicate very quickly. Hi, Could you send me the backtrace of the panic. USB is a broadcast system and connecting and disconnecting devices might cause interference. Make sure your driver is self powered. I have not seen this issue before. I'm using a USB disk every day. --HPS ___ 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: USB storage corruption/panic when doing file IO and unplugging (another, non-storage) device
ok, I'll do some more detailed testing in the next few days. Adrian ___ 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: RFC: Project geom-events
Lev Serebryakov l...@freebsd.org wrote: GPT must have backup copy in last sector by standard ... In that case, shouldn't it refuse to install on any provider that is not in fact a disk, so as not to create configurations that cannot work properly? MBR doesn;t have any additional metadata. How adding one will help it? It would add robustness, for cases like the one that started this thread. If MBR put a GEOM metadata block at the end of its provider, it would fix the tasting race when an MBR is installed on a glabelled (or gmirrored) drive. ___ 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: RFC: Project geom-events
Lev Serebryakov l...@freebsd.org wrote: GPT _must_ be placed twice -- at first and last sectors (really, more than one sectors). By standard. Secondary copy must be at end of disk. Period. Then, by standard GPT cannot coexist with GLABEL. Such setup should be disallowed, or at least big nasty message that you have just shoot yourself in the leg should be output. (period) Ok, maybe adding check to geom_part, that it is used on rank-1 provider (whole disk) is not so bad idea. But it then raise question how to install FreeBSD on software mirror, what is useful. To install FreeBSD on a gmirrored disk, use MBR (or dangerously dedicated BSD label) instead of GPT. (This is one reason why BSD label and MBR should not be considered obsolete.) If you want to use gmirror and *have* to use GPT, e.g. if you have a (hypothetical) BIOS which will not boot from MBR, mirror the individual partitions instead of the whole disk. Granted that is more trouble, both to set up initially and to replace a failed drive. ___ 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: RFC: Project geom-events
John j...@freebsd.org wrote: ... gpart should show warning message if user is trying to put GPT on non real disk devices. ... This also seem to prevent something useful like: # camcontrol inquiry da0 pass2: HP EH0146FAWJB HPDD Fixed Direct Access SCSI-5 device pass2: Serial Number 3TB1BKGX9036W9EN pass2: 600.000MB/s transfers, Command Queueing Enabled # camcontrol inquiry da25 pass27: HP EH0146FAWJB HPDD Fixed Direct Access SCSI-5 device pass27: Serial Number 3TB1BKGX9036W9EN pass27: 600.000MB/s transfers, Command Queueing Enabled # gmultipath label ZFS0 da0 da25 # gpart create -s gpt $device # gpart add -s 128 -t freebsd-boot $device # Create 64K boot partition # gpart add -s 4m -t freebsd-ufs -l mb$dev $device # small partition # gpart add-t freebsd-zfs -l $dev $device # Remaining space for zfs It seems like protecting your partitions with multiple paths would be a good thing. I've been experimenting with this and end up with corrupt partitions. The setting of $device is not shown, but I suppose it is the name of the multipath provider. I'm not familiar with gmultipath, but it would not surprise me if (like most GEOMs) it were putting its metadata in the last block(s) of its providers and therefore encountering the same issues as gmirror and glabel. In that case, the best fix may be to define the multipathing per-partition instead of per-device (if that is possible), or to use MBR/BSD instead of GPT for partitioning. ___ 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: ports on 10.0-CURRENT: r226027 is incorrect fix
On Sat, 8 Oct 2011 18:35:13 +0100 Chris Rees utis...@gmail.com mentioned: Last I heard, portmgr explicitly disapproved of this fix-- have I missed something??? Erwin specifically said not to do it. Since when can anyone just commit stuff to bsd.port.mk, regardless of its location? This is a bad solution, please revert it or I will when I get back. We're going to end up being asked to support it on ports@ otherwise. You certianly missed something, including the rationale behind the portmgr@ descision of not committing to the ports tree (!) bsd.port.mk. Go find some useful work to do like deleting old ports or whatever. You might want to consider deleting all mine ports, as I'm not going to support them anymore (after you backed out this fix without approval I don't have a working ports tree anymore on any of my 3 workstations). -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ 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: ports on 10.0-CURRENT: r226027 is incorrect fix
On 10/10/11 21:04, Stanislav Sedov wrote: On Sat, 8 Oct 2011 18:35:13 +0100 Chris Rees utis...@gmail.com mentioned: Last I heard, portmgr explicitly disapproved of this fix-- have I missed something??? Erwin specifically said not to do it. Since when can anyone just commit stuff to bsd.port.mk, regardless of its location? This is a bad solution, please revert it or I will when I get back. We're going to end up being asked to support it on ports@ otherwise. You certianly missed something, including the rationale behind the portmgr@ descision of not committing to the ports tree (!) bsd.port.mk. Go find some useful work to do like deleting old ports or whatever. You might want to consider deleting all mine ports, as I'm not going to support them anymore (after you backed out this fix without approval I don't have a working ports tree anymore on any of my 3 workstations). Hello? Is there need for this barbarian rude tone? Regards, oh ___ 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
Patch for ports on 10-current
Until the pointy-haireds come up with a better solution, here is a patch that incorporates work that others have done into a manageable form so that those interested in working with ports on 10-current have some tools to work with: http://dougbarton.us/bam.patch You need to do the equivalent of 'portmaster -o devel/libtool-fixed libtool' to get the fixed version. In addition to the OSVERSION check I added knobs to selectively disable the 2 parts of the fix to aid in development and testing. Also, make sure that you have the latest /usr/share/mk/bsd.port.mk with the similar fix backed out. Hopefully there will be a better fix soon, but until there is, I hope that this helps. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: flash for 9-beta3
On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote: On Sat, October 8, 2011 20:03, Doug Barton wrote: On 10/08/2011 14:53, Warren Block wrote: nspluginwrapper needs to be run as the end user. The pkg-message tells them to do that. ops, haven't seen it though. all the ports cleaned by the clean part of the command got on my way :( I did, no good though. FF still says no plugins. is it FF 7 compatible ? matheus thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 for ports on 10-current
Doug Barton do...@freebsd.org writes:
Until the pointy-haireds come up with a better solution, here is a patch
that incorporates work that others have done into a manageable form so
that those interested in working with ports on 10-current have some
tools to work with:
http://dougbarton.us/bam.patch
[...]
+.if ${OSVERSION} = 100 !defined(NO_LIBTOOL_FIXED)
The issue does not lie in OSVERSION but in OSREL. So, why not be smarter
and detect if a user has UNAME_r workaround in environment by
.if ${OSREL:R} = 10 !defined(NO_FOO_FIX)
___
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 for ports on 10-current
On 10/10/2011 15:00, Nali Toja wrote:
Doug Barton do...@freebsd.org writes:
Until the pointy-haireds come up with a better solution, here is a patch
that incorporates work that others have done into a manageable form so
that those interested in working with ports on 10-current have some
tools to work with:
http://dougbarton.us/bam.patch
[...]
+.if ${OSVERSION} = 100 !defined(NO_LIBTOOL_FIXED)
The issue does not lie in OSVERSION but in OSREL. So, why not be smarter
and detect if a user has UNAME_r workaround in environment
Because by doing it the way I did it the user can apply both fixes, or
either fix individually by using the right combination of knobs.
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.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: cvs commit: ports/security/cyrus-sasl2 Makefile ports/security/cyrus-sasl2/files patch-plugins::gssapi.c
On 10/09/2011 09:29, Hajimu UMEMOTO wrote: Hi, On Fri, 07 Oct 2011 16:48:52 -0700 Doug Barton do...@freebsd.org said: dougb In case anyone wants to take this on, this port fails to install on 10.0 dougb because it uses its own version of libtool. I took a quick look but dougb there wasn't a solution obvious enough for me. :) I didn't have 10-current box, yet. So, I've just upgraded my 9-current box to today's current, and tried to rebuild cyrus-sasl2 port on it. However, I couldn't reproduce the problem. It built just fine, here. Any thought? So I was able to confirm that the patch which had previously been in /usr/share/mk/bsd.port.mk was what caused it to fail. Hopefully that information will be helpful to those working on improving the generic fix. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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 for ports on 10-current
On Mon, Oct 10, 2011 at 1:59 PM, Doug Barton do...@freebsd.org wrote: Until the pointy-haireds come up with a better solution, here is a patch that incorporates work that others have done into a manageable form so that those interested in working with ports on 10-current have some tools to work with: http://dougbarton.us/bam.patch You need to do the equivalent of 'portmaster -o devel/libtool-fixed libtool' to get the fixed version. In addition to the OSVERSION check I added knobs to selectively disable the 2 parts of the fix to aid in development and testing. Also, make sure that you have the latest /usr/share/mk/bsd.port.mk with the similar fix backed out. Hopefully there will be a better fix soon, but until there is, I hope that this helps. Thanks! This is better than nothing at very least. (By the way Python seems to be using a different way of getting FreeBSD version and for some reason that causes problem for certain applications) Cheers, -- Xin LI delp...@delphij.net https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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: flash for 9-beta3
On 10/10/11 15:30, Nenhum_de_Nos wrote: On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote: On Sat, October 8, 2011 20:03, Doug Barton wrote: On 10/08/2011 14:53, Warren Block wrote: nspluginwrapper needs to be run as the end user. The pkg-message tells them to do that. ops, haven't seen it though. all the ports cleaned by the clean part of the command got on my way :( I did, no good though. FF still says no plugins. is it FF 7 compatible ? matheus I ran into this recently. Though I have not figured out a more correct fix.. add this to your .bashrc: export MOZ_PLUGIN_PATH=/usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox or.. .cshrc setenv MOZ_PLUGIN_PATH /usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox and flash will work with the newer firefox. -Phil. ___ 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: ports on 10.0-CURRENT: r226027 is incorrect fix
On Mon, Oct 10, 2011 at 1:33 PM, Hartmann, O. ohart...@zedat.fu-berlin.de wrote: On 10/10/11 21:04, Stanislav Sedov wrote: On Sat, 8 Oct 2011 18:35:13 +0100 Chris Rees utis...@gmail.com mentioned: Last I heard, portmgr explicitly disapproved of this fix-- have I missed something??? Erwin specifically said not to do it. Since when can anyone just commit stuff to bsd.port.mk, regardless of its location? This is a bad solution, please revert it or I will when I get back. We're going to end up being asked to support it on ports@ otherwise. You certianly missed something, including the rationale behind the portmgr@ descision of not committing to the ports tree (!) bsd.port.mk. Go find some useful work to do like deleting old ports or whatever. You might want to consider deleting all mine ports, as I'm not going to support them anymore (after you backed out this fix without approval I don't have a working ports tree anymore on any of my 3 workstations). Hello? Is there need for this barbarian rude tone? Can everyone calm down a little bit, step back and think twice before making reactions? Stop it, as this hurts the project as a family. Cheers, -- Xin LI delp...@delphij.net https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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: ports on 10.0-CURRENT: r226027 is incorrect fix
On Mon, 10 Oct 2011 12:04:19 -0700 Stanislav Sedov s...@freebsd.org mentioned: On Sat, 8 Oct 2011 18:35:13 +0100 Chris Rees utis...@gmail.com mentioned: Last I heard, portmgr explicitly disapproved of this fix-- have I missed something??? Erwin specifically said not to do it. Since when can anyone just commit stuff to bsd.port.mk, regardless of its location? This is a bad solution, please revert it or I will when I get back. We're going to end up being asked to support it on ports@ otherwise. You certianly missed something, including the rationale behind the portmgr@ descision of not committing to the ports tree (!) bsd.port.mk. Go find some useful work to do like deleting old ports or whatever. You might want to consider deleting all mine ports, as I'm not going to support them anymore (after you backed out this fix without approval I don't have a working ports tree anymore on any of my 3 workstations). Quoting myself. Sorry to all if this sounded rude, I might have overreacted. I didn't meant to be personal, it's just the whole situation is disappointing. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ 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: flash for 9-beta3
On Mon, October 10, 2011 18:38, Phil Oleson wrote: On 10/10/11 15:30, Nenhum_de_Nos wrote: On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote: On Sat, October 8, 2011 20:03, Doug Barton wrote: On 10/08/2011 14:53, Warren Block wrote: nspluginwrapper needs to be run as the end user. The pkg-message tells them to do that. ops, haven't seen it though. all the ports cleaned by the clean part of the command got on my way :( I did, no good though. FF still says no plugins. is it FF 7 compatible ? matheus I ran into this recently. Though I have not figured out a more correct fix.. add this to your .bashrc: export MOZ_PLUGIN_PATH=/usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox or.. .cshrc setenv MOZ_PLUGIN_PATH /usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox and flash will work with the newer firefox. -Phil. thanks Phil, but no good to me :/ Both dirs don't exist, and I tried exporting to browser_plugins dir also ... thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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: subversion-freebsd dependencies
Hi! On a newly installed development machine I installed subversion-freebsd from ports and ended up with a huge dependency chain. If you're just using it for FreeBSD you can un-check all the OPTIONS. If you might want to use the http:// protocol to check something out the neon option works well and is fairly painless. It doesn't help to remove tcl build dependency, as sqlite3 is unconditional dependency :( There is the sqlite-autoconf-3070800.tar.gz on the SQLite download page. This source code builds fine without tcl installed. But FreeBSD port still uses sqlite-src-XXX.zip which marked as Legacy Source Code Distribution Formats (Not Recommended) So it seems that tcl dependency may be avoided. -- Alexander Zagrebin ___ 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
