From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Subject: Re: gcc on Sparc Solaris 8
Date: Mon, 30 Sep 2019 19:23:00 -0000 [thread overview]
Message-ID: <c0e92f28-4c78-9032-a850-aaa5213eba8e@blastwave.org> (raw)
In-Reply-To: <1157198014.1780392.1569854535577@mail.yahoo.com>
> but in Solaris 10 there are problems with X11 libraries.
For example: XAllocColorCells is not working.
A very basic Xlib function is not working ?? Really ??
This ?
Status XAllocColorCells(display, colormap, contig,
plane_masks_return, nplanes,
pixels_return, npixels)
Display *display;
Colormap colormap;
Bool contig;
unsigned long plane_masks_return[];
unsigned int nplanes;
unsigned long pixels_return[];
unsigned int npixels;
As for floating point numbers.
Floating point numbers exist in binary with a trivial format of a sign
bit and then some bits for an exponent and then lastly a string of bits
to represent the significand. The significand ( or mantissa ) data also
has an implied leading bit of "1" for normal numbers. How you choose to
print them out is entirely your business.
The Oracle Solaris 12.6 Developer tools are a free download and I do
suggest you look at them. I am fairly sure that support for Solaris in
gcc has been dropped as of last year. At least for Solaris 10. Sadly I
have never seen Solaris 11 in the wild. Maybe that works and maybe it
does not. Have you considered simply moving over to FreeBSD or even dare
I say it Linux? I have heard in various places that this "Linux" thing
works quite well and I have even seen it running neatly. Could be worth
a look. :) Just don't go lookng too closely for POSIX compliance or even
cross platform clean compiles.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next prev parent reply other threads:[~2019-09-30 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1157198014.1780392.1569854535577.ref@mail.yahoo.com>
2019-09-30 14:42 ` rolf perau via gcc-help
2019-09-30 19:23 ` Dennis Clarke [this message]
[not found] <370931742.2089515.1569886162496.ref@mail.yahoo.com>
2019-09-30 23:29 ` rolf perau via gcc-help
[not found] <2147124760.1726006.1569850372525.ref@mail.yahoo.com>
2019-09-30 13:32 ` rolf perau via gcc-help
2019-09-30 13:39 ` Jonathan Wakely
2019-09-30 19:34 ` Dennis Clarke
2019-09-30 19:36 ` Dennis Clarke
[not found] <691082870.1339340.1569819291085.ref@mail.yahoo.com>
2019-09-30 4:55 ` rolf perau via gcc-help
2019-09-30 6:11 ` Dennis Clarke
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=c0e92f28-4c78-9032-a850-aaa5213eba8e@blastwave.org \
--to=dclarke@blastwave.org \
--cc=gcc-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).