Huge thanks to Alan Davis and Nick Batchelor for
inspiring me to give it another shot (was in the
process of installing linux when I got their
emails).
Turns out that Nick was on target : Although I'd
already got the "compiler backend" installed, as
part of the default installation, I hadn't added
other components such as the 'standard header files'
(although what use a compiler is without these, I'm
not quite sure). The fact that some headers existed
but in the wrong locations was also confusing...
Still, having added these extra filesets, things seem
to be working fine.
Thanks again to those 2 gentlemen... owe you lunch
if you're ever in KL,
Chas
ps. sorry for the late post/summary (other systems
fell sick in the meantime)
>From Nick.Batchelor_at_unilever.com
--------------------------------
We had problems linking oracle on a newly installed 4.0b box with lots
of
missing libraries. It turned out that I had not installed a number of
core filesets to do with software development support. Things like:
OSFCMPLRS410 - Compiler back end (software deveopment)
OSFINCLUDE410 - Standard header files (software development)
... and others in the software development set of filesets.
This could explain why you are short of the odd library and header
file.
They are on the OS install CD under .../ALPHA/BASE
>From Alan.Davis_at_digital.com
---------------------------
One thing to check is the compilers defaults file
in /usr/ccs/cmplrs/cc/comp.config and make sure that
it hasn't been modified. This can introduce very subtle
problems into the compiling process.
I'm also including a script that will run the fverify
program on all the installed subsets to check for
missing files/links/directories, incorrect ownership
and perms, and verify the checksums. Note that any files
that have been patched via manual patch install or dupatch
will be flagged as incorrect in their original subsets.
Alan Davis
<<allverify>>
#!/bin/sh
# to redirect output to a file use
# sh
# allverify 2> allverify.log
cd /
for i in `ls /usr/.smdb./*.lk`
do
x=`basename $i`
i=`echo ${x} | cut -f1 -d'.'`
echo ${i} 1>&2
/usr/lbin/fverify -n ${1} < /usr/.smdb./${i}.inv
done
>A late follow up and not much of a summary, I'm afraid.
>I uninstalled all the patches (to return to the base
>system) but still all C compilations failed due to the
>inability to find libraries and the old "object file deleted"
>gems.
>
>2 Different types of follow up were received :
>
>1. A couple people with similar setups offered me binaries
> (and there is already a binary for perl available for DU4.0b
> available). Cheers but that didn't really provide a long term
> solution... we are constantly installing / testing new
> tools.
>
>2. Best leads were from the comp.unix.programmer groups ....
> Typical follow-ups were :
> [snip]
> >cc: Severe: /usr/include/sys/types.h, line 77: Cannot find file
><standards.h>
> >...
> >But I do indeed have standards.h on my system :
> >/usr/sys/include/standards.h
> Sounds to me like you are missing the /usr/include/sys symlink to
> ./sys/include/sys on your system.
>
> I wonder what else is missing. Good luck!
> [/snip]
>
> Whilst /usr/include/sys --> ../sys/include/sys does in fact
> exist, I guess my C libs are really messed up.
>
>One more clean installation from scratch, totally by the book
>and if that fails, I guess there's little option but to follow the
>advice of some fellow programmers - linux.
>(which is not too drastic for simple web/cgi/database services.)
>
>chas
>
>
>
>Original Post :
>---------------
>
>>>Sorry to bother you with what maybe a trivial problem but
>>>my C compiler seems to be having immense problems finding
>>>any of its own libraries. (This C compiler shipped with the
>>>Operating System - Digital Unix 4.0b)
>>>
>>>A normally-straightforward installation of 'top' gives the following
>>>output from 'make' :
>>>
>>>[snip]
>>># make install
>>>cc -DHAVE_GETOPT -c top.c
>>>cc: Severe: /usr/include/sys/types.h, line 77: Cannot find file
><standards.h>
>>>specified in #include directive.
>>>#include <standards.h>
>>>-^
>>>cc: Error: /usr/include/sys/types.h, line 77: Object file deleted.
>>>#include <standards.h>
>>>-^
>>>*** Exit 1
>>>Stop.
>>>[/snip]
>>>
>>>But I do indeed have standards.h on my system :
>>>/usr/sys/include/standards.h
>>>
>>>So, I copied /usr/sys/include/standards.h to /usr/include
>>>
>>>This did the trick for including standards.h, but then 'make'
>>>couldn't even find stdio.h.
>>>
>>>I could go on copying these files over but that's not
>>>really going to help in the long run. This seems to be
>>>something fundamentally wrong with my system ?
>>>(This is an out-of-the-box, standard Digital Unix 4.0b Alpha)
>>>
>>>Needless to say I'm not getting very far with installation
>>>of GCC or other applications,
>>>
>>>Thank you very much for any advice,
>>>
>>>chas
>
>
Received on Sun May 03 1998 - 11:08:07 NZST