Re: fvwm 2.5.17 Issue
In message [EMAIL PROTECTED], Parv writes: in message [EMAIL PROTECTED], wrote Cy Schubert thusly... Fvwm2 2.5.17 was released, however it contains a nasty little bug which causes it to ignore colour specification for the text in a title bar. Until this issue is addressed, I will hold off on updating the port. Thanks Cy for both being current with the fvwm release holding back till the bug is fixed. I noticed other bugs in it too, such as various config statements no longer being recognised yet the strings exist in the source and the binary. I haven't looked at it closely yet but I suspect a serious yet small bug in pointer arithmetic, it's doing strange things. The more I look at it, it looks much less likely that that this release will ever be committed to the ports tree. I'm hoping that 2.5.18 will fix these bugs. Anyhow, for those who are gluttons for punishment, you can get 2.5.17 from http://komquats.com/ports/fvwm2-devel-2.5.17.tar.bz2. The files will not be available this weekend as my network will be down much of the weekend and possibly even parts of next week. -- Cheers, Cy Schubert [EMAIL PROTECTED] FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ 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!
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.] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: is somebody working on a xorg 7.1 port to FreeBSD ?
On Fri, 2006-07-21 at 08:51 +0200, Andreas Klemm wrote: Hi, interested to know, if there was only a talk or work going on to bring xorg 7.1 into freebsd ports. Yes, see: http://agrajag.ijs.si/trac/wiki/X11R7.0 -- Joel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't install ruby-bdb on RELEASE-6.1
On Friday 21 July 2006 09:45, Jim Trigg wrote: On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote: Jim Trigg wrote: I'm setting up a new system with 6.1-RELEASE, and I forgot to install portupgrade from a package during the OS install. ruby-bdb fails to build, complaining that it doesn't know how to make 'all' (it doesn't specify which directory it's in, but it's right after it runs extconf.rb). Any clues? (Note: when I posted this earlier I mentioned changing LOCALBASE. Further testing has shown that it fails regardless of LOCALBASE setting.) Make sure you have a fresh ports tree. May be you should reinstall ruby. I did have a fresh ports tree, and I've tried that. Full list of what I've done: - Installed 6.1-RELEASE from CD OK, fine. - Installed cvsup - Ran cvsup ports-all Please explain this a little more. What's ports-all? Is that the name of a sup-file you're using? If so, what's in it? - Attempted to install portupgrade with BDB4; ruby-bdb failed to build What is the failure message. The failure could have occurred at the beginning of ruby-bdb. Do you have /usr/ports/databases/db(what version?) installed? - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to $LOCALBASE Are you saying you uninstalled the ports-tree and reinstalled it using cvsup, or are you saying you uninstalled the installed ports? Is there a reason you are messing with LOCALBASE? Is this a linux thing you're doing? - Attempted to install portupgrade with BDB4; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE back to /usr/local - Installed ruby18, attempted to install ruby-bdb; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE back to /opt - Installed portupgrade with BDB1. See below. Thanks, Jim ___ Jim - I would suggest that you use portsnap rather than cvsup for the ports tree. Cvsup will work, and it will work fine, but portsnap will work better and faster and with less problems. I suggest you do it this way: actually the way I do it is: perf500# script /home/script/portsnap/20060721 (that's today's date) Script started, output file is /home/script/portsnap/20060721 perf500# portsnap fetch extract You don't have to run 'script', but in case there's a failure, I like to have something to look at to see if I can find what went wrong. You could just run 'portsnap fetch extract'. NOTE: unless you blow the ports-tree off, you only run 'portsnap fetch extract' once. After that you use: 'portsnap fetch update'. The first time you do this, it takes a bit of time to complete. After that, on my systems anyway, it takes about 2 minutes as compared to 15 to 20 using cvsup. If you're blowing off the ports-tree and rerunning cvsup to install it, portsnap is going to be way faster. What is the output from 'df -m'? Do you have anything in /etc/make.conf? I would suggest installing /usr/ports/databases/db43 before trying to install portupgrade. It might work out a little better for you. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade boost-python fails
# portupgrade -R boost-python ** Port marked as IGNORE: lang/python: at line 1477 (evaluated to true) ** Proceeding anyway since NO_IGNORE is defined ** Invalid package name: lang/python: 1 open conditional:: Must not contain whitespace. --- Skipping 'devel/boost-python' (boost-python-1.33.1) because a requisite package 'python-2.4.3' (lang/python) failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! lang/python (python-2.4.3)(invalid package name) * devel/boost-python (boost-python-1.33.1) --- Packages processed: 0 done, 0 ignored, 1 skipped and 1 failed When I tried without the -R I got something similar: # portupgrade boost-python ** Port marked as IGNORE: devel/boost-python: at line 1477 (evaluated to true) ** Proceeding anyway since NO_IGNORE is defined ** Invalid package name: devel/boost-python: 1 open conditional:: Must not contain whitespace. ** Listing the failed packages (*:skipped / !:failed) ! devel/boost-python (boost-python-1.33.1) (invalid package name) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed David -- Sure God created the world in only six days, but He didn't have an established user-base. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu broken on AMD64 system
This has already been fixed. Please re-cvsup and try again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu broken on AMD64 system
Awesomeeverything works fine again! You are getting faster and faster at these forums as time progresses:-) Just today I presented a plan at the company where I'm employed to use a open source BI tool and emphasized that the support from the community is excellent!! FreeBSD is NO EXCEPTION!!! Thanks --- Mark Linimon [EMAIL PROTECTED] wrote: This has already been fixed. Please re-cvsup and try again. mcl __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade boost-python fails
I just ran cvsup again and retried the portupgrade -R. Everything builds cleanly now. :) David -- Sure God created the world in only six days, but He didn't have an established user-base. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
