All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Castelow <DCastelow@Airspan.com>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Problem with TI SDK Build 05.
Date: Wed, 22 Aug 2018 11:10:04 +0000	[thread overview]
Message-ID: <a6fd8789fd5b47049bfc6eeceae2d84e@Airspan.com> (raw)


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

Hi,

I had an issue building the latest TI SDK for Sitara processors (05_00_00_15), and Kemal from TI suggested I post my findings here for comment.

So the build I attempted was for

$ MACHINE=am335x-evm bitbake arago-base-tisdk-image

following instructions from

http //software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview.html <http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview.html#id13>

and using both Linux Mint 17.3 (trusty based) and Ubuntu Xenial (16.04) as host machines, giving essentially the same error.

The problem appears in failure to build libtool-cross successfully.

I have traced this back to something in the bitbake recipes/patches that modify the libtool configure script:
See http://e2e.ti.com/support/arm/sitara_arm/f/791/p/718479/2660196#2660196 for the history.

The build does succeed if I ensure HOST_SYS is defined:
As I said in my last post to that thread,
Compilation/build is successful if I edit

arago/tisdk/sources/oe-core/meta/classes/nativesdk.bbclass

-#HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}"
+HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}"

I think this is because there are libtool related .bb files and .patch files that reference either ${host_alias}-libtool or ${HOST_SYS}-libtool.

If HOST_SYS is empty, then the executable would be called -libtool, and then the configure script fails to clean up as it attempts to execute

rm -libtool

which won't work as the file name starts with a - (were this to work, it would need to do the mv/rm of ./${file} rather than just of ${file}).

I'm not sure if this is the correct solution to the problem, but it suggests the need to set HOST_SYS as part of the build instructions.

Can you advise if this is correct?

[cid:GLOMO2018_e6c86ab3-4fac-42ae-88d7-eab266a26da8.png] tfx

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

[-- Attachment #2: GLOMO2018_e6c86ab3-4fac-42ae-88d7-eab266a26da8.png --]
[-- Type: image/png, Size: 65769 bytes --]

                 reply	other threads:[~2018-08-22 11:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a6fd8789fd5b47049bfc6eeceae2d84e@Airspan.com \
    --to=dcastelow@airspan.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.