Firebird client fails port install

Da Rock rock_on_the_web at comcen.com.au
Mon Dec 15 13:10:28 PST 2008


On Mon, 2008-12-15 at 15:49 -0500, Lowell Gilbert wrote:
> Da Rock <rock_on_the_web at comcen.com.au> writes:
> 
> > On Mon, 2008-12-15 at 14:29 -0500, Lowell Gilbert wrote:
> >> Da Rock <rock_on_the_web at comcen.com.au> writes:
> >> 
> >> > I'm trying to install php5-extensions (which includes firebird), but its
> >> > failing with an error code 1 on firebird20-client. It does mention
> >> > running make to build firebird, but not as root. So I've tried
> >> > everything to get this to work: running make as my wheel group user,
> >> > installing as a pkg instead.
> >> >
> >> > What could I be missing?
> >> >
> >> > (And before anybody asks: I ran portsnap fetch update twice yesterday -
> >> > and I did run the update. I've learnt my lesson from last time...)
> >> 
> >> Unless you set variables to put the work directory somewhere non-standard,
> >> the ports system will try to do its building under each port's directory,
> >> which is normally not writable by regular users.  Similarly, installing a
> >> port (or a package, for the same reasons) normally requires root
> >> permissions for access to system directories and in many cases to let
> >> programs installed by ports run as special-purpose users.
> >> 
> >> What is the reason you're trying to install ports as a different user?
> >> 
> >
> > Because the first stop error occurs and it says to run make to build
> > firebird, but it also says "Please do not build firebird as 'root'
> > because this may cause conflicts with SysV semaphores of running
> > services."
> 
> I can't see exactly what's happening (partly because you didn't show the
> actual failure messages), but I do notice that php5-extensions can build
> without firebird.  In fact, that's what it does by default, so you must
> have explicitly told it to build that.  If you don't need it, you can go
> back in and set the php5-extensions port options to not include
> firebird, and you will avoid this particular problem.
> 

I did that in the end, but that doesn't really solve the problem now
does it? I'll take it up with ports and see if I can't figure out whats
wrong...



More information about the freebsd-questions mailing list