From: LC Bruzenak <lenny@magitekltd.com>
To: Linux-audit@redhat.com
Subject: build 32 on 64
Date: Tue, 23 Sep 2008 16:41:58 -0500 [thread overview]
Message-ID: <1222206118.6513.116.camel@homeserver> (raw)
I guess with the latest audit code there is no easy way to build the
32-bit variants on a 64-bit machine?
The compiles work fine, however the python checking code in pycheck will
not work because the installed python is 64-bit whereas the .so it
accesses (auparse.so; built) is 32-bit.
The build logs on koji look as if it is compiling natively in both
instances.
Thx,
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
reply other threads:[~2008-09-23 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1222206118.6513.116.camel@homeserver \
--to=lenny@magitekltd.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