From: "MIYOSHI,DENNIS (HP-Loveland,ex1)" <dennis.miyoshi@hp.com>
To: "'Sam Ravnborg'" <sam@ravnborg.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Build fails for ia64 with linux-2.6.0-test1-bk2 with missing file .
Date: Tue, 22 Jul 2003 07:41:16 -0700 [thread overview]
Message-ID: <F341E03C8ED6D311805E00902761278C0D2A2BE3@xfc04.fc.hp.com> (raw)
Thanks Sam. Shouldn't the Makefile take care of this?
Dennis E. Miyoshi, PE
Hendrix Release Manager
Hewlett-Packard Company
825 14th Street, S.W., MS E-200
Loveland, CO 80537
(970) 898-6110
-----Original Message-----
From: Sam Ravnborg [mailto:sam@ravnborg.org]
Sent: Tuesday, July 22, 2003 8:36 AM
To: MIYOSHI,DENNIS (HP-Loveland,ex1)
Cc: 'linux-kernel@vger.kernel.org'
Subject: Re: Build fails for ia64 with linux-2.6.0-test1-bk2 with missing
file .
> Failed with the following:
> kernel/profile.c:11:26: asm/sections.h: No such file or directory
> kernel/profile.c: In function `profile_init':
> kernel/profile.c:38: `_etext' undeclared (first use in this function)
> kernel/profile.c:38: (Each undeclared identifier is reported only once
> kernel/profile.c:38: for each function it appears in.)
> kernel/profile.c:38: `_stext' undeclared (first use in this function)
> make[1]: *** [kernel/profile.o] Error 1
> make: *** [kernel] Error 2
cp include/asm-i386/sections.h include/asm-ia64/sections.h should do the
trick.
Sam
next reply other threads:[~2003-07-22 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 14:41 MIYOSHI,DENNIS (HP-Loveland,ex1) [this message]
2003-07-22 19:35 ` Build fails for ia64 with linux-2.6.0-test1-bk2 with missing file Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 19:40 MIYOSHI,DENNIS (HP-Loveland,ex1)
2003-07-22 20:13 ` David Mosberger
2003-07-22 14:11 MIYOSHI,DENNIS (HP-Loveland,ex1)
2003-07-22 14:36 ` Sam Ravnborg
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=F341E03C8ED6D311805E00902761278C0D2A2BE3@xfc04.fc.hp.com \
--to=dennis.miyoshi@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 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).