Hi All, Tried to install tidy prior to installing php5 on my sandbox machine. The attempt resulted in this error: ---> Building tidy with target all DEBUG: Executing org.macports.build (tidy) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_tid y/work/tidy" && make all' make: *** No rule to make target `all'. Stop. Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_tid y/work/tidy" && make all " returned error 2 Command output: make: *** No rule to make target `all'. Stop. Warning: the following items did not execute (for tidy): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. What's weird, is that I successfully installed tidy (and php5) about 4-5 weeks ago both on the sandbox and this machine. Comparing the two portfiles (this machine and the attempted fresh install on the sandbox) showed only a different time stamp & commit email address and additional livecheck directives. Everything else looked unchanged. Any ideas? Thanks, Jeff
On Sep 14, 2007, at 13:38, Jeff Stubbs wrote:
Tried to install tidy prior to installing php5 on my sandbox machine. The attempt resulted in this error:
---> Building tidy with target all DEBUG: Executing org.macports.build (tidy) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_t idy/work/tidy" && make all' make: *** No rule to make target `all'. Stop. Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_t idy/work/tidy" && make all " returned error 2 Command output: make: *** No rule to make target `all'. Stop.
Warning: the following items did not execute (for tidy): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.
What's weird, is that I successfully installed tidy (and php5) about 4-5 weeks ago both on the sandbox and this machine. Comparing the two portfiles (this machine and the attempted fresh install on the sandbox) showed only a different time stamp & commit email address and additional livecheck directives. Everything else looked unchanged.
I can confirm the problem, and don't know yet why it happens.
Ryan Schmidt wrote:
On Sep 14, 2007, at 13:38, Jeff Stubbs wrote:
Tried to install tidy prior to installing php5 on my sandbox machine. The attempt resulted in this error:
---> Building tidy with target all DEBUG: Executing org.macports.build (tidy) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_tidy/work/tidy" && make all' make: *** No rule to make target `all'. Stop. Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_tidy/work/tidy" && make all " returned error 2 Command output: make: *** No rule to make target `all'. Stop.
Warning: the following items did not execute (for tidy): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.
What's weird, is that I successfully installed tidy (and php5) about 4-5 weeks ago both on the sandbox and this machine. Comparing the two portfiles (this machine and the attempted fresh install on the sandbox) showed only a different time stamp & commit email address and additional livecheck directives. Everything else looked unchanged.
I can confirm the problem, and don't know yet why it happens.
What platform on you trying to install on? This is the same error I reported on esound, and libmng on a PBook G4 10.4.10 and in those cases seems to be a bug in the 'configure' script generated by autoconf. The configure script does not produce any output when run and does not produce a Makefile, but exits 0, so no error is reported in that step. Since there is no Makefile you get an error at the next step (make) about 'no rule'.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Sep 14, 2007, at 4:14 PM, David Moylan wrote:
Ryan Schmidt wrote:
On Sep 14, 2007, at 13:38, Jeff Stubbs wrote:
Tried to install tidy prior to installing php5 on my sandbox machine. The attempt resulted in this error:
<snip>
What's weird, is that I successfully installed tidy (and php5) about 4-5 weeks ago both on the sandbox and this machine. Comparing the two portfiles (this machine and the attempted fresh install on the sandbox) showed only a different time stamp & commit email address and additional livecheck directives. Everything else looked unchanged. I can confirm the problem, and don't know yet why it happens. What platform on you trying to install on? This is the same error I reported on esound, and libmng on a PBook G4 10.4.10 and in those cases seems to be a bug in the 'configure' script generated by autoconf. The configure script does not produce any output when run and does not produce a Makefile, but exits 0, so no error is reported in that step. Since there is no Makefile you get an error at the next step (make) about 'no rule'.
Platform: G3 minitower, 10.4.10, latest macports. Ryan: Does PHP really require tidy? I was just trying to provide as many options for the mapserver software that I later plan on installing. Jeff
On Sep 14, 2007, at 20:42, Jeff Stubbs wrote:
On Sep 14, 2007, at 4:14 PM, David Moylan wrote:
Ryan Schmidt wrote:
On Sep 14, 2007, at 13:38, Jeff Stubbs wrote:
Tried to install tidy prior to installing php5 on my sandbox machine. The attempt resulted in this error:
<snip>
What's weird, is that I successfully installed tidy (and php5) about 4-5 weeks ago both on the sandbox and this machine. Comparing the two portfiles (this machine and the attempted fresh install on the sandbox) showed only a different time stamp & commit email address and additional livecheck directives. Everything else looked unchanged. I can confirm the problem, and don't know yet why it happens. What platform on you trying to install on? This is the same error I reported on esound, and libmng on a PBook G4 10.4.10 and in those cases seems to be a bug in the 'configure' script generated by autoconf. The configure script does not produce any output when run and does not produce a Makefile, but exits 0, so no error is reported in that step. Since there is no Makefile you get an error at the next step (make) about 'no rule'.
Platform: G3 minitower, 10.4.10, latest macports.
I'm on a MacBook Pro, Intel Core 2 Duo, 10.4.10, MP trunk from a couple weeks ago, Xcode 2.4.1. This problem is clearly not very picky about the systems it appears on. I think something broke somewhere, since I didn't used to have any trouble installing tidy. I just haven't had any time to investigate what's going on.
Ryan: Does PHP really require tidy? I was just trying to provide as many options for the mapserver software that I later plan on installing.
No, it does not. That's why it's a variant. If you want to use any of the tidy functions in php, described here: http://php.net/tidy then you need the +tidy variant. If you do not, then you do not.
participants (3)
-
David Moylan
-
Jeff Stubbs
-
Ryan Schmidt