From: Kris Van Hees <kris.van.hees@oracle.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
Mark Wielaard <mark@klomp.org>,
frysk@sourceware.org
Subject: Re: frysk-imports/tests ChangeLog Makefile.am frys ...
Date: Fri, 29 Jun 2007 11:49:00 -0000 [thread overview]
Message-ID: <20070629035911.GA6090@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20070628155928.GA8897@host0.dyn.jankratochvil.net>
I very much agree. It certainly indicates that something is wrong with
the frysk compilation setup in terms of dealing with elfutils.
In retrospect, perhaps it would be better for me to remove those rpms
from the build systems, and have it continue to fail as long as this
problem remains in the tree. But at least for the automated builds, I
feel it is more important (at this point) to be able to work around
the problem and get successful builds that can be tested.
Cheers,
Kris
On Thu, Jun 28, 2007 at 05:59:28PM +0200, Jan Kratochvil wrote:
> On Thu, 28 Jun 2007 17:47:33 +0200, Kris Van Hees wrote:
> > 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)
>
> It looks very fragile to me if the project is able to touch system elfutils
> while the same package with different version is bundled. I would fear that
> nonmatching versions of these two elfutils can be a source of many surprises.
prev parent reply other threads:[~2007-06-29 3:59 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
2007-06-28 17:42 ` Jan Kratochvil
2007-06-29 11:49 ` Kris Van Hees [this message]
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=20070629035911.GA6090@ca-server1.us.oracle.com \
--to=kris.van.hees@oracle.com \
--cc=frysk@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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).