From: Syd Polk <spolk@redhat.com>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>,
Ian Roxborough <irox@redhat.com>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Can't configure in source dir..
Date: Tue, 10 Oct 2000 13:51:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20001010135207.00dd5570@pop.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0010101632060.742-100000@asdf.capslock.lan>
>Ouch, my brain hurts. ;o) This is the first time I've ever seen
>a package require such an oddball build method. ;o) I'll try it
>though. It might be better to patch the build process than to
>try to come up with a convoluted RPM build method to work around
>it.
>
>Any idea _why_ it does this? I am almost positive 451 did not
>require this. Looking at the configure script it appears that it
>is done for some internal cygnus reason.. Is there a:
>
>./configure --Im-not-cygnus-so-dont-do-that
Building for multiple platforms for the same source tree is the reason why
we build in a separate directory. It looks like I used the wrong version of
autoconf to generate the configure file; I will investigate a patch soon.
Syd Polk spolk@redhat.com
Engineering Manager +1 415 777 9810 x 241
Red Hat, Inc.
next prev parent reply other threads:[~2000-10-10 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 12:43 Mike A. Harris
2000-10-10 13:12 ` Ian Roxborough
2000-10-10 13:37 ` Mike A. Harris
2000-10-10 13:51 ` Syd Polk [this message]
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=4.2.0.58.20001010135207.00dd5570@pop.cygnus.com \
--to=spolk@redhat.com \
--cc=irox@redhat.com \
--cc=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).