mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Javier Fileiv <javier.fileiv@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Fwd:  Problem adding new package.
Date: Sun, 6 Oct 2013 11:59:28 +0200	[thread overview]
Message-ID: <CABvwO2AKtEGcsSjhPqoZkszGx-yuTegdaCVZ-zPm=xWzJS+HGA@mail.gmail.com> (raw)
In-Reply-To: <CABvwO2D==XqM_d06=kA8PZPTQdtNPWdHwOnBXrexGb6HZwZh2w@mail.gmail.com>


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

---------- Forwarded message ----------
From: Javier Fileiv <javier.fileiv@gmail.com>
Date: 2013/10/6
Subject: Re: [ptxdist] Problem adding new package.
To: Marc Kleine-Budde <mkl@pengutronix.de>


when ptxdist runs ./configure this is the output

checking build system type... x86_64-host-linux-gnu
checking host system type... arm-v4t-linux-gnueabi
checking target system type... arm-v4t-linux-gnueabi
checking for arm-v4t-linux-gnueabi-gcc... arm-v4t-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-v4t-linux-gnueabi-gcc accepts -g... yes
checking for arm-v4t-linux-gnueabi-gcc option to accept ISO C89... none
needed
checking for arm-v4t-linux-gnueabi-ranlib... arm-v4t-linux-gnueabi-ranlib
checking for arm-v4t-linux-gnueabi-ar... arm-v4t-linux-gnueabi-ar
checking how to run the C preprocessor... arm-v4t-linux-gnueabi-cpp
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for tputs in -lncurses... yes
configure: creating ./config.status
config.status: creating config/config
finished target speech_tools.prepare



2013/10/6 Javier Fileiv <javier.fileiv@gmail.com>

> What does it mean?? Isnt there any work around?
>
>
> 2013/10/5 Marc Kleine-Budde <mkl@pengutronix.de>
>
>> On 10/05/2013 08:14 PM, Javier Fileiv wrote:
>> > Im trying to build Edinburgh Speech Tools package for my mini2440 using
>> > ptxdist.
>> >
>> > The steps to install it on the host pc are ./configure and make, just
>> that.
>>
>> It looks like they use autotools, but they have their own build system
>> in the background. Which seems to be broken for normal autoools style
>> cross compiling.
>>
>> Marc
>>
>> --
>> Pengutronix e.K.                  | Marc Kleine-Budde           |
>> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
>> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
>> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>>
>>
>

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

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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2013-10-06  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 18:14 [ptxdist] " Javier Fileiv
2013-10-05 18:27 ` Marc Kleine-Budde
2013-10-06  8:56   ` Javier Fileiv
     [not found]     ` <CABvwO2D==XqM_d06=kA8PZPTQdtNPWdHwOnBXrexGb6HZwZh2w@mail.gmail.com>
2013-10-06  9:59       ` Javier Fileiv [this message]
2013-10-06 10:04     ` Marc Kleine-Budde
2013-10-09  7:22       ` Javier Fileiv
2013-10-09  7:27         ` Javier Fileiv
2013-10-09 11:11           ` Marc Kleine-Budde
2013-10-09 18:50             ` Javier Fileiv
2013-10-09 19:21               ` Marc Kleine-Budde
2013-10-10 19:53                 ` Javier Fileiv

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='CABvwO2AKtEGcsSjhPqoZkszGx-yuTegdaCVZ-zPm=xWzJS+HGA@mail.gmail.com' \
    --to=javier.fileiv@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