On Wed, Mar 21, 2007, David M. Fetter wrote:
>It seems that for some reason gcc is not acknowledging
>our /usr/local/include directory in it's includes when building.  In
>fact, there is this specific bit in the spec file:
>
>    %{l_shtool} subst -v -s \
>        -e 's;PREFIX_INCLUDE_DIR;PREFIX_INCLUDE_DIR_DISABLED;g' \
>        gcc/configure
>
>We happen to use /usr/local as our openpkg prefix since this is an
>unused location for us across all of our systems and it is a common
>place where software like this is typically found so it makes it easy
>for the end users to find.  In any case, we're still looking into this
>but it seems that by removing this bit from the spec file, it causes
>another series of dilemmas.  One such dilemma is that multilib is being
>enabled on RHEL4 64-bit when apparently that's not a good thing on that
>particular platform.  Any help with this would be great.  Thanks.  :-)

A symlink from a ``normal'' OpenPKG instance to /usr/local?

I often make symlinks such as %{l_prefix}/bin/perl to /usr/local/bin/perl
to deal with software that may have this hard coded.

Bill
--
INTERNET:   [EMAIL PROTECTED]  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

The difference between science and the fuzzy subjects is that science
requires reasoning while those other subjects merely require scholarship.
                -- Robert Heinlein
______________________________________________________________________
OpenPKG                                             http://openpkg.org
User Communication List                      openpkg-users@openpkg.org

Reply via email to