Very Computer

by **swan..** » Fri, 14 May 1993 00:01:00

Last year I developed a curses based program on my SUN IPC (Sunos 4.1.2).
Sunos 4.1.2 has a SysV version of curses, that is the version I used.
I recently tried to compile my program with the new SUN C compiler
(version 2.0.1 I think). The curses routines that come with this compiler
are BSD routines. BSD curses and SysV curses do not seem to be compatible.
The compilation crashed (unrecognized symbols being a glaring problem).
I logged into a Solaris 2.1 based SUN that also had the new Sun C compiler
installed, and it too had BSD curses.

I would like to know why Sun chose BSD curses for their C compiler. I
thought they would surely use SysV curses for Solaris 2.x, since it is
SysV based (or does SVR4 use BSD curses by default?).

Is the source for SysV curses available via anon ftp?

Thanks for any help you can send.

--

by **Zeyd M. Ben-Hal** » Fri, 14 May 1993 12:21:05

>Last year I developed a curses based program on my SUN IPC (Sunos 4.1.2).
>Sunos 4.1.2 has a SysV version of curses, that is the version I used.
>I recently tried to compile my program with the new SUN C compiler
>(version 2.0.1 I think). The curses routines that come with this compiler
>are BSD routines. BSD curses and SysV curses do not seem to be compatible.
>The compilation crashed (unrecognized symbols being a glaring problem).
>I logged into a Solaris 2.1 based SUN that also had the new Sun C compiler
>installed, and it too had BSD curses.

>I would like to know why Sun chose BSD curses for their C compiler. I
>thought they would surely use SysV curses for Solaris 2.x, since it is
>SysV based (or does SVR4 use BSD curses by default?).

On most sun systems SYSV curses is accessable by compiling with -I/usr/5include
and linking with -L/usr/5lib.

Quote:>Is the source for SysV curses available via anon ftp?

You can get the latest sources to ncurses from netcom.com:pub/zmbenhal.

Zeyd

>Thanks for any help you can send.

>--

by **David Swang** » Fri, 14 May 1993 21:58:34

> >Last year I developed a curses based program on my SUN IPC (Sunos 4.1.2).
> >Sunos 4.1.2 has a SysV version of curses, that is the version I used.
> >I recently tried to compile my program with the new SUN C compiler
> >(version 2.0.1 I think). The curses routines that come with this compiler
> >are BSD routines. BSD curses and SysV curses do not seem to be compatible.
> >The compilation crashed (unrecognized symbols being a glaring problem).
> >I logged into a Solaris 2.1 based SUN that also had the new Sun C compiler
> >installed, and it too had BSD curses.

> >I would like to know why Sun chose BSD curses for their C compiler. I
> >thought they would surely use SysV curses for Solaris 2.x, since it is
> >SysV based (or does SVR4 use BSD curses by default?).

> On most sun systems SYSV curses is accessable by compiling with -I/usr/5include
> and linking with -L/usr/5lib.

This seems to be true for Sunos 4.1.x, but I these directories do not exist
on the Solaris 2.1 machine I have been using.

by **Joseph M DeAnge** » Sat, 15 May 1993 01:10:03

:
: I would like to know why Sun chose BSD curses for their C compiler. I
: thought they would surely use SysV curses for Solaris 2.x, since it is
: SysV based (or does SVR4 use BSD curses by default?).
:
This may have to do with the PATH variable you are using. I fell
into a trap whereby, Sun had placed a cover function /usr/ucb/cc
to invoke the compiler in BSD compatability mode. See if you
have /usr/ucb ahead of the directory in which you believe the
compiler to be. BTW, we have your environment here and use SYSV
curses so it is definitely doable without using the stuff below.

: Is the source for SysV curses available via anon ftp?
:
There is on uunet.uu.net :
systems/unix/linux/sources/libs/ncurses0.7.tar.Z 184330

by **Zeyd M. Ben-Hal** » Sat, 15 May 1993 17:18:20

>> >I would like to know why Sun chose BSD curses for their C compiler. I
>> >thought they would surely use SysV curses for Solaris 2.x, since it is
>> >SysV based (or does SVR4 use BSD curses by default?).

>> On most sun systems SYSV curses is accessable by compiling with -I/usr/5include
>> and linking with -L/usr/5lib.

>This seems to be true for Sunos 4.1.x, but I these directories do not exist
>on the Solaris 2.1 machine I have been using.

I suggest you complain loudly to SUN, and in the meanwhile get ncurses0.7.1
from netcom.com:pub/zmbenhal/
You'll need both 0.7 and the 0.7.1 update.

Zeyd

by **Greg Bra** » Sat, 15 May 1993 08:06:20

>I would like to know why Sun chose BSD curses for their C compiler. I
>thought they would surely use SysV curses for Solaris 2.x, since it is
>SysV based (or does SVR4 use BSD curses by default?).

I don't know about Solaris 2.X, but the SPARCWorks C compiler that I
have under SunOS 4.1.3 has a "sys5" option. From the man page:

-sys5 Adds the System V header files and libraries to
the compiler directory search paths.

Did you try this?

greg
--

by **David Swang** » Fri, 21 May 1993 05:58:28

>> >I would like to know why Sun chose BSD curses for their C compiler. I
>> >thought they would surely use SysV curses for Solaris 2.x, since it is
>> >SysV based (or does SVR4 use BSD curses by default?).

>> On most sun systems SYSV curses is accessable by compiling with -I/usr/5include
>> and linking with -L/usr/5lib.

>This seems to be true for Sunos 4.1.x, but I these directories do not exist
>on the Solaris 2.1 machine I have been using.

Ok, ok, I think I found out what is wrong. The Solaris machines I used
were set up with the 'default' installation. This default installation
does not include a lot of stuff, such as programming tools, and
curses. C is now unbundled starting with Solaris 2.x. When Sun C was
installed on my local machines, the installation didn't check if the
programming tools were installed. Anyway, theoretically, these machines
could be easily updated if there is room on the disks.

Thanks for the help!

David Swanger

Very Computer

curses curses curses

curses curses curses

curses curses curses

curses curses curses

curses curses curses

curses curses curses

curses curses curses

curses curses curses