Github messages for voidlinux
 help / color / mirror / Atom feed
From: ypsvlq <ypsvlq@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] vice: update to 3.6.1.
Date: Sun, 11 Sep 2022 19:16:18 +0200	[thread overview]
Message-ID: <20220911171618.jrfohtzswvvS0l0xFgQAfGipChUawTy7xqTIqqw74UM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37480@inbox.vuxu.org>

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

New review comment by ypsvlq on void-packages repository

https://github.com/void-linux/void-packages/pull/37480#discussion_r967860267

Comment:
Not specifying it there causes 
```
=== configuring in src/resid (/builddir/vice-3.6.1/src/resid)
configure: running /bin/sh ./configure '--prefix=/usr' --disable-option-checking  '--sysconfdir=/etc' '--sbindir=/usr/bin' '--bindir=/usr/bin' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--localstatedir=/var' '--host=x86_64-unknown-linux-gnu' '--build=x86_64-unknown-linux-gnu' '--libdir=NONE/lib64' '--disable-sdlui2' '--without-sdlsound' '--enable-native-gtk3ui' '--enable-desktop-files' '--with-pulse' '--enable-external-ffmpeg' '--enable-cpuhistory' '--enable-x64' '--disable-pdf-docs' 'build_alias=x86_64-unknown-linux-gnu' 'host_alias=x86_64-unknown-linux-gnu' 'CC=cc' 'CFLAGS=-fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -fdebug-prefix-map=/builddir/vice-3.6.1=.' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed    ' 'CPPFLAGS=
 ' 'CPP=cpp' 'CXX=g++' 'CXXFLAGS=-fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe    -fdebug-prefix-map=/builddir/vice-3.6.1=.' 'PKG_CONFIG=pkg-config' '--disable-option-checking' '--srcdir=.' --cache-file=
configure: error: expected an absolute directory name for --libdir: NONE/lib64
configure: error: ./configure failed for src/resid
=> ERROR: vice-3.6.1_1: do_configure: '${configure_script} ${configure_args}' exited with 1
```

  parent reply	other threads:[~2022-09-11 17:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  8:54 [PR PATCH] " ypsvlq
2022-06-10 16:02 ` [PR REVIEW] " paper42
2022-06-10 16:02 ` paper42
2022-06-10 16:02 ` paper42
2022-06-10 17:10 ` ypsvlq
2022-06-10 17:20 ` [PR PATCH] [Updated] " ypsvlq
2022-09-09  2:15 ` github-actions
2022-09-10  7:27 ` ypsvlq
2022-09-10 10:22 ` [PR REVIEW] " paper42
2022-09-10 10:22 ` paper42
2022-09-10 10:22 ` paper42
2022-09-11 17:16 ` ypsvlq [this message]
2022-09-11 17:20 ` ypsvlq
2022-09-11 17:46 ` [PR PATCH] [Updated] " ypsvlq
2022-09-11 17:46 ` [PR REVIEW] " ypsvlq
2022-12-11  2:03 ` github-actions
2022-12-11  2:47 ` ypsvlq
2023-03-12  2:02 ` github-actions
2023-03-12  8:18 ` ypsvlq
2023-04-07 21:37 ` [PR REVIEW] " zlice
2023-06-24 18:59 ` classabbyamp
2023-06-24 18:59 ` classabbyamp
2023-06-24 19:36 ` [PR PATCH] [Updated] " ypsvlq
2023-06-24 19:46 ` ypsvlq
2023-06-24 19:57 ` [PR PATCH] [Updated] vice: update to 3.7.1 ypsvlq
2023-06-24 20:01 ` ypsvlq
2023-06-24 20:16 ` [PR PATCH] [Merged]: " classabbyamp

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=20220911171618.jrfohtzswvvS0l0xFgQAfGipChUawTy7xqTIqqw74UM@z \
    --to=ypsvlq@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).