public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Wayne Dernoncourt <wayned@cpcug.org>
To: Ian Roxborough <irox@redhat.com>
Cc: SourceNav <sourcenav@sources.redhat.com>
Subject: Re: help on installation
Date: Wed, 14 Mar 2001 04:05:00 -0000	[thread overview]
Message-ID: <Pine.GSO.3.96.1010314065557.10164A-100000@cpcug.org> (raw)
In-Reply-To: <3AAEDF03.B13EF5B@redhat.com>

On Tue, 13 Mar 2001, Ian Roxborough wrote:

> Wayne Dernoncourt wrote:

> > On Tue, 13 Mar 2001, Ian Roxborough wrote:
> > > conftest.c is generated by configure to check the basics
> > > of your compiler.  Does you compiler work for a quick
> > > "Hello World!" program?

> > I just dug up a small C program that I had written back in August for
> > a class, it compiled and linked fine.

> Well that's good (assuming that you used the same gcc).

It could be the wrong make (wrong version), so far there are at
least two versions of make, gmake could also be there somewhere.
Not sure how to find out which one is being used - which just
returns - no results.

> > > If you look in config.log you should get more information
> > > on why it failed.

> > I don't see a config.log anywhere in my current directory structure.
> > I used ls -lR * |grep "Mar 13", here are the results:

> config.log will be in the same directory that you run configure in.
> Note that you should not runing configure in the source directory.
> Create a build directory and run configure from there. I.e

> $ mkdir build
> $ cd build
> $ ../src/configure --prefix=/where/you/want/to/install
> $ less config.log

I would think the log file would be in the same directory I ran it
from.  I had unzipped and untarred in my home directory (~) which
created ~/SN452, I ran configure from ~ (./SN452/configure).  Maybe
I'll create a sub-directory and see what happens.  But I didn't
see a log file in ~.  It only took a dozen or so trys with an error
message of "needs to be run from a parallel directory" - maybe
since I'm a level above, not a peer level it doesn't work....

Take care      |   This clown speaks for himself, his job doesn't
Wayne D.       |   pay for this, etc. (directly anyway)

  reply	other threads:[~2001-03-14  4:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13  7:04 Wayne Dernoncourt
2001-03-13 10:48 ` Ian Roxborough
2001-03-13 11:39   ` Wayne Dernoncourt
2001-03-13 13:01   ` Wayne Dernoncourt
2001-03-13 19:01     ` Ian Roxborough
2001-03-14  4:05       ` Wayne Dernoncourt [this message]
2001-03-14  7:56         ` Wayne Dernoncourt
2001-03-14  9:39           ` Wayne Dernoncourt
2001-03-14  9:53             ` Ian Roxborough
2001-03-14 11:51             ` D-Man
2001-03-14 13:35               ` Wayne Dernoncourt
2001-03-14 13:54                 ` Ben Elliston
2001-03-14 14:46                   ` Wayne Dernoncourt
2001-03-14 14:14                 ` Ian Roxborough
2001-03-14 14:36                   ` Wayne Dernoncourt
2001-03-14 14:48                     ` Ian Roxborough
2001-03-14 15:57                       ` Wayne Dernoncourt
2001-03-15  0:40                 ` Khamis Abuelkomboz (UUNET)
2001-03-15 11:21                   ` Syd Polk
2001-03-14  9:51           ` Ian Roxborough

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.GSO.3.96.1010314065557.10164A-100000@cpcug.org \
    --to=wayned@cpcug.org \
    --cc=irox@redhat.com \
    --cc=sourcenav@sources.redhat.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).