Bug 206980 - www/firefox: build fails if WRKDIRPREFIX has symlinks
Summary: www/firefox: build fails if WRKDIRPREFIX has symlinks
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: i386 Any
: --- Affects Only Me
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-06 17:09 UTC by roger.marsh
Modified: 2019-08-14 08:05 UTC (History)
1 user (show)

See Also:
jbeich: maintainer-feedback+

Attachments
log generated by portmaster for firefox installation (80.89 KB, text/plain)
2016-02-06 17:09 UTC, roger.marsh 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description roger.marsh 2016-02-06 17:09:45 UTC 
Created attachment 166664 [details]
log generated by portmaster for firefox installation

With /etc/make.conf set to:

WRKDIRPREFIX=/home/david/portbuildwork
PACKAGES=/home/david/portbuildpkg

the firefox installation by:

portmaster -H -D -B -m MAKE_JOBS_UNSAFE=yes \
                    /usr/ports/www/firefox

fails, generating the attached log file.

Without the WRKDIRPREFIX and PACKAGES settings (actually no /etc/make.conf file) the portmaster instruction above works fine.

Ports tree from a portsnap downloaded 2 February 2016.
Comment 1 Jan Beich freebsd_committer freebsd_triage 2016-02-06 21:28:10 UTC 
(In reply to roger.marsh from comment #0)
> WRKDIRPREFIX=/home/david/portbuildwork

Try replacing /home with /usr/home as documented in the Handbook. mozbuild may not like symlinks in path.  I'm using WRKDIRPREFIX=$HOME/.cache myself but without /usr/home.

https://encrypted.google.com/search?q=freebsd+%22%2Fhome%22+vs.+%22%2Fusr%2Fhome%22
Comment 2 roger.marsh 2016-02-07 16:46:59 UTC 
That does it.  Perhaps the 500 or so other ports that had worked already blinded me!  And the previous two upgrades!

Thanks.
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-01-13 03:58:25 UTC 
If I understand comment1 right, it solved. So it could closed.