Re: Using g++2.1 with standard C library on SunOS 4.1.1 Rev B.

Thread View: gnu.gcc.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Mike Stump Sat, 29 Aug 1992 13:32

#1023

Author: Mike Stump
Date: Sat, 29 Aug 1992 13:32

31 lines
1735 bytes

You might want to use the header files from libg++, as these problems
will not arise then.

> Date: Fri, 21 Aug 92 13:41:02 EDT
> From: samborn@lynchpin.mtkgc.com (Kevin Samborn)
> Message-Id: <9208211741.AA09577@lynchpin.mtkgc.com>
> To: bug-gcc@prep.ai.mit.edu

> I am trying to use g++2.1 on SunOS 4.1.1 Rev B.  

> Whenever I include standard include files, (in this case coming from
> /usr/lang/SC1.0/CC/include), I get the errors similar to the following:

> In file included from /usr/lang/SC1.0/include/CC/malloc.h:9,
>                  from /usr/lang/SC1.0/include/CC/stdlib.h:21,
>                  from Main.C:1:
> /usr/lang/SC1.0/include/CC/alloca.h:10:
>         declaration of `char * __builtin_alloca (int)'
> <built-in>:0: conflicts with built-in
>         declaration `void * __builtin_alloca (int)'
> In file included from /usr/openwin3/include/X11/Xos.h:69,
>                  from /usr/openwin3/include/X11/Intrinsic.h:37,
>                  from Main.C:2:
> /usr/lang/SC1.0/include/CC/strings.h:22:
>         declaration of `unsigned int  strlen (const char *)'
> <built-in>:0: conflicts with built-in
>         declaration `int  strlen (const char *)'

> This happens even when I pass the -fno-builtin option to g++.

> Is there anyway to turn off type checking for builtin functions?

Re: Using g++2.1 with standard C library on SunOS 4.1.1 Rev B.

#1032

Author: Kevin Samborn
Date: Mon, 31 Aug 1992 14:23

41 lines
2049 bytes

/\/\ On Sat, 29 Aug 92 06:32:59 PDT, Mike Stump said:

   Mike> You might want to use the header files from libg++, as these
   Mike> problems will not arise then.

How do I do this?  The headers that are causing me the problems are
(right now) the headers malloc.h and stdlib.h.  Both of these are
included from X Window header files.

What I would really like to do, is turn off builtin functions, and the
builtin function prototypes.

> I am trying to use g++2.1 on SunOS 4.1.1 Rev B.

> Whenever I include standard include files, (in this case coming from
> /usr/lang/SC1.0/CC/include), I get the errors similar to the
> following:

> In file included from /usr/lang/SC1.0/include/CC/malloc.h:9,
>                  from /usr/lang/SC1.0/include/CC/stdlib.h:21,
>                  from Main.C:1:
> /usr/lang/SC1.0/include/CC/alloca.h:10:
>         declaration of `char * __builtin_alloca (int)'
> <built-in>:0: conflicts with built-in
> declaration `void * __builtin_alloca (int)'
> In file included from /usr/openwin3/include/X11/Xos.h:69,
>                  from /usr/openwin3/include/X11/Intrinsic.h:37,
>                  from Main.C:2:
> /usr/lang/SC1.0/include/CC/strings.h:22:
>         declaration of `unsigned int  strlen (const char *)'
> <built-in>:0: conflicts with built-in
>         declaration `int  strlen (const char *)'

> This happens even when I pass the -fno-builtin option to g++.

> Is there anyway to turn off type checking for builtin functions?

--
kevin samborn
Sakura Global Capital
samborn@mtkgc.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads