All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: staging ABI changes and broken idium
Date: Wed, 12 Mar 2008 09:24:39 +0100	[thread overview]
Message-ID: <200803120924.42667.zecke@selfish.org> (raw)
In-Reply-To: <fr828g$l2n$1@ger.gmane.org>

On Wednesday 12 March 2008 08:54:56 Koen Kooi wrote:
> Holger Freyther schreef:

Makefile's:
	with sed s,/usr/include,/stuff/tmp/staging/arm-linux/usr/include,

	the include path:
	-I/stuff/tmp/staging/arm-linux/usr/include  gets transformed to
	-I/stuff/tmp/staging/arm-linux/stuff/tmp/staging/arm-linux/usr/include

	The effect is: The first path is right the 2nd is wrong and no headers
	are found. We still need to remove -I/usr/include and -L/usr/lib from the
	compiler line.

	So either we change the sed -i s... to not change the path if it is already 
	${STAGING_INCDIR}, I would need some sed help here and move this sed
	string to base.bbclass (also for STAGING_LIBDIR), or go 
	for  -I/usr/include,-I${STAGING_INCDIR}

binconfig:
	yes the binconfig.bbclass should point to the absolute staging inc and libdir
	and there such a sed could make sense.


I see we patch: configure.in/configure, Makefile and once or twice some other 
files. let me follow up with fishy files.



      parent reply	other threads:[~2008-03-12  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  7:27 staging ABI changes and broken idium Holger Freyther
2008-03-12  7:54 ` Koen Kooi
2008-03-12  7:59   ` Koen Kooi
2008-03-12  8:18     ` Holger Freyther
2008-03-12  9:17       ` Richard Purdie
2008-03-12  9:42         ` Holger Freyther
2008-03-12  8:37     ` Holger Freyther
2008-03-12  8:24   ` Holger Freyther [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=200803120924.42667.zecke@selfish.org \
    --to=zecke@selfish.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.