Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jay Snyder <jay.snyder@tycoelectronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Openembedded-devel Digest, Vol 43, Issue 98
Date: Tue, 23 Feb 2010 08:47:52 -0500	[thread overview]
Message-ID: <4B83DC88.7070705@tycoelectronics.com> (raw)
In-Reply-To: <mailman.3988.1266916925.14961.openembedded-devel@lists.openembedded.org>

>
>
> 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



       reply	other threads:[~2010-02-23 13:54 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 ` Jay Snyder [this message]
2010-02-23 14:58   ` reply to digest mails, was: Re: Openembedded-devel Digest, Vol 43, Issue 98 Koen Kooi
2010-02-23 22:37     ` Philip Balister
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=4B83DC88.7070705@tycoelectronics.com \
    --to=jay.snyder@tycoelectronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox