qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michele Denber <denber@mindspring.com>
To: qemu-devel@nongnu.org
Subject: Re: Building in Solaris 11.4
Date: Sat, 27 Jun 2020 17:19:23 -0400	[thread overview]
Message-ID: <5EF7B7DB.6040305@mindspring.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]

Well I removed the "static" from the line

static int openpty(int *amaster, int *aslave, char *name,
                    struct termios *termp, struct winsize *winp)

in util/qemu-openpty.c.  I odn't know if that was the right thing to do 
but it did allow it to compile.  Now I'm  stopped here:

...
CC      monitor/trace.o
util/drm.c: In function 'qemu_drm_rendernode_open':
util/drm.c:41:16: error: 'struct dirent' has no member named 'd_type'; 
did you mean 'd_name'?
          if (e->d_type != DT_CHR) {
                 ^~~~~~
                 d_name
util/drm.c:41:26: error: 'DT_CHR' undeclared (first use in this 
function); did you mean 'TH_CWR'?
          if (e->d_type != DT_CHR) {
                           ^~~~~~
                           TH_CWR
util/drm.c:41:26: note: each undeclared identifier is reported only once 
for each function it appears in
gmake: *** [/export/home/denber/qemu-5.0.0/rules.mak:69: util/drm.o] Error 1

This looks like more "not in Solaris" POSIX stuff.  See

https://stackoverflow.com/questions/35215109/struct-dirent-does-not-have-de-type-in-header-file

    "The only fields in the dirent structure that are mandated by
    POSIX.1 are: d_name[], of unspecified size, with at most NAME_MAX
    characters preceding the terminating null byte; and (as an XSI
    extension) d_ino. /The other fields are unstandardized, and not
    present on all systems/; see NOTES below for some further details.

    then continues

    Only the fields d_name and d_ino are specified in POSIX.1-2001. The
    remaining fields are available on many, but not all systems. Under
    glibc, programs can check for the availability of the fields not
    defined in POSIX.1 by testing whether the macros
    _DIRENT_HAVE_D_NAMLEN, _DIRENT_HAVE_D_RECLEN, _DIRENT_HAVE_D_OFF, or
    _DIRENT_HAVE_D_TYPE are defined.

    *Other than Linux, the d_type field is available mainly only on BSD
    systems.* This field makes it possible to avoid the expense of
    calling lstat(2) if further actions depend on the type of the file.
    If the _BSD_SOURCE feature test macro is defined, then glibc defines
    the following macro constants for the value returned in d_type:"

But I'm not sure what to make of this.


             - Michele



[-- Attachment #2: Type: text/html, Size: 4135 bytes --]

             reply	other threads:[~2020-06-27 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27 21:19 Michele Denber [this message]
2020-06-28 13:22 ` Building in Solaris 11.4 Peter Maydell
2020-06-28 14:16   ` Peter Tribble
  -- strict thread matches above, loose matches on Subject: below --
2020-06-24 21:31 Michele Denber
2020-06-24 21:48 ` Eric Blake
2020-06-24 21:53   ` Eric Blake
     [not found]   ` <5EF4D332.6040003@gmx.com>
2020-06-25 18:32     ` Michele Denber
2020-06-27 16:24 ` Michele Denber
2020-06-29 12:12   ` Thomas Huth
2020-06-29 20:25     ` Michele Denber
2020-06-30  5:10       ` Thomas Huth

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=5EF7B7DB.6040305@mindspring.com \
    --to=denber@mindspring.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).