Opened 10 years ago

Last modified 10 years ago

#43561 closed defect

srecord-1.63 — at Version 1

Reported by: alinp@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc:
Port: srecord

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

Hi...I'm trying my had at updating the port for srecord to be current (v 1.63) and I'm running into a strange issue. I get a failure running MacPorts for an install operation when I run:

$ sudo port -d install srecord

the error I get is :

...
make: Entering directory `/opt/local/var/macports/build/_Users_alinp_MacPorts_devel_srecord/srecord/work/srecord-1.63'
libtool --mode=install /usr/bin/install -c bin/srec_cat /opt/local/bin/srec_cat
libtool: install: /usr/bin/install -c bin/.libs/srec_cat /opt/local/bin/srec_cat
install: /opt/local/bin/srec_cat: Operation not permitted
make: *** [/opt/local/bin/srec_cat] Error 71
make: Leaving directory `/opt/local/var/macports/build/_Users_alinp_MacPorts_devel_srecord/srecord/work/srecord-1.63'
Command failed:  cd "/opt/local/var/macports/build/_Users_alinp_MacPorts_devel_srecord/srecord/work/srecord-1.63" && /usr/bin/make -w install prefix=/opt/local/var/macports/build/_Users_alinp_MacPorts_devel_srecord/srecord/work/destroot/opt/local 
Exit code: 2
Error: org.macports.destroot for port srecord returned: command execution failed
DEBUG: Error code: CHILDSTATUS 6359 2
DEBUG: Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec destroot"
    (procedure "portdestroot::destroot_main" line 2)
    invoked from within
"$procedure $targetname"

but if I run the offending command on the command line as follows:

$ sudo /usr/bin/install -c bin/.libs/srec_cat /opt/local/bin/srec_cat

it all works fine. Why would I get an error like this when running the port command but I don't when I run at the command line? Sorry if this is a dumb question...I really did look everywhere I could think of for an answer before posting this.

Thanks!

Alin

Change History (1)

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

Description: modified (diff)

Because the port is not respecting the restrictions MacPorts enforces. MacPorts requires ports to install files within the workpath, more specifically within the destroot, usually. This port is trying to install directly to the prefix, which is prohibited.

Note: See TracTickets for help on using tickets.