Re: How to get portinstall to 'shut up' so I can run it in background
Doug Barton wrote: Ben Kelly wrote: Maybe I am doing something wrong, but I have never been able to get nohup to work correctly with portupgrade for this sort of this. For example: ianto# nohup portupgrade -a >& /tmp/port.log & You just want to do 'nohup portupgrade -a &' output will be captured in nohup.out. Ben is right. When you run portupgrade with nohup and background the process -- either with '&' or by ctrl-z followed with a bg -- it gets suspended until the job is brought back to the foreground. Portupgrade acts very strangely when it's not attached to a tty. -- Russell A. Jackson <[EMAIL PROTECTED]> Network Analyst California State University, Bakersfield He asked me if I knew what time it was -- I said yes, but not right now. -- S. Wright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: All those 'Ports System Re-engrg" posts
On Tue, Dec 04, 2007 at 11:06:32PM -0800, Jason C. Wells wrote: > I seem to recall Jordan writing that the ports system was never > intended to last as long as it did. I think he said the same thing > about sysinstall. He was probably correct in both cases. However, we have this "userbase" thing to think about at the moment ... mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: All those 'Ports System Re-engrg" posts
Chuck Robey wrote: >>Seeing as no one here who has the ability to do the job also still has >>enough innocence to get snagged into it Teehee! Mark Linimon wrote: He lost me around the "these days, the horsepower to rebuild ports is easily available." He clearly has not idea, whatsoever, of what the current work is. My recent attempts to deal with port management in my own unique (foolish?) way has me considering this conclusion. Let FreeBSD do all the work by taking advantage of binary package installs. Then do my custom patched stuff later. I'm sort of scratching my head as to why I have been rolling my own all these years. (mumble grumble Kerberos mumble grumble) Frankly I am amazed that you can build a large chunk of thousands of ports. Ports have weathered the decade pretty well. I seem to recall Jordan writing that the ports system was never intended to last as long as it did. I think he said the same thing about sysinstall. Later, Jason ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get portinstall to 'shut up' so I can run it in background
Ben Kelly wrote: > Maybe I am doing something wrong, but I have never been able to get > nohup to work correctly with portupgrade for this sort of this. For > example: > > ianto# nohup portupgrade -a >& /tmp/port.log & You just want to do 'nohup portupgrade -a &' output will be captured in nohup.out. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get portinstall to 'shut up' so I can run it in background
Doug Barton wrote: On Mon, 3 Dec 2007, Wes Morgan wrote: On Tue, 4 Dec 2007, Stefan Sperling wrote: Screen also has log functionality. Toggle with: Ctrl+A, then Shift+H You can also use "script" to capture the output fairly easily. So you have to use two different programs, one of which is a port, to accomplish what nohup will do by itself. :) My point being that a lot of people seem to think that screen(1) is the answer, no matter what the question, when often simpler answers exist. If you're one of those people, that's fine, I learned a long time ago I'm not going to change your mind. But I do think it's useful to note that there are other valid solutions, even if simply for completeness sake. Maybe I am doing something wrong, but I have never been able to get nohup to work correctly with portupgrade for this sort of this. For example: ianto# nohup portupgrade -a >& /tmp/port.log & [1] 6238 ianto# [1] + Suspended (tty output)portupgrade -a >& /tmp/port.log ianto# ianto# cat /tmp/port.log ianto# I've never had time to figure out why it suspends, though. Anyone know? Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: has FreeBSD's libc been swigged?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck Robey wrote: > Need to do some python work, using a lot of FreeBSD's base libs, and I > was wondering, if any ports have swigged the FreeBSD libs? I'll do it > if I must, just trying to save me some work. py-freebsd? - -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHViD7hcUczkLqiksRAqEKAJ9Ix2KGCPVn6UjD6V9PLFqHz/l7ZACdFVsS Us6bZAMRLkE8BqyAZBjcasQ= =qobz -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
some general comments on my re-engineering project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 One of the people who gave me the hardest time was able to tell me in a way that was clear to me what his issue with how I presented stuff was (privately)... since I am not a mind reader I don't know how prevalent this among the other people who gave me a hard time on the survey... the purposes of this post is to clarify some of the things that I never meant to imply or appear to be asking for in the survey or my defense of it. 1. I *NEVER* meant or intended to be asking for any kind of "permission" to undertake (or not undertake) the project from the larger FreeBSD community I was only attempting to collect data to double check my own personal intuition as to what features/issues needed to be addressed if an when such a project goes beyond the "neat idea" stage 2. I was not attempting to say mine was the only "true" way or that it even made sense to incorpate any of my ideas into any aspect of FreeBSD (even after the coding is done) 3. Unlike the majority of the FreeBSD community (it seems) I believe in early and frequent user involvment in system development and that was my one and only goal with the survey (and a few follow ups I have in mind) 4. The reason for not releasing any of the survey results is not to "play" games but to avoid the "california presidential election syndrom" (people do not vote because the networks have already called the election) - -- Aryeh M. Friedman FloSoft Systems Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHVg6S358R5LPuPvsRAtagAKCzBxx5eeMQQOSpbqK6arFh/NWMhwCg0piF aFl44Y3O6GQsjqzgJEyU3Uk= =1mC3 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get portinstall to 'shut up' so I can run it in background
On Tue, 4 Dec 2007, Doug Barton wrote: On Mon, 3 Dec 2007, Wes Morgan wrote: On Tue, 4 Dec 2007, Stefan Sperling wrote: Screen also has log functionality. Toggle with: Ctrl+A, then Shift+H You can also use "script" to capture the output fairly easily. So you have to use two different programs, one of which is a port, to accomplish what nohup will do by itself. :) My point being that a lot of people seem to think that screen(1) is the answer, no matter what the question, when often simpler answers exist. If you're one of those people, that's fine, I learned a long time ago I'm not going to change your mind. But I do think it's useful to note that there are other valid solutions, even if simply for completeness sake. Actually, I was educated on "nohup", so don't consider it a total waste :). I just personally don't start a terminal without also running screen. However, nohup is in the base system, so it is clearly a more available solution. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get portinstall to 'shut up' so I can run it in background
On Mon, 3 Dec 2007, Wes Morgan wrote: On Tue, 4 Dec 2007, Stefan Sperling wrote: Screen also has log functionality. Toggle with: Ctrl+A, then Shift+H You can also use "script" to capture the output fairly easily. So you have to use two different programs, one of which is a port, to accomplish what nohup will do by itself. :) My point being that a lot of people seem to think that screen(1) is the answer, no matter what the question, when often simpler answers exist. If you're one of those people, that's fine, I learned a long time ago I'm not going to change your mind. But I do think it's useful to note that there are other valid solutions, even if simply for completeness sake. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: net/freeradius - fixed for RELENG_7 amd64 and 6.x with gcc 4.2
On Tue, 4 Dec 2007, David Wood wrote: (ade@ cc'd as maintainer of devel/libtool) Dear all, I posted previously on the ports mailing list about problems that were showing up with net/freeradius when built with gcc 4.2 on 6.x and on 7.x amd64. At that time I was wondering if there was an arcane problem in the toolchain, maybe in libtool. In fact, the solution appears to be straightforward, and not libtool's fault. radiusd was being built -pie, which was the default from upstream. Patching the upstream Makefile.in to remove -pie seems to resolve both problems. Thanks to Sean McNeil for the report. The moral of the story appears to be "don't use -pie with libtool". I have no idea why the upstream Makefile.in is like this; I will chase it with the FreeRADIUS developers. I've just submitted ports/118425 http://www.freebsd.org/cgi/query-pr.cgi?pr=118425 which should fix that, as well as chasing a heimdal shared library version bump. I believe those two fixes may qualify for committing during the current ports freeze; I've alerted portmgr@ separately. I've also incorporated a couple of other outstanding fixes, though I realise that they may well not qualify to be committed alongside the others because of the ports freeze. H... A seemingly silimar issue came up a while back. It was supposed to have been fixed - http://lists.freebsd.org/pipermail/cvs-src/2007-May/078660.html I wonder if perhaps there is something more that needs to be done. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maintaining of *-aspell ports
У уторак, 4. децембра 2007. у 21:30:36 +0100 Thierry Thomas <[EMAIL PROTECTED]> је написао(ла): > Selon Nikola Lečić <[EMAIL PROTECTED]> le Mar 4 déc > 16:51:19 2007 : > > > У уторак, 4. децембра 2007. у 07:43:15 +0100 > > Thierry Thomas <[EMAIL PROTECTED]> је написао(ла): > > > > Thierry, thank you (and Peter) for replies. I asked because I wasn't > > sure if some kind of automation (linked with textproc/aspell) was > > employed here... > > > >> don't hesitate to adopt one of them! > > > > OK, I'd gladly take care of sr-aspell. > > Great! Because we have a ports freeze, it's not possible to change > the maintainership ATM, but just send a PR. Done: http://www.freebsd.org/cgi/query-pr.cgi?pr=118437. -- Nikola Lečić :: Никола Лечић ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slab Allocator And Wait Queues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bubble Reading wrote: > Hi, > > Does someone know if there is something like Linux Slab Allocator and Linux > Wait Queues in FreeBSD? > > I am trying to port a linux code to FreeBSD which makes use of these. Do you mean kernel code or userland code? For slab allocator, FreeBSD provided a mechanism called "UMA" which provided similar functionality; Wait queues... We usually use msleep(9) and wakeup(9), but I am not sure if that is what you want... Cheers, - -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHVfw/hcUczkLqiksRAjQSAJ9xvmj3MRQv8bpsg3Oho8DvxkHLEACgrO88 R0s3xkvutlYojeMq7moaVoU= =Ry3O -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maintaining of *-aspell ports
Selon Nikola Lečić <[EMAIL PROTECTED]> le Mar 4 déc 16:51:19 2007 : У уторак, 4. децембра 2007. у 07:43:15 +0100 Thierry Thomas <[EMAIL PROTECTED]> је написао(ла): Thierry, thank you (and Peter) for replies. I asked because I wasn't sure if some kind of automation (linked with textproc/aspell) was employed here... don't hesitate to adopt one of them! OK, I'd gladly take care of sr-aspell. Great! Because we have a ports freeze, it's not possible to change the maintainership ATM, but just send a PR. -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: has FreeBSD's libc been swigged?
On Dec 4, 2007, at 1:45 PM, Chuck Robey wrote: Vivek Khera wrote: On Dec 3, 2007, at 3:40 PM, Chuck Robey wrote: Need to do some python work, using a lot of FreeBSD's base libs, and I was wondering, if any ports have swigged the FreeBSD libs? I'll do it if I must, just trying to save me some work. Not understanding your use of the word "swigged", all I can say is that the ports do not touch the system libraries except in the rare case of things like openssl which have the _option_ to install on top of the system ssl libraries. devel/swig is a well-known interface generator, which automates writing the interfaces, so that the scripting languages can make direct use of compiled languaes. My particular target is to get python to use FreeBSD llibraries, so your comment is amiss in this case, although you are correct in general.. Aha! Well, I've even used SWIG in the past with perl, but I didn't catch the connection. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: has FreeBSD's libc been swigged?
Vivek Khera wrote: On Dec 3, 2007, at 3:40 PM, Chuck Robey wrote: Need to do some python work, using a lot of FreeBSD's base libs, and I was wondering, if any ports have swigged the FreeBSD libs? I'll do it if I must, just trying to save me some work. Not understanding your use of the word "swigged", all I can say is that the ports do not touch the system libraries except in the rare case of things like openssl which have the _option_ to install on top of the system ssl libraries. devel/swig is a well-known interface generator, which automates writing the interfaces, so that the scripting languages can make direct use of compiled languaes. My particular target is to get python to use FreeBSD llibraries, so your comment is amiss in this case, although you are correct in general.. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HELP needed by experienced porter for simple review
On Tue, 04 Dec 2007 06:36:20 -0600, GP <[EMAIL PROTECTED]> wrote:
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to
FILESDIR. The WRKDIR/WRKSRC are the place where you work anything
inside. However, move from WRKSRC to FILESDIR might create problem in
future so avoid that.
When I leve it out I get this error:
===> Installing for kissdx-0.13.10a
** Missing /usr/ports/distfiles/files/kissdx.in for kissdx-0.13.10a.
*** Error code 1
Ummm... I went back to see your first orignal thread. I noticed that
you put Makefile and others in /usr/ports/distfiles/? You should create
'kissdx' and 'kissdx/files' (mkdir -p kissdx/files) directories. You
should make your port looks like this:
OK its all moved to a handmade subdir. Probably nicer that way, but I
still have to make the files dir in the Makefile and put the script in
it! or am I missing something?
Maybe I don't understand the files dir!!? could it mean that the startup
script can not come from the tarball? (I've done some work for including
FreeBSD stuff into the original package. So that would be a capitulation
to Linux then wouldnt it?: all is writen for Linux and then adapted for
FreeBSD :o)
Send me tarball of your update kissdx port and I will taking a peek.
Cheers,
Mezz
You should follow this below:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html
You put your 'kissdx.in' in kissdx/files/ and it will doing every thing
for you as explained in rc-scripts.html.
I'm sorry to say that i doesn't explain this for me. Porters handbook
still requires a lot of implicit knowledge. (But I'm getting there by
small increments :O)
Thanks and BR
/Simon
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
net/freeradius - fixed for RELENG_7 amd64 and 6.x with gcc 4.2
(ade@ cc'd as maintainer of devel/libtool) Dear all, I posted previously on the ports mailing list about problems that were showing up with net/freeradius when built with gcc 4.2 on 6.x and on 7.x amd64. At that time I was wondering if there was an arcane problem in the toolchain, maybe in libtool. In fact, the solution appears to be straightforward, and not libtool's fault. radiusd was being built -pie, which was the default from upstream. Patching the upstream Makefile.in to remove -pie seems to resolve both problems. Thanks to Sean McNeil for the report. The moral of the story appears to be "don't use -pie with libtool". I have no idea why the upstream Makefile.in is like this; I will chase it with the FreeRADIUS developers. I've just submitted ports/118425 http://www.freebsd.org/cgi/query-pr.cgi?pr=118425 which should fix that, as well as chasing a heimdal shared library version bump. I believe those two fixes may qualify for committing during the current ports freeze; I've alerted portmgr@ separately. I've also incorporated a couple of other outstanding fixes, though I realise that they may well not qualify to be committed alongside the others because of the ports freeze. Best wishes, David -- David Wood [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maintaining of *-aspell ports
У уторак, 4. децембра 2007. у 07:43:15 +0100 Thierry Thomas <[EMAIL PROTECTED]> је написао(ла): > Le Mar 4 déc 07 à 4:46:50 +0100, Nikola Lečić > <[EMAIL PROTECTED]> écrivait : > > > All ~80 *-aspell ports have '[EMAIL PROTECTED]'. Does > > this mean that someone should take maintainership? > > Of course, that's why their maintainership has been released: Thierry, thank you (and Peter) for replies. I asked because I wasn't sure if some kind of automation (linked with textproc/aspell) was employed here... > don't hesitate to adopt one of them! OK, I'd gladly take care of sr-aspell. -- Nikola Lečić :: Никола Лечић ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: has FreeBSD's libc been swigged?
On Dec 3, 2007, at 3:40 PM, Chuck Robey wrote: Need to do some python work, using a lot of FreeBSD's base libs, and I was wondering, if any ports have swigged the FreeBSD libs? I'll do it if I must, just trying to save me some work. Not understanding your use of the word "swigged", all I can say is that the ports do not touch the system libraries except in the rare case of things like openssl which have the _option_ to install on top of the system ssl libraries. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [RFC/P] Port System Re-Engineering
--On Monday, December 03, 2007 22:03:50 -0500 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: It was one of several examples... jesus how I wish I could post some of the private replies I got so people could see the amount of frustration out there with the current system but that would color other replies so I will wait until I don't get any new survey replies for 24 hrs then I will post a summary and verbatum the ones the orginal authors let me do this with. Well, that does it for me. You're the first person ever in this list to go into my killfile. The last thing I want is to sit here and read carping and bitching from people who think the ports system is f'd up but have no intention of getting off their butts and writing code to "fix" it. Feel free to respond. I won't see it. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Slab Allocator And Wait Queues
Hi, Does someone know if there is something like Linux Slab Allocator and Linux Wait Queues in FreeBSD? I am trying to port a linux code to FreeBSD which makes use of these. -- Regards, Bubble ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: snort-2.7.0.1_1
Hi, Since you are listed as the mainainer for the snort package on FreeBSD, can you update the snort port to the latest version? The latest version includes flow connection for non-TCP traffic which is not accepted by the current port. This causes snort to exit with a fatal error. Best regards, Hansa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HELP needed by experienced porter for simple review
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to
FILESDIR. The WRKDIR/WRKSRC are the place where you work anything
inside. However, move from WRKSRC to FILESDIR might create problem in
future so avoid that.
When I leve it out I get this error:
===> Installing for kissdx-0.13.10a
** Missing /usr/ports/distfiles/files/kissdx.in for kissdx-0.13.10a.
*** Error code 1
Ummm... I went back to see your first orignal thread. I noticed that you
put Makefile and others in /usr/ports/distfiles/? You should create
'kissdx' and 'kissdx/files' (mkdir -p kissdx/files) directories. You
should make your port looks like this:
OK its all moved to a handmade subdir. Probably nicer that way, but I still
have to make the files dir in the Makefile and put the script in it! or am I
missing something?
Maybe I don't understand the files dir!!? could it mean that the startup
script can not come from the tarball? (I've done some work for including
FreeBSD stuff into the original package. So that would be a capitulation to
Linux then wouldnt it?: all is writen for Linux and then adapted for FreeBSD
:o)
You should follow this below:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html
You put your 'kissdx.in' in kissdx/files/ and it will doing every thing
for you as explained in rc-scripts.html.
I'm sorry to say that i doesn't explain this for me. Porters handbook still
requires a lot of implicit knowledge. (But I'm getting there by small
increments :O)
Thanks and BR
/Simon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: chroot: conftest stuck in umtxn state
Erik Cederstrand wrote: Hi! I'm installing some ports into a chroot environment that will eventually go on a separate machine. When installing python25, the installation gets stuck in the configure phase when checking for pthread: # chroot /perfmon/slaves/src/packages/CURRENT-2007.11.27.13.29.20/ /bin/sh -c "cd /usr/ports/lang/python25; WRKDIRPREFIX=/tmp make BATCH=yes install clean; " [...] checking whether cc accepts -Olimit 1500... no checking whether pthreads are available without options... no checking whether cc accepts -Kpthread... no checking whether cc accepts -Kthread... no checking whether cc accepts -pthread... and then the installation freezes. top shows conftest is in umtx state: 1696 root1 960 3200K 840K umtxn0:00 0.00% conftest and is only killable with kill -9. /usr/ports in the chroot is nullfs-mounted, and ports options files have been pre-installed in the chroot's /var/db/ports The host: # uname -a FreeBSD perfmonserver.itu.dk 7.0-BETA4 FreeBSD 7.0-BETA4 #1: Mon Dec 3 16:15:35 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERFMONSERVER i386 The chroot contains CURRENT from various dates, in this case 2007.11.27.13.29.20. It is compiled with this src.conf (and no other config modifications): WITHOUT_ATM= true WITHOUT_AUDIT= true WITHOUT_AUTHPF= true WITHOUT_BIND= true WITHOUT_BLUETOOTH= true WITHOUT_CALENDAR= true WITHOUT_CDDL= true WITHOUT_CVS= true WITHOUT_DICT= true WITHOUT_EXAMPLES= true WITHOUT_FORTRAN= true WITHOUT_GAMES= true WITHOUT_GPIB= true WITHOUT_HTML= true WITHOUT_I4B= true WITHOUT_IPFILTER= true WITHOUT_IPX= true WITHOUT_LPR= true WITHOUT_MAN= true WITHOUT_PF= true WITHOUT_RESCUE= true WITHOUT_SENDMAIL= true WITHOUT_SHAREDOCS= true WITHOUT_USB= true If I try to install python25 on the host, this problem does not occur. Any debugging help would be greatly appreciated. I should have done a more thorough googling. It seems this problem was fixed that same day. Rebuilding now, and will return if the problem persists. Erik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
chroot: conftest stuck in umtxn state
Hi! I'm installing some ports into a chroot environment that will eventually go on a separate machine. When installing python25, the installation gets stuck in the configure phase when checking for pthread: # chroot /perfmon/slaves/src/packages/CURRENT-2007.11.27.13.29.20/ /bin/sh -c "cd /usr/ports/lang/python25; WRKDIRPREFIX=/tmp make BATCH=yes install clean; " [...] checking whether cc accepts -Olimit 1500... no checking whether pthreads are available without options... no checking whether cc accepts -Kpthread... no checking whether cc accepts -Kthread... no checking whether cc accepts -pthread... and then the installation freezes. top shows conftest is in umtx state: 1696 root1 960 3200K 840K umtxn0:00 0.00% conftest and is only killable with kill -9. /usr/ports in the chroot is nullfs-mounted, and ports options files have been pre-installed in the chroot's /var/db/ports The host: # uname -a FreeBSD perfmonserver.itu.dk 7.0-BETA4 FreeBSD 7.0-BETA4 #1: Mon Dec 3 16:15:35 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERFMONSERVER i386 The chroot contains CURRENT from various dates, in this case 2007.11.27.13.29.20. It is compiled with this src.conf (and no other config modifications): WITHOUT_ATM= true WITHOUT_AUDIT= true WITHOUT_AUTHPF= true WITHOUT_BIND= true WITHOUT_BLUETOOTH= true WITHOUT_CALENDAR= true WITHOUT_CDDL= true WITHOUT_CVS= true WITHOUT_DICT= true WITHOUT_EXAMPLES= true WITHOUT_FORTRAN= true WITHOUT_GAMES= true WITHOUT_GPIB= true WITHOUT_HTML= true WITHOUT_I4B= true WITHOUT_IPFILTER= true WITHOUT_IPX= true WITHOUT_LPR= true WITHOUT_MAN= true WITHOUT_PF= true WITHOUT_RESCUE= true WITHOUT_SENDMAIL= true WITHOUT_SHAREDOCS= true WITHOUT_USB= true If I try to install python25 on the host, this problem does not occur. Any debugging help would be greatly appreciated. Thanks, Erik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
