Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] sysroot support in toolchain, use correct pathes in staging_dir
Date: Tue, 10 Apr 2007 14:23:57 +0300	[thread overview]
Message-ID: <461B73CD.7040009@cs.helsinki.fi> (raw)
In-Reply-To: <20070410103901.GC15274@aon.at>

Bernhard Fischer kirjoitti:
> Hi,
> 
> This is a heads-up that i mean to correct the pathes to includes and
> libs in the staging dir as suggested in bug 
> http://busybox.net/bugs/view.php?id=1290
> Doing so is ment to ease moving the staging-dir (and it's
> cross-compiler) to a different machine for re-use.

What was the original purpose of putting all headers under /include anyway?

-- Heikki Lindholm

  reply	other threads:[~2007-04-10 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 10:39 [Buildroot] [patch] sysroot support in toolchain, use correct pathes in staging_dir Bernhard Fischer
2007-04-10 11:23 ` Heikki Lindholm [this message]
2007-04-10 12:08   ` Bernhard Fischer
2007-05-15 11:43 ` Bernhard Fischer
2007-06-20 11:36   ` Bernhard Fischer

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=461B73CD.7040009@cs.helsinki.fi \
    --to=holindho@cs.helsinki.fi \
    --cc=buildroot@busybox.net \
    /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