All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: yocto jethro failed on gettext-native
Date: Thu, 26 Apr 2018 17:53:28 +0200	[thread overview]
Message-ID: <5ae1f5fc.0790500a.2fb14.0681@mx.google.com> (raw)
In-Reply-To: <CAJ86T=VSrF4P6-CCTQFJa20i+qgwQby1to4haFd88UMZaghmtQ@mail.gmail.com>

On 25/04/18, Andre McCurdy wrote:
> On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute <oliver.graute@gmail.com> wrote:
> > Hello list,
> >
> > I try to compile yocto jethro environment which is working
> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04.
> >
> > The compilations stops on gettext-native.
> >
> > bitbake -k fsl-image-mfgtool-initramfs
> >
> > | x86_64-linux-libtool:   error: 'libgettextsrc_la-message.lo' is not a valid libtool object
> 
> libgettextsrc_la-message.lo should be a short text file. Could you
> find it in your build tree and post a copy?
> 

the file was a zero byte file. All other *.lo files in that directory
was zero byte too. I assume because of a system crash I had before.

Just a bitbake -c cleansstate and rebuild of gettext-native didn't fixed that.

I deleted all the build-imx6ulevk folder and build everything from
scratch with only one thread, waited a few hours for compilation and now
its working ;)

> > Some ideas whats the cause for this error?
> 
> At a guess, something a little unusual with the setup of your Kubuntu
> system. Combining Ubuntu 16.04 with OE 2.0 isn't so out of the
> ordinary and others would certainly have hit the problem before now if
> it was always seen.
> 
> Did you install all the standard host dependencies?
> 
>   https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html#packages
> 

yes but thanks for the link as reference.

Best regards,

Oliver 


  reply	other threads:[~2018-04-26 15:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 15:03 yocto jethro failed on gettext-native Oliver Graute
2018-04-25 17:49 ` Zoran Stojsavljevic
     [not found]   ` <CAEv37YsacVBmZXtShCij9OxkXmQpUX92QnS=tg_ESO_0NkT3ow@mail.gmail.com>
2018-04-25 18:27     ` Zoran Stojsavljevic
2018-04-25 19:36   ` Oliver Graute
2018-04-25 19:50     ` Burton, Ross
2018-04-25 20:49       ` Randy MacLeod
2018-04-25 20:55       ` Zoran Stojsavljevic
2018-04-25 20:58         ` Zoran Stojsavljevic
2018-05-02 20:36         ` Paul Barker
2018-05-03  3:29           ` Zoran Stojsavljevic
2018-04-26  4:07 ` Andre McCurdy
2018-04-26 15:53   ` Oliver Graute [this message]
2018-04-26 17:33     ` Zoran Stojsavljevic
2018-04-27  6:19       ` Oliver Graute
2018-04-27  9:25         ` Zoran Stojsavljevic
2018-04-27 12:04         ` Philip Balister
2018-04-27 13:27           ` Zoran Stojsavljevic

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=5ae1f5fc.0790500a.2fb14.0681@mx.google.com \
    --to=oliver.graute@gmail.com \
    --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.