Opened 14 years ago

Closed 14 years ago

#25451 closed defect (invalid)

m4 packaging/scripting error: /work/m4-1.4.13 created in the 1.4.14 port

Reported by: selkovjr@… Owned by: blair (Blair Zajac)
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc:
Port: m4

Description

The subject says it; the error I get is:

:info:configure sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work/m4-1.4.14: No such file or directory

Observations:

port search m4
m4 @1.4.14 (devel)
    GNU macro processor
ls -l /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m4/work
-rw-r--r--   1 root  admin   113 Jun 23 04:57 .macports.m4.state
drwxrwxrwx  36 root  admin  1224 Jun 28 06:59 m4-1.4.13

Change History (4)

comment:1 Changed 14 years ago by drkp (Dan Ports)

Owner: changed from macports-tickets@… to blair@…

comment:2 Changed 14 years ago by blair (Blair Zajac)

Did you do a 'port clean' and try to rebuild it?

comment:3 in reply to:  2 Changed 14 years ago by selkovjr@…

Replying to blair@…:

Did you do a 'port clean' and try to rebuild it?

Tried that right now, and it worked.

That worked just now.

I ran into copious troubles previously, trying to update the ports on a machine that was new to me. The ports on it have apparently survived an upgrade to Leopard. I kept running into various library version and architecture conflicts after selfupdate. In frustration, I did

 port -f uninstall installed

That cleaned the mess, and I was able to install all the ports I needed, with m4 presenting the only obstacle, which I surmounted by linking m4-1.4.13 to m4-1.4.14

I did not know about the importance of 'clean' -- thank you for pointing it out.

comment:4 Changed 14 years ago by blair (Blair Zajac)

Resolution: invalid
Status: newclosed

Great that it worked!

Marking the ticket as invalid because it's not an issue with the port.

Note: See TracTickets for help on using tickets.