From: Kris Van Hees <kris.van.hees@oracle.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org, jkratoch@sourceware.org
Subject: Re: frysk-imports/tests ChangeLog Makefile.am frys ...
Date: Thu, 28 Jun 2007 15:59:00 -0000 [thread overview]
Message-ID: <20070628154732.GI21651@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1183026199.3601.18.camel@dijkstra.wildebeest.org>
The automated builds were being plagued by this as wel (except for the
FC6 x86_64 box that for some reason actually had elfutils-libelf-devel
installed). I installed that rpm (and dependencies) on the other two
boxes, and things seem to be much happier now. New runs are in progress
right now, so their results ought to be on the website of the automated
build-and-test system shortly...
Cheers,
Kris
On Thu, Jun 28, 2007 at 12:23:09PM +0200, Mark Wielaard wrote:
> Hi jan,
>
> On Wed, 2007-06-27 at 08:52 +0000, jkratoch@sourceware.org wrote:
> > * frysk4704/vdso-permissions.c: New file.
> > * Makefile.am (systests_PASS_PROGRAM): Added frysk4704/vdso-permissions.
>
> This requires the system gelf.h, which means the user needs to have
> elfutils-libelf-devel installed (on Fedora at least), which is currently
> not documentated to be a requirement on our build page
> http://sourceware.org/frysk/build/ (which was why I didn't have it
> installed on one of my machines here). Does it have to or can it be made
> to work with the included elfutil/libelf in frysk-imports?
>
> Cheers,
>
> Mark
>
next prev parent reply other threads:[~2007-06-28 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070627085227.10528.qmail@sourceware.org>
2007-06-28 10:29 ` Mark Wielaard
2007-06-28 15:47 ` Roland McGrath
2007-06-28 19:37 ` Andrew Cagney
2007-06-29 3:59 ` Roland McGrath
2007-06-28 15:59 ` Kris Van Hees [this message]
2007-06-28 17:42 ` Jan Kratochvil
2007-06-29 11:49 ` Kris Van Hees
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=20070628154732.GI21651@ca-server1.us.oracle.com \
--to=kris.van.hees@oracle.com \
--cc=frysk@sourceware.org \
--cc=jkratoch@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).