portmaster hangs waiting for grep
I am doing my weekly run of portmaster to upgrade ports on my server:
FreeBSD quarto.lib.uchicago.edu 7.3-RELEASE-p3 FreeBSD 7.3-RELEASE-p3
#0: Sat Sep 25 15:46:29 CDT 2010
r...@quarto.lib.uchicago.edu:/usr/obj/usr/src/sys/GENERIC amd64
I updated my ports tree two days ago (Friday, Oct 29) via cron, if
that has any relevance...
Portmaster got its list of things to do, then after upgrading the
first item on its to-do list (mysql-client-5.0.90_2), it is hung up
here:
[snip]
=== Compressing manual pages for mysql-client-5.0.90_2
=== Running ldconfig
/sbin/ldconfig -m /usr/local/lib/mysql
=== Installing ldconfig configuration file
=== Registering installation for mysql-client-5.0.90_2
At this point, nothing happens. Here's some details from ps showing
both the parent portmaster process and where the child is stuck:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 69546 0.0 0.1 7116 2120 p0 I+ 11:04AM 0:00.34 /bin/sh
/usr/local/sbin/portmaster -bwDa -x virtuoso
root 77472 0.0 0.0 7116 2044 p0 I+ 11:04AM 0:00.02 /bin/sh
/usr/local/sbin/portmaster -D -w -b mysql-client-5.0.90_1
root 9375 0.0 0.0 7936 1424 p0 I+ 11:06AM 0:00.00 grep
^SIZE (mysql-5.0.90.tar.gz)
Looking at portmaster source code, it is hung up in this part:
dist_list_temp=`pm_mktemp dist_list`
echo '# Added by portmaster' $dist_list_temp
for file in $distfiles; do
size=`grep ^SIZE (${ds}${file}) $distinfo`
sha256=`grep ^SHA256 (${ds}${file}) $distinfo`
md5=`grep ^MD5 (${ds}${file}) $distinfo`
echo DISTFILE:${ds}${file}:SIZE=${size##*
}:SHA256=${sha256##* }:MD5=${md5##* } \
$dist_list_temp
# Make sure any new distfiles get added to the list
[ -z $DONT_SCRUB_DISTFILES -a ! $$ -eq $PM_PARENT_PID ]
echo ${ds}$file $DI_FILES
done
Specifically, size=`grep ^SIZE (${ds}${file}) $distinfo`. This
suggests that $distinfo isn't set, but it is supposed to be.
FYI my current $dist_list_temp has these contents:
-rw--- 1 rootwheel 22 Oct 31 11:06 f-69546-dist_list.No9h5tNN
% cat /tmp/f-69546-dist_list.No9h5tNN
# Added by portmaster
I am suspicious that this may be related to the recent change in
distinfo that I read about, where the MD5 checksums are being phased
out.
plw
___
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
Portmaster 3.1 upgrade
Hi, I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Portmaster is installed : #pkg_info | grep portmaster portmaster-3.0 Manage your ports without external databases or languages I know that I can uninstall and reinstall portmaster using # pkg_delete portmaster-3.0 and the second command mentionned #make install clean I just write this message because this instruction is written in /usr/ports/UPDATING ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmaster hangs waiting for grep
On Sun, Oct 31, 2010 at 11:41 AM, Peggy Wilkins enli...@gmail.com wrote: I am doing my weekly run of portmaster to upgrade ports on my server: FreeBSD quarto.lib.uchicago.edu 7.3-RELEASE-p3 FreeBSD 7.3-RELEASE-p3 #0: Sat Sep 25 15:46:29 CDT 2010 r...@quarto.lib.uchicago.edu:/usr/obj/usr/src/sys/GENERIC amd64 I updated my ports tree two days ago (Friday, Oct 29) via cron, if that has any relevance... Apparently my ports tree update was just a little too early and I missed the portmaster upgrade to 3.1 (I was using 3.0). Sorry for the extra noise on here! plw ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun 2010-10-31 17:57:52 UTC+0100, Alexandre (axel...@ymail.com) wrote: I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Your shell is trying to do pathname globbing. http://en.wikipedia.org/wiki/Glob_(programming) Instead, use: pkg_delete -f 'portmaster*' or: pkg_delete -f portmaster\* UPDATING should probably be amended upstream to correct this... Regards Andrew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun, 2010-10-31 at 17:57 +0100, Alexandre wrote: I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* The wildcard ( http://en.wikipedia.org/wiki/Wildcard_character ) is interpreted by your shell and expanded into a list of matching files from your current working directory, then sent as a parameter to pkg_delete. What you were probably trying to do was either pkg_delete -f portmaster\* or pkg_delete -f portmaster* m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun, Oct 31, 2010 at 05:57:52PM +0100, Alexandre wrote: Hi, I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Portmaster is installed : #pkg_info | grep portmaster portmaster-3.0 Manage your ports without external databases or languages I know that I can uninstall and reinstall portmaster using # pkg_delete portmaster-3.0 and the second command mentionned #make install clean I just write this message because this instruction is written in /usr/ports/UPDATING Change the pkg_delete invocation from: # pkg_delete -f portmaster* to: # pkg_delete -f 'portmaster*' so the shell will leave the wildcard alone. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp0NEfnFE1t2.pgp Description: PGP signature
Re: Portmaster 3.1 upgrade
Op 31-10-2010 17:57, Alexandre schreef: Hi, I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Portmaster is installed : #pkg_info | grep portmaster portmaster-3.0 Manage your ports without external databases or languages I know that I can uninstall and reinstall portmaster using # pkg_delete portmaster-3.0 and the second command mentionned #make install clean I just write this message because this instruction is written in /usr/ports/UPDATING # pkg_delete -f portmaster\* worked for me (with the extra backslash). Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun, Oct 31, 2010 at 9:57 AM, Alexandre axel...@ymail.com wrote: I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. The command shown in UPDATING is wrong. The correct command is: pkg_delete -xf portmaster -x does name globbing internally to pkg_delete, and should be used over any shell globbing (like *). However, a more correct/safe command to use would be: pkg_delete -xif portmaster -x to pick up all versions of portmaster listed in /var/db/pkg/ -i to ask the user to confirm each version to be deleted -f to force the delete, even if other apps depend on it -- Freddie Cash fjwc...@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: Portmaster 3.1 upgrade
On Mon, 2010-11-01 at 04:18 +1100, andrew clarke wrote: UPDATING should probably be amended upstream to correct this... Regards Andrew While I'm certainly no authority on the issue, I think that's the wrong approach and generally (really not speaking about any specific case) - people, or in this case, system administrators, should know how to operate their working environment and don't just blindly enter commands as they found them, without trying to understand what will happen next and/or how it will get interpreted. Otherwise we will keep ending with things like this particular example from UPDATING: 20100518: Please manually delete apache-2.\* if installed _before_ updating using either portmaster or portupgrade I think there's no need to explain why such dumbing down (even though in a good spirit) can lead to serious issues, or in this case - if someone actually tries to remove the apache-2.\* package, only to find there is no such thing. m. -- Michal Varga, Stonehenge (Gmail account) ___ 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
GCC Upgrade failure for gcc-4.4
on AMD64 Intel quad core Freebsd 7.2 p3 dns1# pkg_info |grep gcc gcc-3.4.6_3,1 GNU Compiler Collection 3.4 gcc-4.2.5.20090325_5 GNU Compiler Collection 4.2 gcc-4.4.6.20101012 GNU Compiler Collection 4.4 gcc-4.5.2.20101028 GNU Compiler Collection 4.5 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' gccxml-0.6.0XML output extension to GCC dns1# \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) Fatal Error: Error count reached limit of 25. gmake[3]: *** [_abs_c4.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[1]: *** [all-target-libgfortran] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc44/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc44. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20101031-60968-1c2q7w2-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gcc-4.4.6.20101012 UPGRADE_PORT_VER=4.4.6.20101012 make ** Fix the problem and try again. Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On 31/10/2010 17:56, Freddie Cash wrote: The correct command is: pkg_delete -xf portmaster -x does name globbing internally to pkg_delete, and should be used over any shell globbing (like *). So dogmatic. '-x' is one alternative. A globbing expression is another. Either can be useful, and either should be used at will and as circumstances warrant. Also note that pkg_delete -xf portmaster is technically not equivalent to pkg_delete -f portmaster\* Instead it's equivalent to pkg_delete -f \*portmaster\* In this case it's an academic distinction because the results are exactly the same. For some other terms, that is certainly not the case. Eg. On my server at the moment: pkg_info -Ix mysql apr-ipv6-devrandom-db48-mysql51-1.4.2.1.3.10 Apache Portability Library mysql-client-5.1.51_1 Multithreaded SQL database (client) mysql-connector-java-5.1.12 MySQL Connector/J: JDBC interface for MySQL mysql-scripts-5.1.51_1 Multithreaded SQL database (scripts) mysql-server-5.1.51_1 Multithreaded SQL database (server) mysqltuner-1.1.0A Script Assist You with MySQL Configuration p5-DBD-mysql-4.017 MySQL driver for the Perl5 Database Interface (DBI) php5-mysql-5.3.3_2 The mysql shared extension for php php5-mysqli-5.3.3_2 The mysqli shared extension for php Compare with: % pkg_info -I mysql\* mysql-client-5.1.51_1 Multithreaded SQL database (client) mysql-connector-java-5.1.12 MySQL Connector/J: JDBC interface for MySQL mysql-scripts-5.1.51_1 Multithreaded SQL database (scripts) mysql-server-5.1.51_1 Multithreaded SQL database (server) mysqltuner-1.1.0A Script Assist You with MySQL Configuration Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: GCC Upgrade failure for gcc-4.4
On 31.10.2010 19:53 (UTC+1), David Southwell wrote: on AMD64 Intel quad core Freebsd 7.2 p3 dns1# pkg_info |grep gcc gcc-3.4.6_3,1 GNU Compiler Collection 3.4 gcc-4.2.5.20090325_5 GNU Compiler Collection 4.2 gcc-4.4.6.20101012 GNU Compiler Collection 4.4 gcc-4.5.2.20101028 GNU Compiler Collection 4.5 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' gccxml-0.6.0XML output extension to GCC dns1# \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) Fatal Error: Error count reached limit of 25. gmake[3]: *** [_abs_c4.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[1]: *** [all-target-libgfortran] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc44/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc44. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20101031-60968-1c2q7w2-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gcc-4.4.6.20101012 UPGRADE_PORT_VER=4.4.6.20101012 make ** Fix the problem and try again. As mentioned before, please see PR http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151792 Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun, Oct 31, 2010 at 11:57 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 31/10/2010 17:56, Freddie Cash wrote: The correct command is: pkg_delete -xf portmaster -x does name globbing internally to pkg_delete, and should be used over any shell globbing (like *). So dogmatic. '-x' is one alternative. A globbing expression is another. Either can be useful, and either should be used at will and as circumstances warrant. Also note that pkg_delete -xf portmaster is technically not equivalent to pkg_delete -f portmaster\* Instead it's equivalent to pkg_delete -f \*portmaster\* Which is why I mentioned the more safe alternative, which you snipped out of your reply: pkg_delete -xif portmaster Note the extra i in the middle, which makes the pkg_delete call interactive, showing the package name to be deleted, and asking the user whether that's the correct package to be deleted. -- Freddie Cash fjwc...@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: GCC Upgrade failure for gcc-4.4
On 31.10.2010 19:53 (UTC+1), David Southwell wrote: on AMD64 Intel quad core Freebsd 7.2 p3 dns1# pkg_info |grep gcc gcc-3.4.6_3,1 GNU Compiler Collection 3.4 gcc-4.2.5.20090325_5 GNU Compiler Collection 4.2 gcc-4.4.6.20101012 GNU Compiler Collection 4.4 gcc-4.5.2.20101028 GNU Compiler Collection 4.5 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' gccxml-0.6.0XML output extension to GCC dns1# \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) ../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1: \xD4\x90v\x01\x08\x04\x1E\xD7\xD9\x90v\x01\x08\x05\xA7\xEE\x7F\xF2 1 Error: Invalid character in name at (1) Fatal Error: Error count reached limit of 25. gmake[3]: *** [_abs_c4.lo] Error 1 gmake[3]: *** Waiting for unfinished jobs gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc44/work/build/x86_64-portbld- freebsd7.2/libgfortran' gmake[1]: *** [all-target-libgfortran] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc44/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc44. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20101031-60968-1c2q7w2-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gcc-4.4.6.20101012 UPGRADE_PORT_VER=4.4.6.20101012 make ** Fix the problem and try again. As mentioned before, please see PR http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151792 OK But what is happening? Is there a fix on the way? David Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/31/10 09:57, Alexandre wrote: | Hi, | | I read in /usr/ports/UPGRADING the instructions to properly upgrade | PORTMASTER 3.1. | It is written to do : | | # pkg_delete -f portmaster* | But when I type the first one, I got the message : | pkg_delete: No match. Sorry about that. Another user wrote me about that privately and I was in the process of fixing it yesterday when my -current system froze up; and I never got back to it. I've updated UPDATING. For those using 3.1, you can once again use portmaster to update itself to 3.2 which I just released. If you are using 3.1 you will have to use the method described in UPDATING. hth, Doug - -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBCAAGBQJMzgUYAAoJEFzGhvEaGryEvg4IAIiOjMj0kvfUeWheVzNVdswD 5MGQdI+wwOwxESvcfjUdRSzuMjya4tD2ARCeS6A2dNrnHeCA4eFuhsF24S+gxruk 8CUcsTLBuoOx83f7eR8n23XNcKzxoCQB9BOrb10hQ/TMhJ0I5Afd7DA1d0SQbdYt 1IApF4Jh4JoCPsYFXg+rsd8e8A3lWstDWCiTmhNtzj6EMdARTXk6QeTPHxP33OyT VisIMDa/0K4oAqgkdFwpfkg3r5DCyk2sAn1jXOgdkQGWCUpAqPHOpdp2mOeboa/i h/IUrsddfs3s4KJCnMl5HL7wl0OtH2MjofJRVoWzOzVSzbU2+oXXoZEtDvuUg24= =H8wT -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: Portmaster 3.1 upgrade
On Sun, Oct 31, 2010 at 14:59, Freddie Cash fjwc...@gmail.com wrote: Which is why I mentioned the more safe alternative, which you snipped out of your reply: pkg_delete -xif portmaster Note the extra i in the middle, which makes the pkg_delete call interactive, showing the package name to be deleted, and asking the user whether that's the correct package to be deleted. In the same vein, why suggest -f ? Looking at the man page, it seems multiple packages can be listed (ie pkg_delete -f portmaster \*) so if someone mistypes, it greatly increases the damage. I don't think anything depends on portmaster so its not really necessary. -- Rob Farmer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster 3.1 upgrade
On Sun 2010-10-31 19:27:17 UTC+0100, Michal Varga (varga.mic...@gmail.com) wrote: UPDATING should probably be amended upstream to correct this... Regards Andrew While I'm certainly no authority on the issue, I think that's the wrong approach and generally (really not speaking about any specific case) - people, or in this case, system administrators, should know how to operate their working environment and don't just blindly enter commands as they found them, without trying to understand what will happen next and/or how it will get interpreted. Indeed - that's why I wrote probably. I can imagine arguments for and against, as you describe... ___ 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
