[Bug driver/47676] New: error: field âOttybâ has incomplete type

[Bug driver/47676] New: error: field âOttybâ has incomplete type

[ak0030470 at techmahindra dot com]

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

           Summary: error: field âOttybâ has incomplete type
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ak0030470@techmahindra.com


Created attachment 23293
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23293
Detailed description and header file extract

Hello,

Scenario:
Environment migrated-
HP-UX --> Linux 
acc --> gcc
----------------
Compilation of the existing code giving below error:

+ gcc -I.-D_HPUX_SOURCE -D_XPG2 -DUNIX -c io_util_FILE.c -o io_util_FILE.o
In file included from ./io_util.h:15,
                 from io_util_FILE.c:13:
/usr/local/include/ncurses/term.h:698: error: field âOttybâ has incomplete type
/usr/local/include/ncurses/term.h:699: error: field âNttybâ has incomplete type
----------------
Header file extract and description is attached for reference.

Thank you.

[Bug driver/47676] error: field âOttybâ has incomplete type

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2011.02.10 12:43:35
     Ever Confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-10 12:43:35 UTC ---
I don't know why you think this is a gcc bug but please follow the instructions
at http://gcc.gnu.org/bugs/ and provide preprocessed source.

This is more likely to be a bug in your code. Even if it's a problem with the
ncurses/term.h header, that's not a GCC bug.

[Bug driver/47676] error: field âOttybâ has incomplete type

[ak0030470 at techmahindra dot com]

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

--- Comment #2 from AK <ak0030470 at techmahindra dot com> 2011-02-10 12:55:11 UTC ---
Thanks Jonathan for initial view.
The same code is being used before, which was compiling properly, but when
migrated to Linux+gcc, it is giving this issue.
In the menwhile, I will also check the instructions sent by you.
Any further suggestions will be of big help.


(In reply to comment #1)
> I don't know why you think this is a gcc bug but please follow the instructions
> at http://gcc.gnu.org/bugs/ and provide preprocessed source.
> This is more likely to be a bug in your code. Even if it's a problem with the
> ncurses/term.h header, that's not a GCC bug.

[Bug driver/47676] error: field âOttybâ has incomplete type

[redi at gcc dot gnu.org]

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-10 13:52:48 UTC ---
(In reply to comment #2)
> The same code is being used before, which was compiling properly, but when
> migrated to Linux+gcc, it is giving this issue.

That's not a compiler bug. That means your code is not portable.

This code will compile on some UNIX platforms, but not on GNU/Linux:

  #include <sys/mman.h>
  caddr_t* p = 0;

But that's not a GCC bug, it's because the code is not portable.

Anyway, if you think it is a bug you need to follow the bug reporting
instructions.

[Bug driver/47676] error: field âOttybâ has incomplete type

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-23 13:28:12 UTC ---
closing due to lack of response