public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
* Updating from 1.12 to 1.16: semantics of "linux custom path" changed?
@ 2012-08-14 22:04 Grant Edwards
  2012-08-14 22:23 ` Grant Edwards
  0 siblings, 1 reply; 2+ messages in thread
From: Grant Edwards @ 2012-08-14 22:04 UTC (permalink / raw)
  To: crossgcc

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Updating from 1.12 to 1.16: semantics of "linux custom path" changed?
  2012-08-14 22:04 Updating from 1.12 to 1.16: semantics of "linux custom path" changed? Grant Edwards
@ 2012-08-14 22:23 ` Grant Edwards
  0 siblings, 0 replies; 2+ messages in thread
From: Grant Edwards @ 2012-08-14 22:23 UTC (permalink / raw)
  To: crossgcc

On 2012-08-14, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> 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.

Doh!  Never mind.

It looks like using a path relative to
crosstool-ng-<ver>/targets/tarballs is right -- one of the failures I
was seeing was due to a corrupted kernel tarball file.

-- 
Grant Edwards               grant.b.edwards        Yow! ... I'm IMAGINING a
                                  at               sensuous GIRAFFE, CAVORTING
                              gmail.com            in the BACK ROOM of a
                                                   KOSHER DELI --


--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-08-14 22:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-14 22:04 Updating from 1.12 to 1.16: semantics of "linux custom path" changed? Grant Edwards
2012-08-14 22:23 ` Grant Edwards

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