Re: WITH_ICONV/WITH_BSD_GREP: Defaults?
On Jan 5, 2012, at 12:04 PM, O. Hartmann wrote: > > Another story seems to be with WITH_ICONV. I didn't realize problems > until I had harsh faults compiling port lang/gcc46 which tend to fail in > a Makefile when WITH_ICONV is enabled. What exactly is the failure you're seeing? I ask because I've recently been wrestling with autoconf trying to generate a configure script that will DTRT on systems with more than one iconv() function available. The standard autoconf recipes don't seem to work correctly in this case. (I've seen it on MacOS when GNU libiconv is installed in addition to the iconv implementation in libc in the base system. I presume the same problem arises on FreeBSD.) In short: this could be a bug in the configure script rather than a bug in FreeBSD's iconv implementation. Tim ___ 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: WITH_ICONV/WITH_BSD_GREP: Defaults?
On 2012.01.05. 21:04, O. Hartmann wrote: In FreeBSD 9 and 10, src.conf could be populated with those two knobs WITH_ICONV and WITH_BSD_GREP For some testing purposes, I switched them both to "enabled", so I could test ports and software against these. I didn't realize any serious issue with WITH_BSD_GREP, but I read, some time ago, that bsdggrep does have some speed issues. What is the actual status of bsdgrep in FreeBSD? Yes, BSD grep has significant performance problems. It is quite a complex issue because GNU grep uses some shortcuts to speed up pattern matching. I don't want to put that in BSD grep because that does not seem correct to me. Such code belongs to the regex library. Not just logically but practically, as well, so that other dependencies can also benefit from a faster pattern matching. However, it cannot be done with the POSIX-compliant API so it requires some extensions. From the last GSoC, there is an ongoing work on this but currently, I'm having exams at the university. I hope I can finish it after my exams. Another story seems to be with WITH_ICONV. I didn't realize problems until I had harsh faults compiling port lang/gcc46 which tend to fail in a Makefile when WITH_ICONV is enabled. But at that point the issue the first time occured, I hadn't deinstalled port converters/libiconv so I can not say whether those issues came due to confusions. But it seems to tend to confusions having remnants of WITH_iconv installation when disabling the build by deleting or commenting out WITH_ICONV. What is the status of WITH_ICONV? The ports seem still to rely on the port libiconv when being built. BSD iconv works quite well in some cases but there are some problems on my TODO list, so I preferred to leave it off by default until they are solved. Gabor ___ 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"
WITH_ICONV/WITH_BSD_GREP: Defaults?
In FreeBSD 9 and 10, src.conf could be populated with those two knobs WITH_ICONV and WITH_BSD_GREP For some testing purposes, I switched them both to "enabled", so I could test ports and software against these. I didn't realize any serious issue with WITH_BSD_GREP, but I read, some time ago, that bsdggrep does have some speed issues. What is the actual status of bsdgrep in FreeBSD? Another story seems to be with WITH_ICONV. I didn't realize problems until I had harsh faults compiling port lang/gcc46 which tend to fail in a Makefile when WITH_ICONV is enabled. But at that point the issue the first time occured, I hadn't deinstalled port converters/libiconv so I can not say whether those issues came due to confusions. But it seems to tend to confusions having remnants of WITH_iconv installation when disabling the build by deleting or commenting out WITH_ICONV. What is the status of WITH_ICONV? The ports seem still to rely on the port libiconv when being built. Thanks in advance, Oliver signature.asc Description: OpenPGP digital signature