pcp
[Top] [All Lists]

Re: RHEL6 build failure

To: Max Matveev <makc@xxxxxxxxx>
Subject: Re: RHEL6 build failure
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 24 May 2011 10:40:56 +1000 (EST)
Cc: pcp <pcp@xxxxxxxxxxx>
In-reply-to: <19930.1226.288864.258008@xxxxxxxxxxxx>
Hi Max,

----- Original Message -----
> On Sat, 21 May 2011 17:02:23 +1000 (EST), Nathan Scott wrote:
> 
> nathans> Guess you're getting pretty sick of these by now :) but
> here's an
> nathans> exciting new build failure in rpm/perl packaging land - this
> time
> nathans> on a fresh RHEL6 install...
> 
> How do you enable debuginfo builds?
> 

Didn't think I did anything special (this was just from ./Makepkgs),
but having said that, at one point I did run debuginfo-install to try
to get a debuginfo kernel rpm installed ... (failed as I wasn't on the
network at the time).  Not sure if thats done something that is able
to affect PCP builds... other than that, this was a stock RHEL6.
> 
> nathans> Any ideas?
> Yes - make the path to the top of the tree longer,
> e.g. /source/git/pcp-3.5.1 will be fine.
> 
> The reason for the build failure is the bogus check in debugedit -
> it's trying to re-write absolute paths in the debug info section of
> ELF files and assumes that it does not have enough room to fit new
> prefix.
> 
> This only affects Perl files so far because it's the only place we're
> using full paths in the include search path. We can change them to be
> relative - I don't see a reason for using pwd in setting PCP_TOPDIR
> but maybe you can remember what was the problem with a8bf0879.

Nope, couple years back now - but "Resolve path issues when building
Perl RPM packages." suggests that if you we make rpm build work without
having that, should be fine.

cheers.

-- 
Nathan

<Prev in Thread] Current Thread [Next in Thread>