All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: reply to digest mails, was: Re: Openembedded-devel Digest, Vol 43, Issue 98
Date: Tue, 23 Feb 2010 14:37:18 -0800	[thread overview]
Message-ID: <4B84589E.1060209@balister.org> (raw)
In-Reply-To: <hm0qff$9v8$1@dough.gmane.org>

On 02/23/2010 06:58 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> When you receive a digest mail it tells you to change the subject line
> to something non-bogus. Please do so in the future.
>
> If it turns out tha that is too hard for people we can consider turning
> off digests.

I tend to delete emails with the subject only containing digest info. 
I'm sure there are a few people who need the digests and no sense making 
life harder for them because of the actions of a few people.

Philip


>
>
> On 23-02-10 14:47, Jay Snyder wrote:
>>>
>>>
>>> try the following:
>>> TARGET_CC_ARCH += "${LDFLAGS}"
>>> This should resolve your problems if you build your executable from
>>> within your OE buildsystem.
>>> In very rare cases (e.g. when you build some programs outside of OE
>>> but use OE to package all) it could be useful to use the following:
>>> INSANE_SKIP_objc = "True"
>>> AFAIK that sould not be commonly used, but it worked for me.
>>>
>>> majo
>>>
>>
>> Updating my GCC recipe with a "git pull" worked (the INSANE_SKIP_obj
>> line got added sometime recently).
>>
>> The TARGET_CC_ARCH += "${LDFLAGS}"  fix is the first thing that I try
>> when i get this problem, and usually fixes it, although there are some
>> packages that required patching Makefile.ac files throughout the
>> project.     As I just stated in another reply, when I get beyond the
>> current project time crunch (coming up on a release deadline), I will
>> submit my recipe patches for inclusion in the OE git repository.
>>
>> Thanks,
>> Jay
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFLg+0vMkyGM64RGpERAoELAKCTgm09I1gjcpAGVfd4CcTpD6WE7wCfdJ/k
> spNEAoXQJqueAMXjoPCgqS8=
> =Kt9W
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



  reply	other threads:[~2010-02-23 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3988.1266916925.14961.openembedded-devel@lists.openembedded.org>
2010-02-23 13:47 ` Openembedded-devel Digest, Vol 43, Issue 98 Jay Snyder
2010-02-23 14:58   ` reply to digest mails, was: " Koen Kooi
2010-02-23 22:37     ` Philip Balister [this message]
2010-02-24  6:21       ` Petr Štetiar
2010-02-23 18:15   ` Khem Raj
2010-02-23 18:19     ` Chris Larson
2010-02-23 18:39       ` Khem Raj
2010-02-23 18:59         ` Chris Larson

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=4B84589E.1060209@balister.org \
    --to=philip@balister.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 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.