From: Grant Edwards <grant.b.edwards@gmail.com>
To: crossgcc@sources.redhat.com
Subject: Updating from 1.12 to 1.16: semantics of "linux custom path" changed?
Date: Tue, 14 Aug 2012 22:04:00 -0000 [thread overview]
Message-ID: <k0ei01$fiu$1@dough.gmane.org> (raw)
Have the semantics of the linux custom kernel path changed between
1.12 and 1.16? The path I used to use no longer works.
CT_KERNEL_LINUX_CUSTOM_TARBALL used to be relative to the top-level
crosstool-ng-<ver> directory.
Now the variable is CT_KERNEL_LINUX_CUSTOM_LOCATION and I can't figure
out where it's relative to. If I put in a path relative to the
top-level build directory, it fails late in the build process because
it expects the path to be relative to targets/tarballs. If I use a
path relative to that directory, then it fails earlier in the process.
What directory is CT_KERNEL_LINUX_CUSTOM_LOCATION relative to?
--
Grant Edwards grant.b.edwards Yow! I wonder if there's
at anything GOOD on tonight?
gmail.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-08-14 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 22:04 Grant Edwards [this message]
2012-08-14 22:23 ` Grant Edwards
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='k0ei01$fiu$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=crossgcc@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).