Issue 445

Summary:	STLport header check fails in configure if STLport directory name contains certain characters.
Product:	Build Tools	Reporter:	oisinboydell
Component:	code	Assignee:	Unknown <non-migrated>
Status:	CLOSED FIXED	QA Contact:	issues@www <issues>
Severity:	Trivial
Priority:	P3	CC:	issues
Version:	619
Target Milestone:	---
Hardware:	Sun
OS:	Solaris
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description oisinboydell 2001-02-16 15:45:42 UTC

Only on Solaris, if the name of your STLport4 directory as supplied on the
command line to configure with --with-stlport4-home contains certain
combinations of "-", "_", "." and numbers then the STLport header check in
configure will fail.
The following is taken from config.log:

configure:1997: checking for STLport4 headers
configure:2007: cc -E  conftest.c >/dev/null 2>conftest.out
"configure", line 2003: invalid input token: 2._
cc: acomp failed for conftest.c
configure: failed program was:
#line 2002 "configure"
#include "confdefs.h"
/export/home/oisin/STL-2._/stlport/hash_map

Note the "invalid input token: 2._" where the "2._" is part of the correct
STLport directory name which I supplied configure using --with-stlport4-home.

Temporary work-around while this is solved: Don't name your STLport home
directory as anything with combinations of "-", "_", "." and numbers if you are
having problems with the STLport header check.

Comment 1 oisinboydell 2001-02-19 16:02:28 UTC

This problem is caused by a bug in the Sun Workshop C compiler preprocessor. The
use of certain combinations of characters such as "-", "_", "." etc. cause the C
preprocessor to fail. I solved this in the configure script by using the C++
preprocessor for the STLport header test when using Solaris. I have checked the
updated confgiure.in into the head of the cvs tree and into branch OO619B.

Comment 2 michael.bemmer 2003-03-16 20:09:20 UTC

As discussed with Armin, he thought these bug were closed, he sees all of them
as verified.

Comment 3 michael.bemmer 2003-03-16 20:13:08 UTC

As discussed with Armin, he thought these bug were closed, he sees all of them
as verified.