Re: Can we please just remove the old Makefile headers?
Em 28-08-2012 01:27, Eitan Adler escreveu: If I understand correctly, you want the idea of multiple maintainers. I am completely for this. It is even trivial to do by adding a comment just below the MAINTAINER line. Or by listing various emails in the MAINTAINER variable, separated by space. Yes, portbuild scripts, portlint, PR auto-assign scripts, etc. need to be modified to deal with this. Gabor ___ 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: Libreoffice, javaPathHelper: not found
Because of the problem above when trying to start Libreoffice. I want to follow the advise in this link: http://forums.freebsd.org/showthread.php?t=27035 and install Libreoffice-legacy. The problem is that I can't find such a port. Where should I look? Thanks /Leslie ___ 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: apcupsd compile fails on 9-stable amd64
On Sat, 25 Aug 2012 14:01:09 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Sat, 25 Aug 2012, Oleg Ginzburg wrote: On Saturday 25 August 2012 18:06:29 Warren Block wrote: Discovered last night that sysutils/apcupsd will not compile on 9-stable amd64 if the USB or SNMP options are enabled. It does compile on 8.3-stable i386. Stock gcc, not clang. ccache is installed, but not used for ports. Any suggestions? ... CXX src/apcupsd.c CXX src/apcnis.c LDsrc/apcupsd /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(s nmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::Append(Asn::ObjectId const, Snmp::Variable*)': snmp.cpp:(.text+0xdc9): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::Sequence::assign(Asn::Sequence const)': asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::ObjectId::demarshal(unsigned char*, unsigned int)': asn.cpp:(.text+0x82b): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o):asn.cpp:(.text+0x934): more undefined references to `operator new[](unsigned long)' follow Ive already register PR for this: http://www.freebsd.org/cgi/query- pr.cgi?pr=ports/170522 Sorry, saw that last night, but forgot about it. The fix works for me. Thanks! Thanks for confirming -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: PKG_NG: pkg deinstall fails with argument list too long
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 27.08.2012 23:23, schrieb Baptiste Daroussin: On Mon, Aug 27, 2012 at 10:22:27PM +0200, olli hauer wrote: Please do not hijack this thread, even if you are also reporting a problem with PKG_NG. Threads are free and nobody bothered to reply to the more urgent problem of the failed deinstallation. On 2012-08-27 20:03, Stefan Esser wrote: PKG_NG seems to have introduced a limit on the size of ports that can be deinstalled: # cd /usr/ports/math/lapack # make deinstall === Deinstalling for math/lapack === Deinstalling lapack-3.4.0_2 The following packages will be deinstalled: lapack-3.4.0_2 The deinstallation will free 28 MB Deinstalling lapack-3.4.0_2...lapack-3.4.0_2 is required by: qrupdate-1.1.1, deleting anyway pkg: Cannot run script(DEINSTALL): Argument list too long *** [deinstall] Error code 3 I have located the line that is causing this error. It is the posix_spawn on line 102 of libpkg/script.c. The argument length is limited to KERN_ARGMAX (sysctl kern.argmax) which seems to be a R/O value initialized to 256KB. AFAICT this is not even a loader tuneable. A new kernel must be built, or pkg must be modified to honor the argument length limit. The argument is the string argument of sh -c string, which can not be split in the general case. In the specific case of math/lapack, the arguments to execve() (called by posix_spawn()) are: argv[0] = sh argv[1] = -c argv[2] = set -- lapack-3.4.0_2 rm -f /usr/local/man/cat3/INSTALL_ilaver.f.3.gz ... /usr/local/man/cat3/zupmtr.f.3.gz.bz2 The argument list must be broken into pieces of less than 256KB, since rising KERN_ARGMAX to 330KB will lead to the same problem with the next port with even longer PLIST. Regards, STefan -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlA8jA8ACgkQ69HRkrVjAEzuXgCfTP0gdtRa2CqWp3iWwKu90LO8 ThkAniYRTiGP870wrHwGKCg/F1UmWneF =UqHR -END PGP SIGNATURE- ___ 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: PKG_NG: pkg deinstall fails with argument list too long
On 28 Aug 2012 10:15, Stefan Esser s...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 27.08.2012 23:23, schrieb Baptiste Daroussin: On Mon, Aug 27, 2012 at 10:22:27PM +0200, olli hauer wrote: Please do not hijack this thread, even if you are also reporting a problem with PKG_NG. Threads are free and nobody bothered to reply to the more urgent problem of the failed deinstallation. On 2012-08-27 20:03, Stefan Esser wrote: PKG_NG seems to have introduced a limit on the size of ports that can be deinstalled: # cd /usr/ports/math/lapack # make deinstall === Deinstalling for math/lapack === Deinstalling lapack-3.4.0_2 The following packages will be deinstalled: lapack-3.4.0_2 The deinstallation will free 28 MB Deinstalling lapack-3.4.0_2...lapack-3.4.0_2 is required by: qrupdate-1.1.1, deleting anyway pkg: Cannot run script(DEINSTALL): Argument list too long *** [deinstall] Error code 3 I have located the line that is causing this error. It is the posix_spawn on line 102 of libpkg/script.c. The argument length is limited to KERN_ARGMAX (sysctl kern.argmax) which seems to be a R/O value initialized to 256KB. AFAICT this is not even a loader tuneable. A new kernel must be built, or pkg must be modified to honor the argument length limit. The argument is the string argument of sh -c string, which can not be split in the general case. In the specific case of math/lapack, the arguments to execve() (called by posix_spawn()) are: argv[0] = sh argv[1] = -c argv[2] = set -- lapack-3.4.0_2 rm -f /usr/local/man/cat3/INSTALL_ilaver.f.3.gz ... /usr/local/man/cat3/zupmtr.f.3.gz.bz2 The argument list must be broken into pieces of less than 256KB, since rising KERN_ARGMAX to 330KB will lead to the same problem with the next port with even longer PLIST. Any reason we can't split it? Chris ___ 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: PKG_NG: pkg deinstall fails with argument list too long
On Tue, Aug 28, 2012 at 11:14:55AM +0200, Stefan Esser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 27.08.2012 23:23, schrieb Baptiste Daroussin: On Mon, Aug 27, 2012 at 10:22:27PM +0200, olli hauer wrote: Please do not hijack this thread, even if you are also reporting a problem with PKG_NG. Threads are free and nobody bothered to reply to the more urgent problem of the failed deinstallation. On 2012-08-27 20:03, Stefan Esser wrote: PKG_NG seems to have introduced a limit on the size of ports that can be deinstalled: # cd /usr/ports/math/lapack # make deinstall === Deinstalling for math/lapack === Deinstalling lapack-3.4.0_2 The following packages will be deinstalled: lapack-3.4.0_2 The deinstallation will free 28 MB Deinstalling lapack-3.4.0_2...lapack-3.4.0_2 is required by: qrupdate-1.1.1, deleting anyway pkg: Cannot run script(DEINSTALL): Argument list too long *** [deinstall] Error code 3 I have located the line that is causing this error. It is the posix_spawn on line 102 of libpkg/script.c. The argument length is limited to KERN_ARGMAX (sysctl kern.argmax) which seems to be a R/O value initialized to 256KB. AFAICT this is not even a loader tuneable. A new kernel must be built, or pkg must be modified to honor the argument length limit. The argument is the string argument of sh -c string, which can not be split in the general case. In the specific case of math/lapack, the arguments to execve() (called by posix_spawn()) are: argv[0] = sh argv[1] = -c argv[2] = set -- lapack-3.4.0_2 rm -f /usr/local/man/cat3/INSTALL_ilaver.f.3.gz ... /usr/local/man/cat3/zupmtr.f.3.gz.bz2 The argument list must be broken into pieces of less than 256KB, since rising KERN_ARGMAX to 330KB will lead to the same problem with the next port with even longer PLIST. Thank you very much, this is already known and being worked on. btw the cat3 lines in plist do not longer exists in the ports tree, I removed this ugly thing a while ago now. what will be done is keeping the currently behaviours if the script allows it, and switch to the slower sh -s whan the script is longer. regards, Bapt pgpxeDt8DxEJA.pgp Description: PGP signature
Bus error xslt
For some time now i can not update a few ports.
these are
sound-juicer-2.32.0_1 needs updating (port has 2.32.0_3)
totem-2.32.0_1 needs updating (port has 2.32.0_2)
tracker-client-0.6.95_13 needs updating (port has 0.6.95_15)
tracker-libtrackergtk-0.6.95_13needs updating (port has 0.6.95_15)
i thougt it would go by.
all these ports fail at the same point and leaves a core file in the
work help dir from the port.
./work/sound-juicer-2.32.0/help/sound-juicer/xsltproc.core
xsltproc -o sound-juicer-C.omf --stringparam db2omf.basename
sound-juicer --stringparam db2omf.format 'docbook' --stringparam
db2omf.dtd -//OASIS//DTD DocBook XML V4.3//EN --stringparam
db2omf.lang C --stringparam db2omf.omf_dir /usr/local/share/omf
--stringparam db2omf.help_dir /usr/local/share/gnome/help
--stringparam db2omf.omf_in
/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/sound-juicer.omf.in
--stringparam db2omf.scrollkeeper_cl `scrollkeeper-config
--pkgdatadir`/Templates/C/scrollkeeper_cl.xml
`/usr/local/bin/pkg-config --variable db2omf gnome-doc-utils`
C/sound-juicer.xml || { rm -f sound-juicer-C.omf; exit 1; }
Bus error (core dumped)
I did reinstall libgcrypt, libxslt, libxml2, libxml++, gmake but i can
not get rid of the bus error.
Can someone help me?
below a longer error from the error
if ! test -d sv/; then mkdir sv/; fi
if [ -f C/legal.xml ]; then d=../; else
d=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/;
fi; \
mo=sv/sv.mo; \
if [ -f ${mo} ]; then mo=../${mo}; else
mo=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/${mo};
fi; \
(cd sv/ \
`which xml2po` -m docbook -e -t ${mo} \
${d}C/legal.xml legal.xml.tmp \
cp legal.xml.tmp legal.xml rm -f legal.xml.tmp)
if ! test -d uk/; then mkdir uk/; fi
if [ -f C/legal.xml ]; then d=../; else
d=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/;
fi; \
mo=uk/uk.mo; \
if [ -f ${mo} ]; then mo=../${mo}; else
mo=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/${mo};
fi; \
(cd uk/ \
`which xml2po` -m docbook -e -t ${mo} \
${d}C/legal.xml legal.xml.tmp \
cp legal.xml.tmp legal.xml rm -f legal.xml.tmp)
if ! test -d zh_CN/; then mkdir zh_CN/; fi
if [ -f C/legal.xml ]; then d=../; else
d=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/;
fi; \
mo=zh_CN/zh_CN.mo; \
if [ -f ${mo} ]; then mo=../${mo}; else
mo=/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/${mo};
fi; \
(cd zh_CN/ \
`which xml2po` -m docbook -e -t ${mo} \
${d}C/legal.xml legal.xml.tmp \
cp legal.xml.tmp legal.xml rm -f legal.xml.tmp)
xsltproc -o sound-juicer-C.omf --stringparam db2omf.basename
sound-juicer --stringparam db2omf.format 'docbook' --stringparam
db2omf.dtd -//OASIS//DTD DocBook XML V4.3//EN --stringparam
db2omf.lang C --stringparam db2omf.omf_dir /usr/local/share/omf
--stringparam db2omf.help_dir /usr/local/share/gnome/help
--stringparam db2omf.omf_in
/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer/sound-juicer.omf.in
--stringparam db2omf.scrollkeeper_cl `scrollkeeper-config
--pkgdatadir`/Templates/C/scrollkeeper_cl.xml
`/usr/local/bin/pkg-config --variable db2omf gnome-doc-utils`
C/sound-juicer.xml || { rm -f sound-juicer-C.omf; exit 1; }
Bus error (core dumped)
gmake[3]: *** [sound-juicer-C.omf] Error 1
gmake[3]: Leaving directory
`/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help/sound-juicer'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0/help'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/audio/sound-juicer/work/sound-juicer-2.32.0'
gmake: *** [all] Error 2
*** [do-build] Error code 1
Stop in /usr/ports/audio/sound-juicer.
=== make failed for audio/sound-juicer
=== Aborting update
Terminated
=== You can restart from the point of failure with this command line:
portmaster flags audio/sound-juicer
Thanks for your time.
regards
Johan
___
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: apcupsd compile fails on 9-stable amd64
On Tue, Aug 28, 2012 at 11:46:31AM +0300, Ion-Mihai Tetcu wrote: On Sat, 25 Aug 2012 14:01:09 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Sat, 25 Aug 2012, Oleg Ginzburg wrote: On Saturday 25 August 2012 18:06:29 Warren Block wrote: Discovered last night that sysutils/apcupsd will not compile on 9-stable amd64 if the USB or SNMP options are enabled. It does compile on 8.3-stable i386. Stock gcc, not clang. ccache is installed, but not used for ports. Any suggestions? ... CXX src/apcupsd.c CXX src/apcnis.c LDsrc/apcupsd /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(s nmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::Append(Asn::ObjectId const, Snmp::Variable*)': snmp.cpp:(.text+0xdc9): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::Sequence::assign(Asn::Sequence const)': asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::ObjectId::demarshal(unsigned char*, unsigned int)': asn.cpp:(.text+0x82b): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o):asn.cpp:(.text+0x934): more undefined references to `operator new[](unsigned long)' follow Ive already register PR for this: http://www.freebsd.org/cgi/query- pr.cgi?pr=ports/170522 Sorry, saw that last night, but forgot about it. The fix works for me. Thanks! Thanks for confirming I do not think the 'fix' is right one. The issue there is that C compiler driver is used to link object files generated by C++ compiler. Basically, you need to change $(CC) to $(CXX) somewhere for LD. pgpuo8lvsURrY.pgp Description: PGP signature
Re: fresh install of kde4 fails - japanese/kiten
Alberto Villa wrote, On 2012-08-27 4:05 PM: On Tue, Aug 28, 2012 at 12:52 AM, Jim Pazarena fpo...@paz.bz wrote: = kiten-4.8.4.tar.bz2 is not in /usr/ports/japanese/kiten/distinfo. = Either /usr/ports/japanese/kiten/distinfo is out of date, or = kiten-4.8.4.tar.bz2 is spelled incorrectly. *** Error code 1 Can you show the output of `make -C /usr/ports/japanese/kiten -V USE_BZIP2`, please? it replies with one word only: yes ___ 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: lang/gcc46 dependency loop on lang/gcc
On 8/27/2012 2:35 PM, Doug Barton wrote: Gerald, It seems that if lang/gcc46 is installed, and then you attempt to update it, lang/gcc shows up in the output of build-depends-list, run-depends-list, or perhaps both. If lang/gcc46 is not installed already, this doesn't happen. This would seem to be an error in the bsd.gcc.mk logic, or perhaps an error in one of the ports' Makefiles, not sure yet. Any chance you could look into this? Doug I believe this was reported in ports/171135 as well for lang/gcc47. Received in private email: --- Installing the new version via the port === Installing for gcc-4.7.2.20120825 === gcc-4.7.2.20120825 depends on file: /usr/local/bin/as - found === gcc-4.7.2.20120825 depends on executable: gcc47 - not found ===Verifying reinstall for gcc47 in /usr/ports/lang/gcc47 ... (more than 100) make: Max recursion level (500) exceeded. *** Error code 2 Stop in /usr/ports/lang/gcc47. *** Error code 1 ... (more than 100) ___ 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: lang/gcc46 dependency loop on lang/gcc
Hello all, I have tested in a new freebsd 9.0. only install gcc47 then upgrade it. 在 2012-8-29，上午3:15，Bryan Drewery br...@shatow.net 写道： On 8/27/2012 2:35 PM, Doug Barton wrote: Gerald, It seems that if lang/gcc46 is installed, and then you attempt to update it, lang/gcc shows up in the output of build-depends-list, run-depends-list, or perhaps both. If lang/gcc46 is not installed already, this doesn't happen. This would seem to be an error in the bsd.gcc.mk logic, or perhaps an error in one of the ports' Makefiles, not sure yet. Any chance you could look into this? Doug I believe this was reported in ports/171135 as well for lang/gcc47. Received in private email: --- Installing the new version via the port === Installing for gcc-4.7.2.20120825 === gcc-4.7.2.20120825 depends on file: /usr/local/bin/as - found === gcc-4.7.2.20120825 depends on executable: gcc47 - not found ===Verifying reinstall for gcc47 in /usr/ports/lang/gcc47 ... (more than 100) make: Max recursion level (500) exceeded. *** Error code 2 Stop in /usr/ports/lang/gcc47. *** Error code 1 ... (more than 100) ___ 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
sysutils/conky Configure Options in Makefile
Hi I have installed conky for use with my wm which is Spectrwm. However, looking in the conky Makefile one of the configure options has been disabled, tcp monitoring (--disable-portmon), which is a feature i'd quite like to have available. Is there a reason the maintainer has disabled this option, perhaps due to security or incompatibility, etc., that anyone knows of? I have emailed the maintainer who's address is in the Makefile but i've not had a response. I wasn't sure if contacting maintainers directly is the correct/preferred approach with such matters so i'm asking here. Thanks in advance to anyone that might have some thoughts to offer on this. Best wishes, Jamie. smime.p7s Description: S/MIME cryptographic signature
Re: sysutils/conky Configure Options in Makefile
One option is to go up to the ports weary, www.freeBSD.org/ports. Put in the name of the port, find it, click on changes, maybe you see what happened. -- Michael Scheidell Will Hack For Food ___ 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: upgrading ports with a lot of dependencies
On Tue, Aug 28, 2012 at 3:52 PM, Matthias Andree matthias.and...@gmx.de wrote: Am 26.08.2012 07:40, schrieb Jim Pazarena: My question is a general one, with the following specific example. I wanted to re-compile the latest phpmyadmin but when I tried that, I get a you must have the latest php5 (5.4.6) when I try php5 I get a dependency of devel/pkgconf when I compile pkgconf, it conflicts with devel/pkg-config Upon investigation it looks like pkg-config is replaced with pkgconf however attempting to remove it show dozens of dependencies preventing the removal. I find this series of challenges frequently as installs move along in age, and usually wind up re-loading the entire server to beat the challenge. There must be an easier way. Advice would be greatly appreciated. Beyond what Matthew stated, use an upgrade tool, and do not do upgrades manually. I found that (a) using portmaster, while at the same time (b) watching /usr/ports/UPGRADING has given me smooth upgrades. portmaster sorts out the if a requisite port was upgraded, rebuild it first and the dependency management hassles. There are other tools that I have less experience with. I stopped using portupgrade a while ago, but now that it has got a new active maintainer, chances are that a new attempt is worthwhile. And, as I mention rather often, pkg-libchk from sysutils/bsdadminscripts can save you from rebuilding a LOT of ports. pkg_libchk -o | grep LIBNAME | cut -d: -f1 | sort | uniq dep-ports (where LIBNAM is the sharable (.so) installed by the port in question) portmaster -D `cat dep-ports` -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.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: lang/gcc46 dependency loop on lang/gcc
On 08/28/2012 01:44 PM, Gerald Pfeifer wrote: On Mon, 27 Aug 2012, Doug Barton wrote: This would seem to be an error in the bsd.gcc.mk logic, or perhaps an error in one of the ports' Makefiles, not sure yet. Any chance you could look into this? I had done that when Robert contacted me first and could not find anything. FYI, Robert has some interesting stuff in make.conf that he is commenting out and testing. For future reference, if a user approaches you(pl.) about a problem compiling your port with portmaster the easiest way to determine if portmaster is a suspect or not is to ask the user to try the same action without using portmaster. In this case I'm pretty confident that this would have shown that portmaster was not the issue. Aside from my concern about using my time most effectively, I like to see the users get help ASAP. Any chance portmaster could tell us where the loop comes from? I looked at the -v option, but that one did not seem to provide this information and I feel stuck right now. As I pointed out earlier, it's 'make build-depends-list' But as for being stuck, I'm waiting on Robert to report his findings on which make.conf option hung him up. Is it possible you have some special setting somewhere, Robert, like USE_GCC=... as a global setting somewhere? (Though, shouldn't even that work with portmaster assuming that this part of the process, forcing deinstallation of the old version and installing a new package, does not depend on any other ports?) Portmaster waits until it builds the new thing successfully before uninstalling the old thing. Doug ___ 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: lang/gcc46 dependency loop on lang/gcc
Doug Barton writes: But as for being stuck, I'm waiting on Robert to report his findings on which make.conf option hung him up. Life Happened(tm), which means I'll get to this first thing tomorrow, Robert Huff ___ 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: lang/gcc46 dependency loop on lang/gcc
On 08/28/2012 03:12 PM, Robert Huff wrote: Doug Barton writes: But as for being stuck, I'm waiting on Robert to report his findings on which make.conf option hung him up. Life Happened(tm), which means I'll get to this first thing tomorrow, Sure, of course. :) I just wanted to let Gerald know he was off the hook for debugging this until we hear back from you. Doug ___ 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: fresh install of kde4 fails - japanese/kiten
Alberto Villa wrote, On 2012-08-28 3:31 AM:
On Tue, Aug 28, 2012 at 2:07 AM, Jim Pazarena fpo...@paz.bz wrote:
Can you show the output of `make -C /usr/ports/japanese/kiten -V
USE_BZIP2`, please?
it replies with one word only:
yes
Please, keep kde@ CCed.
Can you paste (http://pastebin.com) /usr/ports/japanese/kiten/Makefile
and /etc/make.conf, please? You have USE_BZIP2 defined somewhere,
while it shouldn't be.
Script started on Tue Aug 28 20:08:17 2012
laptop# grep kiten .source/typescript
=== kdeedu-4.8.4 depends on file: /usr/local/kde4/bin/kiten - not found
===Verifying install for /usr/local/kde4/bin/kiten in
/usr/ports/japanese/kiten
= kiten-4.8.4.tar.bz2 is not in /usr/ports/japanese/kiten/distinfo.
= Either /usr/ports/japanese/kiten/distinfo is out of date, or
= kiten-4.8.4.tar.bz2 is spelled incorrectly.
Stop in /usr/ports/japanese/kiten.
laptop# exit
Script done on Tue Aug 28 20:08:36 2012
*** cat of /usr/ports/japanese/kiten/Makefile **
# New ports collection Makefile for:kiten
# Date created: 6 September 2011
# Whom: Alberto Villa avi...@freebsd.org
#
# $FreeBSD: ports/japanese/kiten/Makefile,v 1.2 2012/02/16 15:57:01
ashish Exp $
#
PORTNAME= kiten
PORTVERSION=${KDE4_VERSION}
PORTREVISION= 1
CATEGORIES= japanese kde
MASTER_SITES= ${MASTER_SITE_KDE}
MASTER_SITE_SUBDIR= ${KDE4_BRANCH}/${PORTVERSION}/src
DIST_SUBDIR=KDE
MAINTAINER= k...@freebsd.org
COMMENT=Japanese reference/study tool for KDE 4
CONFLICTS= kdeedu-4.[0-6].*
USE_KDE4= kdehier kdelibs kdeprefix automoc4
KDE4_BUILDENV= yes
USE_QT_VER= 4
QT_COMPONENTS= corelib moc_build qmake_build rcc_build uic_build
USE_BZIP2= yes
MAKE_JOBS_SAFE= yes
.include bsd.port.mk
*** cat of /etc/make.conf **
BATCH=YES
# added by use.perl 2012-08-28 01:04:47
PERL_VERSION=5.14.2
___
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: Libreoffice, javaPathHelper: not found
2012-08-28 23:11, Kevin Oberman skrev: On Tue, Aug 28, 2012 at 1:20 AM, Leslie Jensen les...@eskk.nu wrote: Because of the problem above when trying to start Libreoffice. I want to follow the advise in this link: http://forums.freebsd.org/showthread.php?t=27035 and install Libreoffice-legacy. The problem is that I can't find such a port. Where should I look? The problem that caused this error was fixed about two releases of libreoffice ago and the legacy port is no longer needed (and has been removed). You simply should not see that error when building the current libreoffice port (v3.5.6). Unfortunately that's exactly what I do :-( I compiled and installed v3.5.6 yesterday and I still get the same error. /Leslie ___ 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
