Use of C99 extra long double math functions after r236148
Yesterday r236148 (Allow inclusion of libc++ to work after including math.h) was comitted to head, many thanks. Does this mean, that extra long double functions like acoshl, expm1l or log1pl are now "really implemented"? As far as I understand, they had only been declared before? If this is right, are they usable on a recent CURRENT, built with gcc42 (system compiler), by ports which use gcc46 (not clang)? If not, are there any plans to implement these functions in the near future? The use of C99 extra long double functions would be of interest for example for programs like math/R, especially its upcoming releases. Many thanks for any clarification. Regards, Rainer Hurling ___ 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"
Repeated build failures in expr due to yyparse
Running a make -s -j5 buildworld; cleaned the entire obj tree meanwhile. Builds are running on a slightly older HEAD thought with an updated libc and some headers. I can reproduce this all the time. Buildworld at this stage should be self-contained, right? So why is it failing? ===> bin/expr (all) cc1: warnings being treated as errors /zoo/bz/HEAD.svn/bin/expr/expr.y: In function 'main': /zoo/bz/HEAD.svn/bin/expr/expr.y:291: warning: implicit declaration of function 'yyparse' /zoo/bz/HEAD.svn/bin/expr/expr.y:291: warning: nested extern declaration of 'yyparse' expr.c: At top level: expr.c:813: warning: no previous prototype for 'yyparse' *** Error code 1 -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ 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: WARNING - DO NOT test: IPv6 offload support in HEAD + patch for stable/9
On 26. May 2012, at 14:01 , Bjoern A. Zeeb wrote: Hey. > WARNING - please refrain from testing IPv6 or updating your HEAD if you do > not have any of the above two NICs and rely on IPv6, or if you have updated > and > are experiencing problems. Disabling -txcsum -tso for the moment should be an > often unhelpful workaround. It seems I was just lucky with my choice of other It was not, as there was a further bug, which was fixed last night with http://svn.freebsd.org/changeset/base/236130 To fix the full problem, here's a proposed patch for testing on the latest HEAD or review: http://people.freebsd.org/~bz/20120527-02-fix-v6-csum-offload.diff I'd be happy to hear back from anyone on short notice that it works for him, and I'll get it in for (possible) further refinements. /bz -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ 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"
OptionalObsoleteFiles.inc completeness
Hi! I'm running a little pet project of improving completeness of tools/build/mk/OptionalObsoleteFiles.inc file and thus delete-old* targets with regard to all possible WITHOUT_* knobs. E.g. when WITHOUT_foo is defined in src.conf, make delete-old should remove related files completely, to make a system look exactly like it's world was installed with that knob set. First of all, an automatic script to check for leftovers after delete-old for all possible knobs is available from [2]. Feel free to run in on different architectures and FreeBSD branches; I'm currently running it on amd64. I also think that it should be run during preparation of each FreeBSD release. There are some questions I'd like to discuss. 1) named config file var/named/etc/namedb/named.conf was intentionally left out from OptionalObsoleteFiles.inc, so I did the same for other configs which may be changed by users. Since this approach requires maintaining a whitelist of such files to ignore them in checking leftovers, I think it'd be better to introduce special variable for config files, e.g. OLD_CONFIGS and corresponding target, delete-old-configs, which will by default remove configs interactively, with an option to remove them in batch mode. 2) Is this ok to backport the list from current to stable branches? Pro - it's really simple, con - it will contain files never installed with this (old) branch. I also plan to make similar script for checking completeness of delete-old* targets for the case of system update. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/168341 [2] https://github.com/AMDmi3/obsolete-files-checker -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: [CFT][CFR] Resurrect handling of VersionAddendum in OpenSSH
Sat, May 26, 2012 at 02:34:20PM +0400, Eygene Ryabinkin wrote: > Can anyone who uses SSH test this patch and report their findings > to the respective PR. Also, code reviews are welcome too. I head been blessed by des@ to commit the code into -CURRENT and I did so, http://svnweb.freebsd.org/base?view=revision&revision=236139 so people who run HEAD will automatically receive this fix starting from now. -- Eygene Ryabinkin,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] pgp7UPlMJwV5C.pgp Description: PGP signature