From: "Mike A. Harris" <mharris@opensourceadvocate.org>
To: sourcenav@sourceware.cygnus.com
Subject: Can't configure in source dir..
Date: Tue, 10 Oct 2000 12:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0010101533380.742-100000@asdf.capslock.lan> (raw)
I get the following error after untarring the SN source, cd'ing
into the dir and trying to configure:
10 mharris@asdf:~/rpmbuild/SOURCES/SN452-source$ ./configure
Configuring for a i586-pc-linux-gnu host.
*** Cannot configure in source tree.
*** Make a parallel directory and configure there.
No matter what directory I put the sources in I get this. I've
got 3 copies of the untarred sources right now and it still does
not configure no matter what. Looking at the configure script I
find:
# Don't allow builds at Cygnus to be done with
srcdir==builddir. We
# can assume srcdir==. in this case, because of code above.
if test "$srcdir" = .; then
echo '***' "Cannot configure in source tree." >&2
echo '***' "Make a parallel directory and configure
there." >&2
exit 1
fi
Short of removing this line from the script, what is the
recommended method to build this thing. ;o) I just followed the
instructions in the top level README file and it does not work.
10 mharris@asdf:~/rpmbuild/SOURCES/SN452-source$ ./configure
--prefix=/opt/source-navigator --srcdir=.
Configuring for a i586-pc-linux-gnu host.
*** Cannot configure in source tree.
*** Make a parallel directory and configure there.
$ ./configure --prefix=/opt/source-navigator \
--srcdir=. --secretdecoderring=~/.decoderrings/sourcenav.ring
configure: Unrecognized
option: "--secretdecoderring=/home/mharris/.decoderrings/sourcenav.ring"; use
--help for usage.
Is there some problem with compiling this as non-root? I really
don't want to have to be root to build packages.. Any ideas?
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open source advocate
Computer Consultant - Capslock Consulting
Copyright 2000 all rights reserved
----------------------------------------------------------------------
[Favorite quotes of Linus Torvalds - Sept 6, 2000]
I'm a bastard. I have absolutely no clue why people can ever think
otherwise. Yet they do. People think I'm a nice guy, and the fact is that
I'm a scheming, conniving bastard who doesn't care for any hurt feelings
or lost hours of work if it just results in what I consider to be a better
system. And I'm not just saying that. I'm really not a very nice person.
I can say "I don't care" with a straight face, and really mean it.
-- Linus Torvalds on linux-kernel mailing list
next reply other threads:[~2000-10-10 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 12:43 Mike A. Harris [this message]
2000-10-10 13:12 ` Ian Roxborough
2000-10-10 13:37 ` Mike A. Harris
2000-10-10 13:51 ` Syd Polk
2000-10-10 13:55 ` Ben Elliston
2000-10-10 14:04 ` Mike A. Harris
2000-10-10 14:39 ` Ben Elliston
2000-10-10 14:56 ` Tom Tromey
2000-10-10 15:25 ` Mike A. Harris
2000-10-10 13:15 ` Ben Elliston
2000-10-10 13:16 ` Mo DeJong
2000-10-10 13:46 ` Syd Polk
2000-10-10 13:26 William Gacquer
2000-10-10 13:41 ` Mike A. Harris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0010101533380.742-100000@asdf.capslock.lan \
--to=mharris@opensourceadvocate.org \
--cc=sourcenav@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).