From: "Ashwin Bihari" <raz0redge@hotmail.com>
To: Aron.J.Silverton@motorola.com, beena@gdatech.com, dank@kegel.com
Cc: listmember@orkun.us, linuxppc-embedded@lists.linuxppc.org
Subject: RE: Cross-compile package combinations
Date: Tue, 16 Dec 2003 14:34:35 -0500 [thread overview]
Message-ID: <BAY9-F64wEC1pxHVmu200077e21@hotmail.com> (raw)
>I was referring to the kernel headers used to build the tools as opposed to
>the building of the actual kernel. I'll have to look through the crosstool
>scripts, but I'd guess that if the file already exists, it won't download
>it. I'll probably bump up the version on my kernel to match what crosstool
>wants to see and then put it in the location that I specified in my
>crosstool configuration.
>
>Thanks,
>
>Aron
Aron,
Ahh my bad! :) There is a kernel header define that you can set. On the
version of crosstool I used, they were on top of that file. I just manually
pointed it to the kernel source/headers I had and it was happy.
~Ashwin
_________________________________________________________________
Get holiday tips for festive fun.
http://special.msn.com/network/happyholidays.armx
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-12-16 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 19:34 Ashwin Bihari [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 19:14 Cross-compile package combinations Silverton Aron-C1710C
2003-12-16 19:07 Ashwin Bihari
2003-12-16 18:53 Silverton Aron-C1710C
2003-12-16 20:14 ` Wolfgang Denk
2003-12-11 21:57 Silverton Aron-C1710C
2003-12-11 23:15 ` Beena
2003-12-12 4:26 ` Dan Kegel
2003-12-16 18:21 ` Beena
2003-12-11 16:29 Ashwin Bihari
2003-12-11 14:29 Silverton Aron-C1710C
2003-12-11 0:28 Ashwin Bihari
2003-12-10 23:50 Silverton Aron-C1710C
2003-12-11 6:18 ` Dan Kegel
2003-12-11 16:06 ` listmember
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=BAY9-F64wEC1pxHVmu200077e21@hotmail.com \
--to=raz0redge@hotmail.com \
--cc=Aron.J.Silverton@motorola.com \
--cc=beena@gdatech.com \
--cc=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=listmember@orkun.us \
/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 NNTP newsgroup(s).