Subject Re: [IBDI] instructions for building interbase on redhat 6.2
Author Oliver Sturm
Hallo Mark,

Am Sonntag, 30. Juli 2000 um 10:14:30, haben Sie geschrieben:

Thanks for those instructions! I started my build tries fresh and
tried to follow them. I have some annotations:

>       $/opt/interbase/bin/isql -i ../builds_win32/original/metadata.sql
>       $rm yachts.gdb
>       $ln -s ../metadata.gdb yachts.gdb        Expect the error:

Two things here:

- I need to use -user and -password for the isql command. That becomes
a running problem in the build process. Is there a way to set that
globally which I'm not aware of?
- Why do you call that link "yachts.gdb" here? The original, which is
created by the script, is called "yachts.lnk". Maybe that's the
source of the problem you encounter below.


>     $cd /tmp/build/Interbase/
>     $cd msgs
>     $rm msg.gdb
>     $/opt/interbase/bin/gbak -C /tmp/build/codes/msg.gbak
> msg.gdb

-user sysdba -password masterkey ?


> To the following:

> # Run the codes program, thus generating codes.h, iberror.h,
> etc
> # compare and copy the file only if the files are different
> run_codes:      force $(CODES)
>        
> $(CP) ../codes/*.h jrd
> #      
> $(SH) '$(CD) source/jrd; $(CODES)'
>          $(SH)
> '$(CMP) source/jrd/iberror.h $(INCLUDE_ ........

This means that the line starting $(SH) should be commented out. Also,
especially for those not very acquainted with make, the single lines
MUST have a TAB (no spaces) at the beginning.


> Remove all the dependancies by finding the following text:
> #GDS_PYXIS=            
> gds_pyxis.a

> And change it to:
> GDS_PYXIS=
> #GDS_PYXIS=            
> gds_pyxis.a

Formatting is not very nice here. It should actually say:

Remove all the dependancies by finding the following text:
#GDS_PYXIS=gds_pyxis.a

And change it to:
GDS_PYXIS=
#GDS_PYXIS=gds_pyxis.a

Be aware of those formatting problems in all other places.

>  8.  Finally doing some building.

> We are now ready to start building the database engine. 
> Change to the root directory and start the build - (however you still have
> to do some typing yet).

>     $cd /tmp/build/InterBase    $build_kits builds SUPER


Okay, now here is where it stops for me.

1) Why do all those gpre lines have no -user -password arguments? They
don't work for me that way.
2) I could work around by executing the first occurrence (security.e)
manually, using those parameters.
3) When I get to the second occurrence (array.e), gpre dumps core when
trying to process the file. Any ideas how that might come?



MfG,
Oliver Sturm

--
Who is General Failure and why is he reading my disk?
--
Oliver Sturm / <sturm@...>

Key ID: 71D86996
Fingerprint: 8085 5C52 60B8 EFBD DAD0 78B8 CE7F 38D7 71D8 6996