From: Wim Vinckier <wimpunk@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Running autogen.sh in prepare step
Date: Thu, 21 Aug 2014 15:16:02 +0200 [thread overview]
Message-ID: <CAMyOCn-avZ8dmRzy6rnG2Rr2SzhnzgYoC92FOQfrZdKgZRBLFQ@mail.gmail.com> (raw)
In-Reply-To: <20140821094429.GA30261@omega>
Hi,
On Thu, Aug 21, 2014 at 11:44 AM, Alexander Aring <alex.aring@gmail.com> wrote:
> Hi,
>
> On Thu, Aug 21, 2014 at 11:20:05AM +0200, Wim Vinckier wrote:
>> Hi,
>>
>> I'm trying to compile axis2c for arm but it fails. I'm wondering if
>> I'm running autogen.sh correctly. Currently I run it from my
>> operating system but maybe I have to do it from the crosscompile
>> environment so I'm wondering how I have to specify in my make file how
>> to run autogen.sh in the prepare step.
>>
>
> I think this can be done if you add a patches directory and add a
> autogen.sh file in there. Note this should be executable.
>
> Like screen see [0]. We have patches which change the buildsystem so we
> need to rerun autoreconf, etc.
>
> At the most cases autogen.sh in ./patches/foobar/autogen.sh is a
> symlink to ./patches/autogen.sh
>
> But in your BSP there should not be a patches/autogen.sh, I prefer to
> copy this file from ptxdist in my BSP patches directory. Easier for me
> to bring new rules mainline.
>
> - Alex
>
> [0] http://git.pengutronix.de/?p=ptxdist.git;a=tree;f=patches/screen-4.0.3
>
Thanks for the tip. I found more about it in the ptx guru document. I
currently managed to build it but it looks like pkg-config still files
when I try to use libxml. I think I'll have to read some extra
manuals.
wim.
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-08-21 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 9:20 Wim Vinckier
2014-08-21 9:44 ` Alexander Aring
2014-08-21 13:16 ` Wim Vinckier [this message]
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=CAMyOCn-avZ8dmRzy6rnG2Rr2SzhnzgYoC92FOQfrZdKgZRBLFQ@mail.gmail.com \
--to=wimpunk@gmail.com \
--cc=ptxdist@pengutronix.de \
/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