Re: CVS commit: pkgsrc/www/webkit-gtk

[David Holland <dholland-pkgchanges%netbsd.org@localhost>]

On Sun, May 06, 2012 at 03:43:05PM +0200, John Marino wrote:
 > "Drop MAKE_JOBS_SAFE=no, I cannot reporduce the issue when I added it."
 > 
 > I also have been able to build it fine with MAKE_JOBS = 7,
 > repeatedly without failing.
 > 
 > The difference is 2 hours, 51 minutes vs 50 minutes in build times
 > on my quad AMD.  I'd like to have those 2 hours back if possible.
 > 
 > Are we absolutely sure this is jobs unsafe?

Yes.

  CC     Source/JavaScriptCore/API/tests/Programs_minidom-Node.o
  CC     Source/JavaScriptCore/API/tests/Programs_minidom-NodeList.o
  CC     Source/JavaScriptCore/API/tests/Programs_minidom-minidom.o
  CC     
Source/WebKit/gtk/tests/Programs_unittests_testapplicationcache-testapplicationcache.o
  CCLD   Programs/unittests/testdomdocument
  CCLD   Programs/unittests/testdomdomwindow
  CCLD   Programs/unittests/testdomnode
  CCLD   Programs/unittests/testhttpbackend
  CCLD   Programs/unittests/testfavicondatabase
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
  CCLD   Programs/unittests/testloading
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
  CCLD   Programs/unittests/testglobals
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
.: Can't open ./libjavascriptcoregtk-1.0.la
.: Can't open ./libwebkitgtk-1.0.la
libtool: link: cannot find the library `libjavascriptcoregtk-1.0.la' or 
unhandled argument `libjavascriptcoregtk-1.0.la'
gmake[1]: *** [Programs/unittests/testfavicondatabase] Error 1

Notice that it's still compiling "javascriptcore" when it starts
trying to link with it.

-j8 on a four-way Intel x86_64.

 > David, are your results repeatable?

Yes. Joerg also was getting the same behavior.

If it didn't depend on gmake, I'd fix it.

-- 
David A. Holland
dholland%netbsd.org@localhost