Opened 18 years ago

Closed 18 years ago

#7063 closed defect (fixed)

BUG: ncurses build fails

Reported by: fulton@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc: markd@…
Port:

Description

On Panther (10.3.9), ncursesw builds but ncurses fails during the destroot phase:

Error: Target com.apple.destroot returned: error deleting "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_devel_ncurses/work/destroot/opt/local/share/delete-me/man3": file already exists Error: /opt/local/bin/port: Status 1 encountered during processing.

Change History (5)

comment:1 Changed 18 years ago by blb@…

Owner: changed from darwinports-bugs@… to mww@…

Assign to maintainer.

comment:2 Changed 18 years ago by mww@…

Summary: ncurses build failsBUG: ncurses build fails

would you mind providing me with a full trace? $> port clean ncurses $> port -d destroot ncurses > logfile 2>&1

comment:3 Changed 18 years ago by markd@…

Cc: markd@… added

I've duplicated the problem and it only occurs on 10.3. On 10.4 it works fine. The man3 directory has a bunch of symlinks and it doesn't want to delete with "file delete -force ${destroot}${prefix}/share" so the port errors out at the destroot phase. Change that to "system rm -rf ${destroot}${prefix}/share" and it completes fine.

So the question is why does "file delete -force" choke on 10.3 but work fine on 10.4? And what is the best way to fix it in any case.

comment:4 Changed 18 years ago by mww@…

(In reply to comment #4)

So the question is why does "file delete -force" choke on 10.3 but work fine on 10.4? And what is the best way to fix it in any case.

I suppose this is due to the older Tcl version that comes with 10.3; do we have another case where this is a problem? If this really is a Tcl-issue for 10.3, we'd have to consider to skip 'file delete' altogether perhaps.

comment:5 Changed 18 years ago by markd@…

Resolution: fixed
Status: newclosed

Revision 2 of the port has been committed to fix this problem.

Note: See TracTickets for help on using tickets.