Ticket #126 (new defect)

Opened 2 months ago

Last modified 2 months ago

Build Failed on RHEL5 (32bit)

Reported by: ambvi01 Assigned to: admin
Priority: blocker Milestone: asap
Component: compile Version: main
Keywords: RHEL5, 32bit, Compile Cc:

Description

I followed the readme, and just ran ./runbuild.sh 

...failed updating 374 target(s)...
...skipped 97 target(s)...
...updated 9189 target(s)...
./runbuild.sh: line 70: buildrel: command not found
Mon Apr 28 12:28:13 EDT 2008

I have attached the complete build log to this ticket.

Running on RedHat? Enterprise Linux 5 Server 32bit

Is there a way of building Ingres without the GTK deps?

Attachments

jam_04_28_08_1206.log (1.4 MB) - added by ambvi01 on 04/28/08 17:20:12.
Complete build log
runbuild_04_28_08_1206.log (1.3 kB) - added by ambvi01 on 04/28/08 17:32:31.
runbuild.sh output log
jam_04_29_08_0806.log (1.4 MB) - added by omega187@gmail.com on 04/29/08 05:11:09.
error output for ubuntu 8.04 64bit

Change History

04/28/08 17:20:12 changed by ambvi01

  • attachment jam_04_28_08_1206.log added.

Complete build log

04/28/08 17:32:31 changed by ambvi01

  • attachment runbuild_04_28_08_1206.log added.

runbuild.sh output log

04/28/08 18:06:53 changed by omega187@gmail.com

same bug in ubuntu 8.04 Hardy Heron 64bit

04/28/08 18:35:12 changed by maspa05

Looking at the jam log the first failure is here 

IIUCHARMAP /home/build/main/build/files/ucharmaps/ca-big5-cht-2004 
unimapcompile: error while loading shared libraries: /home/build/main/build/lib/libcompat.1.so: cannot restore segment prot after reloc: Permission denied

Googling that "cannot restore segment prot after reloc" error it appears to be related to SELinux. I know in the past I've had problems installing with SELinux enabled, though I know someone who worked out which security attributes on which files needed to be changed to allow it.

That's installing, building with SELinux would be trickier because you'll need to modify some files after they're created but before they're used later in the build, unimapcompile being the first example. Effectively you'd need to re-write some of the jam rules - which is doable but non-trivial.

It would probably be much simpler to disable SELinux. You can do this by editting /etc/sysconfig/selinux and making sure it has the line 

S

04/28/08 18:52:39 changed by maspa05

oops - what happened there?

The line should be 

SELINUX=disabled

and then reboot.

HTH Paul

04/29/08 05:11:09 changed by omega187@gmail.com

  • attachment jam_04_29_08_0806.log added.

error output for ubuntu 8.04 64bit

04/29/08 06:50:41 changed by anonymous

Omega,

That's a different error. From your log - 

Cc /home/omega/ingres/testing/src/tools/port/eval_unix_vms/lp32/salign.o 
In file included from /usr/include/features.h:354,
                 from /usr/include/stdlib.h:25,
                 from /home/omega/ingres/testing/src/tools/port/eval_unix_vms/salign.c:5:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory

	cc -c -Dint_lnx -DADD_ON32 -m32 -fsigned-char -fno-strength-reduce -D_REENTRANT -DLINUX -D_GNU_SOURCE 
	-DXLIB_ILLEGAL_ACCESS  -I/home/omega/ingres/testing/src/tools/port/eval_unix_vms 
	-I/home/omega/ingres/testing/src/tools/port/hdr_unix_vms -I/home/omega/ingres/testing/src/cl/hdr/hdr_unix 
	-I/home/omega/ingres/testing/src/cl/hdr/hdr_unix_win 
	-I/home/omega/ingres/testing/src/cl/hdr/hdr -I/home/omega/ingres/testing/src/cl/clf/hdr_unix_win 
	-I/home/omega/ingres/testing/src/cl/clf/hdr -I/home/omega/ingres/testing/src/gl/hdr/hdr -o 
	/home/omega/ingres/testing/src/tools/port/eval_unix_vms/lp32/sali

(follow-up: ↓ 6 ) 04/29/08 06:52:06 changed by anonymous

(OK, I really need to stop posting long comments as they're obviously being truncated Part two...)

lp32 is the 32-bit compatibility module for 64-bit builds. Looks like there's a header file that's either missing or in a different place (stubs-32.h) on Ubuntu 8.04. I'd recommend you enter a new ticket with a title like "stubs-32.h missing, build fails on Ubuntu 8.04".

BTW, when diagnosing a build failure the first thing to do is look in the jam log and look for the first failed target - i.e. search from the top for "failed". The bit at the end about numbers of targets failed, skipped and updated is just a summary.

Cheers Paul

(in reply to: ↑ 5 ) 04/29/08 07:27:45 changed by anonymous

Sorry about that, and thank you kindly.

05/18/08 17:29:33 changed by rosan01

  • milestone set to asap.