Opened 12 years ago

Closed 12 years ago

#34220 closed defect (invalid)

libsdl: invalid command name "vercmp"

Reported by: rigstars2@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.99
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: libsdl

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I keep getting this error -

Error: Unable to open port: invalid command name "vercmp"

when I try to install ffmpeg (sudo port install ffmpeg) or if I try to upgrade this libsdl (sudo port upgrade libsdl)

I have updated to latest ports doing (sudo port selfupdate) followed by a (sudo port upgrade outdated) and even ran (sudo port sync)

OS I'm using is Mac OS X Lion and installed using trunk base when Lion was still very new .. Any help, please.

Thanks!

Change History (6)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Description: modified (diff)
Summary: invalid command "vercmp" on Mac OS X Lion installing mpeg portinvalid command "vercmp"

Please run "port version" to see what version of MacPorts you really have. The "rpm-vercomp" command, which has been in MacPorts for years and years, was renamed to "vercmp" a couple versions of MacPorts ago. Please also attach the main.log file of the failure; I've looked in the ffmpeg port and it doesn't itself call vercmp so I need to see the log to know what's really going on.

comment:2 Changed 12 years ago by rigstars2@…

port version returned Version: 2.0.99

also, the full error message I get is this

#sudo port install ffmpeg
Error: Unable to open port: invalid command name "vercmp"
Error: Unable to execute port: upgrade libsdl failed

here's a snippet of the main.log

:debug:main universal variant already exists, so not adding the default one
:debug:main No need to upgrade! libvpx 1.0.0_0 >= libvpx 1.0.0_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main libsdl 1.2.15_0 exists in the ports tree
:debug:main libsdl 1.2.14_9 +x11 is the latest installed
:debug:main libsdl 1.2.14_9 +x11 is active
:debug:main Merging existing variants '+x11' into variants
:debug:main new fully merged portvariants: x11 +
:debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libsdl
:debug:main OS darwin/11.3.0 (Mac OS X 10.7) arch i386
:debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided
:debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided
:debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
:debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/xcodeversion-1.0.tcl
:debug:main invalid command name "vercmp"
    while executing
"vercmp $xcodeversion 4.2"
    invoked from within
"if {[vercmp $xcodeversion 4.2] >= 0 && [vercmp $xcodeversion 4.2.1] <= 0 && ($build_arch == "i386" || [variant_isset universal])} {
    # clang crashe..."
    (file "Portfile" line 33)
    invoked from within
"source Portfile"
    invoked from within
"$workername eval source Portfile"
    (procedure "mportopen" line 47)
    invoked from within
"mportopen $porturl [array get interp_options] [array get variations]"
:error:main Unable to open port: invalid command name "vercmp"
:debug:main upgrade libsdl failed
    while executing
"macports::_upgrade_mport_deps $mport $target"
    (procedure "mportexec" line 33)
    invoked from within
"mportexec $workername $target"
:error:main Unable to execute port: upgrade libsdl failed
:notice:main To report a bug, see <http://guide.macports.org/#project.tickets>

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Port: libsdl added
Summary: invalid command "vercmp"libsdl: invalid command name "vercmp"

Ah, it's the libsdl port that has the problem.

P.S: Remember to use WikiFormatting.

comment:4 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Still, I don't see why it would be a problem.

I still believe your MacPorts is older than the vercmp command, meaning it's pretty old. You mentioned having run selfupdate, but selfupdate won't upgrade you at all until MacPorts 2.1.0 final is released. Please install MacPorts 2.1.0 beta 1 instead.

comment:5 Changed 12 years ago by rigstars2@…

thanks ryan. Appreciate the help. I uninstalled the version I had and download and installed 2.1.0 beta 1 but after installing it, the version still said MacPorts 2.0.99 anyways, I'm no longer getting those errors now. So, I think I'm good. Thanks again.

comment:6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

Correct, MacPorts 2.1.0 beta 1 identifies itself as 2.0.99. MacPorts 2.1.0 final will identify itself as 2.1.0.

Note: See TracTickets for help on using tickets.