Hi all The grep port is broken here on Tiger: Making install in po /./install-sh -c -d /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_grep/work/destroot//opt/local/share make[1]: /./install-sh: Command not found make[1]: *** [install-data-yes] Error 127 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing. In the following generated Mafile: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_grep/work/grep-2.5.3/po There is this strange part: MKDIR_P = .././install-sh -c -d mkdir_p = $(top_builddir)/./install-sh -c -d Looks like test code which needs to be cleaned up and $(top_builddir) is empty at this point. If I replace it with: MKDIR_P = .././install-sh -c -d mkdir_p = .././install-sh -c -d and then resume the port install, then it works. Best regards Olivier
On Jan 20, 2008, at 14:51, Olivier Croquette wrote:
The grep port is broken here on Tiger:
Making install in po /./install-sh -c -d /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysut ils_grep/work/destroot//opt/local/share make[1]: /./install-sh: Command not found make[1]: *** [install-data-yes] Error 127 make: *** [install-recursive] Error 1
Error: Status 1 encountered during processing.
Yes, I filed a ticket on this problem two months ago: http://trac.macosforge.org/projects/macports/ticket/13343 I've added your email address to the ticket's Cc list so you'll be informed of any progress.
In the following generated Mafile: /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysut ils_grep/work/grep-2.5.3/po
There is this strange part:
MKDIR_P = .././install-sh -c -d mkdir_p = $(top_builddir)/./install-sh -c -d
Looks like test code which needs to be cleaned up and $ (top_builddir) is empty at this point.
If I replace it with: MKDIR_P = .././install-sh -c -d mkdir_p = .././install-sh -c -d
and then resume the port install, then it works.
Perhaps the port could include a patch to make this change automatically.
Hi Ryan, Ryan Schmidt wrote, On 20/01/08 22:30:
Yes, I filed a ticket on this problem two months ago:
Thanks for the info. If I find the time, I will have a look in the internals of the port to see what's going wrong.
http://trac.macosforge.org/projects/macports/ticket/13343
I've added your email address to the ticket's Cc list so you'll be informed of any progress.
Thanks! I have added a bit more information.
participants (2)
-
Olivier Croquette
-
Ryan Schmidt