From: "Michael Ellerman" <michael@ellerman.id.au>
To: "Nathan DeBardeleben" <ndebard@lanl.gov>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
"Michael K. Dolan Jr." <email@michaeldolan.com>,
systemtap@sourceware.org
Subject: Re: elfutils on Debian?
Date: Thu, 16 Mar 2006 02:52:00 -0000 [thread overview]
Message-ID: <dc1166600603151852m8f501c2sa00e0e4496c07e5a@mail.gmail.com> (raw)
In-Reply-To: <441834FD.80903@lanl.gov>
On 3/16/06, Nathan DeBardeleben <ndebard@lanl.gov> wrote:
> Frank Ch. Eigler wrote:
> >> [...] Someone on the list sent me a patch file, couple days back.
> >> [...] Ronald McGrath replied with a patch that sadly didn't apply
> >> cleanly - I tried building afterwards anyway and it didn't work. [...]
> >>
> >
> > That patch is for elfutils configury, not systemtap. Try applying
> > it to the patched-elfutils source directory, on top of the
> > "compatibility" patch.
> >
> Oh, I did.
> Here's a log:
> > debian:~/elfutils-0.119> patch -p1 < elfutils-systemtap.patch
> > patching file Makefile.am
> > Hunk #1 succeeded at 2 with fuzz 2 (offset 1 line).
> > Hunk #2 FAILED at 29.
> > 1 out of 2 hunks FAILED -- saving rejects to file Makefile.am.rej
> > patching file Makefile.am
> > patch: **** malformed patch at line 26:
> > \$$ORIGIN/../libasm:\$$ORIGIN/../libdw:\$$ORIGIN/../backends:\$$ORIGIN/../libelf
> This was after previously patching with the portability patch, which
> went in smooth as butter.
> Here's the reject file:
> > ***************
> > *** 29,34 ****
> > -I$(srcdir)/../libdw -I$(srcdir)/../libdwfl \
> > -I$(srcdir)/../lib -I..
> >
> > YACC = @YACC@ -d
> > AM_YFLAGS = -pld
> > AM_LFLAGS = -Pld -olex.yy.c
> > --- 29,36 ----
> > -I$(srcdir)/../libdw -I$(srcdir)/../libdwfl \
> > -I$(srcdir)/../lib -I..
> >
> > + AM_LDFLAGS = -Wl,-rpath-link,../libelf:../libdw
> > +
> > YACC = @YACC@ -d
> > AM_YFLAGS = -pld
> > AM_LFLAGS = -Pld -olex.yy.c
>
> Maybe I'm applying it wrong. Tips?
Yeah, it's -p0 format :D
prev parent reply other threads:[~2006-03-16 2:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 5:50 Michael Ellerman
2006-03-15 6:28 ` Ananth N Mavinakayanahalli
2006-03-15 14:00 ` Frank Ch. Eigler
2006-03-15 14:05 ` Michael K. Dolan Jr.
2006-03-15 14:15 ` Michael Ellerman
2006-03-15 14:35 ` Frank Ch. Eigler
2006-03-15 19:33 ` Roland McGrath
2006-03-16 2:53 ` Michael Ellerman
2006-03-16 3:00 ` Frank Ch. Eigler
2006-03-16 3:06 ` Michael Ellerman
2006-03-16 3:14 ` Frank Ch. Eigler
2006-03-16 16:02 ` William Cohen
[not found] ` <44181EE3.3030908@michaeldolan.com>
2006-03-15 14:19 ` Michael Ellerman
2006-03-15 14:35 ` Nathan DeBardeleben
2006-03-15 14:50 ` Frank Ch. Eigler
2006-03-15 15:38 ` Nathan DeBardeleben
2006-03-16 2:52 ` Michael Ellerman [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=dc1166600603151852m8f501c2sa00e0e4496c07e5a@mail.gmail.com \
--to=michael@ellerman.id.au \
--cc=email@michaeldolan.com \
--cc=fche@redhat.com \
--cc=ndebard@lanl.gov \
--cc=systemtap@sourceware.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).