Re: portmaster-with-package-support release candidate available for testing
On Saturday 12 December 2009 03:10:34 Doug Barton wrote: > Yes, the error message you posted is exactly what's supposed to > happen. "There is nothing at $PACKAGESITE" is a whole different > category of problems than "the latest version of the package is not > available at $PACKAGESITE." In the latter case with --packages-build > or -P|--packages portmaster will simply build the port for you. If > there is nothing at $PACKAGESITE at all that's something that requires > the user's attention. good... thanks for listening to me! i could have some question/suggestion about --packages-build and --delete-build-only in the future, but i need some real usage to test it, now... i'll be back :) thanks again! -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla ... and furthermore ... I don't like your trousers. ___ 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: portmaster-with-package-support release candidate available for testing
Alberto Villa wrote: > On Friday 11 December 2009 20:22:26 Doug Barton wrote: >> First, I'm assuming that you are using version 2.14 from ports. That's >> the latest version at the moment. > > i was using the latest revision, which seems to be the same as 2.14. > upgraded to 2.14, now > >> Next, I tried the exact same command line you used in your example and >> it worked for me. > > it works for me too, now... great! Good news! > the only thing i have (referred to the next problem) is > PACKAGESITE=ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9- > current in the environment > >> Then run the commands that are giving you problems again. I did see >> your other messages about -P and --packages-build aborting if they >> can't find a package, that shouldn't be happening either, and does not >> happen in my testing; so something is definitely not working the way >> it should for you and I want to make sure that we figure out what it is. > > could it be because my PACKAGESITE is actually an empty directory? > log here: http://pastebin.ca/1711679 Yes, the error message you posted is exactly what's supposed to happen. "There is nothing at $PACKAGESITE" is a whole different category of problems than "the latest version of the package is not available at $PACKAGESITE." In the latter case with --packages-build or -P|--packages portmaster will simply build the port for you. If there is nothing at $PACKAGESITE at all that's something that requires the user's attention. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!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: portmaster-with-package-support release candidate available for testing
On Saturday 12 December 2009 02:09:52 Alberto Villa wrote: > could it be because my PACKAGESITE is actually an empty directory? ok, i see that i should use the default (8-current), but the program shouldn't fail anyway -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla I don't do it for the money. -- Donald Trump, Art of the Deal ___ 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: portmaster-with-package-support release candidate available for testing
On Friday 11 December 2009 20:22:26 Doug Barton wrote: > First, I'm assuming that you are using version 2.14 from ports. That's > the latest version at the moment. i was using the latest revision, which seems to be the same as 2.14. upgraded to 2.14, now > Next, I tried the exact same command line you used in your example and > it worked for me. it works for me too, now... great! > If that doesn't expose the problem we're going to have to do more > digging. First, are your world and kernel up to date and in synch? just for reference, i'm working in a jail with 9-current installed last night (my live system is 8-rc2). i use jexec to access the jail, since i'm rebuilding all my ports to move my system to current > Do you have anything in ~/.portmasterrc > and/or /usr/local/etc/portmaster.rc currently? Next, do this: > echo 'PM_VERBOSE=vopt' > ~/.portmasterrc the only thing i have (referred to the next problem) is PACKAGESITE=ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9- current in the environment > Then run the commands that are giving you problems again. I did see > your other messages about -P and --packages-build aborting if they > can't find a package, that shouldn't be happening either, and does not > happen in my testing; so something is definitely not working the way > it should for you and I want to make sure that we figure out what it is. could it be because my PACKAGESITE is actually an empty directory? log here: http://pastebin.ca/1711679 -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla Treaties are like roses and young girls -- they last while they last. -- Charles DeGaulle ___ 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"
deskutils/calibre build error
The deskutils/calibre port fails to build on both 7.2-STABLE and 8.0-STABLE i386: # portinstall -cv calibre ---> Session started at: Thu, 10 Dec 2009 22:45:09 -0600 [Gathering depends for deskutils/calibre ..[snip] done] ---> Fresh installation of deskutils/calibre started at: Thu, 10 Dec 2009 22:47:57 -0600 ---> Installing 'calibre-0.6.18' from a port (deskutils/calibre) ---> Build of deskutils/calibre started at: Thu, 10 Dec 2009 22:48:00 -0600 ---> Building '/usr/ports/deskutils/calibre' ===> Cleaning for calibre-0.6.18 ===> Vulnerability check disabled, database not found ===> Found saved configuration for calibre-0.6.18 => calibre-0.6.18.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://calibre.kovidgoyal.net/downloads/. fetch: http://calibre.kovidgoyal.net/downloads/calibre-0.6.18.tar.gz: Moved Permanently => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. calibre-0.6.18.tar.gz 100% of9 MB 831 kBps 00m00s ===> Extracting for calibre-0.6.18 => MD5 Checksum OK for calibre-0.6.18.tar.gz. => SHA256 Checksum OK for calibre-0.6.18.tar.gz. ===> Patching for calibre-0.6.18 ===> Applying FreeBSD patches for calibre-0.6.18 ===> calibre-0.6.18 depends on package: py*-setuptools>=0 - found ===> calibre-0.6.18 depends on package: py*-sip>=0 - found ===> calibre-0.6.18 depends on package: py*-qt4-core>=0 - found ===> calibre-0.6.18 depends on package: py*-qt4-gui>=0 - found ===> calibre-0.6.18 depends on file: /usr/local/bin/python2.6 - found ===> calibre-0.6.18 depends on package: qt4-qmake>=4.5.3 - found ===> calibre-0.6.18 depends on package: qt4-moc>=4.5.3 - found ===> calibre-0.6.18 depends on shared library: MagickWand.2 - found ===> calibre-0.6.18 depends on shared library: fontconfig.1 - found ===> calibre-0.6.18 depends on shared library: poppler-qt4.3 - found ===> calibre-0.6.18 depends on shared library: wmflite - found ===> calibre-0.6.18 depends on shared library: podofo - found ===> calibre-0.6.18 depends on shared library: intl - found ===> Configuring for calibre-0.6.18 ===> Building for calibre-0.6.18 * * Running build * ### Building extension pdfreflow ### c++ -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -fPIC -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -pthread -I/usr/local/include/python2.6 -I/usr/local/include/poppler -I/usr/local/include/ImageMagick -I/usr/include -c /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/images.cpp -o /usr/ports/deskutils/calibre/work/calibre/build/objects/pdfreflow/images.o c++ -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -fPIC -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -pthread -I/usr/local/include/python2.6 -I/usr/local/include/poppler -I/usr/local/include/ImageMagick -I/usr/include -c /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/main.cpp -o /usr/ports/deskutils/calibre/work/calibre/build/objects/pdfreflow/main.o c++ -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -fPIC -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -pthread -I/usr/local/include/python2.6 -I/usr/local/include/poppler -I/usr/local/include/ImageMagick -I/usr/include -c /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/links.cpp -o /usr/ports/deskutils/calibre/work/calibre/build/objects/pdfreflow/links.o c++ -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -fPIC -O2 -pipe -march=prescott -I/usr/local/include -fno-strict-aliasing -pthread -I/usr/local/include/python2.6 -I/usr/local/include/poppler -I/usr/local/include/ImageMagick -I/usr/include -c /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/reflow.cpp -o /usr/ports/deskutils/calibre/work/calibre/build/objects/pdfreflow/reflow.o /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/reflow.cpp: In member function 'virtual void calibre_reflow::XMLOutputDev::drawImageMask(GfxState*, Object*, Stream*, int, int, GBool, GBool, GBool)': /usr/ports/deskutils/calibre/work/calibre/src/calibre/ebooks/pdf/reflow.cpp:672: error: no matching function for call to 'calibre_reflow::XMLOutputDev::drawImageMask(GfxState*&, Object*&, Stream*&, int&, int&, GBool&, GBool&)' /usr/local/include/poppler/OutputDev.h:238: note: candidates are: virtual void OutputDev::drawImageMask(GfxState*, Object*, Stream*, int, int, GBool, GBool, GBool) Traceback (most recent call last): File "setup.py", line 99, in sys.exit(main()) File "setup.py", line 85, in main command.run_all(opts) File "/usr/ports/deskutils/calibre/work/calibre/setup/__init__.py", line 159, in run_all self.run_cmd(self, opts) File "/usr/ports/deskutils/calibre/work/calibre/setup/__init__.py", line 155, in run_cmd cmd.run(opts) File "/usr/ports/deskutils/calib
mplayer from SVN
Hello, Does anybody have a port for building mplayer from SVN? Thanks! ___ 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: portmaster-with-package-support release candidate available for testing
Alberto Villa wrote: > On Friday 11 December 2009 15:12:58 Alberto Villa wrote: >> On Thursday 10 December 2009 21:08:41 Doug Barton wrote: >>> The fix for this is in the svn tree now, please give it a try. I have >>> fixed a few bugs since 2.13 was committed, so I'll be pushing the svn >>> code into cvs very soon. >> thanks! i'm testing it right now > > mh, i'm sorry, again... > > could you check this error? http://pastebin.ca/1711185 > the gmake package is in /usr/ports/packages... this happens with every > package (tested with nasm and yasm... both failing when creating the new > package, while they are successfully installed) First, I'm assuming that you are using version 2.14 from ports. That's the latest version at the moment. Next, I tried the exact same command line you used in your example and it worked for me. Also, the error message about glob.c doesn't come from portmaster. What's even more odd is that of the 6 files named "glob.c" in the src tree, none of them have that function, and gmake doesn't even have a file named glob.c, so I'm really wondering where that error is coming from. The point where that error comes in your log is at package creation time, try the following command and see if you get the same error: pkg_create -b gmake-3.81_3 If that doesn't expose the problem we're going to have to do more digging. First, are your world and kernel up to date and in synch? And is your ports tree up to date? Do you have anything in ~/.portmasterrc and/or /usr/local/etc/portmaster.rc currently? Next, do this: echo 'PM_VERBOSE=vopt' > ~/.portmasterrc Then run the commands that are giving you problems again. I did see your other messages about -P and --packages-build aborting if they can't find a package, that shouldn't be happening either, and does not happen in my testing; so something is definitely not working the way it should for you and I want to make sure that we figure out what it is. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!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: Port version difficulties (maybe one for the Python crowd)
On Mon, Dec 07, 2009 at 05:12:03PM -0500, Greg Larkin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Kevin Golding wrote: > > In article <4b1d617a.6020...@freebsd.org>, Greg Larkin > > writes > >> This might get you further: > >> > >> fbsd70# make -V \ > >> PYDISTUTILS_PKGVERSION:C/\(\[\[:digit:\]\]\.\[\[:digit:\]\]\)\./\\1_/g > >> 0.1_0 > >> fbsd70# > > > > Well that does indeed work in that context, but I have no idea why it > > appears to do nothing in the Makefile. It seems completely unchanged: > > > > pkg_delete: unexec command for '/usr/local/bin/easy_install-2.6 -q -m -S > > /usr/local/lib/python2.6/site-packages django-signals-ahoy==0.1.0' > > failed > > > > I actually had to double check I did indeed update the correct file. A > > bit strange anyway. > > > > Kevin > > Hi Kevin, > > There's a lot more backslash escaping required in the :C suffix above > when running the make command directly in the shell. If you remove some > of the backslashes in the equivalent line in the Makefile, should be all > set. Then you can check to make it's working by running "make -V > PYEASYINSTALL_UNINSTALLARGS". A bit off-topic, and a bit late, but you can avoid the need for those additional backslashes by simply placing the string in apostrophes (single quotes). It's the shell that tries to interpret the string before passing it to "make" itself, and the single quotes tell the shell to not even try to interpret the string. So, just do: make -V 'PYDISTUTILS_PKGVERSION:C/([[:digit:]]\.[[:digit:]])\./\1_/g' ...and you'll see what make(1) thinks of the quoted string, just as if you'd put it in the Makefile. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI pgpXa9EbTWuFM.pgp Description: PGP signature
Re: portmaster-with-package-support release candidate available for testing
On Friday 11 December 2009 15:12:58 Alberto Villa wrote: > On Thursday 10 December 2009 21:08:41 Doug Barton wrote: > > The fix for this is in the svn tree now, please give it a try. I have > > fixed a few bugs since 2.13 was committed, so I'll be pushing the svn > > code into cvs very soon. > > thanks! i'm testing it right now mh, i'm sorry, again... could you check this error? http://pastebin.ca/1711185 the gmake package is in /usr/ports/packages... this happens with every package (tested with nasm and yasm... both failing when creating the new package, while they are successfully installed) thanks :P -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla Hailing frequencies open, Captain. ___ 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: builds but doesn't work; WAS: port www/kazehakase fails to build on i386 and ia64
On Thu, Dec 03, 2009 at 02:02:25PM +, Anton Shterenlikht wrote: > As of yesterday, apparently, xulrunner was superceded by libxul. > > Now I can build www/kazehakase with libxul on ia64 (still building on i386, > will report when done). But trying to do anything with kazehakase > leads to this error: > > (kazehakase:30357): Kazehakase-CRITICAL **: kz_embed_selection_is_collapsed: > assertion `KZ_IS_EMBED(kzembed)' failed > > (kazehakase:30357): Kazehakase-CRITICAL **: kz_embed_can_cut_selection: > assertion `KZ_IS_EMBED(kzembed)' failed > > (kazehakase:30357): Kazehakase-CRITICAL **: kz_embed_can_copy_selection: > assertion `KZ_IS_EMBED(kzembed)' failed > > (kazehakase:30357): Kazehakase-CRITICAL **: kz_embed_can_paste: assertion > `KZ_IS_EMBED(kzembed)' failed > Failed to bind socket "/tmp/kazehakase/dbus-server/dbus-6TLY3VVU1V": No such > file or directory > process 30357: arguments to dbus_server_get_data() were incorrect, assertion > "server != NULL" failed in file dbus-server.c line 1131. > This is normally a bug in some application using the D-Bus library. > D-Bus not compiled with backtrace support so unable to print a backtrace > > [7]Abort kazehakase > > I've updated fbsd to kern.osreldate: 94, and rebuilt kazehakase with make DEBUG_FLAGS="-O0 -g", but still get the same error. And bt doesn't really give anything useful: > kazehakase (kazehakase:3889): Gtk-WARNING **: WebKit/GTK+: missing action WebKit/GTK+ Failed to bind socket "/tmp/kazehakase/dbus-server/dbus-ZOQalM8C4L": No such file or directory process 3889: arguments to dbus_server_get_data() were incorrect, assertion "server != NULL" failed in file dbus-server.c line 1131. This is normally a bug in some application using the D-Bus library. D-Bus not compiled with backtrace support so unable to print a backtrace Abort (core dumped) > I cannot see how I can enable backtrace in dbus ports. And for kazehakase bt gives: (gdb) bt #0 0x2000423107a0 in thr_kill () from /lib/libc.so.7 #1 0x in ?? () Previous frame identical to this frame (corrupt stack?) (gdb) -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: portmaster-with-package-support release candidate available for testing
On Friday 11 December 2009 15:12:58 Alberto Villa wrote: > by the way, will it always abort when the option --packages-build won't > find a package? the same happens with -P -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla You are fairminded, just and loving. ___ 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: CUPS/PAM configuration authentication problem.
On Fri, 11 Dec 2009 14:44:12 + David Southwell wrote: > > Hi > Thanks to some help from people on the freebsd-questions lists I have > finally succeeded in getting cups the server to communicate with my > printer and print. > HOWEVER!! > > One minor niggling problem remains. I still cannot communicate with the > cups management interface on http://localhost:631 due to password > authentication failure. > > On good authority I believe I have a PAM configuration error most likely - > and > was told to check my /etc/pam.d/cups file. Not that I would know what to do > with it when I found it!!! > > However there is no /etc/pam.d/cups file !! > > BUT: there is a /usr/local/etc/pam.d/cups > > which has the following lines: > authrequiredpam_unknown.so nodelay > account requiredpam_unknown.so I looked at the cups configuration script, and it appears you have found a bug in configuring the PAM option. (Which defaults to "off", so it probably isn't tested much.) Where the file says "pam_unknown.so" it should say "pam_unix.so". Make that simple change and you should be up and running. But if you don't know what to do with the PAM file, you might as well just rebuild cups-base with the PAM option turned back off. You don't need PAM if all you want is normal Unix authentication. HTH ___ 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"
CUPS/PAM configuration authentication problem.
Hi Thanks to some help from people on the freebsd-questions lists I have finally succeeded in getting cups the server to communicate with my printer and print. HOWEVER!! One minor niggling problem remains. I still cannot communicate with the cups management interface on http://localhost:631 due to password authentication failure. I have asked for help on the cups-general mailing list. That list has light traffic and so far there is no solution in sight. Thanks in advance for any help with the problem. I try logging in as 'root' with correct root password in the login dialogue. I altered the cupsd.conf loglevel to debug and attached some sample the output to the end of this post. It seems as though the cupsd is not receiving the input (probably due to some config error on my part!). I have tried using a number of different browsers but get the same result. Prior to testing I did: dns1# lppasswd -g wheel -a root The standard cups error log showed cupsdAuthorize: pam_start() returned 4 (system error)! On good authority I believe I have a PAM configuration error most likely - and was told to check my /etc/pam.d/cups file. Not that I would know what to do with it when I found it!!! However there is no /etc/pam.d/cups file !! BUT: there is a /usr/local/etc/pam.d/cups which has the following lines: authrequiredpam_unknown.so nodelay account requiredpam_unknown.so Shown below is ls -l for each directory! Wanted --- good model for pam.d/cups and where to put it!!! [NB This is a freebsd 7.2 p3 amd64 system with intel quad core.] dns1# ls -l /etc/pam.d/ total 38 -r--r--r-- 1 root wheel 2907 May 1 2009 README -rw-r--r-- 1 root wheel 322 May 1 2009 atrun -rw-r--r-- 1 root wheel 199 May 1 2009 cron -rw-r--r-- 2 root wheel 547 May 1 2009 ftp -rw-r--r-- 2 root wheel 547 May 1 2009 ftpd -rw-r--r-- 1 root wheel 467 May 1 2009 gdm_disabled -rw-r--r-- 1 root wheel 365 May 1 2009 imap -rw-r--r-- 1 root wheel 467 May 1 2009 kde -rw-r--r-- 1 root wheel 374 May 1 2009 login -rw-r--r-- 1 root wheel 662 May 1 2009 other -rw-r--r-- 1 root wheel 319 May 1 2009 passwd -rw-r--r-- 1 root wheel 365 May 1 2009 pop3 -rw-r--r-- 1 root wheel 328 May 1 2009 rsh -rw-r--r-- 1 root wheel 739 May 1 2009 sshd -rw-r--r-- 1 root wheel 380 May 1 2009 su -rw-r--r-- 1 root wheel 705 May 1 2009 system -rw-r--r-- 1 root wheel 754 May 1 2009 telnetd -rw-r--r-- 1 root wheel 532 May 1 2009 xdm dns1# ls -l /usr/local/etc/pam.d total 16 -r--r--r-- 1 root wheel 69 Dec 10 09:19 cups -r--r--r-- 1 root wheel 672 Dec 7 10:06 gdm -r--r--r-- 1 root wheel 98 Nov 29 17:42 gnome-screensaver -r--r--r-- 1 root wheel 135 Nov 4 22:09 polkit -r--r--r-- 1 root wheel 135 Dec 2 09:00 polkit-1 -r--r--r-- 1 root wheel 399 Sep 27 18:20 sudo -r--r--r-- 1 root wheel 399 Sep 27 18:20 sudo.default -r--r--r-- 1 root wheel 98 Nov 5 03:22 xscreensaver # RESTART CUPS HERE:I [10/Dec/2009:11:06:07 +] Scheduler shutting down normally. D [10/Dec/2009:11:06:07 +] Discarding unused server-stopped event... D [10/Dec/2009:11:06:07 +] cupsdDeregisterPrinter(p=0x801f78800(LaserJet-2200), removeit=1) X [10/Dec/2009:11:06:07 +] kevent() returned Bad file descriptor I [10/Dec/2009:11:06:07 +] Saving job cache file "/var/cache/cups/job.cache"... I [10/Dec/2009:11:06:07 +] Listening to ::1:631 (IPv6) I [10/Dec/2009:11:06:07 +] Listening to 127.0.0.1:631 (IPv4) I [10/Dec/2009:11:06:07 +] Listening to /var/run/cups.sock (Domain) D [10/Dec/2009:11:06:07 +] cupsdDenyIP(loc=0x801f800a0(/), address=0:0:0:0, netmask=0:0:0:0) D [10/Dec/2009:11:06:07 +] cupsdDenyIP(loc=0x801f80100(/admin), address=0:0:0:0, netmask=0:0:0:0) D [10/Dec/2009:11:06:07 +] cupsdDenyIP(loc=0x801f80160(/admin/conf), address=0:0:0:0, netmask=0:0:0:0) I [10/Dec/2009:11:06:07 +] Remote access is disabled. D [10/Dec/2009:11:06:07 +] Added auto ServerAlias dns1.vizion2000.net D [10/Dec/2009:11:06:07 +] Added auto ServerAlias dns1 I [10/Dec/2009:11:06:07 +] Loaded configuration file "/usr/local/etc/cups/cupsd.conf" I [10/Dec/2009:11:06:07 +] Using default TempDir of /var/spool/cups/tmp... I [10/Dec/2009:11:06:07 +] Configured for up to 100 clients. I [10/Dec/2009:11:06:07 +] Allowing up to 100 client connections per host. I [10/Dec/2009:11:06:07 +] Using policy "default" as the default! I [10/Dec/2009:11:06:07 +] Full reload is required. I [10/Dec/2009:11:06:07 +] Loaded MIME database from "/usr/local/share/cups/mime" and "/usr/local/etc/cups": 35 types, 40 filters... D [10/Dec/2009:11:06:07 +] Loading printer LaserJet-2200... D [10/Dec/2009:11:06:07 +] load_ppd: Loading /var/cache/cups/LaserJet-2200.ipp... D [10/Dec/2009:11:06:07 +] cupsdRegisterPrinter(p=0x801f78800(LaserJet-2200)) D [10/Dec/2009:11:06:07 +] load_ppd: Loading /var/
Re: Depending on a Python egg
In article ,
Eygene Ryabinkin writes
>Wed, Dec 09, 2009 at 12:54:43PM +, Kevin Golding wrote:
>> RUN_DEPENDS=${PYTHON_SITELIBDIR}/${PYLXML_EGG}:${PORTSDIR}/devel/py-
>> lxml
>
>What about
>-
>RUN_DEPENDS=${PYTHON_PKGNAMEPREFIX}lxml>=0:${PORTSDIR}/devel/py-lxml
>-
>that should be specified after the inclusion of bsd.port.pre.mk?
A little slow I know (sorry, technical difficulties in other areas) but
that does seem the solution.
Thanks!
Kevin
___
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: portmaster-with-package-support release candidate available for testing
On Thursday 10 December 2009 21:08:41 Doug Barton wrote: > The fix for this is in the svn tree now, please give it a try. I have > fixed a few bugs since 2.13 was committed, so I'll be pushing the svn > code into cvs very soon. thanks! i'm testing it right now by the way, will it always abort when the option --packages-build won't find a package? -- Alberto Villa http://wiki.FreeBSD.org/AlbertoVilla Cthulhu Saves -- in case He's hungry later. ___ 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] switch to Emacs 23
On Fri, 11 Dec 2009 13:26:41 +0100 Jan Henrik Sylvester wrote: > Boris Samorodov wrote: > > here is a patch to switch to Emacs 23 as a default. There are > > 50 affected ports. Tests were done at tinderbox. Please give > > this patch a try. I'm going to fire up an exp run after some > > testing. The patch is relative to PORTSDIR: > You already know that I have been running emacs23 (with auctex, cedet, > elib, and jde) for a while with patches that are practically the same, > but in case you are waiting for more success reports with your current > patch, I rebuild my *emacs*-ports on two different 8.0-RELEASE > machines (i386 and amd64), created packages, moved them on to another > machine, and tried emacs (with auctex) there. Everything seems to be > fine. Gary, Jan, thanks for testing. I've submitted a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=141369 -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
regression: port www/squid fails to build on ia64 head
ia64 kern.osrelease: 9.0-CURRENT kern.osrevision: 199506 kern.osreldate: 94 while upgrading squid from squid-2.7.7 I get: cc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT yp_auth.o -MD -MP -MF .deps/yp_auth.Tpo -c -o yp_auth.o yp_auth.c mv -f .deps/yp_auth.Tpo .deps/yp_auth.Po cc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT nis_support.o -MD -MP -MF .deps/nis_support.Tpo -c -o nis_support.o nis_support.c mv -f .deps/nis_support.Tpo .deps/nis_support.Po cc -O2 -pipe -fno-strict-aliasing -D_REENTRANT -g -o yp_auth yp_auth.o nis_support.o -L../../../lib -lmiscutil -lcrypt -pthread -lmd -lm nis_support.o(.text+0x82): In function `get_nis_password': : undefined reference to `yp_match' *** Error code 1 Stop in /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/basic_auth/YP. *** Error code 1 Please advise many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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] switch to Emacs 23
Boris Samorodov wrote: here is a patch to switch to Emacs 23 as a default. There are 50 affected ports. Tests were done at tinderbox. Please give this patch a try. I'm going to fire up an exp run after some testing. The patch is relative to PORTSDIR: You already know that I have been running emacs23 (with auctex, cedet, elib, and jde) for a while with patches that are practically the same, but in case you are waiting for more success reports with your current patch, I rebuild my *emacs*-ports on two different 8.0-RELEASE machines (i386 and amd64), created packages, moved them on to another machine, and tried emacs (with auctex) there. Everything seems to be fine. Thanks for all your effort! Cheers, Jan Henrik ___ 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: update of java/jdk16 fails under amd64
Am 11.12.2009 11:47 (UTC+1) schrieb Kostik Belousov: On Fri, Dec 11, 2009 at 09:50:14AM +1000, Dima Panov wrote: On Friday 11 December 2009 07:07:48 Rainer Hurling wrote: When trying to update from jdk-1.6.0.3p4_12 to jdk-1.6.0.3p4_13 under recent 9.0-CURRENT (amd64) the following error occurs. Does anyone else observe this behaviour? It seems that something with threading or signal handling is not as it should be? Thanks in advance, Rainer Hurling - >>>Recursively making hpi all @ Thu Dec 10 21:55:41 CET 2009 ... gmake[3]: Entering directory `/usr/ports/java/jdk16/work/j2se/make/java/hpi' Begin Processing SUBDIRS: native >>>Recursively making native all @ Thu Dec 10 21:55:41 CET 2009 ... gmake[4]: Entering directory `/usr/ports/java/jdk16/work/j2se/make/java/hpi/native' mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/lib mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/bin mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/lib/ext Begin parallel compiles: /usr/ports/java/jdk16/work/j2se/make/java/hpi/native gmake[5]: Entering directory `/usr/ports/java/jdk16/work/j2se/make/java/hpi/native' /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe-Damd64 -DARCH='"amd64"' -DRELEA E='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th reads/CClassHeaders -I.. ../../../src/solaris/javavm/export -I../../../../src/share/javavm/export -I../../../../src/share/javavm/include -I../../../.. src/solaris/javavm/include -I../../../../src/solaris/hpi/native_threads/include -I../../../../src/solaris/hpi/include -I../.. ../../src/solaris/hpi/export -I../../../../src/share/hpi/include -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS -DMOOT_PRIORITIES-c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre ads/obj64/th eads_md.o ../../../../src/solaris/hpi/native_threads/src/threads_md.c /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEA E='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th reads/CClassHeaders -I.. ../../../src/solaris/javavm/export -I../../../../src/share/javavm/export -I../../../../src/share/javavm/include -I../../../.. src/solaris/javavm/include -I../../../../src/solaris/hpi/native_threads/include -I../../../../src/solaris/hpi/include -I../.. ../../src/solaris/hpi/export -I../../../../src/share/hpi/include -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS -DMOOT_PRIORITIES-c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre ads/obj64/mo itor_md.o ../../../../src/solaris/hpi/native_threads/src/monitor_md.c /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEA E='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th reads/CClassHeaders -I.. ../../../src/solaris/javavm/export -I../../../../src/share/javavm/export -I../../../../src/share/javavm/include -I../../../.. src/solaris/javavm/include -I../../../../src/solaris/hpi/native_threads/include -I../../../../src/solaris/hpi/include -I../.. ../../src/solaris/hpi/export -I../../../../src/share/hpi/include -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS -DMOOT_PRIORITIES-c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre ads/obj64/co dvar_md.o ../../../../src/solaris/hpi/native_threads/src/condvar_md.c /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEA E='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th reads/CClassHeaders -I.. ../../../src/solaris/javavm/export -I../../../../src/share/javavm/export -I../../../../src/share/javavm/include -I../../../../src/solaris/javavm/include -I../../../../src/solaris/hpi/native_threads/include -I../../../../src/solaris/hpi/include -I../../../../src/solaris/hpi/export -I../../../../src/share/hpi/include -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DUSE_PTHREADS -DMOOT_PRIORITIES-c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre ads/obj64/interrupt_md.o ../../../../src/solaris/hpi/native_thread
Re: update of java/jdk16 fails under amd64
On Fri, Dec 11, 2009 at 09:50:14AM +1000, Dima Panov wrote: > On Friday 11 December 2009 07:07:48 Rainer Hurling wrote: > > When trying to update from jdk-1.6.0.3p4_12 to jdk-1.6.0.3p4_13 under > > recent 9.0-CURRENT (amd64) the following error occurs. Does anyone else > > observe this behaviour? > > > > It seems that something with threading or signal handling is not as it > > should be? > > > > Thanks in advance, > > Rainer Hurling > > > > > > - > > > > >>>Recursively making hpi all @ Thu Dec 10 21:55:41 CET 2009 ... > > > > gmake[3]: Entering directory > > `/usr/ports/java/jdk16/work/j2se/make/java/hpi' Begin Processing SUBDIRS: > > native > > > > >>>Recursively making native all @ Thu Dec 10 21:55:41 CET 2009 ... > > > > gmake[4]: Entering directory > > `/usr/ports/java/jdk16/work/j2se/make/java/hpi/native' > > mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/lib > > mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/bin > > mkdir -p /usr/ports/java/jdk16/work/control/build/bsd-amd64/lib/ext > > Begin parallel compiles: > > /usr/ports/java/jdk16/work/j2se/make/java/hpi/native > > gmake[5]: Entering directory > > `/usr/ports/java/jdk16/work/j2se/make/java/hpi/native' > > /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused > > -Wno-parentheses -pipe-Damd64 -DARCH='"amd64"' -DRELEA > > E='"1.6.0_03-p4"' > > -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' > > -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. > > -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th > > reads/CClassHeaders -I.. ../../../src/solaris/javavm/export > > -I../../../../src/share/javavm/export > > -I../../../../src/share/javavm/include -I../../../.. > > src/solaris/javavm/include > > -I../../../../src/solaris/hpi/native_threads/include > > -I../../../../src/solaris/hpi/include -I../.. > > ../../src/solaris/hpi/export -I../../../../src/share/hpi/include > > -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS > > -DMOOT_PRIORITIES-c -o > > /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre > > ads/obj64/th eads_md.o > > ../../../../src/solaris/hpi/native_threads/src/threads_md.c /usr/bin/gcc > > -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe > > -Damd64 -DARCH='"amd64"' -DRELEA > > E='"1.6.0_03-p4"' > > -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' > > -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. > > -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th > > reads/CClassHeaders -I.. ../../../src/solaris/javavm/export > > -I../../../../src/share/javavm/export > > -I../../../../src/share/javavm/include -I../../../.. > > src/solaris/javavm/include > > -I../../../../src/solaris/hpi/native_threads/include > > -I../../../../src/solaris/hpi/include -I../.. > > ../../src/solaris/hpi/export -I../../../../src/share/hpi/include > > -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS > > -DMOOT_PRIORITIES-c -o > > /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre > > ads/obj64/mo itor_md.o > > ../../../../src/solaris/hpi/native_threads/src/monitor_md.c /usr/bin/gcc > > -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe > > -Damd64 -DARCH='"amd64"' -DRELEA > > E='"1.6.0_03-p4"' > > -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' > > -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. > > -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th > > reads/CClassHeaders -I.. ../../../src/solaris/javavm/export > > -I../../../../src/share/javavm/export > > -I../../../../src/share/javavm/include -I../../../.. > > src/solaris/javavm/include > > -I../../../../src/solaris/hpi/native_threads/include > > -I../../../../src/solaris/hpi/include -I../.. > > ../../src/solaris/hpi/export -I../../../../src/share/hpi/include > > -I../../../../src/share/hpi/export -D_REENTRANT -DNATIVE -DU E_PTHREADS > > -DMOOT_PRIORITIES-c -o > > /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_thre > > ads/obj64/co dvar_md.o > > ../../../../src/solaris/hpi/native_threads/src/condvar_md.c /usr/bin/gcc > > -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe > > -Damd64 -DARCH='"amd64"' -DRELEA > > E='"1.6.0_03-p4"' > > -DFULL_VERSION='"1.6.0_03-p4-rhurlin_10_dec_2009_21_46-b00"' > > -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_A LBSD_SOURCE -D_LP64=1 -I. > > -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/hpi/native_th > > reads/CClassHeaders -I.. ../../../src/solaris/javavm/export > > -I../../../../src/share/javavm/export > > -I../../../../src/share/javavm/include > > -I../../../../src/solaris/javavm/include > > -I../../../../src/solaris/hpi/native_threads/include > > -I../../../../src/solaris/h
tetex and texlive port
Hi all, I often use TeXLive instead of teTeX which isn't been developed anymore. After I remove teTeX from system, I encounter some problems when building/upgrading ports. For example, _evince_, _lyx_ couldn't be built without teTeX. (In fact, evince and lyx can be used with TeXLive.) It's nice to install teTeX, install LyX then remove teTeX. But as far as I know, teTeX is quite big and I don't know to pull it from the repository then just remove it. Because TeXLive is now the most sexy way for TeX users on *nix system, I suggest that FreeBSD should add TeXLive port, and something likes *texwrapper* that allows users to select teTeX or TeXLive. We can even move teTeX to *obsolete* :) I haven't any depth knowledge about the ports, but I can give some helps. I've just built TeXLive on my FreeBSD system (The latest TeXLive supports binary distribution for NetBSD while the previous ones have something for FreeBSD users.) Just my two cents. Regards, PS: Build TeXLive on FreeBSD (i386) http://viettug.org/wiki/tex/TeXLive_2009_Install_On_FreeBSD -- Anh Ky Huynh - TeX: http://viettug.org/ - BSD: http://lovebsd.net/ ___ 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"
