Re: TeXLive
Similar question. I tried to install the texlive-xetex. The installation is successful, but there is no .fmt files installed. On Sun, Oct 9, 2011 at 9:58 PM, Stephen Montgomery-Smith step...@missouri.edu wrote: Hey guys, I did make -C /usr/ports/ports-mgmt/**portshaker-config install # Ensure TEXLIVE is checked portshaker -v Now I have a whole bunch of texlive ports installed under /usr/ports/print. Am I just supposed to build the ports I need, or is there some grand texlive-build-all port that is in this long list somewhere? __**_ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@freebsd.org -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
On Sun, Oct 09, 2011 at 09:58:50PM -0500, Stephen Montgomery-Smith wrote: Now I have a whole bunch of texlive ports installed under /usr/ports/print. Am I just supposed to build the ports I need, or is there some grand texlive-build-all port that is in this long list somewhere? I updated this page: http://code.google.com/p/freebsd-texlive/wiki/Installing You should at least install texlive-scheme-minimal but if you don't know exactly what you need, you may consider texlive-scheme-full ;-) Regards, Romain -- Romain Tartière rom...@blogreen.orghttp://romain.blogreen.org/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) pgpGB3s5Kxjyg.pgp Description: PGP signature
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/161455multimedia/transcode should depend on ffmpeg o ports/161442[MAINTAINER] devel/gps: Update to version 5.0.1 o ports/161441New port: databases/4store o ports/161440[NEW PORT] devel/libk8055: Velleman K8055 USB experime o ports/161437devel/bmake: update to 20111001 snapshot o ports/161427[MAINTAINER] textproc/xmlada: Update to version 4.2.0. o ports/161426math/gotoblas-2.1.13_2 fails to build (segmentation fa o ports/161423[UPDATE] update 3 Pure language's modules o ports/161422New port: math/pure-rational - Rational number library o ports/161420[patch] [new port] graphics/mapnik: update to 2.0.0 o ports/161415audio/lmms port upgrade to 0.4.12 f ports/161406[PATCH] net-mgmt/netdisco: update to 1.1 o ports/161405[patch] [maintainer] net/openafs: catch up to sys_ ker f ports/161403net/libtcp4u: Fix double colon on do-configure target o ports/161399Update port multimedia/cx88 to 1.4.1 o ports/161395New port: sysutils/mcelog o ports/161392[MAINTAINER UPDATE] Update devel/tortoisehg2 o ports/161379security/openssl compile error caused by abbreviated-r f ports/161366net/openafs doesn't install on 9-BETA3 o ports/161351Revised Port: www/web-traceroute o ports/161346[NEW PORT] emulators/kcemu v0.5.1 f ports/161338[patch] update x11-toolkits/swt to 3.7 o ports/161334[patch] sysutils/monit rc.d script is run too soon o ports/161302[patch] math/giacxcas update to 0.9.3 f ports/161301[PATCH] databases/cassandra: update to 0.8.6 f ports/161299science/paraview: CLANG: Linking CXX shared library . o ports/161288[New port] www/linux-flashplugin11 f ports/161271[patch] x11/cl-clx: loading with clozure fails, dep-op o ports/161268sysutils/fusefs-ntfs fails to mount ntfs invalid argu f ports/161244[PATCH] audio/libmikmod: fix failed patching o ports/161239Graphics/pgplot fails to build w/gcc46 o ports/161231[NEW PORT] www/sencha-touch: The First HTML5 Mobile We o ports/161226security/fprint_demo: Updates to last git version o ports/161225security/pam_fprint: Updates to the last git version o ports/161218Update x11-toolkits/swt-devel to version 3.6.2 o ports/161213cad/astk-client clean fails o ports/161191[UPDATE] devel/z80ex to v1.1.19 o ports/161167security/botan configure does not work with python 3.1 f ports/161152deskutils/parcellite: update to version 1.0.1 o ports/161146maintainer of textproc/tex2im o ports/161145maintainer of games/xgalaga o ports/161139restore sysutils/gpart o ports/161131net/heybuddy 0.2.1 - 0.2.2 f ports/161119Update textproc/lucene to version 3.4.0 f ports/161117[patch] games/sl fix build under clang o ports/161106sysutils/openipmi is dropping core o ports/161095[patch] extra-patch-xclient updated for exim-4.76 f ports/161085Update security/metasploit port o ports/161081[patch] request change of maintainer due to timeout f ports/161072update mail/davmail to 3.9.4 o ports/161070infinite loop for graphics/xfig on 9.0-CURRENT o ports/161034[NEW PORT] databases/ocaml-mysql: OCaml bindings to li o ports/161027Update security/dradis to 2.7.2 f ports/161020Update security/unssh to 1.5 f ports/161005graphics/geos: CLANG : for functional-style cast from o ports/161004version update of sysutils/ldap-account-manager f ports/160991net/opennx : Unexpected termination of nxssh f ports/160969[patch] sysutils/zfs-snapshot-mgmt: embed ruby version o ports/160962NEW PORT: mail/spamdb-curses Curses interface for Open f ports/160927lang/gauche: needs upgrade f ports/160891[UPDATE]: audio/qmpdclient Update to new release, 1.2. o ports/160882Update to the www/fusionpbx port to 2.0.9 o ports/160881update to misc/freeswitch-scripts port o ports/160879Update to net/freeswitch-core port o ports/160870www/mod_security port not updated o ports/160861New port: security/racoon-tool Manage setkey and racoo o
Current problem reports assigned to po...@freebsd.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. No matches to your query ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/chicken, fails to package, needs MAKE_JOBS_UNSAFE
Doug Barton wrote: Also, once it got built, it failed to package: === Building package for chicken-4.7.0 tar: lib/chicken/6/modules.db: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Stop in /usr/ports/lang/chicken. Seems to work for me on 8.2-RELEASE amd64. Can you send me your build/install/package logs? I'll try to reproduce the problem. Sure, here you go: http://people.freebsd.org/~dougb/chicken-build.log FYI, I did some more testing and it only fails on i386. I confirmed your experience that it works fine on 8-amd64. Doug, is there something peculiar about your i386 box? I tested on my laptop and on a clean VirtualBox setup (both 8.2-RELEASE, i386); in both cases the installation (and make package) work fine. Can you show a list of the installed ports on your system? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
I updated this page: http://code.google.com/p/freebsd-texlive/wiki/Installing Are there any plans on getting these committed to the mainline ports tree? I'd be willing to work with you on that. You should at least install texlive-scheme-minimal but if you don't know exactly what you need, you may consider texlive-scheme-full ;-) Regards, Romain -- Romain Tartière rom...@blogreen.org http://romain.blogreen.org/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
On 10/10/2011 03:29 AM, Romain Tartière wrote: On Sun, Oct 09, 2011 at 09:58:50PM -0500, Stephen Montgomery-Smith wrote: Now I have a whole bunch of texlive ports installed under /usr/ports/print. Am I just supposed to build the ports I need, or is there some grand texlive-build-all port that is in this long list somewhere? I updated this page: http://code.google.com/p/freebsd-texlive/wiki/Installing You should at least install texlive-scheme-minimal but if you don't know exactly what you need, you may consider texlive-scheme-full ;-) That is exactly what I need! Next, tlmgr doesn't work. ls -l /usr/local/bin/tlmgr lrwxr-xr-x 1 root wheel 33 Oct 10 03:35 /usr/local/bin/tlmgr - ../texmf/scripts/texlive/tlmgr.pl I'm sure that should be ../share/texmf/scripts/texlive/tlmgr.pl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
On 10/10/2011 06:44 AM, Eitan Adler wrote: Are there any plans on getting these committed to the mainline ports tree? I'd be willing to work with you on that. I agree with Eitan. I don't see a reason why texlive shouldn't make it into the mainstream ports. What you need is to work with someone with a ports commit bit, and who is willing to take some responsibility to perform updates in a timely manner (because submitting PR's can take quite a while). Eitan has a ports commit bit, as do I. Since Eitan asked first, he gets first dibs, but I am willing to play that role as well. Stephen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
On 10/10/2011 07:23 AM, Stephen Montgomery-Smith wrote: On 10/10/2011 06:44 AM, Eitan Adler wrote: Are there any plans on getting these committed to the mainline ports tree? I'd be willing to work with you on that. I agree with Eitan. I don't see a reason why texlive shouldn't make it into the mainstream ports. What you need is to work with someone with a ports commit bit, and who is willing to take some responsibility to perform updates in a timely manner (because submitting PR's can take quite a while). Eitan has a ports commit bit, as do I. Since Eitan asked first, he gets first dibs, but I am willing to play that role as well. Stephen And Romain, I see that you have a commit bit as well! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: firefox 7.0.1
ajtiM wrote on 09.10.2011 15:19: Hi! I have Firefox 7.0.1 installed but no one of plugins work which I didn't have a proble before. I made in /usr/local/lib/firefox dorectory plugins and made a symlink from /usr/local/lib/web_browser/plugins but doesn't works. One of the plugins is gnash plugin which I use for youtube. Hi, Mitja. I'm sorry if i telling something obvious, but when i used firefox as my main browser, i was able to see youtube by enabling html5 option in my profile - http://youtube.com/html5. It worked in most (but not all) cases for me. -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: TeXLive
On 10/10/11 07:23, Stephen Montgomery-Smith wrote: On 10/10/2011 06:44 AM, Eitan Adler wrote: Are there any plans on getting these committed to the mainline ports tree? I'd be willing to work with you on that. I agree with Eitan. I don't see a reason why texlive shouldn't make it into the mainstream ports. Also, someone might object that it introduces 2000 ports into the print category. But as a counterargument, www and devel have similar numbers of ports. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Oddness building Quassel with v9.0
Hello! I am running 64bit PC-BSD v9.0beta3 (updated from beta2), originally installed from USBFULL 9.0beta2. I have tried to do a pbi_makeport of Quassel to obtain the monolithic build of Quassel. I did my best to instigate this desired outcome by using the pbi.conf file with the appropriate options. No matter what I did, I could not gain the 'monolithic' Quassel as a result but it seems to be a relatively complex issue. What I have discovered (to me) is certainly odd. I have successfully built the Quassel 'monolithic' version as a port, but if I attempt to run Quassel (monolithic) as my normal user, what seems to appear is the client rather than the monolithic which reports Disconnected from core and the output to shell as below: [tigersharke@Mutant] /usr/ports/irc/quassel quassel [1] 96992 [tigersharke@Mutant] /usr/ports/irc/quassel 2011-10-08 16:21:53 Warning: SslServer: Certificate file /home/tigersharke/.config/ quassel-irc.org/quasselCert.pem does not exist 2011-10-08 16:21:53 Warning: SslServer: Unable to set certificate file Quassel Core will still work, but cannot provide SSL for client connections. Please see http://quassel-irc.org/faq/cert to learn how to enable SSL support. 2011-10-08 16:21:53 Warning: SslServer: Certificate file /home/tigersharke/.config/quassel-irc.org/quasselCert.pem does not exist (QSQLITE, QSQLITE3, QMYSQL3, QMYSQL) Core is currently not configured! Please connect with a Quassel Client for basic setup. Unable to open database SQLite for thread QThread(0x80c01b8d0) - unable to open database file Error opening database QSqlDatabasePrivate::database: unable to open database: unable to open database file Error opening database Selected storage backend is not available: SQLite Core::setupInternalClientSession(): You're trying to run monolithic Quassel with an unusable Backend! Go fix it! [1]Done quassel [tigersharke@Mutant] /usr/ports/irc/quassel When I try to run the monolithic Quassel as root (which of course I should not), it works and I get the following output in the shell: [tigersharke@Mutant] /usr/ports/irc/quassel# quassel [1] 99917 [tigersharke@Mutant] /usr/ports/irc/quassel# Error: /var/tmp/kdecache-tigersharke is owned by uid 1001 instead of uid 0. 2011-10-08 16:38:39 Warning: SslServer: Certificate file /home/tigersharke/.config/quassel-irc.org/quasselCert.pem does not exist 2011-10-08 16:38:39 Warning: SslServer: Unable to set certificate file Quassel Core will still work, but cannot provide SSL for client connections. Please see http://quassel-irc.org/faq/cert to learn how to enable SSL support. 2011-10-08 16:38:39 Warning: SslServer: Certificate file /home/tigersharke/.config/quassel-irc.org/quasselCert.pem does not exist (QSQLITE, QSQLITE3, QMYSQL3, QMYSQL) 2011-10-08 16:38:39 Info: SQLite Storage Backend is ready. Quassel Schema Version: 17 2011-10-08 16:38:39 Info: Restoring previous core state... [1]Done quassel [tigersharke@Mutant] /usr/ports/irc/quassel# Building Quassel from ports with v8.2 was not a problem. I could build the monolithic version and then run it as my normal user. However, I did not attempt building a Quassel PBI with PC-BSD v8.2. Thank you for your time and effort! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Current problem reports assigned to po...@freebsd.org
It's been quite a few weeks that this empty/pointless message has been sent to the list, what needs to happen to make it stop? On 10/10/2011 04:08, FreeBSD bugmaster wrote: Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. No matches to your query ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- 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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/cross-gcc and cross-binutils: how to set TGTARCH and TGTABI
On Sat, 8 Oct 2011 09:51:00 + (GMT) Thomas Mueller mueller6...@bellsouth.net mentioned: You cannot use this port to build toolchaing for compiling Linux and NetBSD applications. This port creates toolchain using the newlib libc library, which is used by some embedded operating systems (e.g. rtems, ecos). It can also be used to build bare-metal standalone applications. Linux on the other hand is using glibc and NetBSD their own libc implementation, so this toolchain would not work. Stanislav Sedov Thanks for clarification. What you say was not obvious from the pkg-descr. Now I will know one blind alley to avoid in cross-compiling for Linux and NetBSD. What is your target? Do you just want to cross-build the Linux and NetBSD kernels, or userland applications? For Linux we can probably try to add a port that uses glibc instead of newlib. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Current problem reports assigned to po...@freebsd.org
On Mon, Oct 10, 2011 at 3:22 PM, Doug Barton do...@freebsd.org wrote: It's been quite a few weeks that this empty/pointless message has been sent to the list, what needs to happen to make it stop? Assign bugs to ports@ - then it won't be empty anymore. -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Current problem reports assigned to po...@freebsd.org
On 10/10/2011 14:48, Eitan Adler wrote: On Mon, Oct 10, 2011 at 3:22 PM, Doug Barton do...@freebsd.org wrote: It's been quite a few weeks that this empty/pointless message has been sent to the list, what needs to happen to make it stop? Assign bugs to ports@ - then it won't be empty anymore. There is already freebsd-ports-bugs, and there is already a report generated for that. A report for ports@ is worse than useless. -- 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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
net/nss-pam-ldapd breaks top(1) on 8.2/i386
I've recently started using net/nss-pam-ldapd (0.7.13_2). The systems on which it is deployed are all i386, either 8.2-RELEASE or recent 8-STABLE. It works well for me except that it breaks top(1) - obviously at the point where top translates uid's to names. Forcing top(1) to skip the uid/username translation with 'top -u' keeps top(1) happy; but without passing -u, top(1) segfaults as shown below. Thus far top(1) appears to be the only utility affected: other utilities like finger(1), getent(1) and id(1) are fine; login and general work via console, sshd or X all work fine. My /etc/nsswitch.conf files include the following. Removing 'ldap' from the 'passwd' line makes top(1) happy but, of course, only local uid's resolve in that case. group: files ldap passwd: files ldap I have tried stripping /usr/local/etc/nslcd.conf all the way back to just the following 3 lines to rule out any other custom configuration but top(1) still dies (but, hey, this proves that the config defaults are magic). uid nslcd gid nslcd uri DNS Here is what top(1) does. Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...(no debugging symbols found)...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2820eef9 in __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 (gdb) bt #0 0x2820eef9 in __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 #1 0x2820b60f in _nss_ldap_getpwent_r () from /usr/local/lib/nss_ldap.so.1 #2 0x28125815 in __nss_compat_getpwent_r () from /lib/libc.so.7 #3 0x281b1aad in nsdispatch () from /lib/libc.so.7 #4 0x2819fcaa in getpwent_r () from /lib/libc.so.7 #5 0x2819fcf3 in getpwent_r () from /lib/libc.so.7 #6 0x2819f794 in acl_get_brand_np () from /lib/libc.so.7 #7 0x2819f84b in getpwent () from /lib/libc.so.7 #8 0x0804e51b in ?? () #9 0x08051cc6 in ?? () #10 0x08055360 in optind () #11 0xbfbfe808 in ?? () #12 0x in ?? () #13 0x in ?? () #14 0xbfbfe978 in ?? () #15 0x28054639 in ?? () from /libexec/ld-elf.so.1 #16 0x2808f000 in ?? () #17 0x0120 in ?? () #18 0x0054 in ?? () #19 0x0004 in ?? () #20 0x in ?? () #21 0x0002 in ?? () #22 0x in ?? () #23 0xbfbfe978 in ?? () #24 0x0804f594 in winch () Previous frame identical to this frame (corrupt stack?) (gdb) q If I'm the only one seeing this, can anybody spot what I'm doing wrong? This looks a lot like what I found in a thread in -stable@ from January 2010 which was seen on 8.0/amd64, but the fix proffered there is already applied in the version of the port I'm using. http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054379.html Thanks. -- John Marshall pgpf4VuQyQoTN.pgp Description: PGP signature
