public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Eric Lund" <eric.lund@pcisys.net>
To: help-gcc@gnu.org
Subject: Searching for port of glibc and posix threads to Solaris 2.5.1
Date: Tue, 07 Dec 1999 15:17:00 -0000	[thread overview]
Message-ID: <s4r4ub7tqeg101@corp.supernews.com> (raw)

Hi,

My development team does numerous software demonstrations, for which we must
get a temporary demo license for our Sun Workshop Compiler on Solaris 2.5.1
on Sparc platforms.  We would like to avoid this, so we want to port our
code to the GNU GCC compiler.  Unfortunately, the glibc has not been ported
to Solaris, as far as I can tell.  Also, the POSIX threads library is ported
only to Linux platforms.

Has anyone out there heard of ports of glibc and the threads library to
Solaris (2.5.1)?

Cheers,
Eric






WARNING: multiple messages have this Message-ID

From: "Eric Lund" <eric.lund@pcisys.net>
To: help-gcc@gnu.org
Subject: Searching for port of glibc and posix threads to Solaris 2.5.1
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <s4r4ub7tqeg101@corp.supernews.com> (raw)
Message-ID: <19991231222400.hp-r57y8-APPfOjG-SbEYLimpC34vj15KcEaxFdVR5c@z> (raw)

Hi,

My development team does numerous software demonstrations, for which we must
get a temporary demo license for our Sun Workshop Compiler on Solaris 2.5.1
on Sparc platforms.  We would like to avoid this, so we want to port our
code to the GNU GCC compiler.  Unfortunately, the glibc has not been ported
to Solaris, as far as I can tell.  Also, the POSIX threads library is ported
only to Linux platforms.

Has anyone out there heard of ports of glibc and the threads library to
Solaris (2.5.1)?

Cheers,
Eric






             reply	other threads:[~1999-12-07 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07 15:17 Eric Lund [this message]
1999-12-31 22:24 ` Eric Lund

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s4r4ub7tqeg101@corp.supernews.com \
    --to=eric.lund@pcisys.net \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).