public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: updated libunwind patch for v2.6 kernel
Date: Wed, 15 Jun 2005 17:35:44 +0000	[thread overview]
Message-ID: <17072.26352.66968.954556@napali.hpl.hp.com> (raw)
In-Reply-To: <200506100531.j5A5VYSB001927@napali.hpl.hp.com>

Bob,

>>>>> On Wed, 15 Jun 2005 12:55:50 -0400, Bob Picco <bob.picco@hp.com> said:

  Bob> ia64-linux-gcc -Wp,-MD,arch/ia64/unwind/.init_local.o.d  -nostdinc -isystem /usr/local/lib/gcc-lib/ia64-linux/3.3/include -D__KERNEL__ -Iinclude  -DHAVE_BUGGY_SEGREL -DHAVE_ATOMIC_H  -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -O2     -fomit-frame-pointer -g -pipe  -ffixed-r13 -mfixed-rangeñ2-f15,f32-f127 -falign-functions2 -frename-registers -fno-optimize-sibling-calls     -mconstant-gp -DKBUILD_BASENAME=init_local -DKBUILD_MODNAME=init_local -c -o arch/ia64/unwind/init_local.o arch/ia64/unwind/init_local.c
  Bob> In file included from arch/ia64/unwind/init.h:26,
  Bob> from arch/ia64/unwind/init_local.c:26:
  Bob> arch/ia64/unwind/unwind_i.h:33:25: libunwind_i.h: No such file or directory

Looks like the compiler command is missing the -Iinclude/linux, which
should get added via CPPFLAGS in arch/ia64/unwind/Makefile:

CPPFLAGS        += -DHAVE_ATOMIC_H $(call addtree,-Iinclude/linux)

are you building in the source tree itself?  If so, can you try
building with make O=objdir and see if that fixes the problem.  I'm
unsure if addtree is safe to be called from the Makefile, but I didn't
want to worry about relatively minor build questions at this time.

Thanks,

	--david

  parent reply	other threads:[~2005-06-15 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  5:31 updated libunwind patch for v2.6 kernel David Mosberger
2005-06-15 16:55 ` Bob Picco
2005-06-15 17:35 ` David Mosberger [this message]
2005-06-15 17:55 ` Bob Picco

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=17072.26352.66968.954556@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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