* [ptxdist] Running autogen.sh in prepare step
@ 2014-08-21 9:20 Wim Vinckier
2014-08-21 9:44 ` Alexander Aring
0 siblings, 1 reply; 3+ messages in thread
From: Wim Vinckier @ 2014-08-21 9:20 UTC (permalink / raw)
To: ptxdist
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.
wim.
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ptxdist] Running autogen.sh in prepare step
2014-08-21 9:20 [ptxdist] Running autogen.sh in prepare step Wim Vinckier
@ 2014-08-21 9:44 ` Alexander Aring
2014-08-21 13:16 ` Wim Vinckier
0 siblings, 1 reply; 3+ messages in thread
From: Alexander Aring @ 2014-08-21 9:44 UTC (permalink / raw)
To: ptxdist
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
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ptxdist] Running autogen.sh in prepare step
2014-08-21 9:44 ` Alexander Aring
@ 2014-08-21 13:16 ` Wim Vinckier
0 siblings, 0 replies; 3+ messages in thread
From: Wim Vinckier @ 2014-08-21 13:16 UTC (permalink / raw)
To: ptxdist
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-08-21 13:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-21 9:20 [ptxdist] Running autogen.sh in prepare step Wim Vinckier
2014-08-21 9:44 ` Alexander Aring
2014-08-21 13:16 ` Wim Vinckier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox