[MacPorts] #31315: npm build fails on MacPorts

MacPorts noreply at macports.org
Mon Sep 19 00:07:02 PDT 2011


#31315: npm build  fails on MacPorts
-------------------------------+--------------------------------------------
 Reporter:  matt@…             |       Owner:  ciserlohn@…           
     Type:  defect             |      Status:  new                   
 Priority:  Normal             |   Milestone:                        
Component:  ports              |     Version:  2.0.3                 
 Keywords:                     |        Port:  npm                   
-------------------------------+--------------------------------------------
Changes (by ryandesign@…):

  * owner:  macports-tickets@… => ciserlohn@…
  * priority:  High => Normal


Old description:

> Logfile: https://gist.github.com/e9115a90e6a194ecd3de
>
> I got on the node.js IRC channel and talked to the creator of node. He
> didn't catch I was installing with MacPorts at first, but he checked out
> the log I linked above and made a couple comments about how you're
> building npm. He said he's not experienced with MacPorts and wasn't sure
> if these things were the way things work with it. Anyway, his additional
> feedback:
>
> :debug:patch Executing command line:  cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_npm/npm/work/npm-1.0.30"
> && /usr/bin/patch -p0 <
> '/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/npm/files
> /patch-scripts-doc-build.sh'
> ^
> He asked why you need to patch it for a Mac when it's developed on a Mac.
>
> Also "...why they're running `make docs` when the docs are already up to
> date in the release package.  (or, if they're not getting the release
> package from registry.npmjs.org, why not?)"
>
> And last: "anyway, looks like macports is pulilng the git repo, not the
> released tarball. the docs aren't built, so it's failing to build them.
> also unclear as to why it's running "make" rather than "make install" but
> maybe they do that in a second step or something"
>
> Thanks!

New description:

 Logfile: https://gist.github.com/e9115a90e6a194ecd3de

 I got on the node.js IRC channel and talked to the creator of node. He
 didn't catch I was installing with MacPorts at first, but he checked out
 the log I linked above and made a couple comments about how you're
 building npm. He said he's not experienced with MacPorts and wasn't sure
 if these things were the way things work with it. Anyway, his additional
 feedback:

 {{{
 :debug:patch Executing command line:  cd
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_npm/npm/work/npm-1.0.30"
 && /usr/bin/patch -p0 <
 '/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/npm/files
 /patch-scripts-doc-build.sh'
 ^
 }}}
 He asked why you need to patch it for a Mac when it's developed on a Mac.

 Also "...why they're running `make docs` when the docs are already up to
 date in the release package.  (or, if they're not getting the release
 package from registry.npmjs.org, why not?)"

 And last: "anyway, looks like macports is pulilng the git repo, not the
 released tarball. the docs aren't built, so it's failing to build them.
 also unclear as to why it's running "make" rather than "make install" but
 maybe they do that in a second step or something"

 Thanks!

--

-- 
Ticket URL: <https://trac.macports.org/ticket/31315#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list