Github messages for voidlinux
 help / color / mirror / Atom feed
From: dotnetfox <dotnetfox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Tigervnc 1.12
Date: Wed, 24 Nov 2021 03:48:39 +0100	[thread overview]
Message-ID: <20211124024839.BTa00QYzQXpqexRAkJ51b6sF6HUm88iTJ-SK1cswfS0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34001@inbox.vuxu.org>

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

New comment by dotnetfox on void-packages repository

https://github.com/void-linux/void-packages/issues/34001#issuecomment-977450466

Comment:
For those who are planning to update the package to this version, be aware of the following:
- pam-devel has to be added to makedepends.
- CMake throws deprecation warnings at you.
- CMake cannot find pam-devel while other packages with the same building style, in fact, are able to find and build with it (maybe implementation of checks is different?). The check is implemented this way:
```
# Check for PAM library
if(UNIX AND NOT APPLE)
  check_include_files(security/pam_appl.h HAVE_PAM_H)
  set(CMAKE_REQUIRED_LIBRARIES -lpam)
  check_function_exists(pam_start HAVE_PAM_START)
  set(CMAKE_REQUIRED_LIBRARIES)
  if(HAVE_PAM_H AND HAVE_PAM_START)
    set(PAM_LIBS pam)
  else()
    message(FATAL_ERROR "Could not find PAM development files")
  endif()
endif()
```

If someone is able to solve this "issue" with CMake (more like insanity) and finds this information helpful in some way, then you have my thanks.

  reply	other threads:[~2021-11-24  2:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 21:02 [ISSUE] " bern-coder
2021-11-24  2:48 ` dotnetfox [this message]
2022-06-11  2:13 ` github-actions
2022-06-25  2:15 ` [ISSUE] [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=20211124024839.BTa00QYzQXpqexRAkJ51b6sF6HUm88iTJ-SK1cswfS0@z \
    --to=dotnetfox@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).