Re: ask about stable
On 20 Feb 2013, at 06:03, Nurhermansyah eka ekanoti...@gmail.com wrote: hi all.. if I could make a stable version for freebsd 9.1-release ?? thanks Hi, Did you mean I'm running 9.1-RELEASE and I want to update it to 9-STABLE ? If not, kindly clarify... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ask about stable
Here, I think this is what you're looking for: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html You should be able to move from 9.1-RELEASE to 9-STABLE with freebsd-update :) On Feb 20, 2013, at 9:57 AM, Nurhermansyah eka ekanoti...@gmail.com wrote: hi, oh ya .. true .. I'm running 9.1-RELEASE and I want to update to 9-STABLE it's how to update to 9-STABLE? thank you sorry if my english is bad, i from indonesia.. 2013/2/20 Damien Fleuriot m...@my.gd On 20 Feb 2013, at 06:03, Nurhermansyah eka ekanoti...@gmail.com wrote: hi all.. if I could make a stable version for freebsd 9.1-release ?? thanks Hi, Did you mean I'm running 9.1-RELEASE and I want to update it to 9-STABLE ? If not, kindly clarify... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ask about stable
On Feb 20, 2013, at 4:29 AM, Fleuriot Damien m...@my.gd wrote: Here, I think this is what you're looking for: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html You should be able to move from 9.1-RELEASE to 9-STABLE with freebsd-update :) Except that the freebsd-update(8) man page includes the following: DESCRIPTION The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only available if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. In other words, you can't use it to track -STABLE or -CURRENT. Cheers, Paul. On Feb 20, 2013, at 9:57 AM, Nurhermansyah eka ekanoti...@gmail.com wrote: hi, oh ya .. true .. I'm running 9.1-RELEASE and I want to update to 9-STABLE it's how to update to 9-STABLE? thank you sorry if my english is bad, i from indonesia.. 2013/2/20 Damien Fleuriot m...@my.gd On 20 Feb 2013, at 06:03, Nurhermansyah eka ekanoti...@gmail.com wrote: hi all.. if I could make a stable version for freebsd 9.1-release ?? thanks Hi, Did you mean I'm running 9.1-RELEASE and I want to update it to 9-STABLE ? If not, kindly clarify... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ask about stable
On Feb 20, 2013, at 3:09 PM, Paul Mather p...@gromit.dlib.vt.edu wrote: On Feb 20, 2013, at 4:29 AM, Fleuriot Damien m...@my.gd wrote: Here, I think this is what you're looking for: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html You should be able to move from 9.1-RELEASE to 9-STABLE with freebsd-update :) Except that the freebsd-update(8) man page includes the following: DESCRIPTION The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only available if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. In other words, you can't use it to track -STABLE or -CURRENT. Cheers, Paul. Ewww epic fail on my part. I only do source updates here hence the confusion. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Mounting from zfs... failed with error 2, again
Succeed. Thank you. -- Zhihao Yuan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: stable/9 r245439 breaks security/pam_ssh_agent_auth on stable/9 (WAS: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9)
On Wed, Feb 6, 2013 at 12:28 AM, Stefan Bethke s...@lassitu.de wrote: Am 05.02.2013 um 23:06 schrieb Stefan Bethke s...@lassitu.de: Am 05.02.2013 um 19:09 schrieb Kimmo Paasiala kpaas...@gmail.com: On Tue, Feb 5, 2013 at 12:36 AM, Kimmo Paasiala kpaas...@gmail.com wrote: On Sun, Feb 3, 2013 at 7:22 PM, Chris Rees cr...@freebsd.org wrote: On 3 February 2013 17:15, Stefan Bethke s...@lassitu.de wrote: Am 03.02.2013 um 10:57 schrieb Chris Rees cr...@freebsd.org: On 3 February 2013 03:55, Kimmo Paasiala kpaas...@gmail.com wrote: There is no PR yet with my fix and therefor no commit to ports tree that would fix the problem. I'll file a PR soon (TM). The problem was in base, and is fixed there. Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. Is there some confusion about which problem is addressed by Kimmo's patch? Hm, perhaps it might be necessary then. Kimmo, please would you submit the patch you had as a PR? I'm sure Wesley would appreciate the hint. Chris I'll file a PR when I have recovered from a nasty flu. Right now I'm not fit for thinking... I changed the title of this thread to a better one. -Kimmo It looks like the port was updated just recently to a new version that has its own problems that are no longer related strnvis(3). I'll have to give up for now. (freebsd-ports added to cc:) I can confirm that with the new port version on a two day old current, the module doesn't work: $ uname -a FreeBSD freebsd-current.lassitu.de 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r246283: Sun Feb 3 16:55:16 CET 2013 r...@freebsd-current.lassitu.de:/usr/obj/usr/src/sys/GENERIC amd64 $ pkg info|grep pam pam_ssh_agent_auth-0.9.4 PAM module which permits authentication via ssh-agent $ sudo ls sudo: unable to initialize PAM: No error: 0 If I downgrade to the previous port version (and apply Kimmo's patch), it's working properly. Here's a slightly different error message on 9-stable: $ uname -a FreeBSD diesel.lassitu.de 9.1-STABLE FreeBSD 9.1-STABLE #7 r245996: Sun Jan 27 22:36:05 CET 2013 r...@diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL amd64 stb@diesel:~$ sudo ls sudo: unable to initialize PAM: No such file or directory Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 Latest version pam_ssh_agent_auth-0.9.4_1 seems to finally work without any extra patches when built on a 9.1-RELEASE system. -Kimmo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Poudriere questions
Hello, we use NanoBSD to build the software installations for our hosting platform and I'm trying to better automate the process of building packages. Poudriere looked like an interesting tool to me, so I tried it. Quite painless, but two questions currently remain: To me it looks like Poudriere populates the build jail/chroot from release tarballs fetched from an FTP server - but I'd rather use, say, 8.3p6 as the build platform as well as the one at runtime. At ~300+ installed ports I simply do not know if anything links statically against base system libraries and I want to catch all security updates included in RELENG_X_Y. How would I go about that? Second, how do I specify build time options that are not available via the dialog most ports use for make config? Currently we use an ad hoc shell script that simply installs all the ports I want, and the line for e.g. Apache reads: cd /usr/ports/www/apache22 make -DBATCH -DPROXY=on -DPROXY_HTTP=on -DSUEXEC=on -DSUEXEC_DOCROOT=/var/apache -DSUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install I can enable all options that simply taken an on setting, but what about the paths for suexec? Obviously they are critical to the operation of our servers. If this is the wrong list, I can of course take the discussion to -ports or anything else more appropriate. The Poudriere wiki doesn't mention external ressources besides IRC. Thanks Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Poudriere questions
On 02/20/13 17:08, Patrick M. Hausen wrote: Hello, we use NanoBSD to build the software installations for our hosting platform and I'm trying to better automate the process of building packages. Poudriere looked like an interesting tool to me, so I tried it. Quite painless, but two questions currently remain: To me it looks like Poudriere populates the build jail/chroot from release tarballs fetched from an FTP server - but I'd rather use, say, 8.3p6 as the build platform as well as the one at runtime. At ~300+ installed ports I simply do not know if anything links statically against base system libraries and I want to catch all security updates included in RELENG_X_Y. How would I go about that? I'm not sure I get what you ask. You can make poudriere fetch sources from any subversion branch/tag and compile those, instead of using the distribution files. For example: poudriere jail -c -j 91releng -v releng/9.1 -m svn will fetch sources from the 9.1 security fix branch with all the latest security fixes, compile those and crate a new jail. Second, how do I specify build time options that are not available via the dialog most ports use for make config? Currently we use an ad hoc shell script that simply installs all the ports I want, and the line for e.g. Apache reads: cd /usr/ports/www/apache22 make -DBATCH -DPROXY=on -DPROXY_HTTP=on -DSUEXEC=on -DSUEXEC_DOCROOT=/var/apache -DSUEXEC_LOGFILE=/var/apache/GLOBAL/suexec_log install I can enable all options that simply taken an on setting, but what about the paths for suexec? Obviously they are critical to the operation of our servers. I think your best bet is using customized make.conf files in /usr/local/etc/poudriere.d. This is documented well in the CUSTOMIZATION section of the poudriere(8) man page. for example you could create a file make.conf there with the above options defined and all jails would read it. BTW be aware that ports using OPTINSng will prefer their own syntax for defining their options in make.conf. i.e. OPTIONS_SET+= XFT OPENSSL If this is the wrong list, I can of course take the discussion to -ports or anything else more appropriate. The Poudriere wiki doesn't mention external ressources besides IRC. -- Guido Falsi m...@madpilot.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Poudriere questions
Hello, Am 20.02.2013 um 18:07 schrieb Guido Falsi m...@madpilot.net: I'm not sure I get what you ask. You can make poudriere fetch sources from any subversion branch/tag and compile those instead of using the distribution files. For example: poudriere jail -c -j 91releng -v releng/9.1 -m svn will fetch sources from the 9.1 security fix branch with all the latest security fixes, compile those and crate a new jail. That was precisely what I was looking for - thanks. I think your best bet is using customized make.conf files in /usr/local/etc/poudriere.d. This is documented well in the CUSTOMIZATION section of the poudriere(8) man page. And pray that no other software package besides Apache uses an option named SUEXEC_DOCROOT and I want a different value for that one ... ;-) Is there no way to specify make variables that need values in the port specific options file? But here, too - thanks for the hint. That _should_ work in my case, though it is not generally applicable. Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Poudriere questions
On 02/20/13 18:19, Patrick M. Hausen wrote:
Hello,
Am 20.02.2013 um 18:07 schrieb Guido Falsi m...@madpilot.net:
I'm not sure I get what you ask. You can make poudriere fetch sources from any
subversion branch/tag and compile those
instead of using the distribution files. For example:
poudriere jail -c -j 91releng -v releng/9.1 -m svn
will fetch sources from the 9.1 security fix branch with all the latest
security fixes, compile those and crate a new jail.
That was precisely what I was looking for - thanks.
I think your best bet is using customized make.conf files in
/usr/local/etc/poudriere.d.
This is documented well in the CUSTOMIZATION section of the poudriere(8) man
page.
And pray that no other software package besides Apache uses an option named
SUEXEC_DOCROOT and I want a different value for that one ... ;-)
Is there no way to specify make variables that need values in the port specific
options file?
There is no per port file, but, bbeing make.conf a file sourced by make,
you can use make syntax:
.if ${.CURDIR:M*www/apache22*}
SUEXEC_DOCROOT=/foo/bar
.endif
this will make the variable defined only if working in a patch
containing the string www/apache22. You can be even more stringent with
the matching.
But here, too - thanks for the hint. That _should_ work in my case, though it is
not generally applicable.
Usually putting variables in the make.conf files (or the per jail, per
portstrree or even the per set ones) should be enough in most cases.
--
Guido Falsi m...@madpilot.net
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why can't gcc-4.2.1 build usable libreoffice?
Am 19.02.2013 19:54, schrieb Mikhail T.: These were, indeed, complaints, but not about the port not working after I broke it. My complaint is that, though the port works out of the box, the office@ maintainers have given up on the base compiler too easily -- comments in the makefile make no mention of any bug-reports filed with anyone, for example. It sure seems, no attempts were made to analyze the failures... I don't think, such going with the flow is responsible and am afraid, the inglorious days of building a special compiler just for the office will return... Feel free to debug MyFavouriteOffice to the point where it will build with base GCC, but don't complain if the *office teams don't look at your patches. If there are compiler bugs in gcc 4.2, there is no place where anyone will care for anyone else to file them, not upstream (abandoned 4.2.X years ago), not FreeBSD (decided to switch to clang instead). What is your point, besides getting software from the museum to build stuff from the relative future? LibreOffice's own Native_Build page https://wiki.documentfoundation.org/Development/Native_Build makes no mention of a required compiler version. Unless a compiler is documented to not support a required feature, it is supposed to work. Thus, filing a bug-report with LibreOffice could've been fruitful -- if it is the code, rather than the toolchain, that are at fault... That will likely only buy you the compiler requirement you are currently missing, and it is likely to be the exact version that they used to build their official binaries, with a newer versions may work, but no promises attached. Feel free to query the LibreOffice developers if, and according to which conditions, they'd take your patches to make LO build with our decrepit gcc 4.2.1. Am I really the only one here disturbed by the fact, that the compilers shipped as cc(1) and/or c++(1) in our favorite operating system's most recent stable versions (9.1 and 8.3) are considered buggy? Not just old -- and thus unable to process more modern language-standards/features, but buggy -- processing those features incorrectly? There is certainly nothing in our errata http://www.freebsd.org/releases/9.1R/errata.html about it... You have not yet proven that either the base compilers or LibreOffice are at fault. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
messed up my ports somehow
I was having problems with broken missing dependencies, etc. Long story short I fixed it by wiping a lot of stuff and reinstalling it, but now portmaster does not seem to be working. running portmaster -l lists none of the installed ports. Any ideas on how to fix it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: messed up my ports somehow
What about either of these 2 ? pkg_info pkg info On Feb 20, 2013, at 8:14 PM, Craig Yoshioka crai...@nanoimagingservices.com wrote: I was having problems with broken missing dependencies, etc. Long story short I fixed it by wiping a lot of stuff and reinstalling it, but now portmaster does not seem to be working. running portmaster -l lists none of the installed ports. Any ideas on how to fix it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: messed up my ports somehow
Then, I'm taking a wild guess at what I think is happening. You have WITH_PKGNG=yes in /etc/make.conf Your portmaster is built without the PKGNG patch. Would you go to /usr/ports/ports-mgmt/portmaster/ then issue 'make config' If I'm right, you're only missing the patch, tick the option and issue: make clean make make deinstall make reinstall On Feb 20, 2013, at 8:22 PM, Craig Yoshida crai...@scripps.edu wrote: pkg_info lists no packages pkg info seems to list them all. --- Craig Yoshioka, Ph.D. (619) 623-2233 (cell) The Scripps Research Institute 10550 N. Torrey Pines Rd. La Jolla, CA 92037 On Feb 20, 2013, at 11:15 AM, Fleuriot Damien m...@my.gd wrote: What about either of these 2 ? pkg_info pkg info On Feb 20, 2013, at 8:14 PM, Craig Yoshioka crai...@nanoimagingservices.com wrote: I was having problems with broken missing dependencies, etc. Long story short I fixed it by wiping a lot of stuff and reinstalling it, but now portmaster does not seem to be working. running portmaster -l lists none of the installed ports. Any ideas on how to fix it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
watchdogs
Hi. I have a bunch of FreeBSDs that hangs (and I really want to do something to fight this). May be it's the zfs or may be it's the pf (I also have a bunch of really stable ones, so it's hard to isolate and tell). Since 9.x hang more often I suppose it's pf. I use ichwd.ko and watchdogd to reboot a machine when it hangs. It works pretty well; I'm also working on a various WITNESS/INVARIANTS stuff and I'm trying to report it to gnats, but obviously it would be much nicer if the system would panic and leave some debuggable core after a hang (so far I don't have any, so I can only guess). I've read about software watchdog in kernel and I doesn'y quite understand: it's said that kernel software watchdog is able to panic when a deadlock occurs. Can this be achieved with ichwd ? Another one: as far as I understand ichwd reboots my machine on a hardware level, right ? So am I right saying that software watchdog can be, in theory, also deadlocked, thus, being kinda less reliable solution ? Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: watchdogs
On 2/20/13 11:36 AM, Eugene M. Zheganin wrote: Hi. I have a bunch of FreeBSDs that hangs (and I really want to do something to fight this). May be it's the zfs or may be it's the pf (I also have a bunch of really stable ones, so it's hard to isolate and tell). Since 9.x hang more often I suppose it's pf. I use ichwd.ko and watchdogd to reboot a machine when it hangs. It works pretty well; I'm also working on a various WITNESS/INVARIANTS stuff and I'm trying to report it to gnats, but obviously it would be much nicer if the system would panic and leave some debuggable core after a hang (so far I don't have any, so I can only guess). I've read about software watchdog in kernel and I doesn'y quite understand: it's said that kernel software watchdog is able to panic when a deadlock occurs. Can this be achieved with ichwd ? Another one: as far as I understand ichwd reboots my machine on a hardware level, right ? So am I right saying that software watchdog can be, in theory, also deadlocked, thus, being kinda less reliable solution ? Yes all your assumptions are correct. There is an 'enhanced watchdog' branch that I am working on that offers a pre-watchdog timeout panic. However since this is done via the software you may not get your pre-timeout panic and only have a reboot. Later revisions may include facilities for generating NMI to trigger panic/logs and the followed by a hard reset by external hardware. Perhaps ichwd offers ability to send NMI? Let me check sources. -Alfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: messed up my ports somehow
fixed you, sir, are a rock star. --- Craig Yoshioka, Ph.D. (619) 623-2233 (cell) The Scripps Research Institute 10550 N. Torrey Pines Rd. La Jolla, CA 92037 On Feb 20, 2013, at 11:24 AM, Fleuriot Damien m...@my.gdmailto:m...@my.gd wrote: Then, I'm taking a wild guess at what I think is happening. You have WITH_PKGNG=yes in /etc/make.conf Your portmaster is built without the PKGNG patch. Would you go to /usr/ports/ports-mgmt/portmaster/ then issue 'make config' If I'm right, you're only missing the patch, tick the option and issue: make clean make make deinstall make reinstall On Feb 20, 2013, at 8:22 PM, Craig Yoshida crai...@scripps.edumailto:crai...@scripps.edu wrote: pkg_info lists no packages pkg info seems to list them all. --- Craig Yoshioka, Ph.D. (619) 623-2233 (cell) The Scripps Research Institute 10550 N. Torrey Pines Rd. La Jolla, CA 92037 On Feb 20, 2013, at 11:15 AM, Fleuriot Damien m...@my.gdmailto:m...@my.gd wrote: What about either of these 2 ? pkg_info pkg info On Feb 20, 2013, at 8:14 PM, Craig Yoshioka crai...@nanoimagingservices.commailto:crai...@nanoimagingservices.com wrote: I was having problems with broken missing dependencies, etc. Long story short I fixed it by wiping a lot of stuff and reinstalling it, but now portmaster does not seem to be working. running portmaster -l lists none of the installed ports. Any ideas on how to fix it? ___ freebsd-stable@freebsd.orgmailto:freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.orgmailto:freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.orgmailto:freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.orgmailto:freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why can't gcc-4.2.1 build usable libreoffice?
On 2013-Feb-19 09:23:37 -0500, Mikhail T. mi+t...@aldan.algebra.com wrote: See, my understanding always was, the only possible reasons for a compiler to produce a non-starting executable are: 1. The code is buggy. 2. The compiler is buggy. 3. Both of the above. My question was, which is it? You left out: 4. Code relies on language features that are not supported by the compiler. (It's not a bug that gcc 4.2.1 (eg) doesn't suppert C++11) 5. Code relies on specific compiler features Feel free to answer your own question if it's important to you. No-one else is particularly interested. Yes, 4.6 is supposed to work and is supported by the office@ team. My question was about 4.2.1, which happens to be the base cc/c++ in 8.x and in 9.x as well, if world was built WITHOUT_CLANG. I too observe the 4.2.1-compiled office die at start-up -- the splash screen starts nicely and exits after kicking off the actual soffice.bin which segfaults. As others have indicated, the toolchain provided in the base system is intended only for building the base system. If it works for you for other purposes, that's good. If you believe it has bugs, feel free to submit PRs. If the bugs don't affect the base system, they are unlikely -- Peter Jeremy pgpzlf8YtE7jb.pgp Description: PGP signature
Re: Poudriere questions
Hi, Guido,
Am 20.02.2013 um 18:28 schrieb Guido Falsi m...@madpilot.net:
Is there no way to specify make variables that need values in the port
specific
options file?
There is no per port file, but, bbeing make.conf a file sourced by make, you
can use make syntax:
.if ${.CURDIR:M*www/apache22*}
SUEXEC_DOCROOT=/foo/bar
.endif
That will not just do fine, but really great. Since I have only one target
platform
to build for, a central place to keep configuration is preferred, anyway.
Though I'm a seasoned admin, I did not know make was that capable. So two
reasons to say thanks. Case closed. ;-)
Kind regards,
Patrick
--
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de http://www.punkt.de
Gf: Jürgen Egeling AG Mannheim 108285
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
SOLVED Re: messed up my ports somehow
Glad I could help :) On 20 Feb 2013, at 21:00, Craig Yoshida crai...@scripps.edu wrote: fixed you, sir, are a rock star. --- Craig Yoshioka, Ph.D. (619) 623-2233 (cell) The Scripps Research Institute 10550 N. Torrey Pines Rd. La Jolla, CA 92037 On Feb 20, 2013, at 11:24 AM, Fleuriot Damien m...@my.gd wrote: Then, I'm taking a wild guess at what I think is happening. You have WITH_PKGNG=yes in /etc/make.conf Your portmaster is built without the PKGNG patch. Would you go to /usr/ports/ports-mgmt/portmaster/ then issue 'make config' If I'm right, you're only missing the patch, tick the option and issue: make clean make make deinstall make reinstall On Feb 20, 2013, at 8:22 PM, Craig Yoshida crai...@scripps.edu wrote: pkg_info lists no packages pkg info seems to list them all. --- Craig Yoshioka, Ph.D. (619) 623-2233 (cell) The Scripps Research Institute 10550 N. Torrey Pines Rd. La Jolla, CA 92037 On Feb 20, 2013, at 11:15 AM, Fleuriot Damien m...@my.gd wrote: What about either of these 2 ? pkg_info pkg info On Feb 20, 2013, at 8:14 PM, Craig Yoshioka crai...@nanoimagingservices.com wrote: I was having problems with broken missing dependencies, etc. Long story short I fixed it by wiping a lot of stuff and reinstalling it, but now portmaster does not seem to be working. running portmaster -l lists none of the installed ports. Any ideas on how to fix it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why can't gcc-4.2.1 build usable libreoffice?
20.02.2013 15:41, Peter Jeremy ???(??): You left out: 4. Code relies on language features that are not supported by the compiler. (It's not a bug that gcc 4.2.1 (eg) doesn't suppert C++11) If a compiler does not support a feature, it is supposed to error-out upon encountering it, not generate invalid code. If this was, in fact, the reason for the problem, it would've been a compiler bug. 5. Code relies on specific compiler features Depending on what you mean by compiler features here, this is simply a duplicate of either your own 4 or my 1. Feel free to answer your own question if it's important to you. No-one else is particularly interested. Is that why you decided to chime-in? Because you are not particularly interested? Maybe, you should've remained outside this lovely discussion, if this was really true? Jung-uk Kim answered my question, though. As others have indicated, the toolchain provided in the base system is intended only for building the base system. This was never true before and it is rather sad, if it were really becoming the truth now. More than likely, though, this is just a cheap excuse. Kind of like: you did not pay for the code, did you, so don't expect it to work. -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why can't gcc-4.2.1 build usable libreoffice?
On 20 February 2013 13:53, Mikhail T. mi+t...@aldan.algebra.com wrote: As others have indicated, the toolchain provided in the base system is intended only for building the base system. This was never true before and it is rather sad, if it were really becoming the truth now. More than likely, though, this is just a cheap excuse. Kind of like: you did not pay for the code, did you, so don't expect it to work. That's because of a mad dash for new C/C++ functionailty post 4.2 which also happened to coincide with a licence change to GPLv3. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why can't gcc-4.2.1 build usable libreoffice?
On 2/20/13, Matthias Andree matthias.and...@gmx.de wrote: What is your point, besides getting software from the museum to build stuff from the relative future? I can't speak for the OP, but I tried it because clang, gcc46, and gcc47 wouldn't produce a working executable at all for a long time (and continue to fail) on my 9.0 and 9.1 systems. There's been so much libreoffice breakage that I don't even bother reporting it or making much effort to fix it. I just reboot to Windows for the cases where I need a working libreoffice. I don't much care whether gcc 4.2 produces a working libreoffice; I just wish something did. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?
On 17 Feb, Torfinn Ingolfsen wrote: Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo@kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-quiet$ dmesg | grep CPU | head -1 CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics(3618.02-MHz K8-class CPU) Unfortunately, the amdtemp.ko module doesn't work: tingo@kg-quiet$ kldstat | grep temp 101 0x8123e000 f0f amdtemp.ko tingo@kg-quiet$ sysctl dev.amdtemp sysctl: unknown oid 'dev.amdtemp' Based on a thread[1] on the forums, amdtemp.c from -CURRENT work. But it doesn't compile under FreeBSD 8.3-stable: Updating amdtemp is on my TODO list. It has some issues even on -CURRENT. This is kind of far down my priority list because on most of my AMD machines, I can also get the temperature without amdtemp: % sysctl hw.acpi.thermal.tz0.temperature hw.acpi.thermal.tz0.temperature: 30.0C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?
On Wed, Feb 20, 2013 at 10:29:05PM -0800, Don Lewis wrote: On 17 Feb, Torfinn Ingolfsen wrote: Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo@kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-quiet$ dmesg | grep CPU | head -1 CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics(3618.02-MHz K8-class CPU) Unfortunately, the amdtemp.ko module doesn't work: tingo@kg-quiet$ kldstat | grep temp 101 0x8123e000 f0f amdtemp.ko tingo@kg-quiet$ sysctl dev.amdtemp sysctl: unknown oid 'dev.amdtemp' Based on a thread[1] on the forums, amdtemp.c from -CURRENT work. But it doesn't compile under FreeBSD 8.3-stable: Updating amdtemp is on my TODO list. It has some issues even on -CURRENT. This is kind of far down my priority list because on most of my AMD machines, I can also get the temperature without amdtemp: % sysctl hw.acpi.thermal.tz0.temperature hw.acpi.thermal.tz0.temperature: 30.0C There's an implication in your statement here, so I want to clarify for readers (as the author of sysutils/bsdhwmon): acpi_thermal(4) does not necessarily tie in to an on-die DTS within the CPU. Your motherboards and CPUs (both matter! (e.g. for Intel CPUs, see PECI (not a typo)) may offer this tie-in, but such is not the case for many people. I tend to find ACPI thermal zones used in laptops and very rarely anywhere else. acpi_thermal(4) may return temperatures from zones that are mapped to readings from Super I/O chips or dedicated H/W monitoring ICs (such as ones provided by Nuvuton/Winbond, LM, ITE, ADT, etc.). It all depends on how the BIOSes ACPI tables are written/what maps to what. Such ICs DO NOT have anything to do with the on-die DTS which both amdtemp(4) and coretemp(4) use -- instead, these chips use external thermistors which may be placed anywhere on the motherboard (such as under the CPU socket, or wherever the manufacturer chooses (and more often than not, does not document)). My point: under the CPU thermistor != within the CPU DTS. They measure two different things, and are not guaranteed to be even remotely similar. I can show proof of this (a very large delta between Core i5 core DTSes and an on-board IT87xxx) if requested. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
