public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wine-1.1.16 and amd64
Date: Mon, 2 Mar 2009 19:35:00 +0200	[thread overview]
Message-ID: <200903021935.00955.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <49AC1357.9090406@ritirata.org>

On Monday 02 March 2009 19:11:51 Antonio Quartulli wrote:
> Hi all!
> I am trying to upgrade wine to version 1.1.16 on my Gentoo AMD64 but I
> got a problem because it can't compile (or maybe link) on my amd64 system.
>
> x86_64-pc-linux-gnu-gcc -m32 -c -I. -I. -I../../include -I../../include
>  -D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
> -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits
> -Wpointer-arith  -march=core2 -O3 -pipe -msse4.1 -fomit-frame-pointer
> -o activeds_main.o activeds_main.c
> /usr/bin/ld: Relocatable linking with relocations from format elf32-i386
> (main.o) to format elf64-x86-64 (acledit.gf6Map.o) is not supported
> winebuild: /usr/bin/ld -r failed with status 256
> winegcc: ../../tools/winebuild/winebuild failed
> make[2]: *** [acledit.dll.so] Error 2
>
> this is one of the errors that I got.
>
> Is there a way to build wine on a 64bit system without using the win64
> flag (i still want to run win32 binaries).
>
> Bye!


Bug #260726 at b.g.o.

Apparently if you remove the offending line recently added by vapier to the 
ebuild, it may build. However, variable results have been reported.

Failing that, I suggest you do what I did - mask 1.1.6 and be content with 
1.1.15

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2009-03-02 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 17:11 [gentoo-user] Wine-1.1.16 and amd64 Antonio Quartulli
2009-03-02 17:35 ` Alan McKinnon [this message]
2009-03-02 17:45   ` Antonio Quartulli

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=200903021935.00955.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.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