public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: linux-audit@redhat.com
Subject: Re: Audit Cross Compile Support
Date: Fri, 20 Sep 2013 08:36:03 -0500	[thread overview]
Message-ID: <523C4F43.6030209@magitekltd.com> (raw)
In-Reply-To: <OFC4FC59E0.9B4DCED9-ON86257BEC.0044EE26-86257BEC.004502B4@rockwellcollins.com>


[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]

On 09/20/2013 07:33 AM, clshotwe@rockwellcollins.com wrote:
> Everyone,
>
> I apologize for my previous patch submission (8/23/2013 set of
> patches) without any background information.  I am looking to cross
> compile audit for the ARM and PPC platforms.  I am not sure if this
> has been looked into before but I would get some feedback on a general
> approach.  
>
> I tried to do a base cross compile but I ran into an issue when the
> table header files are generated, the executable generated by the
> makefile were built for the target and not the host.  I modified the
> makefile to build them for the host but I realized the executables
> would pull in the headers from the host rather than the target.  I
> attempted to work around this by porting the gen_tables.c algorithm to
> a python script to duplicate the header file generation using the
> target headers rather than the host.  Is this a good approach?  Is
> there a better way that this could be done a better way that does not
> use python?  Is this a desired feature?

I use mock. It's pretty straightforward.

LCB

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com


[-- Attachment #1.2: Type: text/html, Size: 2131 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2013-09-20 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 12:33 Audit Cross Compile Support clshotwe
2013-09-20 13:36 ` LC Bruzenak [this message]
     [not found]   ` <CAC2S8kgC4Riy_8y0znbDFjQPo0AAaxZEe7uwc7bZqCWXzfcU6A@mail.gmail.com>
2013-09-20 15:18     ` clshotwe
2013-09-20 15:30       ` LC Bruzenak
     [not found]       ` <523C684F.5030901@magitekltd.com>
2013-09-20 15:35         ` LC Bruzenak
2013-09-20 15:40           ` clshotwe
2013-09-20 16:07 ` Steve Grubb
2013-09-20 17:54   ` clshotwe
2013-09-26 18:54   ` [PATCH 0/3] " Clayton Shotwell
  -- strict thread matches above, loose matches on Subject: below --
2013-11-12 10:15 AKASHI Takahiro
2013-11-14 16:05 ` clshotwe

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=523C4F43.6030209@magitekltd.com \
    --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