Read-only /usr/ports (problem with fontconfig)

[Mike Meyer]

In <20030405000650.GA44940 at rigel.bajus.ca>, Cory Bajus <cbajus at mts.net> typed:
> Is a read-only /usr/ports directory supported?

Yes, it is. You're supposed to be able to build ports off of a CDROM.

> I received the following error message during installation of
> x11-fonts/fontconfig (as part of a build of x11/XFree86-4):
> 
>  install -c -o root -g wheel -m 444 ./fontconfig.pc /usr/X11R6/libdata/pkgconfig
> /fontconfig.pc
> gmake[2]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc
> onfig-2.1.92'
> gmake[1]: Leaving directory `/usr/work/usr/ports/x11-fonts/fontconfig/work/fontc
> onfig-2.1.92'
> ===>   Generating temporary packing list
> cannot create /usr/ports/x11-fonts/fontconfig/pkg-install: read-only file system
> *** Error code 2
> Stop in /usr/ports/x11-fonts/fontconfig.
> *** Error code 1
> Stop in /usr/ports/x11/XFree86-4-libraries.
> *** Error code 1
> Stop in /usr/ports/x11/XFree86-4.
> 
> My /usr/ports directory is NFS mounted (read-only) from another
> system.  I have the following entries in /etc/make.conf to allow
> multiple clients to share the same /usr/ports tree:
> 
> WRKDIRPREFIX=   /usr/work      (local directory)
> DISTDIR=        /usr/distfiles (NFS mounted read-write)
> 
> Is it normal for a port to try to write into /usr/ports when
> WRKDIRPREFIX is defined like this?

No, it isn't. I've been using a setup similar to yours for years, and
have never had a problem. I could swear I saw a note in the porter's
handbook that scratch files were supposed to be built in $(WRKDIR),
which is in $(WRKDIRPREFIX). I'd contact the maintainer of the of the
fontconfig port about this - it seems like it's touching something it
shouldn't.

	<mike
-- 
Mike Meyer <mwm at mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.