Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: any thoughts on current dev branch e2fsprogs build error?
Date: Thu, 3 Dec 2009 12:34:32 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912031233230.6255@localhost> (raw)
In-Reply-To: <200912031051.36434.holger+oe@freyther.de>

On Thu, 3 Dec 2009, Holger Hans Peter Freyther wrote:

> On Thursday 03 December 2009 10:42:04 Robert P. J. Day wrote:
> >   on a fully updated dev branch, the tail end of the log file:
> >
> > ... snip ...
> > making all in e2fsck
>
> what changed on your system? can you look at the Makefile? at the
> config.log? why does it list -lpthread?

  i can only guess that some variable that used to expand to something
now doesn't anymore and, somehow, "-lpthread" is being picked up as a
target because of it.

  i'll make sure i'm up to date, then try again.  e2fsprogs has been
building fine all this time.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



      reply	other threads:[~2009-12-03 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  9:42 any thoughts on current dev branch e2fsprogs build error? Robert P. J. Day
2009-12-03  9:51 ` Holger Hans Peter Freyther
2009-12-03 17:34   ` Robert P. J. Day [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=alpine.LFD.2.00.0912031233230.6255@localhost \
    --to=rpjday@crashcourse.ca \
    --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