Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: xorgxrdp and xrdp
Date: Thu, 01 Jul 2021 21:59:41 +0200	[thread overview]
Message-ID: <20210701195941.pCYuhQhjnad1sc9tBrMZyqfbfFUaAxIAqX24X4jz-hA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31512@inbox.vuxu.org>

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/31512#issuecomment-872512326

Comment:
Well.

Cross build fails because default build target generate keys with just-compiled binary.
Keys shouldn't be generated build-time, disable with 

    @@ -55,6 +53,11 @@ pre_configure() {
            ./bootstrap
     }
     
    +post_configure() {
    +       vsed -i keygen/Makefile -e 's@./xrdp-keygen@:@'
    +       vsed -i keygen/Makefile -e 's@$(OPENSSL)@:@'
    +}
    +
     post_install() {
            vsv xrdp
            vsv xrdp-sesman

Musl build fails because of wrong --build target passed. Pass none, build style gets that right.

Build of test need check-devel in checkdepends.

xorgxrdp should be build for all archs.

depends= are filled automatically, see 04-generate-runtime-deps in build log.

  parent reply	other threads:[~2021-07-01 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  9:49 [PR PATCH] " combro2k
2021-06-15 10:25 ` combro2k
2021-06-15 15:01 ` New package: " combro2k
2021-07-01 19:59 ` Chocimier [this message]
2022-03-15 12:00 ` Anachron
2022-03-16  9:48 ` combro2k
2022-06-15  2:16 ` github-actions
2022-06-30  2:14 ` [PR PATCH] [Closed]: " github-actions
2022-07-29  8:34 ` dezifit

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=20210701195941.pCYuhQhjnad1sc9tBrMZyqfbfFUaAxIAqX24X4jz-hA@z \
    --to=chocimier@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).