Build warnings, and install problems.

[Mike A. Harris]

On Wed, 11 Oct 2000, Ben Elliston wrote:

>Hi Mike,
>
>   During the build I get tonnes of:
>
>   In file included from ../../../db/PORT/../include/db.h:45,
>                    from ../../../db/PORT/../recno/rec_utils.c:44:
>   ../../../db/PORT/include/compat.h:108: warning: `BYTE_ORDER'
>   redefined
>   /usr/include/endian.h:47: warning: this is the location of the
>
>I submitted a patch recently that eliminates this annoying warning so that
>you can see real warnings instead.  It'll be in the next release.

Ok good, so it isn't something I foobed.  ;o)

>   Looks to me like it isn't installing in my BUILDROOT.  Looks like it
>   is trying to install on my system instead.  If this is true, can
>   someone suggest how to have it install elsewhere?
>
>How did you configure the tree?

Hmm. I thought I put that in my message:

%setup -n SN452-source

%build
# Clean out the buildroot dir to prevent common errors
#[ $RPM_BUILD_ROOT != "/" ] && rm -rf $RPM_BUILD_ROOT

mkdir build-redhat
cd build-redhat
../configure --prefix=/opt/source-navigator
make all-snavigator


%install
cd build-redhat
make install-snavigator


The %install section fails with all sorts of permission denied
messages and appears it is trying to install into the system dirs
instead of the build root.


>   Does SN require any part of the build process to be "root"?  Is it
>   possible for an ordinary user to build it, then install it in
>   ~/source-navigator fully functionally?  If so how?
>
>No, you can be an ordinary user to build and install S-N:
>
>	/path/to/src/configure --prefix=$HOME/source-navigator
>
>.. is all you need.

Ok, great.  My above configure line should set everything up
properly for a package that will install into
/opt/source-navigator.

The install section follows instructions either Mo, Ian or you
sent me..  It doesn't work though.  I don't want to compile as
root on this system, so I can't do a test install other than as
an ordinary user, and it doesn't work for me.  I don't see why
the install section would require me to have write access to
/opt/ since it shouldn't be putting things there during RPM build
install time, only at package install time.

Any ideas?

Thanks,
TTYL

----------------------------------------------------------------------
      Mike A. Harris  -  Linux advocate  -  Open source advocate
              Computer Consultant - Capslock Consulting
                 Copyright 2000 all rights reserved
----------------------------------------------------------------------

[Quote: Linus Torvalds - Aug 27, 2000 - linux-kernel mailing list]
"And I'm right.  I'm always right, but in this case I'm just a bit more
right than I usually am." -- Linus Torvalds