portinstall breaks with -m -j 4
When a port installs dependencies prior to building and the -j flag is set for make, portupgrade somehow breaks installing dependencies. If I simply do # cd /usr/ports/category/port # make install -j 4 it works fine, but the command # portinstall category/port -m '-j 4' does not work if dependencies have to be installed. I have tried to get some insight in this and it seems that the ports depended on simply head to the do-install target, omitting things like do-extract, do-patch and do-build. The cause is a mystery to me, though. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portinstall breaks with -m -j 4
[LoN]Kamikaze wrote: When a port installs dependencies prior to building and the -j flag is set for make, portupgrade somehow breaks installing dependencies. If I simply do # cd /usr/ports/category/port # make install -j 4 it works fine, but the command # portinstall category/port -m '-j 4' does not work if dependencies have to be installed. I have tried to get some insight in this and it seems that the ports depended on simply head to the do-install target, omitting things like do-extract, do-patch and do-build. The cause is a mystery to me, though. -j is not supported for ports. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portmanager
Hi, I've been using portmanager for a while but one of the sudden portmanager dumped core: #portmanager -u ... ... 00494 bitstream-vera-1.10_2 /x11-fonts/bitstream-vera 00493 glitz-0.4.4_1 /graphics/glitz 00492 libthai-0.1.5_1 /devel/libthai 00491 automake-1.9.6 /devel/automake19 00490 autoconf-2.59_2 /devel/autoconf259 00489 m4-1.4.4 /devel/m4 00488 gawk-3.1.1_1 /lang/gawk 00487 mc-light-4.1.40.p9_6 /misc/mc-light 00486 ratmenu-1.4 /x11-wm/ratmenu MGrStrlen error: NULL marker not found in string Assertion failed: (0), function MGrStrlen, file MGrStrlen.c, line 54. Abort (core dumped) Any idea? -- ___Pozdrawiam!Kind regards!Herzliche Grüsse! /o \/| [EMAIL PROTECTED] ICQ#6099687 gadu-gadu#1404178 \___/\| The essence of life is not long life, but true life. . ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: gettext-0.14.5_2 - BROKEN PORT!
Mr Alexus [EMAIL PROTECTED] writes: Lowell Gilbert wrote: alexus [EMAIL PROTECTED] writes: === Building for gettext-0.14.5_2 Making all in autoconf-lib-link Making all in m4 Making all in tests Making all in gettext-runtime make all-recursive Making all in doc Making all in intl /bin/sh /usr/local/bin/libtool --mode=compile cc -c -DLOCALEDIR=\/usr/local/share/locale\ -DLOCALE_ALIAS_PATH=\/usr/local/share/locale\ -DLIBDIR=\/usr/local/libdata\ -DIN_LIBINTL -DENABLE_RELOCATABLE=1 -DIN_LIBRARY -DINSTALLDIR=\/usr/local/lib\ -DNO_XMALLOC -Dset_relocation_prefix=libintl_set_relocation_prefix -Drelocate=libintl_relocate -DDEPENDS_ON_LIBICONV=1 -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe ./bindtextdom.c libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime/intl. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/popt. *** Error code 1 Stop in /usr/ports/archivers/rpm. *** Error code 1 Stop in /usr/ports/emulators/linux_base-fc4. dev# uname -a FreeBSD dev.hotcamsluts.com 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #0: Mon Jul 3 01:22:25 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 dev# It works for me. Are you sure you have followed the updating instructions in /usr/ports/UPDATING? [In this case, particularly the libtool update note from 20060223, but you should check the file whenever you update your ports tree.] it's a fresh bare minimum install, all i need is a linux support, so i went to /usr/ports/emulators/linux_base-fc4 and tried building it, and gettext wouldn't build.. Where did you install a -p2 from? Normally you need to upgrade from a base install to get a patch release (I think they are released as snapshots, but newcomers generally don't know about those). Probably, you still need to deal with the libtool issue. Just remove whatever libtool(s) you have installed (via pkg_delete(1)), make clean the port you were building, and (probably) it will build fine. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portinstall breaks with -m -j 4
Dmitry Morozovsky wrote: On Sat, 22 Jul 2006, [LoN]Kamikaze wrote: L -j is not supported for ports. L L L Well, it should be, with all the multi-core CPUs coming. And all other L targets work fine with -j. It's solely the install target that's broken. L L Is there any reason why it is not supported? Too many software authors do not design their build invironment for parallel work. Many ports broke in configure and/or build phases just with make -j2. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] Well, at least the ports system itself should not be broken able to work with this. With larger ports I manage to reduce build times by 40% with distcc and a second machine. As far as I see it the number of ports breaking is rather low. On many ports it simply doesn't have an effect, but so far only editors/vim really breaks on my systems. BTW, I apologize for this is not at all a portupgrade issue, but an issue of the ports system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: openldap-server-2.3.24: default loglevel and /var/log/debug.log
When running slapd on a valilla FreeBSD 6.1-RELEASE /var/log/debug.log is rotating frequently. It seems that the default loglevel is set to 256; correct? Is this the default for openldap? I've been grepping through the sources but was unable to verify my hypothesis. How can I know the actual default loglevel? Because slapd is logging through local4 and /etc/syslog.conf contains *.=debug /var/log/debug.log the file is growing rapidly. Are these defaults recommended for a production server? If not, what are the recommendations concerning slapd loglevel and/or syslog.conf configuration? Regards, Thierry. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: openldap-server-2.3.24: default loglevel and /var/log/debug.log
Thierry Lacoste wrote: It seems that the default loglevel is set to 256; correct? Is this the default for openldap? I've been grepping through the sources but was unable to verify my hypothesis. How can I know the actual default loglevel? http://www.openldap.org/doc/admin23/slapdconfig.html#Configuration%20File%20Directives Section 6.2.1.5: Default: loglevel 256 So, Correct, yes. However that loglevel records the activity of the server in about the same level of detail as you'ld hope to see from any other network server. Because slapd is logging through local4 and /etc/syslog.conf contains *.=debug /var/log/debug.log the file is growing rapidly. Are these defaults recommended for a production server? If not, what are the recommendations concerning slapd loglevel and/or syslog.conf configuration? Having slapd write logs is certainly a good thing. However it seems that your only choice of how to log what slapd does is via syslog using the LOG_LOCAL4 facility. If the slapd logging is too voluminous and clogging up files that should show other logs, you can tell syslog not to include it. Eg for your debug.log: !-slapd *.=debug /var/log/debug.log Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: portinstall breaks with -m -j 4
BTW, I apologize for this is not at all a portupgrade issue, but an issue of the ports system. It is an issue with individual ports -- actually not the port (e.g. Makefile framework, pkg-*) but the individual applications (IIUC). Well, at least the ports system itself should not be broken able to work with this. With larger ports I manage to reduce build times by 40% with distcc and a second machine. As far as I see it the number of ports breaking is rather low. Please feel free to suggest a framework (complete with regression test framework) where the infrastructure code can learn which ports are safe. I think it's going to be a harder problem than you think it is. Note that appears to work and can be shown to work under arbitrary build circumstances for all users are IMHO going to be two very different classes of problem -- and the latter will need to be solved before it can be used on the package-building cluster. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: openldap-server-2.3.24: default loglevel and /var/log/debug.log
Thanks a lot. It seems that the default loglevel is set to 256; correct? Is this the default for openldap? I've been grepping through the sources but was unable to verify my hypothesis. How can I know the actual default loglevel? http://www.openldap.org/doc/admin23/slapdconfig.html#Configuration%20File%2 0Directives Section 6.2.1.5: Default: loglevel 256 So, Correct, yes. However that loglevel records the activity of the server in about the same level of detail as you'ld hope to see from any other network server. With no negative impact on performance for a loaded production server? My /var/log/debug.log was already rotating every hour and the machine is only in a testing phase. Because slapd is logging through local4 and /etc/syslog.conf contains *.=debug /var/log/debug.log the file is growing rapidly. Are these defaults recommended for a production server? If not, what are the recommendations concerning slapd loglevel and/or syslog.conf configuration? Having slapd write logs is certainly a good thing. However it seems that your only choice of how to log what slapd does is via syslog using the LOG_LOCAL4 facility. If the slapd logging is too voluminous and clogging up files that should show other logs, you can tell syslog not to include it. Eg for your debug.log: !-slapd *.=debug /var/log/debug.log Actually I did *.=debug;local4.none/var/log/debug.log local4.debug /var/log/slapd.log But clearly /var/log/slapd.log is now rotating fast. I'm using nss_ldap and a simple id lacoste generates more than 2 KB of logs. I was considering keeping that setting for testing purposes and either turn to local4.info in syslog.conf or set loglevel=0 in slapd.conf when in production. Is this a bad idea? Regards, Thierry. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hpijs/hplip, foomatic-rip, and CUPS 1.2.0
On Jul 22, 2006, at 9:32 PM, Anthony Agelastos wrote: On Jul 17, 2006, at 7:49 PM, Anish Mistry wrote: On Monday 17 July 2006 19:05, Anthony Agelastos wrote: On Jul 16, 2006, at 11:19 PM, John Merryweather Cooper wrote: Anthony Agelastos wrote: On Jul 16, 2006, at 10:08 PM, John Merryweather Cooper wrote: Anthony Agelastos wrote: On Jul 16, 2006, at 3:19 PM, Doug Barton wrote: For future reference, please don't post to both -ports and - questions. Thank you for this clarification. Anthony Agelastos wrote: Does anyone out there have network printing working with hpijs/ hplip and CUPS 1.2.0? Yes. You need to follow the instructions at file:///usr/local/share/doc/hplip-0.9.11/install/step4/cups/ net.html I do not think I explained my situation very well. This printer (hp LaserJet 1160Le) is connected directly to my FreeBSD server via USB. If I print something logged on the server (via lp for instance), it prints. I wish to print to this printer from all of the computers on my LAN. When I try to print something from one of these computers, that is when it bombs and displays the foomatic-rip error message (foomatic-rip failed). The directions on that sheet appear to be if I wanted to print to this network printer that wasn't directly connected to the FreeBSD server. Am I mistaken about this? Also, there is no button on the printer that will print such a page, so I would have to figure out how to find this IP address by other means. I cannot see how to find it in the CUPS web interface. I assume CUPS issues it an IP address. The error_log that I have posted on previous threads is attached to this email (the successful print jobs were done locally while the error occurred when I printed to the printer from my MacBook Pro). Does anyone have any suggestions? I should note that prior to the CUPS upgrade to 1.2.0 (and the recent gnutls update), my setup was working (I was able to print from the server itself as well as all of the rest of the computers on my LAN). I have rebuilt all packages several times (except for the OS). On my MacBook Pro, when I go to the CUPS web interface, I see the following for the printer: [EMAIL PROTECTED]HP LaserJet 1160 Foomatic/ hpijs (recommended) Description: hp LaserJet 1160Le Location: Den Printer State: idle, accepting jobs. 192.168.0.3 is the IP address of my FreeBSD server on my LAN. It looks as if Mac OS X 10.4.7 runs CUPS 1.1.23, but I could be mistaken. It has found the printer through Bonjour (zeroconf I believe is another name for it), so I didn't have to do any configuring. Could there be an incompatibility within these versions of CUPS? I have found the following page which lists several issues and talks about how CUPS 1.2.0 is broken in several places. Could one of these be the issue? http://www.bsdforums.org/forums/showthread.php?t=42391 On a sidenote, I was having difficulties installing hpijs when hplip was already installed I'm working on that. Thank you for your assistance on this. 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 freebsd-ports- [EMAIL PROTECTED] You need to restart CUPS when the printer attaches via USB or else CUPS won't know about the USB port and you'll get this error every time. I just did a /usr/local/etc/rc.d/cupsd restart and then printed something from my laptop. Same error. dell# lpstat -t scheduler is running no system default destination device for Create_PDF: cups-pdf:/ device for hp_LaserJet_1160Le: /dev/ulpt0 Create_PDF accepting requests since Sun Jun 25 11:27:52 2006 hp_LaserJet_1160Le accepting requests since Sun Jul 16 22:36:15 2006 printer Create_PDF is idle. enabled since Sun Jun 25 11:27:52 2006 printer hp_LaserJet_1160Le is idle. enabled since Sun Jul 16 22:36:15 2006 /usr/local/libexec/cups/filter/foomatic-rip failed hp_LaserJet_1160Le-30 iqgrande 7168 Sun Jul 16 22:36:02 2006 jmc What are the permissions/ownership on /dev/ulpt0? jmc I do not remember if I created the user + group cups hplip or if the system automatically did so for me. In any event, there are the following entries: The hplip port automatically creates the user. If you are using hplip then you shouldn't have ulpt in your kernel or be loading it as a module. eg. You printer MUST attach as a ugen device. Once it is attaching as a ugen device you should run hp-setup to correctly configure the printer via the HP utilities. If there is any confusion I'd suggest updating to 1.6.6a from the following PR and following all the instructions in the pkg-message from the PR as it explains everything you need to do to get hpluip up and running correctly. http://www.freebsd.org/cgi/query-pr.cgi?pr=100413 -- Anish Mistry [EMAIL
