FreeBSD ports problem
I have been trying to install virtualbox support for my FreeBSD 9.1. A package named v4l_compat-1.0.20120501.tar.gz is causing problems in the installation. The package was downloaded automatically and it exists in /usr/ports/distfiles, yet it keeps giving an error stating that the file doesn't exist. Please help. *Harpreet Singh Chawla* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD ports problem
On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla preet10101...@gmail.com wrote: I have been trying to install virtualbox support for my FreeBSD 9.1. A package named v4l_compat-1.0.20120501.tar.gz is causing problems in the installation. The package was downloaded automatically and it exists in /usr/ports/distfiles, yet it keeps giving an error stating that the file doesn't exist. Please help. *Harpreet Singh Chawla* ___ No idea about virtualbox port, but have you tried deleting the offending file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? Amitabh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD ports problem
On Thu, Aug 29, 2013 at 11:39 PM, Harpreet Singh Chawla preet10101...@gmail.com wrote: yup...did it...and downloaded manually... But its giving a checksum matching error. *Harpreet Singh Chawla* On 29 August 2013 22:48, Amitabh Kant amitabhk...@gmail.com wrote: On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla preet10101...@gmail.com wrote: I have been trying to install virtualbox support for my FreeBSD 9.1. A package named v4l_compat-1.0.20120501.tar.gz is causing problems in the installation. The package was downloaded automatically and it exists in /usr/ports/distfiles, yet it keeps giving an error stating that the file doesn't exist. Please help. *Harpreet Singh Chawla* ___ No idea about virtualbox port, but have you tried deleting the offending file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? Amitabh After deleting, you don't need to download it manually. The port should download it if needed. Try updating your ports tree to see if the problem has been rectified. Amitabh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ports problem in an old system ver 4.9
I have an old FreeBSD 4.9 installation that I cannot upgrade. I wanted to install something from the ports, but I am getting this error on almost every port; # make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for rsnapshot-1.3.1 /sbin/sha256: not found *** Error code 127 Stop in /usr/ports/sysutils/rsnapshot. Wondering if anyone has an idea where to look. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports problem in an old system ver 4.9
On May 26, 2011, at 3:01 PM, David Banning wrote: I have an old FreeBSD 4.9 installation that I cannot upgrade. You've also got a FreeBSD installation which the ports tree does not support. I wanted to install something from the ports, but I am getting this error on almost every port; # make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for rsnapshot-1.3.1 /sbin/sha256: not found *** Error code 127 Stop in /usr/ports/sysutils/rsnapshot. I believe you can obtain a sha256 binary from GNU coreutils (although GNU calls it sha256sum), and then install it to /sbin. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports problem in an old system ver 4.9
On Thu, 26 May 2011 15:40:09 -0700 Chuck Swiger cswi...@mac.com wrote: On May 26, 2011, at 3:01 PM, David Banning wrote: I have an old FreeBSD 4.9 installation that I cannot upgrade. You've also got a FreeBSD installation which the ports tree does not support. I wanted to install something from the ports, but I am getting this error on almost every port; # make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for rsnapshot-1.3.1 /sbin/sha256: not found *** Error code 127 Stop in /usr/ports/sysutils/rsnapshot. I believe you can obtain a sha256 binary from GNU coreutils (although GNU calls it sha256sum), and then install it to /sbin. It's not drop-in replacement. The FreeBSD version sensibly just outputs the hash when hashing from stdin, but the gnu version prints a trailing -. It may be that the ports makefiles ignore the extra field, but it may require a wrapper script. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ports problem
Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Of course time will probably prove it to be an utterly boneheaded thing to do, but it seems to work for now. # mv /usr/X11R6 /usr/X11R6-2 # ln -s /usr/X11R6-2 /usr/X11R6 # make install Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. Of course time will probably prove it to be an utterly boneheaded thing to do, but it seems to work for now. # mv /usr/X11R6 /usr/X11R6-2 # ln -s /usr/X11R6-2 /usr/X11R6 # make install You should put it back and run the mergebase script. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
RW wrote: On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. I didn't read it that way. You're right though. I'll check out mergebase.sh, see if it does anything I need. Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
Adam J Richardson wrote: RW wrote: On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. I didn't read it that way. You're right though. I'll check out mergebase.sh, see if it does anything I need. From what I can see, ports used to respect the settings of X11BASE and LOCALBASE, but even though they are still supposed to do that, well, I can see from my own attempts here on my box, that they don't do that. I found a bunch of stuff that either assumed /usr/local, or got the install path by reading the pkgconfig .pc files. LONG time back, I showed folks that it was a fairly trivial (two code lines) thing that was needed to make the X11 stuff go wherever you wanted it to go, but those two lines were in the 'imake' shell wrapper, and folks felt that the imake wrapper was holy writ for some reason, and would not let me make any changes to it. Pity. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports problem
Hello.
I am having multiple problems with the ports collection
# cd /usr/ports/ports-mgmt/portupgrade
# make install clean
=== Installing for portupgrade-2.3.1,2
=== portupgrade-2.3.1,2 depends on file: /usr/local/bin/ruby18 - found
=== portupgrade-2.3.1,2 depends on file:
/usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so - found
=== portupgrade-2.3.1,2 depends on file: /usr/local/bin/perl5.8.8 - found
=== Generating temporary packing list
=== Checking if ports-mgmt/portupgrade already installed
=== bin (install)
install -o root -g wheel -m 555 .build/pkg_fetch /usr/local/sbin/pkg_fetch
install -o root -g wheel -m 555 .build/pkg_glob /usr/local/sbin/pkg_glob
install -o root -g wheel -m 555 .build/pkg_sort /usr/local/sbin/pkg_sort
install -o root -g wheel -m 555 .build/pkgdb /usr/local/sbin/pkgdb
install -o root -g wheel -m 555 .build/portcvsweb /usr/local/sbin/portcvsweb
install -o root -g wheel -m 555 .build/portsclean /usr/local/sbin/portsclean
install -o root -g wheel -m 555 .build/portsdb /usr/local/sbin/portsdb
install -o root -g wheel -m 555 .build/portupgrade
/usr/local/sbin/portupgrade
install -o root -g wheel -m 555 .build/portversion
/usr/local/sbin/portversion
/usr/local/sbin/pkg_deinstall - /usr/local/sbin/pkg_glob
/usr/local/sbin/pkg_which - /usr/local/sbin/pkgdb
/usr/local/sbin/portinstall - /usr/local/sbin/portupgrade
/usr/local/sbin/ports_glob - /usr/local/sbin/portsdb
=== etc (install)
install -o root -g wheel -m 555 .build/status-pkg.sh
/usr/local/etc/pkgtools.status-pkg.sh
install -o root -g wheel -m 444 pkgtools.conf
/usr/local/etc/pkgtools.conf.sample
=== lib (install)
install -o root -g wheel -m 444 .build/pkg.rb .build/pkgdb.rb
.build/pkgdbtools.rb .build/pkginfo.rb .build/pkgmisc.rb .build/pkgtools.rb
.build/pkgtsort.rb .build/pkgversion.rb .build/portinfo.rb .build/ports.rb
.build/portsdb.rb `/usr/local/bin/ruby18 -rrbconfig -e 'puts %s/%s.%s %
%w[sitedir MAJOR MINOR].map { |k| Config::CONFIG[k] }'`
=== man (install)
install -o root -g wheel -m 444 pkg_deinstall.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 pkg_fetch.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 pkg_glob.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 pkg_sort.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 pkgdb.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 portcvsweb.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 portsclean.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 portsdb.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 portupgrade.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 portversion.1.gz /usr/local/man/man1
install -o root -g wheel -m 444 pkgtools.conf.5.gz /usr/local/man/man5
/usr/local/man/man1/pkg_which.1.gz - /usr/local/man/man1/pkgdb.1.gz
/usr/local/man/man1/portinstall.1.gz - /usr/local/man/man1/portupgrade.1.gz
/usr/local/man/man1/ports_glob.1.gz - /usr/local/man/man1/portsdb.1.gz
=== misc (install)
=== misc/bash (install)
mkdir -p /usr/local/share/examples/pkgtools/bash
install -o root -g wheel -m 444 complete.sample
/usr/local/share/examples/pkgtools/bash
=== misc/tcsh (install)
mkdir -p /usr/local/share/examples/pkgtools/tcsh
install -o root -g wheel -m 444 complete.sample
/usr/local/share/examples/pkgtools/tcsh
=== misc/zsh (install)
mkdir -p /usr/local/share/zsh/site-functions
install -o root -g wheel -m 444 _pkgtools /usr/local/share/zsh/site-functions
mkdir -p /usr/local/share/doc/pkgtools
install -c -o root -g wheel -m 444 ChangeLog NEWS README
/usr/local/share/doc/pkgtools
=== Running ldconfig
/sbin/ldconfig -m /usr/local/lib/compat/pkg
ldconfig: warning: /usr/local/lib/compat/pkg: No such file or directory
=== Installing ldconfig configuration file
if [ ! -f /usr/local/etc/pkgtools.conf ]; then /bin/cp -p
/usr/local/etc/pkgtools.conf.sample /usr/local/etc/pkgtools.conf; fi
/bin/mkdir -p /usr/local/lib/compat/pkg
/bin/cat /usr/ports/ports-mgmt/portupgrade/pkg-message
--
Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade
be aware of alternative dependencies you use.
E.g.
ALT_PKGDEP = {
'www/apache13' = 'www/apache13-modssl',
'print/ghostscript-gnu' = 'print/ghostscript-gpl',
}
Note also, portupgrade knows nothing how to handle ports with different
suffixes (E.g. -nox11). So you should explicitly define variables
(E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or pkgtools.conf
(MAKE_ARGS section) files.
--
=== Registering installation for portupgrade-2.3.1,2
=== Cleaning for portupgrade-2.3.1,2
# portsdb -Uu
portsdb: Command not found.
# cd kdenetwork3
# make
=== Vulnerability check disabled, database not found
=== Found saved configuration for kdenetwork-3.5.4
=
Re: Ports problem
On Sun, 4 Nov 2007 12:30:07 + Desmond Chapman [EMAIL PROTECTED] wrote: Hello. I am having multiple problems with the ports collection # cd /usr/ports/ports-mgmt/portupgrade # make install clean [ build log removed for brevity ] === Registering installation for portupgrade-2.3.1,2 === Cleaning for portupgrade-2.3.1,2 # portsdb -Uu portsdb: Command not found. From the Handbook section 4.5.2 Installing Ports: Note: Some shells keep a cache of the commands that are available in the directories listed in the PATH environment variable, to speed up lookup operations for the executable file of these commands. If you are using one of these shells, you might have to use the rehash command after installing a port, before the newly installed commands can be used. This command will work for shells like tcsh. Use the hash -r command for shells like sh. Look at the documentation for your shell for more information. If you are using root's default shell, then rehash is probably what you want. # cd kdenetwork3 # make [ Log detail omitted ] === qt-copy-3.3.8_6 depends on file: /usr/local/libdata/xorg/libraries - not found ===Verifying install for /usr/local/libdata/xorg/libraries in /usr/ports/x11/xorg-libraries The following is probably causing the multiple problems you are seeing: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 [ More log detail omitted ] I have done the cvsup, csup, portsnap, and followed the instructions ion /usr/ports/UPDATING. I get thses same results each time. How do i fix this? Any help would be appreciated. It appears that you missed the /usr/ports/UPDATING (entry of 20070519) or forgot to run the script. There is a script (mergebase.sh) to run which creates the symlink for /usr/X11R6 (as well as other things). It might be a good idea to review that UPDATING entry and see if there are other things that might apply. HTH, Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 AMD64 Ports Problem
I downloaded the 6.2 AMD64 disk 1 iso, installed it and updated the ports with cvsup. However, when I try to install xorg it's looking for ports that are not in the packages-6.2 folder. Instead they are in the packages-7-current or packages-current folder. Is it safe to install from those folders? In an attempt to get one of the updated ports I put in the /root/.profile PKG_PATH=ftp://ftp.freebsd.org/pub/FreeBSD/ports/amb64/packages-current; and logged out. But when I run PKG_ADD -r dri-7.0.1,2.tbz. It tells me it could not find the port. Why doesnt it pick up the PKG_PATH from the .profile? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 AMD64 Ports Problem
I downloaded the 6.2 AMD64 disk 1 iso, installed it and updated the ports with cvsup. However, when I try to install xorg it's looking for ports that are not in the packages-6.2 folder. Instead they are in the packages-7-current or packages-current folder. Is it safe to install from those folders? In an attempt to get one of the updated ports I put in the /root/.profile PKG_PATH=ftp://ftp.freebsd.org/pub/FreeBSD/ports/amb64/packages-current; and logged out. But when I run PKG_ADD -r dri-7.0.1,2.tbz. It tells me it could not find the port. Why doesnt it pick up the PKG_PATH from the .profile? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 AMD64 Ports Problem
[EMAIL PROTECTED] wrote: I downloaded the 6.2 AMD64 disk 1 iso, installed it and updated the ports with cvsup. However, when I try to install xorg it's looking for ports that are not in the packages-6.2 folder. Instead they are in the packages-7-current or packages-current folder. Is it safe to install from those folders? Not on a 6.2 system. They would link against libc.so.7 and you'd only have libc.so.6 for one. I did not have this problem. In an attempt to get one of the updated ports I put in the /root/.profile PKG_PATH=ftp://ftp.freebsd.org/pub/FreeBSD/ports/amb64/packages-current; and logged out. But when I run PKG_ADD -r dri-7.0.1,2.tbz. It tells me it could not find the port. You want PACKAGESITE i.e. PACKAGESITE=ftp://ftp13.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.2-release/Latest/ The trailing / is important. -- Philip M. Gollucci ([EMAIL PROTECTED]) c:323.219.4708 o:703.749.9295x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 AMD64 Ports Problem
Thats weird. When I updated using cvsup it updated all of the ports in my /usr/ports directory. I then ran make install on /usr/ports/x11/xorg, it then looks for dri-7.0.1,2.tbz, but that file isn't in amd64/packages-6.2-release/latest or amd64/packages-6.2-release/graphics/. It is only in the packages-7-release/graphics directory. Why would xorg require a app that isn't in my current build? How do I get around it if I cant use the packages-7-release files? Thanks for you help Thron On Mon Sep 17 11:21 , Philip M. Gollucci sent: [EMAIL PROTECTED] wrote: I downloaded the 6.2 AMD64 disk 1 iso, installed it and updated the ports with cvsup. However, when I try to install xorg it's looking for ports that are not in the packages-6.2 folder. Instead they are in the packages-7-current or packages-current folder. Is it safe to install from those folders? Not on a 6.2 system. They would link against libc.so.7 and you'd only have libc.so.6 for one. I did not have this problem. In an attempt to get one of the updated ports I put in the /root/.profile PKG_PATH=ftp://ftp.freebsd.org/pub/FreeBSD/ports/amb64/packages-current; and logged out. But when I run PKG_ADD -r dri-7.0.1,2.tbz. It tells me it could not find the port. You want PACKAGESITE i.e. PACKAGESITE=ftp://ftp13.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.2-release/Latest/ The trailing / is important. -- Philip M. Gollucci ([EMAIL PROTECTED]) c:323.219.4708 o:703.749.9295x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 AMD64 Ports Problem
[EMAIL PROTECTED] wrote: Thats weird. When I updated using cvsup it updated all of the ports in my /usr/ports directory. I then ran make install on /usr/ports/x11/xorg, it then looks for dri-7.0.1,2.tbz, but that file isn't in amd64/packages-6.2-release/latest or amd64/packages-6.2-release/graphics/. It is only in the packages-7-release/graphics directory. Why would xorg require a app that isn't in my current build? How do I get around it if I cant use the packages-7-release files? A couple of points: 1) 'make install' doesn't try to install packages, it installs ports. In particular 'make install' doesn't fetch packages from the FTP site, these are added by pkg_add -r (and other commands). 2) Updated packages for 6.x are in the packages-6-stable/ directory. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Subversion ports problem
I'm running 5.3, and I'm trying to upgrade subverson and I get the following: === Building for subversion-1.3.2 cd subversion/libsvn_subr /usr/local/bin/libtool --tag=CC --silent --mode=link cc -O -pipe -g -O2 -L/usr/local/lib/db42 -L/usr/local/lib -rpath /usr/local/lib -o libsvn_subr-1.la auth.lo cmdline.lo config.lo config_auth.lo config_file.lo config_win.lo constructors.lo ctype.lo date.lo error.lo hash.lo io.lo lock.lo md5.lo nls.lo opt.lo path.lo pool.lo quoprint.lo sorts.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo time.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo -L/usr/local/lib -R/usr/local/lib -laprutil-1 -ldb-4.2 -lexpat -liconv -L/usr/local/lib -R/usr/local/lib -lapr-1 -lcrypt -lpthread -lintl /usr/bin/ld: cannot find -ldb-4.2 *** Error code 1 I have db4 up-to-date: db4-4.0.14_1,1 = up-to-date with port I've tried using portupgrade, portinstall and the make system and I get the same error. I've tried installing with WITHOUT_DBD and nothing helps... Any ideas what I am doing wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Subversion ports problem
On Monday 12 June 2006 01:00, Ron wrote: I'm running 5.3, and I'm trying to upgrade subverson and I get the following: === Building for subversion-1.3.2 cd subversion/libsvn_subr /usr/local/bin/libtool --tag=CC --silent --mode=link cc -O -pipe -g -O2 -L/usr/local/lib/db42 -L/usr/local/lib -rpath /usr/local/lib -o libsvn_subr-1.la auth.lo cmdline.lo config.lo config_auth.lo config_file.lo config_win.lo constructors.lo ctype.lo date.lo error.lo hash.lo io.lo lock.lo md5.lo nls.lo opt.lo path.lo pool.lo quoprint.lo sorts.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo time.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo -L/usr/local/lib -R/usr/local/lib -laprutil-1 -ldb-4.2 -lexpat -liconv -L/usr/local/lib -R/usr/local/lib -lapr-1 -lcrypt -lpthread -lintl /usr/bin/ld: cannot find -ldb-4.2 *** Error code 1 I have db4 up-to-date: db4-4.0.14_1,1 = up-to-date with port I've tried using portupgrade, portinstall and the make system and I get the same error. I've tried installing with WITHOUT_DBD and nothing helps... Hello, db-4.2 is required for the port. Go to the /usr/ports/databases/db42 directory and build this port. You should find some conflicts with the installed version, but you can make a portupgrade -vrR db4, and also this may impact other installed packages. Any ideas what I am doing wrong? This should help you... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- . 0 . | Daniel Molina Wegener . . 0 | dmw at unete dot cl 0 0 0 | FreeBSD User ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Subversion ports problem
Hello, db-4.2 is required for the port. Go to the /usr/ports/databases/db42 directory and build this port. You should find some conflicts with the installed version, but you can make a portupgrade -vrR db4, and also this may impact other installed packages. OK, I think I'm starting to understand why this got messed up before. My eyes were playing tricks on me, and I ignored a error I should not have... But now, if I try to install 4.2, I get: === Vulnerability check disabled, database not found === Extracting for db42-4.2.52_4 = MD5 Checksum mismatch for bdb/db-4.2.52.tar.gz. = MD5 Checksum OK for bdb/patch.4.2.52.1. = MD5 Checksum OK for bdb/patch.4.2.52.2. = MD5 Checksum OK for bdb/patch.4.2.52.3. = MD5 Checksum OK for bdb/patch.4.2.52.4. === Refetch for 1 more times files: bdb/db-4.2.52.tar.gz === Vulnerability check disabled, database not found = db-4.2.52.tar.gz doesn't seem to exist in /usr/ports/distfiles/bdb. = Attempting to fetch from http://downloads.sleepycat.com/. fetch: http://downloads.sleepycat.com/db-4.2.52.tar.gz: Requested Range Not Satisfiable I grab this file by hand and it built and subversion built as well. bla.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports problem with openssl-0.9.x
When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? Thanks, Don Hayford [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem with openssl-0.9.x
On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris pgp1WU4ARd8Ol.pgp Description: PGP signature
Re: Ports problem with openssl-0.9.x
Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i === openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/openssl. *** Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade52117.1 make ** Fix the problem and try again. --- Skipping 'misc/kdeutils3' (kdeutils-3.4.2) because a requisite package 'net-snmp-5.2.1.2' (net-mgmt/net-snmp) failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! net-mgmt/net-snmp (net-snmp-5.2.1.2) (unknown build error) * misc/kdeutils3 (kdeutils-3.4.2) So while kde... may not be looking for it, net-snmp is. Perhaps this should be a more general question on what to do if/when various ports get out of sync and are trying to use other inconsistent packages. Thanks - Don Hayford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem with openssl-0.9.x
On Tue, Dec 06, 2005 at 10:03:09PM -0500, Donald T Hayford wrote: Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i I believe you, but update your ports. Kris pgp3esmZQhGUh.pgp Description: PGP signature
Re: Ports problem with openssl-0.9.x
Kris Kennaway wrote: On Tue, Dec 06, 2005 at 10:03:09PM -0500, Donald T Hayford wrote: Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i I believe you, but update your ports. Kris I did have a problem with my ports that I don't fully understand, but .. oh well. I updated ports today and yesterday hoping to get rid of the problem. Apparently when I installed the openoffice.org-2 package OOo_2.0m142_FreeBSD60Intel_install_en-US.tbz, I slipped in a dependency on the beta version of openssl instead of the stable version called for. Don't know how. I fixed the problem by deinstalling the openssl-beta version, installing the openssl-stable version, and then running pkgdb -F to fix the incorrect dependencies that I generated. Thanks much for your help. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problem/question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today Peter Vereshagin had this to say: On Tue, 12 Jul 2005 15:28:05 -0500 (CDT) Denny White [EMAIL PROTECTED] wrote: to install cdrdao which is currently version 1.1.9, I believe, then failed, with message saying there's a vulnerability. There's a fixed my question about the lagtime between fix and inclusion. Meantime, still using burncd. Danny, it uses to be easy to fix the port yourself --- just correct distinfo and version in Makefile to correspond the upgraded source tarball. You should send a message to the port maintainer and your best should be to supply him/her with the upgraded port as a .tbz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for the answer. I went ahead did a make -DDISABLE_VULNERABILITIES install clean in /usr/ports/sysutils/cdrdao. After that, k3b installed without any problem. I cvsup ports on a regular basis, also watch the cvs mailing list. Hopefully, before too long, the port maintainer will fix the problem with cdrdao. I ran into the same thing last month with ruby. Just didn't have much of a handle on how long fixes usually take to show up in the src or ports tree once they're done. Thanks again. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1Mqwy0Ty5RZE55oRAr47AKCM1jc36PsDYN+W7rSy6xxvv8G91QCeK3Kq aQpziLyDfPrq3n0TCgec/Lo= =SxCC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ports problem/question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I know this concerns the ports mailing list, but I just wanted to ask this list, for those who've run into the same the same problem, how long it usually takes before a port is included on the mirrors once a problem has been fixed with it. I tried to install /usr/ports/sysutils/k3b for the cd-writer it got as far as it trying to install cdrdao which is currently version 1.1.9, I believe, then failed, with message saying there's a vulnerability. There's a fixed version at Sourceforge, but I hate to mess with anything on my system that's not been checked, approved included in the ports tree. Hence, my question about the lagtime between fix and inclusion. Meantime, still using burncd. Thanks for any feedback/help. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1Cffy0Ty5RZE55oRAj/xAJ9rGl82pCz/o1S+dUxmtWLjk9GAkACgsxkE H1g3yJ2dNrQSE34M4TfYAM0= =9G7I -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problem/question
On Tue, 12 Jul 2005 15:28:05 -0500 (CDT) Denny White [EMAIL PROTECTED] wrote: to install cdrdao which is currently version 1.1.9, I believe, then failed, with message saying there's a vulnerability. There's a fixed my question about the lagtime between fix and inclusion. Meantime, still using burncd. Danny, it uses to be easy to fix the port yourself --- just correct distinfo and version in Makefile to correspond the upgraded source tarball. You should send a message to the port maintainer and your best should be to supply him/her with the upgraded port as a .tbz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoying ports problem
On Thursday 17 February 2005 11:37 pm, Heinrich Rebehn wrote: Eric Kjeldergaard wrote: On Thu, 17 Feb 2005 10:45:36 +0100, Heinrich Rebehn [EMAIL PROTECTED] wrote: Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Just make will make the program and try to install it as if it were the first time. When it detects the older version, it will want you to do make deinstall make reinstall. For upgrading ports, you may want to look at /usr/ports/sysutils/portupgrade. It makes no difference wether i use make or portupgrade. As soon as ether of them decide that another package that the make candidate depends on, has to be upgraded, the error occurs with that package. Have you tried upgrading using sysutils/portmanager yet? -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoying ports problem
On Friday 18 February 2005 08:37, Heinrich Rebehn wrote: Eric Kjeldergaard wrote: On Thu, 17 Feb 2005 10:45:36 +0100, Heinrich Rebehn [EMAIL PROTECTED] wrote: Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Just make will make the program and try to install it as if it were the first time. When it detects the older version, it will want you to do make deinstall make reinstall. For upgrading ports, you may want to look at /usr/ports/sysutils/portupgrade. The problem is that the OP *is* using portupgrade. It makes no difference wether i use make or portupgrade. As soon as ether of them decide that another package that the make candidate depends on, has to be upgraded, the error occurs with that package. And if you do 'portupgrade -f gnomevfs2' (forced upgrade) *before* 'portupgrade gstreamer-plugins'? It recently solved similar problems for me, in particular with the perl-related ports. Karel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Annoying ports problem
Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Regards, -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoying ports problem
you're in the wrong way... to update all your ports you must use portupgrade from ports, but if you are sure what u'r doing simply add FORCE_PKG_REGISTER=yes in your /etc/make.conf but after time you could have some trouble in your PKGDB bye Davide - Original Message - From: Heinrich Rebehn [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Thursday, February 17, 2005 10:45 AM Subject: Annoying ports problem Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Regards, -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoying ports problem
On Thu, 17 Feb 2005 10:45:36 +0100, Heinrich Rebehn [EMAIL PROTECTED] wrote: Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Just make will make the program and try to install it as if it were the first time. When it detects the older version, it will want you to do make deinstall make reinstall. For upgrading ports, you may want to look at /usr/ports/sysutils/portupgrade. -- If I write a signature, my emails will appear more personalised. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoying ports problem
Eric Kjeldergaard wrote: On Thu, 17 Feb 2005 10:45:36 +0100, Heinrich Rebehn [EMAIL PROTECTED] wrote: Hi list, I have run into an annoying problem several times when upgrading ports. Say, if i want to upgrade gstreamer-plugins, i do: # cd /usr/ports/multimedia/gstreamer-plugins # make This pulls in some dependencies, for example gnomevfs2. gnnomevfs2 will compile fine, but then stops because it wants to install gnomevfs2 instead of reinstalling it: === An older version of devel/gnomevfs2 is already installed (gnomevfs2-2.9.91) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gnomevfs2 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Since i have run into this several times, i must be missing something substantial. What is it? Just make will make the program and try to install it as if it were the first time. When it detects the older version, it will want you to do make deinstall make reinstall. For upgrading ports, you may want to look at /usr/ports/sysutils/portupgrade. It makes no difference wether i use make or portupgrade. As soon as ether of them decide that another package that the make candidate depends on, has to be upgraded, the error occurs with that package. -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: REALLY frustrated with ports problem
Thanks, guys, it was the optimization settings. I was trying the ones I found on the bsd-tuning page, and thought -O3 was okay for non-kernel. You just helped a MAJOR headache go away. ;-) NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: REALLY frustrated with ports problem
On Fri, Mar 05, 2004 at 12:01:36PM +, Jonathon McKitrick wrote: Thanks, guys, it was the optimization settings. I was trying the ones I found on the bsd-tuning page, and thought -O3 was okay for non-kernel. Please be sure to tell whoever wrote the bsd-tuning page that they're giving out bad advice. Kris pgp0.pgp Description: PGP signature
REALLY frustrated with ports problem
What do I have to do to resolve this ports/pthread problem? I am having this problem with MANY ports recently. I don't have it on my 4.8 box, but 4.9-stable is turning into a nightmare. cc -Wall -O3 -pipe -funroll-loops -ffast-math -march=pentiumpro -I. -I. -I/usr /local/include/tk8.4 -I/usr/local/include/tcl8.4 -I/usr/X11R6/include -o bltwis h -DTCLLIBPATH=\/usr/local/lib//tcl8.4\ ./bltUnixMain.c libBLT.a -L/usr/loca l/lib/ -ltk84 -ltcl84 -L/usr/X11R6/lib -lX11 -lm /usr/X11R6/lib/libX11.so: undefined reference to `pthread_cond_signal' /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_cond_broadcast' /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_self_stub_' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_cond_init' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_mutex_unlock' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_self' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_mutex_destroy' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_mutex_lock' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_cond_wait' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_cond_destroy' /usr/X11R6/lib/libX11.so: undefined reference to `pthread_mutex_init' *** Error code 1 Stop in /usr/ports/x11-toolkits/blt/work/blt2.4z/src. NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: REALLY frustrated with ports problem
On Fri, 2004-03-05 at 01:10 +, Jonathon McKitrick wrote: What do I have to do to resolve this ports/pthread problem? cc -Wall -O3 -pipe -funroll-loops -ffast-math -march=pentiumpro Lower your optimization settings and get rid of the -ffoo optimisations? make.conf states you should use -O -pipe only. Most ports have option to increase the optimisation settings, or add the correct ones in their Makefiles. -O3 is going to make your overall system rather unstable. -- You keep using that word. I do not think it means what you think it means. FreeBSD 5.2-CURRENT i386 9:23am up 21:43, 4 users, load averages: 2.47, 2.76, 2.62 signature.asc Description: This is a digitally signed message part
Re: REALLY frustrated with ports problem
On Fri, Mar 05, 2004 at 01:10:46AM +, Jonathon McKitrick wrote: What do I have to do to resolve this ports/pthread problem? I am having this problem with MANY ports recently. I don't have it on my 4.8 box, but 4.9-stable is turning into a nightmare. cc -Wall -O3 -pipe -funroll-loops -ffast-math -march=pentiumpro -I. -I. Read the sample make.conf and do what it says about optimizations. Kris pgp0.pgp Description: PGP signature
Read-only /usr/ports (problem with fontconfig)
Is a read-only /usr/ports directory supported? I received the following error message during installation of x11-fonts/fontconfig (as part of a build of x11/XFree86-4): install -c -o root -g wheel -m 444 ./fontconfig.pc /usr/X11R6/libdata/pkgconfig /fontconfig.pc gmake[2]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc onfig-2.1.92' gmake[1]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc onfig-2.1.92' === Generating temporary packing list cannot create /usr/ports/x11-fonts/fontconfig/pkg-install: read-only file system *** Error code 2 Stop in /usr/ports/x11-fonts/fontconfig. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. My /usr/ports directory is NFS mounted (read-only) from another system. I have the following entries in /etc/make.conf to allow multiple clients to share the same /usr/ports tree: WRKDIRPREFIX= /usr/work (local directory) DISTDIR=/usr/distfiles (NFS mounted read-write) Is it normal for a port to try to write into /usr/ports when WRKDIRPREFIX is defined like this? Thanks in advance, Cory. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Read-only /usr/ports (problem with fontconfig)
In [EMAIL PROTECTED], Cory Bajus [EMAIL PROTECTED] typed: Is a read-only /usr/ports directory supported? Yes, it is. You're supposed to be able to build ports off of a CDROM. I received the following error message during installation of x11-fonts/fontconfig (as part of a build of x11/XFree86-4): install -c -o root -g wheel -m 444 ./fontconfig.pc /usr/X11R6/libdata/pkgconfig /fontconfig.pc gmake[2]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc onfig-2.1.92' gmake[1]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc onfig-2.1.92' === Generating temporary packing list cannot create /usr/ports/x11-fonts/fontconfig/pkg-install: read-only file system *** Error code 2 Stop in /usr/ports/x11-fonts/fontconfig. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. My /usr/ports directory is NFS mounted (read-only) from another system. I have the following entries in /etc/make.conf to allow multiple clients to share the same /usr/ports tree: WRKDIRPREFIX= /usr/work (local directory) DISTDIR=/usr/distfiles (NFS mounted read-write) Is it normal for a port to try to write into /usr/ports when WRKDIRPREFIX is defined like this? No, it isn't. I've been using a setup similar to yours for years, and have never had a problem. I could swear I saw a note in the porter's handbook that scratch files were supposed to be built in $(WRKDIR), which is in $(WRKDIRPREFIX). I'd contact the maintainer of the of the fontconfig port about this - it seems like it's touching something it shouldn't. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating ports problem!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (11.06.2002 @ 1930 PST): Warren Block said, in 0.6K: Lucky I put the water down before reading that--you almost owed me a new keyboard! Gotcher keyboard. ::) Ermmn, I mean, I did it to migrate to the new PORTCOMMENT Makefile variable, which deprecates the pkg-comment files. Okay. Section 2.2.1 of the Porter's Handbook needs to be updated. I can submit a PR, although my last PR is still waiting for action (43755--it's really easy). The reason this hasn't happened yet (other than the fact that nobody's done it) is that the PORTCOMMENTness hasn't been fully ironed out yet. Still being decided is what the variables will be called (COMMENT? PORTCOMMENT? SPORK?), where they will appear officially (I put it in right after MAINTAINER... I've since heard that it should have gone in after *_DEPENDS, and I've also heard that it should go in after all the USE_* varbs), and most importantly, the functionality isn't all there yet. For example: currently, a PORTCOMMENT line cannot contain any apostraphes; unbalanced quotation marks, brackets, or parenthesis; or 2 plus signs in a row (C++, anyone?). All this is currently under review and will be decided once it is no longer under review and has been decided. At that point, then would be a good time to bust out with a PR. Then referring to at that point. The previous sentence failed to make that clear. Also, if you want your vnconfig(8) patch to go through faster, create an actual patch that the docs team can use. Anything that creates less work and more result will be music to a committer's, uhm, fingers. - -Adam - -- Adam Weinberger [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE9yiU6o8KM2ULHQ/0RAqclAJ4maxlsAehzg6BsDPwcp8mfSbrQZQCfd7vP imK+JxQ1aY40WWfUKTH/e80= =dsik -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Updating ports problem!
I just tried to cvsup my ports collection like I do every few days and have for months... However, this time, the update seems to be removing all my ports! This just goes on for pages and pages before I cancel: Edit ports/science/xloops-ginac/Makefile Delete ports/science/xloops-ginac/pkg-comment Edit ports/security/Makefile Edit ports/security/acid/Makefile Delete ports/security/acid/pkg-comment Edit ports/security/aide/Makefile Edit ports/security/aide/distinfo Edit ports/security/aide/files/aide.conf.freebsd Delete ports/security/aide/files/patch-aa With what appears to be every port! What's up with it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Updating ports problem!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (11.06.2002 @ 1856 PST): Scott Carmichael said, in 0.7K: I just tried to cvsup my ports collection like I do every few days and have for months... However, this time, the update seems to be removing all my ports! This just goes on for pages and pages before I cancel: Edit ports/science/xloops-ginac/Makefile Delete ports/science/xloops-ginac/pkg-comment Edit ports/security/Makefile Edit ports/security/acid/Makefile Delete ports/security/acid/pkg-comment Edit ports/security/aide/Makefile Edit ports/security/aide/distinfo Edit ports/security/aide/files/aide.conf.freebsd Delete ports/security/aide/files/patch-aa With what appears to be every port! What's up with it? end of Updating ports problem! from Scott Carmichael I nuked 1500 pkg-comment files today. Nothing to worry about. As long as the Makefiles aren't being deleted, there's nothing wrong. - -Adam - -- Adam Weinberger [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE9ydewo8KM2ULHQ/0RAq8/AJ0fL2bPiLsi540pyVG8K9CuRnj6qACg3Z8Z kLE9KcqKfx+9O6K3ODIKGbQ= =9gqo -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Updating ports problem!
On Wed, 6 Nov 2002, Scott Carmichael wrote: I just tried to cvsup my ports collection like I do every few days and have for months... However, this time, the update seems to be removing all my ports! This just goes on for pages and pages before I cancel: Edit ports/science/xloops-ginac/Makefile Delete ports/science/xloops-ginac/pkg-comment Edit ports/security/Makefile Edit ports/security/acid/Makefile Delete ports/security/acid/pkg-comment Edit ports/security/aide/Makefile Edit ports/security/aide/distinfo Edit ports/security/aide/files/aide.conf.freebsd Delete ports/security/aide/files/patch-aa It's not removing the entire port, just some files within each port so it'll match the master. A couple of pkg-comment files, a patch file... I'm curious as to why Adam deleted so many pkg-comment files, though. -Warren Block * Rapid City, South Dakota USA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Updating ports problem!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (11.06.2002 @ 1909 PST): Warren Block said, in 0.9K: It's not removing the entire port, just some files within each port so it'll match the master. A couple of pkg-comment files, a patch file... I'm curious as to why Adam deleted so many pkg-comment files, though. end of Re: Updating ports problem! from Warren Block They were pissing me off. Ermmn, I mean, I did it to migrate to the new PORTCOMMENT Makefile variable, which deprecates the pkg-comment files. I just readded 105 of them, in an effort to really annoy people with dial-up connections or using CTM. - -Adam - -- Adam Weinberger [EMAIL PROTECTED] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE9ydtYo8KM2ULHQ/0RAl1pAJ497Ni9SLKb+wWIy8BPuA0fV2cu/wCeMiU7 XaGxa0+shEhu8YzYeWKkpcc= =IL92 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Updating ports problem!
On Wed, 6 Nov 2002, Adam Weinberger wrote: (11.06.2002 @ 1909 PST): Warren Block said, in 0.9K: I'm curious as to why Adam deleted so many pkg-comment files, though. They were pissing me off. Lucky I put the water down before reading that--you almost owed me a new keyboard! Ermmn, I mean, I did it to migrate to the new PORTCOMMENT Makefile variable, which deprecates the pkg-comment files. Okay. Section 2.2.1 of the Porter's Handbook needs to be updated. I can submit a PR, although my last PR is still waiting for action (43755--it's really easy). -Warren Block * Rapid City, South Dakota USA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: squirrel mail install-from-ports problem....
On Fri, 2002-10-25 at 02:30, Bsd Neophyte wrote: i'm getting the following error and it says that this should be reported to [EMAIL PROTECTED] but before i do that, i wanted some input to see if i could resolve this issue in a relatively simply way. is this an issue with how i installed apache... should i reinstall if with the --with-apxs2 option? I'd suggest you install PHP4 individually first, eg: cd /usr/ports/www/mod_php4 make -DWITH_APACHE2 install clean Then install squirrelmail, it looks like you have Apache 2 installed and PHP can't autodetect it so it needs that -D option set. -- Simon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: squirrel mail install-from-ports problem....
On Fri, Oct 25, 2002 at 04:04:07PM +0100, Simon Dick wrote:
On Fri, 2002-10-25 at 02:30, Bsd Neophyte wrote:
i'm getting the following error and it says that this should be reported
to [EMAIL PROTECTED]
but before i do that, i wanted some input to see if i could resolve this
issue in a relatively simply way.
is this an issue with how i installed apache... should i reinstall if with
the --with-apxs2 option?
I'd suggest you install PHP4 individually first, eg:
cd /usr/ports/www/mod_php4
make -DWITH_APACHE2 install clean
Then install squirrelmail, it looks like you have Apache 2 installed and
PHP can't autodetect it so it needs that -D option set.
Unfortunately, the Makefile for the squirrelmail port says:
RUN_DEPENDS+= ${LOCALBASE}/libexec/apache/libphp4.so:${PORTSDIR}/www/mod_php4
which means that if ${LOCALBASE}/libexec/apache/libphp4.so cannot be
found at compile/install time, the squirrelmail port will try and
install mod_php4 to fulfil the dependency. Since you've already
installed mod_php4 with the -DWITH_APACHE2 flag, causing the loadable
module to be installed as ${LOCALBASE}/libexec/apache2/libphp4.so, the
system will try and reinstall mod_php4, which you've already
discovered doesn't work.
One solution is to patch the squirrelmail port Makefile:
--- Makefile.orig Fri Sep 20 17:38:46 2002
+++ MakefileFri Oct 25 16:49:45 2002
@@ -13,7 +13,11 @@
MAINTAINER=[EMAIL PROTECTED]
-RUN_DEPENDS+= ${LOCALBASE}/libexec/apache/libphp4.so:${PORTSDIR}/www/mod_php4
+.if defined(WITH_APACHE2)
+RUN_DEPENDS+= ${LOCALBASE}/libexec/apache2/libphp4.so:${PORTSDIR}/www/mod_php4
+.else
+RUN_DEPENDS+= ${LOCALBASE}/libexec/apache/libphp4.so:${PORTSDIR}/www/mod_php4
+.endif
USE_BZIP2= yes
NO_BUILD= yes
Then make -DWITH_APACHE2
The same problem will affect all ports that install PHP code. See for
instance:
o [2002/08/12] ports/41577 portsport security/acid won't see apache2+mod_php4
o [2002/09/21] ports/43225 nbm phpPgAdmin port doesn't work with Apache2 by
default
o [2002/09/21] ports/43227 portssquirrelmail port doesn't support Apache2
o [2002/10/05] ports/43706 nbm Make databases/phpmyadmin operate with apache2
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: squirrel mail install-from-ports problem....
On Fri, 2002-10-25 at 17:01, Matthew Seaman wrote:
On Fri, Oct 25, 2002 at 04:04:07PM +0100, Simon Dick wrote:
On Fri, 2002-10-25 at 02:30, Bsd Neophyte wrote:
i'm getting the following error and it says that this should be reported
to [EMAIL PROTECTED]
but before i do that, i wanted some input to see if i could resolve this
issue in a relatively simply way.
is this an issue with how i installed apache... should i reinstall if with
the --with-apxs2 option?
I'd suggest you install PHP4 individually first, eg:
cd /usr/ports/www/mod_php4
make -DWITH_APACHE2 install clean
Then install squirrelmail, it looks like you have Apache 2 installed and
PHP can't autodetect it so it needs that -D option set.
Unfortunately, the Makefile for the squirrelmail port says:
RUN_DEPENDS+= ${LOCALBASE}/libexec/apache/libphp4.so:${PORTSDIR}/www/mod_php4
which means that if ${LOCALBASE}/libexec/apache/libphp4.so cannot be
found at compile/install time, the squirrelmail port will try and
install mod_php4 to fulfil the dependency. Since you've already
installed mod_php4 with the -DWITH_APACHE2 flag, causing the loadable
module to be installed as ${LOCALBASE}/libexec/apache2/libphp4.so, the
system will try and reinstall mod_php4, which you've already
discovered doesn't work.
One solution is to patch the squirrelmail port Makefile:
Good point, will submit a patch to do that in the squirrelmail port
tonight.
--
Simon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
squirrel mail install-from-ports problem....
i'm getting the following error and it says that this should be reported to [EMAIL PROTECTED] but before i do that, i wanted some input to see if i could resolve this issue in a relatively simply way. is this an issue with how i installed apache... should i reinstall if with the --with-apxs2 option? - Configuring SAPI modules checking for AOLserver support... no checking for Apache 1.x module support via DSO through APXS... configure: error: Use --with-apxs2 with Apache 2.x! === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/ports/www/mod_php4/work/php-4.2.3/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/www/mod_php4. *** Error code 1 Stop in /usr/ports/www/mod_php4. *** Error code 1 Stop in /usr/ports/mail/squirrelmail. - __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: squirrel mail install-from-ports problem....
It may be that dirk@ needs to hear about it...I've had some trouble building mod_php lately also. But I've managed to work around it, albeit not so quickly. As to your question, here's another: is your Apache v 2.x or 1.3.x ? That's what the script is asking for Kevin Kinsey - Original Message - From: Bsd Neophyte [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 24, 2002 8:30 PM Subject: squirrel mail install-from-ports problem i'm getting the following error and it says that this should be reported to [EMAIL PROTECTED] but before i do that, i wanted some input to see if i could resolve this issue in a relatively simply way. is this an issue with how i installed apache... should i reinstall if with the --with-apxs2 option? - Configuring SAPI modules checking for AOLserver support... no checking for Apache 1.x module support via DSO through APXS... configure: error: Use --with-apxs2 with Apache 2.x! === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/ports/www/mod_php4/work/php-4.2.3/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/www/mod_php4. *** Error code 1 Stop in /usr/ports/www/mod_php4. *** Error code 1 Stop in /usr/ports/mail/squirrelmail. - __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 ports problem when trying to build package
in message [EMAIL PROTECTED], wrote [EMAIL PROTECTED] thusly... ... the package does get fubared somehow see below: ... === Building package for XFree86-4.2.0_1,1 Creating package /usr/ports/x11/XFree86-4/XFree86-4.2.0_1,1.tgz Registering depends: XFree86-FontServer-4.2.0 XFree86-Server-4.2.0_4 XFree86-cli ents-4.2.0_2 XFree86-documents-4.2.0 XFree86-font100dpi-4.2.0 XFree86-font75dpi- 4.2.0 XFree86-fontCyrillic-4.2.0 XFree86-fontDefaultBitmaps-4.2.0 XFree86-fontSc alable-4.2.0 XFree86-fontEncodings-4.2.0 XFree86-libraries-4.2.0_2 freetype2-2.1 .2 wrapper-1.0_2 imake-4.2.0_1. Creating gzip'd tar ball in '/usr/ports/x11/XFree86-4/XFree86-4.2.0_1,1.tgz' wn/usr/ports/x11/XFree86-4# ls -l 12:04PM total 14 -rw-r--r-- 1 root wheel 2034 Jul 16 12:03 XFree86-4.2.0_1,1.tgz As you can see the package only takes 2034 bytes... the is something that is not corret here... same here... -rw-r--r-- 1 root wheel2.0k May 27 01:45 XFree86-4.2.0_1,1.tgz What can i be doing wrong? nothing, everything is happening by design. hope you haven't run 'make clean' yet as you may need to make package in every port that's part of the XFree86 4.2 meta port. or, at least that's what i have to do. there may be some knob that -- that i am not aware of -- one can twist to make all the depending packages automagically. also, there may be a way to create packages out of installed ports, i don't know. somebody else should be able to explain what i am trying to say above, or if anything is incorrect. (hint, hint) - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86 ports problem when trying to build package
Hi, I get this error when i try to build x11/XFree86-4 as an port: thrawn/usr/ports/x11/XFree86-4# make package 2:02PM === Extracting for XFree86-4.2.0_1,1 No MD5 checksum file. === XFree86-4.2.0_1,1 depends on shared library: Xft.1 - found === Patching for XFree86-4.2.0_1,1 === Configuring for XFree86-4.2.0_1,1 === Installing for XFree86-4.2.0_1,1 === XFree86-4.2.0_1,1 is already installed - perhaps an older version? If so, you may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of XFree86-4.2.0_1,1 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. thrawn/usr/ports/x11/XFree86-4# I have the port installed but how do I get rid of the complains that it is all ready installed? I just want to build it to a package. Do I have to do something special if the port is all ready installed? More if can be provided as needed. I have the latest cvsup for the ports tree. Thanks in advance. Mvh Mattias Björk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 ports problem when trying to build package
in message [EMAIL PROTECTED], wrote [EMAIL PROTECTED] thusly... I get this error when i try to build x11/XFree86-4 as an port: thrawn/usr/ports/x11/XFree86-4# make package 2:02PM ... === XFree86-4.2.0_1,1 is already installed - perhaps an older version? If so, you may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of XFree86-4.2.0_1,1 without deleting it first, set the variable FORCE_PKG_REGISTER ^ ^ ^ ^ ^ ^ ^ ^ ^ in your environment or the make install command line. *** Error code 1 I have the port installed but how do I get rid of the complains that it is all ready installed? I just want to build it to a package. Do I have to do something special if the port is all ready installed? note the bit about FORCE_PKG_REGISTER. it's used to force the installation on already installed port. so, as th message says, either make it environment variable; in sh-like shelles, it's done via... FORCE_PKG_REGISTER=yes export FORCE_PKG_REGISTER ...or spcify it on the command line, like... # make -DFORCE_PKG_REGISTER install -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
