<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Well, this sounds cool.  Thank you for opening the world of
      Vagrant to me.  I think I am doing this right.  I have run the
      commands and am waiting with this as my last output:</p>
    <p>==&gt; default:  -- Graphics Type:     vnc<br>
      ==&gt; default:  -- Graphics Port:     -1<br>
      ==&gt; default:  -- Graphics IP:       127.0.0.1<br>
      ==&gt; default:  -- Graphics Password: Not defined<br>
      ==&gt; default:  -- Video Type:        cirrus<br>
      ==&gt; default:  -- Video VRAM:        9216<br>
      ==&gt; default:  -- Sound Type:    <br>
      ==&gt; default:  -- Keymap:            en-us<br>
      ==&gt; default:  -- TPM Path:          <br>
      ==&gt; default:  -- INPUT:             type=mouse, bus=ps2<br>
      ==&gt; default: Creating shared folders metadata...<br>
      ==&gt; default: Starting domain.<br>
      ==&gt; default: Waiting for domain to get an IP address...<br>
    </p>
    <p>It's been sitting there for quite some time and an htop shows 2
      of my cores spinning at 100% occupied by qemu...</p>
    <p>I noticed the vnc reference at localhost and tried to connect to
      that and sure enough, I get connected to a boot screen which last
      says:</p>
    <p>Booting from Hard Disk...</p>
    <p>But nothing else happens?  Should I keep waiting?  Do I need to
      escalate permissions to root?  Do I need to add my username to
      some new vagrant group?  Do I need to reboot my box for my dnf
      install stuff to "take"?  Any advice would be appreciated. 
      Looking forward to adding this to my toolbox once I learn.</p>
    <p>Troy<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 7/20/19 9:28 PM, Greg Hellings
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHxvOV+f=BJjs3PBi9O5_LL5N_eT1t=EenTo8pkUJ=mFoeHNXQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div><a href="https://app.vagrantup.com/ppc64le/boxes/fedora30"
            moz-do-not-send="true">https://app.vagrantup.com/ppc64le/boxes/fedora30</a></div>
        <div><br>
        </div>
        <div>That should allow you to bring up a local VM with Fedora 30
          on ppc64le using Vagrant. Only works on systems with a libvirt
          backend to Vagrant (sudo dnf install vagrant vagrant-libvirt
          should do the trick on a Fedora workstation, followed by
          "vagrant up --provider=libvirt" if it doesn't default to that
          provider on a standard "vagrant up").</div>
        <div><br>
        </div>
        <div>The build error was in Rawhide, though, and seems to have
          been due to changes in the headers. Errors from a similar
          cause have come and gone from time to time in the past.
          Sometimes they come and go in automated builds in a transient
          manner. I don't know if you'll see it when you try or not when
          you try.<br>
        </div>
        <div><br>
        </div>
        <div>--Greg<br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sat, Jul 20, 2019 at 10:36
          PM Troy A. Griffitts &lt;<a href="mailto:scribe@crosswire.org"
            moz-do-not-send="true">scribe@crosswire.org</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Anyone
          have access to a PPC64LE box I can play on?<br>
          <br>
          On 7/18/19 12:04 AM, Jaak Ristioja wrote:<br>
          &gt; Yes, it is a sizeable patch. Although there might be
          hacks around this<br>
          &gt; issue, getting rid of the reserved identifiers and using
          the fixed-width<br>
          &gt; types from &lt;cstdint&gt; seems to be the correct
          approach to take.<br>
          &gt;<br>
          &gt; I'm not even sure the patch applies correctly to Sword
          SVN trunk, but<br>
          &gt; since this issue has long been fixed in Sword++, I
          referred to this<br>
          &gt; commit in hopes to accelerate this getting fixed for
          Sword as well. I<br>
          &gt; think it would not benefit anyone if Sword was left
          failing on Fedora<br>
          &gt; rawhide.<br>
          &gt;<br>
          &gt;<br>
          &gt; +Jaak<br>
          &gt;<br>
          &gt;<br>
          &gt; On 18.07.19 06:47, Greg Hellings wrote:<br>
          &gt;&gt; That is a rather sizeable patch. I don't want to just
          apply it wholesale to<br>
          &gt;&gt; the Sword engine without some input from people who
          know more about the<br>
          &gt;&gt; code than I do. It should, however, be workable if
          Troy doesn't have a more<br>
          &gt;&gt; permanent fix in mind.<br>
          &gt;&gt;<br>
          &gt;&gt; --Greg<br>
          &gt;&gt;<br>
          &gt;&gt; On Wed, Jul 17, 2019 at 4:52 PM Jaak Ristioja &lt;<a
            href="mailto:jaak@ristioja.ee" target="_blank"
            moz-do-not-send="true">jaak@ristioja.ee</a>&gt; wrote:<br>
          &gt;&gt;<br>
          &gt;&gt;&gt; In Sword++ we fixed [1] this by using the
          fixed-width integer types<br>
          &gt;&gt;&gt; provided by &lt;cstdint&gt;. Note also that some
          certain names containing<br>
          &gt;&gt;&gt; underscores are reserved to the C++
          implementation [2], e.g. names<br>
          &gt;&gt;&gt; beginning with underscores and names containing
          adjacent underscores.<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; Best regards,<br>
          &gt;&gt;&gt; Jaak<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; [1]: Feel free to integrate<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; <a
href="https://github.com/swordxx/swordxx/commit/3934674fd8db1302c7777c323c0a56235292d6d7"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/swordxx/swordxx/commit/3934674fd8db1302c7777c323c0a56235292d6d7</a><br>
          &gt;&gt;&gt; back to Sword. In Sword++ most of these type
          names were later prefixed<br>
          &gt;&gt;&gt; with std::, e.g. std::uint64_t instead of plain
          uint64_t.<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; [2]: See <a
            href="https://stackoverflow.com/a/228797" rel="noreferrer"
            target="_blank" moz-do-not-send="true">https://stackoverflow.com/a/228797</a>
          for a good summary on this.<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; On 17.07.19 17:52, Greg Hellings wrote:<br>
          &gt;&gt;&gt;&gt; I got an automated report this week that
          Sword 1.8.1 has begun failing to<br>
          &gt;&gt;&gt;&gt; build on ppc64le architecture with type
          redefinition errors. The errors<br>
          &gt;&gt;&gt; are<br>
          &gt;&gt;&gt;&gt; reported here: <a
            href="https://bugzilla.redhat.com/show_bug.cgi?id=1730318"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://bugzilla.redhat.com/show_bug.cgi?id=1730318</a><br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt; To copy from that link, the relevant error
          is:<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt;  /usr/include/asm-generic/int-l64.h:29:25:
          error: conflicting<br>
          &gt;&gt;&gt;&gt; declaration 'typedef long int __s64'<br>
          &gt;&gt;&gt;&gt;     29 | typedef __signed__ long __s64;<br>
          &gt;&gt;&gt;&gt;        |                         ^~~~~<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt;  /usr/include/asm-generic/int-l64.h:30:23:
          error: conflicting<br>
          &gt;&gt;&gt;&gt; declaration 'typedef long unsigned int __u64'<br>
          &gt;&gt;&gt;&gt;     30 | typedef unsigned long __u64;<br>
          &gt;&gt;&gt;&gt;        |                       ^~~~~<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt; I try to shy away from knowing too much about
          C's typing system. I can<br>
          &gt;&gt;&gt;&gt; easily locate the places in our code where we
          are defining those types<br>
          &gt;&gt;&gt;&gt; ourself. However, I don't want to mess up
          proper detection and<br>
          &gt;&gt;&gt;&gt; definition of them in a patch if I can help
          it.<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt; --Greg<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;&gt;
          _______________________________________________<br>
          &gt;&gt;&gt;&gt; sword-devel mailing list: <a
            href="mailto:sword-devel@crosswire.org" target="_blank"
            moz-do-not-send="true">sword-devel@crosswire.org</a><br>
          &gt;&gt;&gt;&gt; <a
            href="http://www.crosswire.org/mailman/listinfo/sword-devel"
            rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
          &gt;&gt;&gt;&gt; Instructions to unsubscribe/change your
          settings at above page<br>
          &gt;&gt;&gt;&gt;<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; _______________________________________________<br>
          &gt;&gt;&gt; sword-devel mailing list: <a
            href="mailto:sword-devel@crosswire.org" target="_blank"
            moz-do-not-send="true">sword-devel@crosswire.org</a><br>
          &gt;&gt;&gt; <a
            href="http://www.crosswire.org/mailman/listinfo/sword-devel"
            rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
          &gt;&gt;&gt; Instructions to unsubscribe/change your settings
          at above page<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;<br>
          &gt;&gt; _______________________________________________<br>
          &gt;&gt; sword-devel mailing list: <a
            href="mailto:sword-devel@crosswire.org" target="_blank"
            moz-do-not-send="true">sword-devel@crosswire.org</a><br>
          &gt;&gt; <a
            href="http://www.crosswire.org/mailman/listinfo/sword-devel"
            rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
          &gt;&gt; Instructions to unsubscribe/change your settings at
          above page<br>
          &gt;&gt;<br>
          &gt;<br>
          &gt; _______________________________________________<br>
          &gt; sword-devel mailing list: <a
            href="mailto:sword-devel@crosswire.org" target="_blank"
            moz-do-not-send="true">sword-devel@crosswire.org</a><br>
          &gt; <a
            href="http://www.crosswire.org/mailman/listinfo/sword-devel"
            rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
          &gt; Instructions to unsubscribe/change your settings at above
          page<br>
          <br>
          _______________________________________________<br>
          sword-devel mailing list: <a
            href="mailto:sword-devel@crosswire.org" target="_blank"
            moz-do-not-send="true">sword-devel@crosswire.org</a><br>
          <a
            href="http://www.crosswire.org/mailman/listinfo/sword-devel"
            rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
          Instructions to unsubscribe/change your settings at above page<br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
    </blockquote>
  </body>
</html>