From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: [9front] macos drawterm aes
Date: Wed, 28 Jun 2017 22:22:07 -0700 [thread overview]
Message-ID: <CAH_zEu7nQvqE13BnHy76=HC8v53vmPT8P61CDAoBVLqaZfPGpg@mail.gmail.com> (raw)
In-Reply-To: <53CB77F1-50B1-4442-B18A-341E6BF553BC@orthanc.ca>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
did you try make CONF=osx?
On Jun 28, 2017 22:19, "Lyndon Nerenberg" <lyndon@orthanc.ca> wrote:
>
> > On Jun 28, 2017, at 10:08 PM, Nick Owens <mischief@offblast.org> wrote:
> >
> > try http://code.9front.org/hg/
>
> Sadly, it exhibits the same problem the other versions I found have -
> Xcode and the unbundled XQuartz have screwed up the include paths for the
> headers. And if I get past this, I'm sure the .a files (or whatever the
> fsck Apple calls them) will be unfounded as well. This is so annoying.
>
>
> (cd gui-x11; /Applications/Xcode.app/Contents/Developer/usr/bin/make)
> gcc -Wall -Wno-missing-braces -ggdb -I.. -I../include -I../kern -c
> -I/usr/X11R6/include -D_THREAD_SAFE -O2 -c -o x11.o x11.c
> x11.c:24:10: fatal error: 'X11/Xlib.h' file not found
> #include <X11/Xlib.h>
> ^
> 1 error generated.
> make[1]: *** [x11.o] Error 1
> make: *** [gui-x11/libgui.a] Error 2
> : lyndon@minnie:/Users/lyndon/src/drawterm; ls /usr/X11R6/include
> ls: /usr/X11R6/include: No such file or directory
> : lyndon@minnie:/Users/lyndon/src/drawterm;
>
> I haven't used Xcode in years, so I'm long past its machinations for
> torturing its internal -I paths into something sane.
>
> If someone has a working drawterm binary (with AES auth) that runs under
> 10.12 I would be forever in your debt.
[-- Attachment #2: Type: text/html, Size: 1842 bytes --]
next prev parent reply other threads:[~2017-06-29 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 4:51 Lyndon Nerenberg
2017-06-29 5:08 ` [9front] " Nick Owens
2017-06-29 5:19 ` Lyndon Nerenberg
2017-06-29 5:22 ` Nick Owens [this message]
2017-06-29 5:23 ` Lyndon Nerenberg
2017-06-29 5:12 ` kokamoto
2017-06-29 5:24 ` Lyndon Nerenberg
2017-06-29 5:31 ` Nick Owens
2017-06-29 5:36 ` Lyndon Nerenberg
2017-06-29 5:37 ` kokamoto
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='CAH_zEu7nQvqE13BnHy76=HC8v53vmPT8P61CDAoBVLqaZfPGpg@mail.gmail.com' \
--to=mischief@offblast.org \
--cc=9front@9front.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).