Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] wine: wine-32bit cannot build with the staging patchset enabled
Date: Sun, 14 Mar 2021 14:25:25 +0100	[thread overview]
Message-ID: <20210314132525.0FO7hvRQiz4qNNAKcnzU69ebIHqsPF03JacyKF-drJI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29456@inbox.vuxu.org>

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

Closed issue by kostadin04 on void-packages repository

https://github.com/void-linux/void-packages/issues/29456

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.11.6_1 x86_64 AuthenticAMD uptodate rFFFFFFFF

* package:  
  wine-32bit-6.3_1 libwine-32bit-6.3_1

### Expected behavior

The packages compile correctly 

### Actual behavior

The build fails with the following messages:

configure: WARNING: unrecognized options: --with-sysroot, --with-libtool-sysroot
checking build system type... x86_64-unknown-linux-gnu
checking host system type... i686-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-c++ accepts -g... yes
checking for i686-pc-linux-gnu-cpp... i686-pc-linux-gnu-cpp
checking for i686-pc-linux-gnu-ld... i686-pc-linux-gnu-ld
checking for the directory containing the Wine tools... configure: error: you must use the --with-wine-tools option when cross-compiling.
=> ERROR: wine-6.3_1: do_configure: '${configure_script} ${configure_args}' exited with 1
=> ERROR:   in do_configure() at common/build-style/gnu-configure.sh:8

### Steps to reproduce the behavior

1. git clone --depth=1 https://github.com/void-linux/void-packages
2. cd void-packages
3. ./xbps-src binary-bootstrap
4. ./xbps-src pkg -o staging -a i686 wine



      parent reply	other threads:[~2021-03-14 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 11:49 [ISSUE] " kostadin04
2021-03-14 13:13 ` Duncaen
2021-03-14 13:14 ` Duncaen
2021-03-14 13:22 ` kostadin04
2021-03-14 13:25 ` Duncaen [this message]

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=20210314132525.0FO7hvRQiz4qNNAKcnzU69ebIHqsPF03JacyKF-drJI@z \
    --to=duncaen@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).