Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe PATCH v2 4/6] gdal: Add recipe for 1.10.1 version
Date: Fri, 3 Jan 2014 22:59:30 +0100	[thread overview]
Message-ID: <20140103215930.GI3707@jama> (raw)
In-Reply-To: <CAP9ODKoxN6pb3JvjzY7x8NPmDj2U0jVtsUgYxrgdx7ney5J2cw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

On Fri, Jan 03, 2014 at 04:01:36PM -0200, Otavio Salvador wrote:
> Hello Martin,
> 
> On Wed, Jan 1, 2014 at 10:36 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Mon, Dec 16, 2013 at 10:30:59PM -0200, Otavio Salvador wrote:
> >> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >> ---
> >> Changes in v2: None
> >
> > Please fix following error detected in:
> > http://jenkins.nas-admin.org/job/oe_shr-image-all_tmpfs_qemuarm/173/consoleFull
> >
> > ERROR: This autoconf log indicates errors, it looked at host include
> > and/or library paths while determining system capabilities.
> > Rerun configure task after fixing this. The path was
> > '/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/gdal/1.10.1-r0/gdal-1.10.1'
> > ERROR: Function failed: do_qa_configure
> > ERROR: Logfile of failure stored in:
> > /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/gdal/1.10.1-r0/temp/log.do_configure.883
> > NOTE: recipe gdal-1.10.1-r0: task do_configure: Failed
> > ERROR: Task 14201
> > (/home/jenkins/oe/shr-core-branches/shr-core/meta-openembedded/meta-oe/recipes-navigation/gdal/gdal_1.10.1.bb,
> > do_configure) failed with exit code '1'
> 
> Can you send me the full log? I failed to identify  what causes it.

It's already gone running another build but next time I see it I'll try
to keep the log.

> 
> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-01-03 21:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  0:30 [meta-oe PATCH v2 1/6] meta-oe: Drop pointercal-xinput from SIGGEN_EXCLUDERECIPES_ABISAFE Otavio Salvador
2013-12-17  0:30 ` [meta-oe PATCH v2 2/6] proj: Use 'lib_package' class and add data files Otavio Salvador
2013-12-17  0:30 ` [meta-oe PATCH v2 3/6] geos: Update to 3.4.2 and rework the packaging Otavio Salvador
2013-12-17  0:30 ` [meta-oe PATCH v2 4/6] gdal: Add recipe for 1.10.1 version Otavio Salvador
2014-01-01 12:36   ` Martin Jansa
2014-01-03 18:01     ` Otavio Salvador
2014-01-03 21:59       ` Martin Jansa [this message]
2014-01-05 13:28         ` Martin Jansa
2013-12-17  0:31 ` [meta-oe PATCH v2 5/6] ntfs-3g-ntfsprogs: Fix runtime dependency for development package Otavio Salvador
2013-12-17  0:31 ` [meta-oe PATCH v2 6/6] geos: Fix -dev installation and upgrade path Otavio Salvador

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=20140103215930.GI3707@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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