Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] make "LDFLAGS ignored" QA errors fatal
Date: Tue, 07 Apr 2009 09:01:16 +0200	[thread overview]
Message-ID: <gretns$4ts$1@ger.gmane.org> (raw)
In-Reply-To: <19c1b8a90904061449s1cc1c4e6pb1c04f2c71cc6beb@mail.gmail.com>

On 06-04-09 23:49, Khem Raj wrote:
> On 4/6/09, Jeremy Lainé<jeremy.laine@bolloretelecom.eu>  wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I have spent quite some time cleaning up a bunch of recipes which were
>> triggering "LDFLAGS ignored" QA errors, and I don't really want to
>> have to do this again in the future. I suggest we stop whitelisting
>> this kind of QA error, using the attached patch.
>>
>> To track down the faulty packages I have made use of oestats output
>> (note that not all QA errors are "LDFLAGS ignored"):
>>
>> http://tinderbox.openembedded.net/packages/?qalog=1
>>
>> In most cases, the problem is that recipes simply pass
>> - -L${STAGING_LIBDIR} as LDFLAGS instead of using the full ${LDFLAGS}
>> variable. The result is that flags such as --hash-style=gnu are
>> getting ignored.
>
> I think we should configure toolchain to pass this flags by gcc driver
> while linking instead of making it a part of LDFLAGS it should help in
> recipes which use gcc to link.

While that would improve the situation a bit, it would also mean that 
we'll have a harder time detecting which recipes ignore LDFLAGS.

regards,

Koen




  reply	other threads:[~2009-04-07  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 16:34 [RFC] make "LDFLAGS ignored" QA errors fatal Jeremy Lainé
2009-04-06 17:58 ` Koen Kooi
2009-04-06 21:49 ` Khem Raj
2009-04-07  7:01   ` Koen Kooi [this message]
2009-04-07  9:23   ` Phil Blundell
2009-04-07 15:41     ` Andrea Adami
2009-04-07 15:50       ` Phil Blundell
2009-04-08  8:50       ` Jeremy Lainé
2009-04-08  9:26         ` Andrea Adami
2009-04-14 19:16     ` Khem Raj

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='gretns$4ts$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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