Ticket #133 (new defect)

Opened 2 months ago

Last modified 2 months ago

lp32 directory not created during install

Reported by: omega187@gmail.com Assigned to: admin
Priority: major Milestone: asap
Component: compile Version: main
Keywords: lp32 fail compile build Cc:

Description

Installation on Ubuntu 8.04 Hardy Heron AMD64. 

Cc /home/omega/ingres/testing/build/demo/udadts/lp32/common.o 
Assembler messages:
Fatal error: can't create /home/omega/ingres/testing/build/demo/udadts/lp32/common.o: 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  -fPIC -Dint_lnx  -I/home/omega/ingres/testing/build/files -I/home/omega/ingres/testing/build/demo/udadts -o /home/omega/ingres/testing/build/demo/udadts/lp32/common.o /home/omega/ingres/testing/src/common/adf/admin/common.c
        
...failed Cc /home/omega/ingres/testing/build/demo/udadts/lp32/common.o ...

That error is repeated for anything in the lp32 directory it seems. The error also causes the install script to infinitely loop doing nothing. I've attached the latest log for you to see...

Attachments

jam_05_01_08_1744.log (1.9 MB) - added by omega187@gmail.com on 05/01/08 16:19:13.
jam build log
jam_05_05_08_0836.log (222.8 kB) - added by omega187@gmail.com on 05/05/08 05:57:54.
Jam build log

Change History

05/01/08 16:19:13 changed by omega187@gmail.com

  • attachment jam_05_01_08_1744.log added.

jam build log

05/02/08 03:49:03 changed by maspa05

Hi Omega,

The first failure in the log is from building the lp32 version of unimapcompile and it's failing because it can't find a 32-bit libxerces-c.so. It doesn't look like you can install a package for that. I'm not sure what's normally done here - possibly build xerces from source.

Let me see if I can find out.

05/02/08 03:57:56 changed by maspa05

OK, have a look at the Community Build Page under the gotchas section on Xerces. It explains how to install a 32-bit version (your existing Xerces is 64bit so no need to build that).

It will be worth looking at the other gotchas for 64-bit builds too.

HTH

Paul

05/05/08 03:53:57 changed by maspa05

Turns out this is not the only gotcha, so I added a HOWTO to the Community Wiki page

05/05/08 05:57:54 changed by omega187@gmail.com

  • attachment jam_05_05_08_0836.log added.

Jam build log

05/05/08 08:09:12 changed by omega187@gmail.com

Alright, so this ticket has been "solved".. basically what happened was that the runbuild was not deleting the "build" directory, and this was causing some trouble. So after some help from PaulM05 on IRC, he gave me the idea to manually remove the build directory, after which there were no more "missing directory" errors.