What is MacPorts doing?

Mon Apr 6 15:30:17 PDT 2009

Hello,
	The results from running "sudo port upgrade installed" are as follows:

		 1)  m4, sqlite3, openssl, glib2, nspr, mesa, pcre, py25,  
spidermonkey (replaced the dual deactivate/active message), xinput,  
abd xrandr were upgraded.
		 2) lcms, bison, flex, gzip, and gstreamer were added.
		 3) render error message disappeared.
		 4) nss failed (see posting regarding nss failure)
		 5) evolution_data_server failed (see evolution_data_server posting  
regarding evolution_data_server failure).
		 6) heimal upgrade failed

/usr/bin/gcc-4.0  -DHAVE_CONFIG_H -I. -I. -I../../../include  - 
I../../../lib/roken -I../../../lib/roken -I./../common  -DFTP_SERVER - 
I/opt/local/include -D_LARGE_FILES= -Wall -Wmissing-prototypes - 
Wpointer-arith -Wbad-function-cast -Wmissing-declarations -Wnested- 
externs  -DINET6 -O2 -D_FORTIFY_SOURCE=0 -MT logwtmp.o -MD -MP - 
MF .deps/logwtmp.Tpo -c -o logwtmp.o logwtmp.c
logwtmp.c: In function 'ftpd_logwtmp_asl':
logwtmp.c:87: error: 'ASL_KEY_FACILITY' undeclared (first use in this  
function)
logwtmp.c:87: error: (Each undeclared identifier is reported only once
logwtmp.c:87: error: for each function it appears in.)
make[3]: *** [logwtmp.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

		 7)  libcanberra upgrade failed.

Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_l 
ibcanberra/work/libcanberra-0.10" && ./configure --prefix=/opt/local  
--enable-gtk " returned error 1
Command output: checking for ALSA... no
checking soundcard.h usability... no
checking soundcard.h presence... no
checking for soundcard.h... no
checking sys/soundcard.h usability... no
checking sys/soundcard.h presence... no
checking for sys/soundcard.h... no
checking machine/soundcard.h usability... no
checking machine/soundcard.h presence... no
checking for machine/soundcard.h... no
checking for PULSE... no
checking for GST... yes
checking for GTK... yes
checking for gconftool-2... /opt/local/bin/gconftool-2
Using config source xml:merged:/opt/local/etc/gconf/ 
gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for TDB... no
checking for lynx... no
configure: WARNING: *** lynx not found, plain text README will not be  
built ***
checking for VORBIS... configure: error: Package requirements  
( vorbisfile ) were not met:

No package 'vorbisfile' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables VORBIS_CFLAGS
and VORBIS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

		 8)  fontforge upgrade failed (see fontforge posting regarding  
fontforge failure).
		 9)  qemu upgrade failed (see qemu posting regarding qemu failure).
		10) textlive_base upgrade failed.

/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning suggest use  
of -bind_at_load, as lazy binding may result in errors or different  
symbols being used
symbol _vendorShellWidgetClass used from dynamic library /opt/local/ 
lib/libXt.dylib(single module) not from earlier dynamic library /opt/ 
local/lib/libXaw.7.dylib(single module)
symbol _vendorShellClassRec used from dynamic library /opt/local/lib/ 
libXt.dylib(single module) not from earlier dynamic library /opt/ 
local/lib/libXaw.7.dylib(single module)
collect2: ld returned 1 exit status
make[2]: *** [xdvi-xaw.bin] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1

	The anomalous behavior disappeared which is what we were shooting  
for.  I believe the textlive_base error changed.

On Apr 6, 2009, at 12:22 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	Three ports depended on render, namely:  xorg-renderproto, cairo,  
> and xrender.  I did a "sudo port -nf" for each.  I then followed  
> with a "sudo port selfupdate" and got the following error:
>
> Error: Synchronization of the local ports tree failed doing rsync
> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync  
> the ports tree: Synchronization of 1 source(s) failed
>
> I then ran "sudo port -d selfupdate" which resulted in no error.  I  
> suspect MacPorts had a hard time with the sync of render after the  
> delinking.  I do not know yet if the executed procedure remove the  
> error.  I am running "sudo port upgrade installed" now to verify if  
> the error disappeared.  This will also see if the resync addressed  
> the textlive issue.  The fix may not have been put in between the  
> last sync and the current one.  I run the selfupdate before each  
> upgrade run to ensure the latest for upgrading.
>
> On Apr 6, 2009, at 2:42 AM, Ryan Schmidt wrote:
>
>>
>> On Apr 3, 2009, at 21:36, Frank J. R. Hanstick wrote:
>>
>>>
>>> On Apr 3, 2009, at 2:36 PM, Joshua Root wrote:
>>>
>>>> Frank J. R. Hanstick wrote:
>>>>> Hello,
>>>>> During a sudo port upgrade installed, the following  appeared:
>>>>>
>>>>> Error: No port render found.
>>>>> Error: No port render found.
>>
>> Some port you have installed was installed when the render port  
>> existed. It has since been superseded by the xorg-renderproto  
>> port. "port dependents render" might tell you what port still has  
>> knowledge of the old render port. "port -nf upgrade thatport"  
>> might fix its dependencies so that it forgets about the render port.
>>
>>>>> --->  Deactivating spidermonkey @1.7.0_2
>>>>> --->  Activating spidermonkey @1.7.0_2
>>>>> --->  Cleaning spidermonkey
>>>>> --->  Deactivating spidermonkey @1.7.0_2
>>>>> --->  Activating spidermonkey @1.7.0_2
>>>>> --->  Cleaning spidermonkey
>>>>>
>>>>> Does anyone have an idea of what is going on.  I had started a  
>>>>> sudo port
>>>>> -d upgrade installed; but, with all the repeated checks, it takes
>>>>> forever to run because this occurs towards the end of the  
>>>>> process.  Any
>>>>> suggestions on a quicker way to find out what is occurring?
>>>>
>>
>> [snip]
>>
>>> 	In any case, what is MacPorts doing at this juncture?
>>
>> I thought it might be this:
>>
>> http://trac.macports.org/ticket/16085
>>
>> But that was fixed in 1.7.1 which you said you have... So I'm not  
>> sure.
>>
>> It probably has to do with using "port upgrade installed" instead  
>> of "port upgrade outdated". So use the latter in the future.
>>
>>
>>
>
> Frank J. R. Hanstick
> trog24 at comcast.net
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Frank J. R. Hanstick
trog24 at comcast.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090406/57dbec91/attachment.html>