[Bug pch/12707] Inclusion of PCH file produces "calling fdopen: Bad file descriptor" error

["kgardas at objectsecurity dot com" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12707



------- Additional Comments From kgardas at objectsecurity dot com  2003-10-21 19:25 -------
Subject: Re:  Inclusion of PCH file produces "calling fdopen:
 Bad file descriptor" error


Yes, when I deleted all pch, gcc was able to build MICO completely. To the
second point about provided *.ii and all neeeded header files. Do you
think it would be better to provide you with complete MICO sources plus
bash script which will duplicate the issue let say on linux? Why am I
asking? Since I will need to nearly provide all header files from MICO
anyway, because of various header files dependency...

Maybe the second choice will be that I will try to debug cc1plus to find
more information for you and provide you with all needed bits like
backtraces, variables values etc...

hanks,

Karel



On Tue, 21 Oct 2003, pinskia at gcc dot gnu dot org wrote:

> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12707
>
>
> pinskia at gcc dot gnu dot org changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |WAITING
>
>
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2003-10-21 15:47 -------
> Can you read: <http://gcc.gnu.org/bugs.html#pch> and provide the needed information?
>
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>

--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com