Bug 155949 - oprofile fails to build on ia64
oprofile fails to build on ia64
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: binutils (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Denys Vlasenko
Depends On:
  Show dependency treegraph
Reported: 2005-04-25 19:37 EDT by Martin K. Petersen
Modified: 2009-01-02 07:23 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-02 07:23:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
opd_kernel.i (105.42 KB, text/plain)
2005-04-26 11:51 EDT, Martin K. Petersen
no flags Details
opd_kernel.s (74.82 KB, text/plain)
2005-04-26 11:51 EDT, Martin K. Petersen
no flags Details

  None (edit)
Description Martin K. Petersen 2005-04-25 19:37:32 EDT
Description of problem:

While compiling upstream oprofile I ran into the following error.
I tried rebuilding oprofile-0.8.1-11.src.rpm provided by RH and got the same result.

Steps to Reproduce:
1. Pristine RHEL4 ia64 machine.
2. rpmbuild --rebuild oprofile-0.8.1-11.src.rpm

Actual results:
make[3]: Entering directory `/home/buildsys/BUILD/oprofile-0.8.1/daemon/liblegacy'
if gcc4 -DHAVE_CONFIG_H -I. -I../../././daemon/liblegacy -I../..  -I
../../././libutil -I ../../././libop -I ../../././libdb -I ../../././daemon  -W
-Wall -fno-common -Wdeclaration-after-statement -fno-omit-frame-pointer -g -O2
-MT opd_24_stats.o -MD -MP -MF ".deps/opd_24_stats.Tpo" -c -o opd_24_stats.o
opd_24_stats.c; \
then mv -f ".deps/opd_24_stats.Tpo" ".deps/opd_24_stats.Po"; else rm -f
".deps/opd_24_stats.Tpo"; exit 1; fi
if gcc4 -DHAVE_CONFIG_H -I. -I../../././daemon/liblegacy -I../..  -I
../../././libutil -I ../../././libop -I ../../././libdb -I ../../././daemon  -W
-Wall -fno-common -Wdeclaration-after-statement -fno-omit-frame-pointer -g -O2
-MT opd_kernel.o -MD -MP -MF ".deps/opd_kernel.Tpo" -c -o opd_kernel.o
opd_kernel.c; \
then mv -f ".deps/opd_kernel.Tpo" ".deps/opd_kernel.Po"; else rm -f
".deps/opd_kernel.Tpo"; exit 1; fi
/tmp/cc064O9o.s: Assembler messages:
/tmp/cc064O9o.s:2171: Error: Epilogue count of 4294967296 exceeds number of
nested prologues (0)
/tmp/cc064O9o.s:2701: Error: Epilogue count of 4294967296 exceeds number of
nested prologues (0)
make[3]: *** [opd_kernel.o] Error 1

The same code compiles fine with Debian sarge's toolchain.
Comment 1 Jakub Jelinek 2005-04-26 06:53:43 EDT
Please provide preprocessed opd_kernel.i (add -save-temps to your
command gcc command line).  Only with preprocessed source we can be sure we
are looking at the same thing.
Can you reproduce it also with gcc instead of gcc4?
Comment 2 Martin K. Petersen 2005-04-26 11:51:05 EDT
Created attachment 113672 [details]
Comment 3 Martin K. Petersen 2005-04-26 11:51:29 EDT
Created attachment 113673 [details]
Comment 4 Martin K. Petersen 2005-04-26 11:52:30 EDT
Yes.  I've tried both gcc and gcc4. Same thing.
Comment 5 Denys Vlasenko 2008-12-18 13:45:45 EST
Seems to work on this hardware / release combination:

[root@hp-sapphire-01 tmp]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 7)

[root@hp-sapphire-01 tmp]# uname -a
Linux hp-sapphire-01.rhts.bos.redhat.com 2.6.9-78.19.EL #1 SMP Fri Nov 21 16:30:22 EST 2008 ia64 ia64 ia64 GNU/Linux

[root@hp-sapphire-01 tmp]# rpm -q binutils

[root@hp-sapphire-01 tmp]# rpm -q gcc4

[root@hp-sapphire-01 tmp]# cat opd.sh
gcc4 -DHAVE_CONFIG_H -W -Wall \
-fno-common -Wdeclaration-after-statement -fno-omit-frame-pointer -g -O2 \
-MT opd_kernel.o -MD -MP -MF "opd_kernel.Tpo" -c -o opd_kernel.o \

[root@hp-sapphire-01 tmp]# sh opd.sh

[root@hp-sapphire-01 tmp]# ls -l
-rw-r--r--  1 root root 107947 Dec 18 13:38 opd_kernel.c
-rw-r--r--  1 root root  32896 Dec 18 13:43 opd_kernel.o

(opd_kernel.c is a file from comment #2)
Comment 6 Denys Vlasenko 2009-01-02 07:22:50 EST
I'm closing it as "works for me". It indeed works for me, and last comment was from three years ago.

Reopen if this is still a problem.

Note You need to log in before you can comment on or make changes to this bug.