Re: Need assistance QNX libc/GNU libstdc++ header file conflicts

[Phil Edwards <phil at jaj dot com>]

On Mon, May 20, 2002 at 11:13:20AM -0700, J.T. Conklin wrote:
> jtc@acorntoolworks.com (J.T. Conklin) writes:
> > The same problem occurs for strchr, strrchr, strpbrk, abs, acos, tanhl, 
> > etc.  I don't know whether the Dinkum/QNX or the stdc++ headers are wrong, 
> > or if it's simply a matter of the two being incompatible with each other.

The latter.  Some C library headers are more C++-friendly than others.
This is an open issue.


> After going down this path a bit further, I realized that adding all
> these conditionals were making c_std headers look very much like the 
> c headers.  Compiling with --enable-cheaders=c allowed me to make a 
> lot of progress.  Is it permissable to have a target config change 
> the --enable-cheaders default from std to c?

I don't think the configury is actually set up to do this.


> I have some other configuration questions.  Is there any reason to add
> an qnx*) entry to configure.target to set os_include_dir?  It appears
> the configure script unconditionally overrides it.

The configure script will see the setting if you add one.  But there is no
reason to create your own os_include_dir unless you actually have changes
to make; at the point, certainly.


> Will I need a separate libstdc++ copyright assignment to contribute
> the QNX target, or will my existing gcc assignment be acceptable?

[private email]


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams