From: Jack Steiner <steiner@sgi.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 31 (GRU build error)
Date: Fri, 1 Aug 2008 08:16:36 -0500 [thread overview]
Message-ID: <20080801131636.GA4023@sgi.com> (raw)
In-Reply-To: <20080731223758.b5985dd7.randy.dunlap@oracle.com>
On Thu, Jul 31, 2008 at 10:37:58PM -0700, Randy Dunlap wrote:
>
> xp_uv.c:(.text+0x4186b): undefined reference to `gru_copy_gpa'
> xpc_uv.c:(.text+0x44616): undefined reference to `gru_create_message_queue'
> xpc_uv.c:(.text+0x44e16): undefined reference to `gru_free_message'
> xpc_uv.c:(.text+0x44e22): undefined reference to `gru_get_next_message'
> xpc_uv.c:(.text+0x44e67): undefined reference to `gru_send_message_gpa'
> xpc_uv.c:(.text+0x45a79): undefined reference to `gru_free_message'
> xpc_uv.c:(.text+0x45a85): undefined reference to `gru_get_next_message'
> make[1]: *** [.tmp_vmlinux1] Error 1
This is not actually a GRU problem. XP is missing a dependency. Dean will
post a patch later today.
>
>
> config attached.
>
>
> and please add a GRU maintainer entry somewhere.
Done. Also added maintainer for XP...
--- jack
next prev parent reply other threads:[~2008-08-01 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 7:58 linux-next: Tree for July 31 Stephen Rothwell
2008-08-01 5:34 ` linux-next: Tree for July 31 (IMA build error) Randy Dunlap
2008-08-01 5:37 ` linux-next: Tree for July 31 (GRU " Randy Dunlap
2008-08-01 13:16 ` Jack Steiner [this message]
2008-08-01 14:55 ` [PATCH] add reverse dependency of CONFIG_SGI_XP upon CONFIG_SGI_GRU Dean Nelson
2008-08-01 17:50 ` Randy Dunlap
2008-08-01 19:19 ` [PATCH] add dependency of CONFIG_SGI_XP upon CONFIG_NET Dean Nelson
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=20080801131636.GA4023@sgi.com \
--to=steiner@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.