[MacPorts] #42014: gjs build failure

[MacPorts]

#42014: gjs build failure
-------------------------+------------------------
  Reporter:  jwhowse4@…  |      Owner:  juanrgar@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.2.1
Resolution:              |   Keywords:
      Port:  gjs         |
-------------------------+------------------------

Comment (by jwhowse4@…):

 Replying to [comment:11 jeremyhu@…]:
 > Replying to [comment:10 jwhowse4@…]:
 > > Replying to [comment:9 jeremyhu@…]:
 > > > I'm curious why the existing is not working for you.  Can you please
 attach the failing build log (that is the mozjs17 build log, not the gjs
 build log), so I can see how the linker is being called.
 > >
 > > The mozjs17 build does not fail for me, it is the gjs build which
 fails.  My understanding is that the gjs build fails because the library
 libmozjs-17.0.dylib created by mozjs17 thinks it is installed in
 ../../../../../../../../../lib when it is actually installed in
 /Volumes/User_Disk/opt/macports/lib.  So in short I do not have a failing
 build log (or in fact any build log) for mozjs17.
 >
 > Yes, thus mozjs17 failed to build correctly.  You didn't get an error
 about it until gjs failed because of mozjs17 failing silently.  Please add
 the mozjs17 build log.  You can recreate it via:
 >
 > {{{
 > sudo port -v -f uninstall mozjs17
 > sudo port -v -s -k install mozjs17
 > }}}
 >
 > The -k will cause it to not be cleaned upon install.

 My apologies for the confusion, your use of the phrase "failing build log"
 confused me.  In any event, attached is the build log for mozjs17.  I
 believe it will be unhelpful, since for some reason the following is now
 the case.

 {{{
 otool -D /Volumes/User_Disk/opt/macports/lib/libmozjs-17.0.dylib
 /Volumes/User_Disk/opt/macports/lib/libmozjs-17.0.dylib:
 /Volumes/User_Disk/opt/macports/lib/libmozjs-17.0.dylib
 }}}

 I have no idea why the library now thinks it is installed in the correct
 location, unless the mozjs17 Portfile has been changed since my last
 build.  The only other possibility that occurs to me is that I had the
 package spidermonkey185 installed when I did the previous build of
 mozjs17, and I uninstalled it before performing this build.

 With this thought in mind I uninstalled mozjs17, installed spidermonkey185
 and then installed mozjs17.  The resulting log file is identical except
 for the time and the result of 'otool -D' is the same.  So I am afraid the
 mystery remains.

-- 
Ticket URL: <https://trac.macports.org/ticket/42014#comment:12>
MacPorts <http://www.macports.org/>
Ports system for OS X