public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mats Liljegren <mats.liljegren@enea.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] Problems with cross-compiling
Date: Mon, 14 Apr 2014 19:22:12 +0200	[thread overview]
Message-ID: <20140414192212.3c97cc76@mats-desktop> (raw)

I've been using Yocto, which does cross-compiling. It has support for
compiling LTP, but I've noticed it has a couple of patches. I found
that one patch was needed for actually compile LTP, which applies to
the file utils/Makefile.

The patch is for an older version of LTP, but I re-implemented it for
the new version. Looking at the following rule:

$(FFSB): $(abs_srcdir)/$(FFSBDIR)
        mkdir -p $(FFSBDIR)
        cd $(FFSBDIR) && "$^/configure" && $(MAKE) top_srcdir="$^" all

This calls configure without parameters, which is most likely wrong for
a cross-compile environment. It is this configure that fails. By simple
removing it, everything works within Yocto.

Is there any reason for keeping this configure here? Or should I make
a patch for removing it?

Regards
Mats Liljegren

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2014-04-14 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 17:22 Mats Liljegren [this message]
2014-04-14 17:41 ` [LTP] Problems with cross-compiling chrubis
2014-04-15  8:31   ` [LTP] [PATCH] utils/Makefile: Move ffsb configure to configure.ac Mats Liljegren
2014-04-15  8:31     ` Mats Liljegren
2014-04-15 11:10       ` chrubis

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=20140414192212.3c97cc76@mats-desktop \
    --to=mats.liljegren@enea.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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