From: Lee Revell <rlrevell@joe-job.com>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Redhat packaging...
Date: Fri, 19 Aug 2005 22:20:12 -0400 [thread overview]
Message-ID: <1124504412.21810.0.camel@mindpipe> (raw)
In-Reply-To: <43068E57.8090900@redfish-solutions.com>
On Fri, 2005-08-19 at 19:58 -0600, Philip Prindeville wrote:
> what do I need to tweak to have things go into the right places
> (i.e. with a command-line build, "make install LIBDIR=..." etc).
You could try --with-redhat=yes also.
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-20 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 1:58 Redhat packaging Philip Prindeville
2005-08-20 2:20 ` Lee Revell [this message]
2005-08-20 17:16 ` Philip Prindeville
2005-08-20 18:27 ` Lee Revell
2005-08-20 3:09 ` Lee Revell
2005-08-22 12:17 ` Takashi Iwai
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=1124504412.21810.0.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=philipp_subx@redfish-solutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.