From: Steve Grubb <sgrubb@redhat.com>
To: George McCollister <george.mccollister@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Patch to fix cross-compiling
Date: Mon, 05 Nov 2012 12:25:04 -0500 [thread overview]
Message-ID: <3191851.D7rVKhzsBN@x2> (raw)
In-Reply-To: <5097CF57.2070204@gmail.com>
On Monday, November 05, 2012 08:38:15 AM George McCollister wrote:
> On 11/05/2012 08:28 AM, Steve Grubb wrote:
> > Well...it breaks the normal build on x86_64:
> Works for me on x86_64. Did you remember to run autogen.sh so configure
> gets regenerated before running configure? If that doesn't help it would
> be helpful to get your lib/Makefile so I could analyze it.
I have a script that I use for testing all patches wrt the build. It have 2
modes, one that pulls a fresh copy from svn to check for missing files and one
that just uses the local svn cache so I can test prior to pushing. It does
something like this:
cwd=`pwd`
mkdir audt
cd audit
cp -r $trunk/* .
./autogen.sh
./configure --with-prelude -with-libwrap
make -j 8 dist
mv audit-$release.tar.gz ~/working/audit/
cd $cwd
rpmbuild -ba ../audit/audit.spec
Its failing under the rpmbuild which does not use the autogen script.
But there is another problem I didn't notice right away...it adds a new file,
m4/ax_cc_for_build.m4. In it is this:
+# This program is free software: you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by the
+# Free Software Foundation, either version 3 of the License, or (at your
+# option) any later version.
The audit package is strictly GPL/LGPL v2.
-Steve
next prev parent reply other threads:[~2012-11-05 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:11 Patch to fix cross-compiling George McCollister
2012-11-05 14:28 ` Steve Grubb
2012-11-05 14:38 ` George McCollister
2012-11-05 17:25 ` Steve Grubb [this message]
2012-11-05 18:52 ` George McCollister
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=3191851.D7rVKhzsBN@x2 \
--to=sgrubb@redhat.com \
--cc=george.mccollister@gmail.com \
--cc=linux-audit@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