problems with gcc-2.96/cpp (from CVS)

[Idar Storvik]

I encountered problems when compiling/using a snapshot of gcc-2.96
(cvs update time Tue Apr 18 11:18:00 METDST 2000).

I was running an HP-UX 10.20 operating system, uname -a gave:
HP-UX gemini B.10.20 A 9000/782 2016395823 two-user license

It appears that gcc-2.96 does not find an include file when using
symbolic links to create a directory image (see attached example).
Possibly the procedure for simplifying file names in gcc/cpp is
not aware of symbolic links.

When using gcc-2.95 I got the expected result (i.e. it was ok).

Here is a description of the directory structure:
-------------------------------------------------

build:                 # where I build things
   doit                # a script to do things
   makefile            # a makefile
   output              # output from make
   t1-2.95.c           # gcc-2.95 output
  (t1-2.96.c           # gcc-2.96 output N.A.)

src:                   # the source dir
   t1@ -> ../tools/t1  # an optional tool linked

tools:                 # the tools dir
   include/            # dir for includes
   t1/                 # dir for tool 1

tools/include:         # ...
   b.h                 # a header file

tools/t1:              # ...
   c.c                 # a source file for tool 1
   c.h                 # a local header file

-------------------------------------------------

The build/doit script compiles c.c using gcc-2.96 and 2.95:
   <path>/gcc -v -I../src/t1/../include ../src/t1/c.c -o t1
   gcc-2.96 does not find include file b.h

See the build/output file for verbose output from the compilation
(I typed make >& output).

The linked directory image in the example above is similar to the
one that is used when linking binutils-x.y.z with gcc.


Regards
Idar Storvik

-- 
Idar.Storvik@cmr.no, tel. +47 55574314
http://www.cmr.no , tel. +47 55574040


-------------- next part --------------
A non-text attachment was scrubbed...
Name: t.tgz
Type: application/x-gzip
Size: 2083 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-bugs/attachments/20000418/adc9de5b/attachment.bin>