All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gphoto2_2.4.8.bb: Stop configure from looking in /usr/local/include
Date: Wed, 3 Nov 2010 20:04:52 +0100	[thread overview]
Message-ID: <AANLkTikcC1DKQ8ADas78qPZRMeGF09MXY8ph7qoZT=1Y@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=d_G9A0Mf2zMzG-9zmec06vYNaB1pLrkDQnyvE@mail.gmail.com>

2010/11/3 Khem Raj <raj.khem@gmail.com>:

>
> yes a more detailed solution is better. you have to go through the
> configure of every
> package and understand the behavior then act upon. As I said before
> its a tedious task
>
I'm well aware of this. That is also why in the infrastructure thread
I suggested using automated testing to find misbehaving packages.

Btw there are 355 .inc files that contain the word autotools and 1899 .bb files.
Of course there are lots of dups in there.
And maybe for the base recipes we can convince the yocto people that
this is a serious QA issue (and they have some people employed to work
on this if I understood properly).

Frans



  reply	other threads:[~2010-11-03 19:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02  1:09 [PATCH] gphoto2_2.4.8.bb: Stop configure from looking in /usr/local/include Graham Gower
2010-11-02  6:38 ` Frans Meulenbroeks
2010-11-02 22:00   ` Khem Raj
2010-11-03  9:42     ` Frans Meulenbroeks
2010-11-03 15:17       ` Khem Raj
2010-11-03 15:44         ` Andrea Adami
2010-11-03 15:47         ` Martin Jansa
2010-11-03 16:07           ` Khem Raj
2010-11-03 19:04             ` Frans Meulenbroeks [this message]
2010-11-03 20:06               ` Khem Raj
2010-11-03 20:21                 ` Frans Meulenbroeks
2010-11-03 20:46                   ` Khem Raj
2010-11-05  7:51                     ` Frans Meulenbroeks
2010-11-05 15:39                       ` Khem Raj
2010-11-05 17:21                         ` Frans Meulenbroeks
2010-11-03  0:04   ` Graham Gower
2010-11-03  7:57     ` Koen Kooi

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='AANLkTikcC1DKQ8ADas78qPZRMeGF09MXY8ph7qoZT=1Y@mail.gmail.com' \
    --to=fransmeulenbroeks@gmail.com \
    --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 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.