> Ok, I've looked into DB even deeper and I think the following
> patch should allow us to be maximum portable and still
> use as fast as possible mutexes:
> 
> Index: db.spec
> ===================================================================
> RCS file: /e/openpkg/cvs/openpkg-src/db/db.spec,v
> retrieving revision 1.44
> diff -u -d -u -d -u -d -r1.44 db.spec
> --- db.spec   26 Apr 2004 08:59:43 -0000      1.44
> +++ db.spec   28 Apr 2004 18:30:29 -0000
> @@ -38,7 +38,7 @@
>  Group:        Database
>  License:      BSD
>  Version:      %{V_version}.%{V_revision}
> -Release:      20040426
> +Release:      20040428
> 
>  #   package options
>  %option       with_compat no
> @@ -90,7 +90,13 @@
>  %build
>      mutex="no"
>      case "%{l_platform -p}" in
> -        ix86-* ) mutex="x86/gcc-assembly" ;;
> +        ix86-*   ) mutex="x86/gcc-assembly"   ;;
> +        ia64-*   ) mutex="ia64/gcc-assembly"  ;;
> +        sparc*-* ) mutex="Sparc/gcc-assembly" ;;
> +        hppa*-*  ) mutex="HPPA/gcc-assembly"  ;;
> +        ppc*-*   ) mutex="PPC/gcc-assembly"   ;;
> +        alpha*-* ) mutex="ALPHA/gcc-assembly" ;;
> +        *        ) mutex="UNIX/fcntl"         ;;
>      esac
>      cd build_unix
>      CC="%{l_cc}" \
> 
> In your case this now selects the ALPHA/gcc-assembly mutex in the hope
> this works equally well on Tru64, but should be both portable 
> enough and
> at the same time a lot faster than the fcntl(3) fallback.
> 
> Sorry, but can you give this a try once again? If this also works,
> I'll commit this to CVS.

It compiles fine!

> > If this is included then I
> > guess the change from:
> >
> > > > http://cvs.openpkg.org/chngview?cn=16152
> >
> > isn't needed anymore.
> 
> Yes, but it also will not hurt, I think.
> 
>                                        Ralf S. Engelschall

True.. but then again... it's another patch against upstream sources that
must be maintained.. and in a few months time when it doesn't cleanly apply
anymore, you will have forgotten why it was needed in the first place..
meaning you'll spend time trying to find out why :-)


Karl.
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   [EMAIL PROTECTED]

Reply via email to