[Bug 220330] www/rubygem-selenium-webdriver fails to build when WRKDIRPREFIX is set

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220330

--- Comment #13 from Marko Cupać <marko.cupac at mimar.rs> ---
(In reply to Matthias Fechner from comment #12)

I was also re-trying builds (after fetching portsnap) and it failed multiple
times. Finally, it build fine a few minutes ago. I'm using ccache, I had some
problems with it in the past, could it be related? Or something in ports
infrastructure? I don't see any changes to the port itself since quite some
time.

log:

Successfully installed selenium-webdriver-3.14.1
1 gem installed
/bin/rm -f -r
/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5/build_info/
/usr/bin/find
/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5
-type f -name '*.so' -exec /usr/bin/strip {} +
/usr/bin/find
/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5
-type f \( -name mkmf.log -or -name gem_make.out \) -delete
/bin/rm -f -r
/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5/gems/selenium-webdriver-3.14.1/ext

/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5/cache
2> /dev/null || true
/bin/rmdir
/wrkdirs/usr/ports/www/rubygem-selenium-webdriver/work/stage/usr/local/lib/ruby/gems/2.5/extensions
2> /dev/null || true
====> Compressing man pages (compress-man)
===========================================================================
=======================<phase: package        >============================
===>  Building package for rubygem-selenium-webdriver-3.14.1
===========================================================================
=>> Cleaning up wrkdir
===>  Cleaning for rubygem-selenium-webdriver-3.14.1
build of www/rubygem-selenium-webdriver | rubygem-selenium-webdriver-3.14.1
ended at Tue Jun  4 12:28:32 CEST 2019
build time: 00:00:17

-- 
You are receiving this mail because:
You are the assignee for the bug.