ports/112058: [PATCH] databases/fpc-ibase: Does not compile with ibase option

[Jason Bacon]

Jose Alonso Cardenas Marquez wrote:
> 2007/4/23, Edwin Groothuis <edwin at freebsd.org>:
>> Synopsis: [PATCH] databases/fpc-ibase: Does not compile with ibase 
>> option
>>
>> Responsible-Changed-From-To: freebsd-ports-bugs->acm
>> Responsible-Changed-By: edwin
>> Responsible-Changed-When: Tue Apr 24 00:20:12 UTC 2007
>> Responsible-Changed-Why:
>> Over to maintainer
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=112058
>>
>
> Rejected, I think that it isn't a real fpc-ibase problem, because you
> could compile firebird first and try to install fpc-ibase later,
> otherwise you could ask to kris@ or maybe skv@ about what they
> use/modify/set to compile the firebird-client without problems on
> FreeBSD (I know that it exists), The pointyhat cluster didn't report
> any problem building fpc-ibase port.
>
> http://pointyhat.freebsd.org/errorlogs/i386-5-latest-logs/fpc-ibase-2.0.4_1.log 
>
> http://pointyhat.freebsd.org/errorlogs/i386-6-latest-logs/fpc-ibase-2.0.4_1.log 
>
>
> Greetings
> ACM

I *can't* compile firebird first.  Here's the tail of my attempt"

~~~~~~~~~~~~~~~~~~~

The Firebird2 package has been configured with the following options:

Architecture : ClassicServer
       Debug : disabled
  64 bit I/O : enabled
 Raw devices : disabled
Lock manager : enabled
Service name : gds_db
Service port : 3050
GPRE modules : c_cxx.cpp

 Install Dir : /var/db/firebird

Now type `make' to compile Firebird2
===>  Building for firebird-client-1.5.3
==> Please do not build firebird as 'root' because this may cause 
conflicts with SysV semaphores of running services.
*** Error code 1

Stop in /usr/ports/databases/firebird-client.
<<<ROOT at sculpin>>> /usr/ports/databases/firebird-client 360 #

~~~~~~~~~~~~~~~~~~~

I get the same result on every system I've tried, which includes 5.4R, 
PCBSD 1.3, and 6.2R.  These are all fresh-out-of-the-box ports trees.  I 
don't know how pointyhat is getting around this problem, but it would 
seem that some special settings are required to make it work, which 
isn't very user-friendly.

If the conflict with semaphores is still an issue, there probably isn't 
much we can do about the firebird port right now, which is why I 
suggested disabling it by default.

Regards,

    Jason