Re: bsd patch regression?

Hi Sean; El 27/08/2013 5:58 p. m., Sean Bruno escribió: Colin generated a patch for xen things that does some pretty typical behavior. bsdpatch really didn't handle it well and rejected some things and flat out refused to create sys/modules/xenhvm/Makefile for me.

Re: [head tinderbox] failure on amd64/amd64

On 14.11.2013 13:42, Sean Bruno wrote: [...] c++ -O2 -pipe -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch

Re: gcc in -current broken

On 23.11.2013 22:23, Michael Butler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After SVN r258501, I get .. === gnu/usr.bin/cc/cc1 (all) - --- cc1-dummy --- cc -O2 -pipe -DGCCVER=\4.2\ -DIN_GCC -DHAVE_CONFIG_H - -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -

[RFT] llquantize for FreeBSD's dtrace

Hello; I am not a Dtrace user (yet) but I started to port the Log/linear quantizations from Illumos: http://dtrace.org/blogs/bmc/2011/02/08/llquantize/ Apparently this patch should do it: http://people.freebsd.org/~pfg/patches/patch-llquantize-complete Unfortunately when I tried to build

Re: [RFT] llquantize for FreeBSD's dtrace

Hello Fabian; --- Sab 23/6/12, Fabian Keil ha scritto: Pedro Giffuni p...@freebsd.org wrote: I am not a Dtrace user (yet) but I started to port the Log/linear quantizations from Illumos: http://dtrace.org/blogs/bmc/2011/02/08/llquantize/ Apparently this patch should do

Re: [RFT] llquantize for FreeBSD's dtrace

--- Sab 23/6/12, Fabian Keil freebsd-lis...@fabiankeil.de ha scritto: ... My suggestion would be to instead try using the test scripts in cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/llquantize/ err.D_LLQUANT_FACTORSMALL.d (for example) has @ = llquantize(0, 1, 0, 10,

Re: [RFT] llquantize for FreeBSD's dtrace

--- Mar 26/6/12, Mark Peek m...@freebsd.org ha scritto: It's a different assertion. Probably some difference between Solaris and BSD. this is very useful, thanks! Try this, change the assert on line 1429 in file dt_cc.c from: assert(!(arg (UINT16_MAX args[i].shift))); to

Re: [RFT] llquantize for FreeBSD's dtrace

--- Mar 26/6/12, Fabian Keil freebsd-lis...@fabiankeil.de ha scritto: Pedro Giffuni p...@freebsd.org wrote: --- Mar 26/6/12, Mark Peek m...@freebsd.org ha scritto: Try this, change the assert on line 1429 in file dt_cc.c from: assert(!(arg (UINT16_MAX args[i].shift

Re: [HEADS-UP] BSD sort is the default sort in -CURRENT

--- Mer 27/6/12, Doug Barton do...@freebsd.org ha scritto: ... I believe we do not make this kind of work with any vendor code that is being updated in the base; Au contraire, we frequently avoid updating the old versions of things we have in the base precisely because they are not

Re: [HEADS-UP] BSD sort is the default sort in -CURRENT

--- Mer 27/6/12, Doug Barton do...@freebsd.org ha scritto: ... Nope. I would think only the maintainer of the package has the authority to make any request in the lines of being bug-for-bug compatible You have a seriously wrong idea of maintainer. The community owns the software,

Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:

Just IMHO; --- Mer 4/7/12, Doug Barton do...@freebsd.org ha scritto: ... This is not what I expect from quality securing! It is simply a mess and definitely another reason and point for the thread Why NOT using FreeBSD. sure libreoffice is so easy to port... /me officially gives

[CFT] Add -Wbounded to gcc

Hello; I have a patch from OpenBSD that adds -Wbounded to gcc: http://people.freebsd.org/~pfg/patches/patch-gcc-bounded Unfortunately it breaks world, or at least binutils, at this time: _ ... cc1: warnings being treated as errors peigen.c: In function '_bfd_pei_swap_aux_in':

Re: [CFT] Add -Wbounded to gcc

--- Mer 11/7/12, Dimitry Andric d...@freebsd.org ha scritto: ... Does it catch any really interesting bound overruns? Nah .. I arrived to the conclusion that it's not really worth it :). If the number of false positives is very large, then it generally isn't worth the pain.  Or the

libedit : feel like obsoleting el_data_get/set

Hello; In my attempt to update libedit and make it somewhat more in line with NetBSD's code I found we added two private functions: el_data_get and el_data_set: http://svnweb.freebsd.org/base?view=revisionrevision=50070  According to OpenGrok we are not using those functions at all, plus we 

Re: MPSAFE VFS -- List of upcoming actions

Hi; Just thought I'd share a link for the fuse-xfs project (for MacFUSE);  http://sourceforge.net/projects/fusexfs/ It's read-only so maybe it can be considered a feature compatible replacement of our kernel driver ;). cheers, Pedro. ps. I added it to the WantedPorts wiki so it won't be

MS Hyper-v for FreeBSD announced

Hi guys, Yesterday, per chance, I had the idea of looking up what the status of the Hyper-V drivers was and I found the announcement: http://blogs.technet.com/b/openness/archive/2012/08/09/available-today-freebsd-support-for-windows-server-hyper-v.aspx  The announcement is much easier to find

[RFT] Some updates to libc/rpc

Hello; The Bull NFS4 for linux project took our RPC support from libc and did some enhancements on it for a while. The libraries have been diverging extensively and many of the changes are linux specific. The complete log of their changes is here:

[CFT] Some updates to libc/rpc (second try)

(Second try with a more benign mailer) Hello; A while back the Bull NFS4 for linux project took our RPC support from libcand did some enhancements on it. The libraries have been diverging extensively and many of the changes are linux specific. The complete log of their changes is here:

Re: Clang as default compiler November 4th

Hello;   Just my $0.02.   - Original Message -  ... Can you, please, read what I wrote ? Fixing _ports_ to compile with clang is plain wrong. Upstream developers use gcc almost always for development and testing. Establishing another constant cost on the porting work puts burden on the

Re: Call for bge(4) testers

Success !!! It fixed kern/169634 for me. If still possible it should be pushed into 9.1-RELEASE. Thank you so much for working on this! Pedro. On 09/14/2012 16:27, YongHyeon PYUN wrote: All, There were lots of reports that stock bge(4) does not work on Dell Rx20/HP DL 360 G8. With the

Re: new DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1

Hello; On 10/13/2012 13:38, Jakub Lach wrote: 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? I stopped following Dragonfly a while ago but it seems like it was some VM SMP related work:

Re: new DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1

Actually ... On 10/13/2012 13:38, Jakub Lach wrote: 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? Their explanation of the changes is here: http://www.shiningsilence.com/dbsdlog/2012/09/19/10403.html Cheers, Pedro.

Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool

--- Gio 29/12/11, Nathan Whitehorn nwhiteh...@freebsd.org ha scritto: ... I'd appreciate any specific comments you might have, and especially specific suggestions for improvements. Except from people who are old hands at sysinstall, I've received almost universally positive comments

Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool

--- Gio 29/12/11, Chris Rees cr...@freebsd.org ha scritto: FWIW; I have practically given up on installing FreeBSD lately and I mostly use PC-BSD. I mainly see two big issues: -X.Org has become very difficult to install. Setting up hald and friends, not to mention that you have

Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool

Hello; --- Gio 29/12/11, Chris Rees cr...@freebsd.org ha scritto: I use the nvidia driver, no idea what people with ATI cards do. I'm sorry to hear you're having trouble with that, if you ever want to try again and you can't work it out get me off list ;) Getting X11 to run on

[CFT] New headers from the maestro3 snd driver

Hello guys; As some of you may have noticed I have been replacing some GPL'd headers from the sound system. In the case of the Maestro3 snd driver, basically the same headers are available in the BSD licensed OSS drivers (in the Attic though - that card is rather old). If someone still has that

[CFT] ext2/3 nanosecond timestamps patch.

Hello; I have been working on implementing some ext4 features that can work in ext3 mode in preparation towards bringing some more of the ext4 work Zheng Liu did for his GSoC 2010 project. The first of this features is nanosecond/birthtime timestamping, which basically means that if the

Re: -ffast-math in Ports and wrong generated code

On 04/04/12 04:29, Andrey Simonenko wrote: On Tue, Apr 03, 2012 at 06:43:00AM -0700, Steve Kargl wrote: On Tue, Apr 03, 2012 at 02:21:11PM +0300, Andrey Simonenko wrote: I use one port from the Ports Collection, that works with FP. Having reinstalled it (its version was not changed) I noticed

Re: -ffast-math in Ports and wrong generated code

On 04/05/12 01:46, Andrey Simonenko wrote: On Wed, Apr 04, 2012 at 09:45:25AM -0500, Pedro Giffuni wrote: On 04/04/12 04:29, Andrey Simonenko wrote: On Tue, Apr 03, 2012 at 06:43:00AM -0700, Steve Kargl wrote: The SVN commit http://svnweb.freebsd.org/base?view=revisionrevision=228756

[CFT]: libedit update (NetBSD CVS 2009-12-28)

Hi; I noticed that libedit is seriously outdated so I tried to sync it with the upstream (NetBSD) tree. For the time being I avoided the international support and related changes since they move some files and, in general, complicates getting things merged properly. The resulting patch is

Re: contrib/jemalloc

Hi; --- Ven 20/4/12, Doug Barton ha scritto: ... The workflow I'm using is documented in the patch (contrib/jemalloc/FREEBSD-upgrade).  Can you tell me how to achieve a similarly streamlined import flow with a vendor branch in the mix?  Also, what history would a vendor branch preserve

Re: contrib/jemalloc

--- Ven 20/4/12, Doug Barton do...@freebsd.org ha scritto: ... With due respect, if doing it the right way is too difficult, the answer is to ask for help rather than giving up. There are plenty of us who are experienced with doing this, and would be glad to assist. In the CVS era I

Re: contrib/jemalloc

On 04/20/12 19:32, David O'Brien wrote: On Fri, Apr 20, 2012 at 02:13:32PM -0700, Pedro Giffuni wrote: Easier said than done. Feel free to give libedit a try. That has nothing to do with our process and everything to do with us blindly hacking away pissing all over to be our own thing

Re: contrib/jemalloc

On 04/21/12 02:23, Doug Barton wrote: ... In libedit we have incomplete merges from upstream (that was CVS fault), we have some changes that are obsolete wrt to how upstream solved the same issues and we have a couple of files that have diverged completely from upstream. I agree that sounds

Re: jemalloc: jemalloc_arena.c:182: Failed assertion: p[i] == 0

On 04/30/12 14:04, Oleksandr Tymoshenko wrote: On 29/04/2012 12:04 PM, Adrian Chadd wrote: .. and the output from the buildworld: .. skipped .. -DSOFTFLOAT_FOR_GCC -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized

Re: [HEADS-UP] BSD sort coming to -CURRENT

Oleg and Gabor; Awesome! Kudos and huge thanks for working on this!! Pedro. On 05/08/12 10:51, Gabor Kovesdan wrote: Hi Folks, Oleg Moskalenko has been working very hard on BSD sort and by now we think it is compatible with the base version (and has even more features, the ideas mostly

Re: panic, seems related to r234386

Hello; On 05/12/12 17:49, Mateusz Guzik wrote: Gave this a spin and found what looks like a deadlock: http://people.freebsd.org/~pho/stress/log/ext2fs.txt Not a new problem, it would seem. Same issue with 8.3-PRERELEASE r232656M. pid 2680 (fts) holds lock for vnode cb4be414 and tries to

GCC update for testing

Hi; I took a bunch of patches that were merged into the GCC 4.1 branch (under GPLv2) and prepared a patch for merging them into our base gcc. These are supposed to be bug fixes only. You can get the patch here: http://people.freebsd.org/~pfg/patches/patch-contrib-gcc And, for those really

Re: GCC update for testing

Hi Dimitry; On 05/17/12 11:44, Dimitry Andric wrote: On 2012-05-17 17:44, Pedro Giffuni wrote: Hi; I took a bunch of patches that were merged into the GCC 4.1 branch (under GPLv2) and prepared a patch for merging them into our base gcc. These are supposed to be bug fixes only. You can get

Re: GCC update for testing

On 05/18/12 02:08, Gleb Kurtsou wrote: On (17/05/2012 10:44), Pedro Giffuni wrote: Hi; I took a bunch of patches that were merged into the GCC 4.1 branch (under GPLv2) and prepared a patch for merging them into our base gcc. These are supposed to be bug fixes only. You can get the patch here

Re: GCC update for testing

Hi again; On 05/17/12 11:44, Dimitry Andric wrote: On 2012-05-17 17:44, Pedro Giffuni wrote: Hi; I took a bunch of patches that were merged into the GCC 4.1 branch (under GPLv2) and prepared a patch for merging them into our base gcc. These are supposed to be bug fixes only. You can get

Re: Why Are You NOT Using FreeBSD?

FWIW; --- Lun 4/6/12, Jakub Lach jakub_l...@mailplus.pl ha scritto: 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 am aware that PC-BSD has been indeed providing

Re: Why Are You NOT Using FreeBSD?

--- Lun 4/6/12, Jakub Lach jakub_l...@mailplus.pl ha scritto: ... 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

Re: ctfconvert again

So I updated my FreeBSD machine to 9.1-RELEASE in the hope of getting past the ctfconvert problem that causes a build of 10-CURRENT to say: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] while compiling every kernel source file. Then I checked out

[CFT] WITH_BSD_PATCH

(Not sure the first announcement made it - Sorry if you get this twice) Fellow FreeBSD developers; As many of you may have noticed as of r246074 we have a new version of patch(1) in the tree! The brief history is this: - Larry Wall developed the first patch(1) implementation which was taken

Dtrace status - material for someone's TODO list.

Hello; Last year I did an attempt to merge some of the changes from illumos' Dtrace into FreeBSD. I don't use Dtrace a lot, so this was done mainly for fun. In general, merging changes from Illumos was pretty straightforward; just a matter of readapting the paths to match our layout. I was

Re: DTrace gone quiet?

Hello; Yes, I was indeed going to post that the culprit is this change from Illumos: 3026 libdtrace should set LD_NOLAZYLOAD=1 to help the pid provider It is an upstream hack for the Solaris ld that they bundled among many changes. I will see how to revert only the part that gives problems.

Re: DTrace gone quiet?

On 04/16/13 15:54, Mark Johnston wrote: On Tue, Apr 16, 2013 at 12:57:08PM -0700, Navdeep Parhar wrote: I just upgraded my kernel and userspace to head (r249552) and I notice that DTrace doesn't output anything until I hit ctrl-c. All previous hits on the probe appear lost. For example: #

Re: Please test upcoming DTrace port mod_usdt for apache22

On 04/16/13 15:55, Olli Hauer wrote: Hi, I've created together with Pedro Giffuni (pfg@) a new DTrace apache port (www/mod_usdt). We are interested in getting some more test results from DTrace and apache users. A complete description is here: http://dtrace.org/blogs/dap/2011/12/13/usdt

Problem loading a kld on i386

Hello; I just built a recent kernel in an i386 virtualbox VM and when trying to load the ext2fs module I get this: #kldload ext2fs link_elf_lookup_symbol: corrupt symbol table link_elf_lookup_symbol: corrupt symbol table link_elf: symbol __moddi3 undefined kldload: can't load ext2fs: No such

Re: (follow-up) Stale NFS file handle for NFS exported UFS from r252435

Hello guys; Thank for finding this, however ... On 10.07.2013 08:53, Claude Buisson wrote: On 07/10/2013 14:32, Claude Buisson wrote: Hi, Upgrading a CURRENT amd64 pure UFS system (watson) from r249744 to r253007, I have hit the following: claude@zorglub$ mount_nfs watson:/home /mnt

Re: (follow-up) Stale NFS file handle for NFS exported UFS from r252435

On 10.07.2013 10:16, Claude Buisson wrote: On 07/10/2013 17:05, Pedro Giffuni wrote: Hello guys; Thank for finding this, however ... snip While I understand this change caused the issue and I am willing to revert it, I think the problem is actually in NFS. At least ext2/3/4 and fuse (so

Re: (follow-up) Stale NFS file handle for NFS exported UFS from r252435

On 10.07.2013 10:16, Claude Buisson wrote: On 07/10/2013 17:05, Pedro Giffuni wrote: Hello guys; Thank for finding this, however ... snip While I understand this change caused the issue and I am willing to revert it, I think the problem is actually in NFS. At least ext2/3/4 and fuse (so

Re: FUSE not work.

Hello; The internal data structures in the FUSE kernel module have been updated to be more compatible with MacFUSE and the linux FUSE. This basically measn you have to rebuild your fuse modules (including NTFS). We should not really update the FUSE_KERNEL_MINOR_VERSION yet. I will add a note

Re: FUSE not work.

(re-posting since the original response didn't make it through) On 19.07.2013 10:29, Alexander Panyushkin wrote: 19.07.2013 17:36, Pedro Giffuni пишет: Hello; The internal data structures in the FUSE kernel module have been updated to be more compatible with MacFUSE and the linux FUSE

Re: FUSE not work.

On 19.07.2013 12:07, Alexander Panyushkin wrote: 19.07.2013 19:42, Pedro Giffuni пишет: (re-posting since the original response didn't make it through) On 19.07.2013 10:29, Alexander Panyushkin wrote: 19.07.2013 17:36, Pedro Giffuni пишет: Hello; The internal data structures in the FUSE

Re: FUSE not work.

On 19.07.2013 23:42, Kevin Oberman wrote: ... fuse is at least partly broken in -current. I discovered that if you mount two devices that use fuse, when you umount any of them, ll are marked as not mounted and disappear from df(1) or mount(8) output, but only one is actually cleanly

Re: poudriere problems with fuse?

Hi; El 24/07/2013 1:22 p. m., Adrian Chadd escribió: Hi Pedro, Bapt tells me that there are FUSE issues in the most recent -HEAD and it's stopping poudriere from running. What's the story here? I reverted all my birthtime changes, the remaining change is only a header update from upstream

Re: poudriere problems with fuse?

On 24.07.2013 13:34, Baptiste Daroussin wrote: On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote: Hi Pedro, Bapt tells me that there are FUSE issues in the most recent -HEAD and it's stopping poudriere from running. Nah poudriere does not use yet fuse :) What's the story here? I

Re: poudriere problems with fuse?

On 24.07.2013 14:07, Baptiste Daroussin wrote: On Wed, Jul 24, 2013 at 01:55:21PM -0500, Pedro Giffuni wrote: On 24.07.2013 13:34, Baptiste Daroussin wrote: On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote: Hi Pedro, Bapt tells me that there are FUSE issues in the most recent

Re: FUSE not work.

On 24.07.2013 13:49, Baptiste Daroussin wrote: ... Yes fuse in base is broken since r248084 downgrade sys/fs/fuse to that version and it will work, I'm investigating. What I fix is the umount umounting all the FS. regards, Bapt Forgot to say r248084 is the last working revision. Sorry for

[Heads up] BSD-licensed patch becoming the default RSN.

Hello; After an exp-run it was found that only two ports presented regressions with the new BSD-licensed patch derived from Open/DragonFly BSD. The issue was related to some patch level detection the previous GNU patch has and the new patch lacks. Otherwise both versions are basically

Re: [Heads up] BSD-licensed patch becoming the default RSN.

Hi Jan; El 26/07/2013 8:01 p. m., Jan Beich escribió: bsdpatch doesn't list files of the failed hunks with -C and -s option. This may be less convenient if you edit a patch directly rather than regen it after polluting the tree. $ patch -CEfsp0 -i /path/to/varsym.diff 1 out of 1 hunks failed 1

Re: [Heads up] BSD-licensed patch becoming the default RSN.

On 26.07.2013 23:11, Jan Beich wrote: Pedro Giffuni writes: Now, just some food for thought, but if you are unsure your patch applies cleanly, why would you choose to use the -s (silent) option? Because by default patch(1) is overly verbose. At first, I'm only interested if a patch applies

Re: [Heads up] BSD-licensed patch becoming the default RSN.

OK; On further revision ... On 26.07.2013 20:01, Jan Beich wrote: bsdpatch doesn't list files of the failed hunks with -C and -s option. This may be less convenient if you edit a patch directly rather than regen it after polluting the tree. $ patch -CEfsp0 -i /path/to/varsym.diff 1 out of 1

Re: svn 260311 breaks gcc builds on releng9 ?

Hello Luigi; On 17.01.2014 15:18, Luigi Rizzo wrote: Hi, I am seeing an odd problem which seems to be triggered by svn260311 I have two machines running snapshots of stable/9 from last fall (one 255898 sep.26, the other 258126 nov.14). All is amd64 Build a recent head (260311 and newer) with

Re: svn 260311 breaks gcc builds on releng9 ?

On 17.01.2014 16:07, Luigi Rizzo wrote: On Fri, Jan 17, 2014 at 12:50 PM, Pedro Giffuni p...@freebsd.org mailto:p...@freebsd.org wrote: Hello Luigi; On 17.01.2014 15:18, Luigi Rizzo wrote: Hi, I am seeing an odd problem which seems to be triggered

Re: [CFT] ASLR, PIE, and segvguard on 11-current and 10-stable

(Dropped the cross-posting, which *is* frowned upon) While I do very much appreciate this work being done, and I agree we should have it in the tree, I would really prefer it opt-in rather opt-out, at least initially. I know this may very well be the subject of a bikeshed of historical

CFR - fflush() behaviour change

Hi; Out of curiosity I took a peek at Apple's libc and generated some diffs against the libc in FreeBSD's 8. Most of the changes are not relevant to FreeBSD anymore as we have grown alternative implementations for things like xlocale. Nevertheless, there are still some small things to look

NPF (was Re: Future of pf / firewall in FreeBSD ? - does it have one ?)

FWIW, and while I still wonder why we need three packet filters … There is yet another firewall implementation in NetBSD: http://www.netbsd.org/~rmind/npf/ It seems to be more portable, it is thought with SMP-friendliness in mind and according to a EuroBSDCon talk ports for FreeBSD and Illumos

Re: Call for testing: elftoolchain tools

FWIW, A nice testing procedure, or even a pet project if generalized, would be to test the tools with a fuzzer like security/afl. Apparently the GNU binutils and Fedora elfutils developers having doing that [1]. Regards, Pedro. [1]

[CFT] Remove NIS

Eh ... No, I am not planning to remove NIS, au contraire, but now that I got your attention ... We have a couple of long standing (2001) NIS-related issues with patches and I am willing to do something about it. Please test: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=26486

Re: [Heads up] : You may need to update your gcc ports.

On 04/21/15 12:43, Bryan Drewery wrote: On 4/5/2015 2:10 PM, Pedro Giffuni wrote: I don't know if someone is keeping up-to-date packages for -current but I will hold the headers update for a while to help such cases. We build head packages _at least_ once a week. Currently we always update

What to do about RCS/OpenRCS

Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot more people than you might think find it useful to have a small version control system for thing

Re: What to do about RCS/OpenRCS

Il giorno 08/mag/2015, alle ore 00:26, Doug Brewer brewer.d...@gmail.com ha scritto: On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org mailto:p...@freebsd.org wrote: Hello; On 05/07/15 14:56

Re: What to do about RCS/OpenRCS

Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob

Re: What to do about RCS/OpenRCS

Hi; On 08/05/2015 10:44 a.m., John Baldwin wrote: On Thursday, May 07, 2015 04:18:38 PM NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't

Re: What to do about RCS/OpenRCS

On 05/08/15 15:59, Davide Italiano wrote: On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni p...@freebsd.org wrote: Hi; I guess I see the following options: 1) Just leave GNU RCS in the tree. 2) Improve OpenRCS so it can be swapped in. 3) Remove RCS dependencies from other parts

CFR: a new __unreachable() builtin

Hello; I am looking at the cdefs in other BSDs hoping to avoid adopting the same definitions with incompatible names and I noticed NetBSD is using a new __builtin_unreachable (void) function from gcc 4.6: https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html Apparently it was interesting

Re: [RFC] Replace gnu groff in base by heirloom doctools

+1 Great idea. Pedro. ___ 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

[Heads up] : You may need to update your gcc ports.

Hello; I was going to add this to the UPDATING file but this file is not meant for changes affecting ports so here it goes instead: 20150415: Our libc headers are starting to use gcc-style attributes to hint the compiler about probable optimizations or errors. Unfortunately

Re: [Heads up] : You may need to update your gcc ports.

On 04/05/15 13:00, Aryeh Friedman wrote: On Sun, Apr 5, 2015 at 1:39 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; I was going to add this to the UPDATING file but this file is not meant for changes affecting ports so here it goes instead: 20150415: Our libc headers are starting

Re: r288669 breaks ports building with USE_GCC=yes

Hi Gerald; > Il giorno 08/nov/2015, alle ore 19:00, Gerald Pfeifer ha > scritto: > > On Tue, 13 Oct 2015, Justin Hibbits wrote: >> As Antoine mentioned, the problem is that lang/gcc does not have this >> patch. USE_GCC uses lang/gcc, not lang/gcc48. So lang/gcc needs to

Re: Need help fixing failing locale tests

FWIW; While I personally don’t use it, Latin is the official language for the Holy See [1]. I think it is still taught in schools in Italy for cultural reasons and because it’s supposed to make easier to learn other “romance” languages. It shouldn't hurt to keep it but I have no strong opinion.

Re: [CFT] Unicode collation string and reworked locale definitions

Hi Baptiste; > Il giorno 03/nov/2015, alle ore 02:17, Baptiste Daroussin <b...@freebsd.org> > ha scritto: > > On Mon, Nov 02, 2015 at 06:59:15PM -0500, Pedro Giffuni wrote: >> First of all, congratulations to Baptiste and Marino for succeeding where >> I failed ma

Re: [CFT] Unicode collation string and reworked locale definitions

Hello; > Il giorno 03/nov/2015, alle ore 10:52, Wolfgang Jenkner <wjenk...@inode.at> > ha scritto: > > On Tue, Nov 03 2015, Pedro Giffuni wrote: > >> What worries me about libtre is that it lacks important functionality like >> word >> delimite

Re: [CFT] Unicode collation string and reworked locale definitions

First of all, congratulations to Baptiste and Marino for succeeding where I failed many moons ago. Also huge thanks to Nexenta and Garret D’Amore for relicensing localedef for us. Concerning regex; Gabor@ did a lot of work on libtre but according to him it was not up to the task performancewise.

Re: r288669 breaks ports building with USE_GCC=yes

Hello; On 12/10/2015 02:56 p.m., Justin Hibbits wrote: The default ports gcc for USE_GCC is still 4.8, which does not support -fstack-protector-strong. This breaks several ports including (from my poudriere run): libfpx and qt4-sqlite3-plugin. - Justin r288669 only applies to base. It was

Re: r288669 breaks ports building with USE_GCC=yes

Hi again; On 12/10/2015 03:16 p.m., Pedro Giffuni wrote: Hello; On 12/10/2015 02:56 p.m., Justin Hibbits wrote: The default ports gcc for USE_GCC is still 4.8, which does not support -fstack-protector-strong. This breaks several ports including (from my poudriere run): libfpx and qt4-sqlite3

Re: r288669 breaks ports building with USE_GCC=yes

(CCing Gerald as this may involve a g++ bug as well.) Hello; On 12/10/2015 03:33 p.m., Justin Hibbits wrote: Hi Pedro, On Mon, Oct 12, 2015 at 3:28 PM, Pedro Giffuni <p...@freebsd.org> wrote: Hi again; On 12/10/2015 03:16 p.m., Pedro Giffuni wrote: Hello; On 12/10/2015 02:56 p.m.,

Re: r288669 breaks ports building with USE_GCC=yes

On 10/12/2015 3:33 PM, Justin Hibbits wrote: Hi Pedro, On Mon, Oct 12, 2015 at 3:28 PM, Pedro Giffuni <p...@freebsd.org> wrote: Hi again; On 12/10/2015 03:16 p.m., Pedro Giffuni wrote: Hello; On 12/10/2015 02:56 p.m., Justin Hibbits wrote: The default ports gcc for USE_GCC is sti

Re: r288669 breaks ports building with USE_GCC=yes

Hi; On 10/12/2015 8:28 PM, Justin Hibbits wrote: Hi Pedro, ... This is on powerpc64. I see the patch has been there for 16 months, but for some reason, the /usr/local/bin/gcc48 doesn't contain the patch. I ran `strings` on the binary, and it has the following string:

Re: r288669 breaks ports building with USE_GCC=yes

On 10/13/2015 9:59 AM, Justin Hibbits wrote: Hi Pedro, ... As Antoine mentioned, the problem is that lang/gcc does not have this patch. USE_GCC uses lang/gcc, not lang/gcc48. So lang/gcc needs to be updated. I see now. FWIW, I installed gcc48 and then I added USE_GCC= yes to the port.

Re: DDB patches

Hello; > Il giorno 19/nov/2015, alle ore 02:34, Dan Partelly > ha scritto: > > Hey Pedro, > > some times ago you got some DDB patches from me in which I added relational > ops support from it. The patch was a bit clobbered, > but last I know you cleaned it up and put

Re: DDB patches

On 11/20/15 08:54, Dan Partelly wrote: Hi Pedro, I think you confuse blackmailing with something much simpler and pragmatic. One needs to asses how things work in your project for real before investing too much time. A template for blackmailing is usually in the form: "I will do this

Re: DDB patches

On 11/20/2015 11:28 AM, Dan Partelly wrote: A template for blackmailing is usually in the form: "I will do this (usually involving saving the world and/or your evidently miserable life) but first you will have to do this (unrelated) thing to see that you are worthy.” It is interesting how

Re: DDB patches

icularly NOT interested in code where the original contributor will walk away as soon as he/she receives criticism or has plans that do not match ours. If this is not your ideal workflow … fork your own BSD, a lot of intelligent people do just that. Pedro. > > Dan > > > >> On 19 Nov

Re: CURRENT: bhyve and Kernel SamePage Mergin

Hi oh; Nothing to worry: for good or bad, FreeBSD has no memory deduplication mechanism implemented. Pedro. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179721 broke some application (xterm, pidign)

Hello Vitalij; Hello. After updating my system to 11.0-ALPHA2 #20 r301583 I'm found that at last some application is broken. here backtrace for xterm #0 0x0008022d48b4 in mbsrtowcs_l () from /lib/libc.so.7 [New Thread 804816000 (LWP 102346/)] (gdb) bt #0 0x0008022d48b4 in

Re: lldb input issue

On 03/06/16 15:20, Pedro Giffuni wrote: El 06/03/2016 a las 15:05, Baptiste Daroussin escribió: On Sun, Mar 06, 2016 at 10:55:27PM +0300, Roman Bogorodskiy wrote: Baptiste Daroussin wrote: On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote: Hi, I'm seeing an issue

  1   2   >