From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap}
Date: Sun, 25 Sep 2022 05:08:03 +0200 [thread overview]
Message-ID: <20220925030803.TRKMEu97PD5KZOb1Sfkf_4ZzD3BwXO9Fpa8yAkNv6n8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/38816#issuecomment-1257109375
Comment:
I tried [six different environments](https://groups.io/g/linuxham/topic/93843043) — {{Void,FreeBSD} laptop,NixOS VM} plus {sway,i3} — and the fltk test programs displayed correctly only on the NixOS VM, in both X and Wayland.
I wanted to figure out what NixOS was doing differently, but I went about it in a very caveman-like way: I went back to the Void system and tried compiling with each dependency I figured I was missing, one-by-one:
```
$ xi -y libXft-devel
$ ./configure && make -j8 && test/preferences && make clean
$ # and so on, for libX{inerama,cursor,fixes,...}
```
But I couldn't get the all-black UI to go away. I also tried `./configure --enable-local{jpeg,zlib,png}` — same behavior.
There is almost certainly something very stupid I'm missing. But I'll devote some more time to finding it before asking [up-upstream](https://www.fltk.org/).
next prev parent reply other threads:[~2022-09-25 3:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 19:29 [PR PATCH] New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap,digi-full} Goorzhel
2022-08-21 19:34 ` classabbyamp
2022-08-21 20:28 ` [PR PATCH] [Updated] " Goorzhel
2022-08-21 20:43 ` New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap} Goorzhel
2022-08-21 20:44 ` Goorzhel
2022-08-21 22:49 ` classabbyamp
2022-08-21 22:53 ` classabbyamp
2022-09-07 6:43 ` Goorzhel
2022-09-07 6:43 ` Goorzhel
2022-09-07 6:45 ` classabbyamp
2022-09-07 6:47 ` Goorzhel
2022-09-07 6:48 ` Goorzhel
2022-09-07 6:49 ` Goorzhel
2022-09-22 5:02 ` [PR PATCH] [Updated] " Goorzhel
2022-09-22 5:02 ` Goorzhel
2022-09-22 5:32 ` Goorzhel
2022-09-23 6:00 ` Goorzhel
2022-09-25 3:08 ` Goorzhel [this message]
2022-12-25 1:58 ` github-actions
2022-12-27 19:17 ` [PR PATCH] [Closed]: " Goorzhel
2022-12-27 19:46 ` Goorzhel
2022-12-27 21:10 ` Goorzhel
2022-12-27 21:14 ` Goorzhel
2023-03-29 1:59 ` github-actions
2023-04-13 1:50 ` [PR PATCH] [Closed]: " github-actions
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=20220925030803.TRKMEu97PD5KZOb1Sfkf_4ZzD3BwXO9Fpa8yAkNv6n8@z \
--to=goorzhel@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).