Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: e2fsprogs is broken in configure/autoreconf
Date: Tue, 14 Apr 2009 15:07:42 -0400	[thread overview]
Message-ID: <20090414190742.GD28306@denix.org> (raw)
In-Reply-To: <20090414161157.GB28306@denix.org>

On Tue, Apr 14, 2009 at 12:11:57PM -0400, Denys Dmytriyenko wrote:
> On Tue, Apr 14, 2009 at 07:42:04AM +0100, Graeme Gregory wrote:
> > Denys Dmytriyenko wrote:
> > > Hi,
> > >
> > > XorA's commit[1] seems to break e2fsprogs for me (omap3evm/davinci), not fix. 
> > > I know, it's not a bug, it's a feature! :) All I know it used to work and it's 
> > > too late now for me to debug it...
> > >
> > > Anyway, the logs are at [2] and [3]. Thanks!
> > >
> > > http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=d187eec071bb0afe8bda13cbf7b89170fe99e384
> > > http://tinderbox.openembedded.net/packages/477200/
> > > http://tinderbox.openembedded.net/public/logs/4350191.txt
> > >
> > >   
> > Interesting, but that log isnt an omap log. Looks to me like an
> > incomplete tmp/ directory for armv5te.
> 
> It is an omap, don't worry. It's just not called such :) Or, you can think 
> about as a generic armv5te machine...
> 
> Anyway, that was a clean build - removing tmp and deploy directory. I'll check 
> if there any configuration issues.

Ah, it now depends on gettext-native, fixed.

-- 
Denys



      reply	other threads:[~2009-04-14 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  5:07 e2fsprogs is broken in configure/autoreconf Denys Dmytriyenko
2009-04-14  5:24 ` Denys Dmytriyenko
2009-04-14  6:42 ` Graeme Gregory
2009-04-14 16:11   ` Denys Dmytriyenko
2009-04-14 19:07     ` Denys Dmytriyenko [this message]

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=20090414190742.GD28306@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox