Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wine amd64 ebuild
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 7, 8, 9, 10, 11  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
stellvia
n00b
n00b


Joined: 26 Jun 2005
Posts: 7

PostPosted: Wed Jun 29, 2005 3:34 pm    Post subject: Reply with quote

That's great. I haven't tried many programs with Wine. But all my icons are black and white... don't know why.

Well... it took me a day to figure out tools/Makefile was making trouble, a few hours to figure out how to use sed, then two days to hack ebuild and keep emerging until it worked. Long process but it's working fine.
Back to top
View user's profile Send private message
sifi
n00b
n00b


Joined: 29 May 2005
Posts: 9
Location: Edinburgh, UK

PostPosted: Wed Jun 29, 2005 4:58 pm    Post subject: Reply with quote

nice one :)

If it helps anyone, I finally got emerging after using:
Code:
ABI=x86 USE="amd64" LDFLAGS="-m32" emerge wine

(with the original ebuild)
Back to top
View user's profile Send private message
Headrush
Watchman
Watchman


Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World

PostPosted: Thu Jun 30, 2005 12:58 am    Post subject: Reply with quote

I finally got a Wine to compile using Wine-20050628 by just copying the 20050524 ebuild and issuing
Code:
ABI=x86 emerge wine


Last edited by Headrush on Thu Jun 30, 2005 3:10 pm; edited 1 time in total
Back to top
View user's profile Send private message
andrewd18
Guru
Guru


Joined: 11 Apr 2004
Posts: 364
Location: Wisconsin, USA

PostPosted: Thu Jun 30, 2005 5:31 am    Post subject: Reply with quote

sifi wrote:
nice one :)

If it helps anyone, I finally got emerging after using:
Code:
ABI=x86 USE="amd64" LDFLAGS="-m32" emerge wine

(with the original ebuild)


ZOMG. It compiles. *dance*

~~ Andrew D.
_________________
Keep Your Toolchain Stable! - emwrap.sh

There's no place like ::1
Back to top
View user's profile Send private message
Poseidon
n00b
n00b


Joined: 18 Apr 2002
Posts: 18
Location: New Hampshire, US

PostPosted: Thu Jun 30, 2005 10:20 pm    Post subject: Steps to get DirectX Patch working on an AMD64. Reply with quote

There has been a lot of talk, but few complete solutions written, so here is the whole process.
Code:

1) Download 20050524.tar.gz or whatever the latest you can get your hands on is and adapt the following procedure accordingly.  Untar this file and rename the directory to "wine"

2) Follow the CVS update procedure on the http://www.winehq.org/cvs site (basically dl the cvs-20050524.tar.gz), this will give you the CVS directory stuctures when "untarred" over the wine dir.

3) Download the latest (currently 2005-06-13) patches release from http://directxwine.sourceforge.net

4) Apply the patch (bzip2 -dc d3d9patch.2005-06-13.diff.bz2 | patch -p0) do this outside the wine dir (../wine)

5) Rename the wine directory back to wine-20050524, and tarball it (tar -czvpf Wine-20050524.tar.gz wine-20050524)

6) Do an overlay, or just copy this file back to the /usr/portage/distfiles directory and recreate the digest (ebuild /usr/portage/app-emulation/wine/wine-20050524.ebuild digest)

7) emerge Wine with: `ACCEPT_KEYWORDS=~amd64 ABI=x86 USE=amd64 LDFLAGS=-m32 emerge --ask wine`

Enjoy!

This worked like a charm for me. Now if I can only get LOTR: Battle for Middle Earth to run on Linux through this I am set!

Regards,
Sebastian
Back to top
View user's profile Send private message
Headrush
Watchman
Watchman


Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World

PostPosted: Thu Jun 30, 2005 10:50 pm    Post subject: Reply with quote

Like all other methods so far, fails when patching d3d.
Code:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -X ignore -Nru clean/wine/dlls/d3d8/basetexture.c patch/wine/dlls/d3d8/basetexture.c
|--- clean/wine/dlls/d3d8/basetexture.c 2005-06-03 19:08:48.000000000 +0100
|+++ patch/wine/dlls/d3d8/basetexture.c 2005-06-14 13:41:56.000000000 +0100
--------------------------
File to patch:
Back to top
View user's profile Send private message
stellvia
n00b
n00b


Joined: 26 Jun 2005
Posts: 7

PostPosted: Fri Jul 01, 2005 4:44 am    Post subject: Reply with quote

If you take a look at config.log after configure, you may find lines about incompatible libraries. If configure cannot find 32-bit libfreetype and *actually* skips it, then it should go through emerge without much troubles. At least it's my own experience, not sure about others. Also, libz.so in emul may be pointing /usr/lib64, and libungif.so is another incompatible one. I'm not sure if these shared libraries being correct has any significant impact on Wine's operation.
Back to top
View user's profile Send private message
andrewd18
Guru
Guru


Joined: 11 Apr 2004
Posts: 364
Location: Wisconsin, USA

PostPosted: Fri Jul 01, 2005 9:13 pm    Post subject: Reply with quote

Headrush wrote:
Like all other methods so far, fails when patching d3d.
Code:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -X ignore -Nru clean/wine/dlls/d3d8/basetexture.c patch/wine/dlls/d3d8/basetexture.c
|--- clean/wine/dlls/d3d8/basetexture.c 2005-06-03 19:08:48.000000000 +0100
|+++ patch/wine/dlls/d3d8/basetexture.c 2005-06-14 13:41:56.000000000 +0100
--------------------------
File to patch:


Try running:
Code:
cat d3d9patch.2005-06-13.diff | patch -p1


Seemed to work for me... 3/12 hunks failed, but I'm doing the emerge now... I'll let you know if I see problems.

*edit* Nope. Bombed... compile worked okay, but the install into /var/blah part was asking for a file that didn't exist. ;_;
*edit #2* I'm thinkin' the 2005-06-13 diff isn't ready for the 2005-06-28 WINE build. I know that in 2005-06-28, the WINE team was adding a few small parts of the d3d9 patches... and that might be where the 2005-06-13 directxwine patch fails. Unfortunately, I'm not a good enough hacker that I could go into the code and figure out what's going on.
_________________
Keep Your Toolchain Stable! - emwrap.sh

There's no place like ::1
Back to top
View user's profile Send private message
tuxfan
Apprentice
Apprentice


Joined: 14 Feb 2003
Posts: 257

PostPosted: Sat Jul 09, 2005 8:01 am    Post subject: Reply with quote

All install works fine, but now my icons are looks ugly black/white. How can I solve that?

Any suggestions?
Back to top
View user's profile Send private message
tuxfan
Apprentice
Apprentice


Joined: 14 Feb 2003
Posts: 257

PostPosted: Sun Jul 10, 2005 9:10 pm    Post subject: Reply with quote

Seems that the GIF images are not displayed correctly. If the images include a transparent background that will come to trouble. Maybe the libungif library does not work in the right way. Any hints how I can check that?
Back to top
View user's profile Send private message
RaZoR1394
Guru
Guru


Joined: 09 Jan 2005
Posts: 356

PostPosted: Sun Jul 10, 2005 9:13 pm    Post subject: Reply with quote

tuxfan wrote:
All install works fine, but now my icons are looks ugly black/white. How can I solve that?

Any suggestions?


I got that problem too and I'm not sure it was related to a wine upgrade. It's very annoying when you're not sure where the button your searching is located exactly...
Back to top
View user's profile Send private message
hulf
n00b
n00b


Joined: 09 Jun 2005
Posts: 47

PostPosted: Mon Jul 11, 2005 8:25 am    Post subject: Reply with quote

Nargh... got latest wine ebuild 20050628 ebuild ..
ebuild /usr/local/portage/app-emulation/wine/wine-20050628.ebuild compile returns

checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

#define PACKAGE_BUGREPORT "wine-devel@winehq.org"
#define PACKAGE_NAME "Wine"
#define PACKAGE_STRING "Wine 20050628"
#define PACKAGE_TARNAME "wine"
#define PACKAGE_VERSION "20050628"

configure: exit 77

Ive set portage/package.keywords app-emulation/wine ~amd64 and tryed
ACCEPT_KEYWORDS=~amd64 ABI=x86 USE=amd64 LDFLAGS=-m32 emerge --ask wine
Back to top
View user's profile Send private message
RaZoR1394
Guru
Guru


Joined: 09 Jan 2005
Posts: 356

PostPosted: Mon Jul 11, 2005 10:43 am    Post subject: Reply with quote

hulf wrote:
Nargh... got latest wine ebuild 20050628 ebuild ..
ebuild /usr/local/portage/app-emulation/wine/wine-20050628.ebuild compile returns

checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

#define PACKAGE_BUGREPORT "wine-devel@winehq.org"
#define PACKAGE_NAME "Wine"
#define PACKAGE_STRING "Wine 20050628"
#define PACKAGE_TARNAME "wine"
#define PACKAGE_VERSION "20050628"

configure: exit 77

Ive set portage/package.keywords app-emulation/wine ~amd64 and tryed
ACCEPT_KEYWORDS=~amd64 ABI=x86 USE=amd64 LDFLAGS=-m32 emerge --ask wine


Have you checked if any of these solutions fix your problem? BTW, is there any special reason you don't emerge from the ebuild in the portage tree?
Back to top
View user's profile Send private message
madman2003
Apprentice
Apprentice


Joined: 20 Feb 2005
Posts: 178

PostPosted: Mon Jul 11, 2005 12:45 pm    Post subject: Reply with quote

The 20050628 ebuild compiled for me in 64 bits mode. Seems to work too :-) (haven't tried much yet)
Back to top
View user's profile Send private message
hulf
n00b
n00b


Joined: 09 Jun 2005
Posts: 47

PostPosted: Mon Jul 11, 2005 1:31 pm    Post subject: Reply with quote

How.. ??!
I have no problem compiling other unmasked programs...
Back to top
View user's profile Send private message
hulf
n00b
n00b


Joined: 09 Jun 2005
Posts: 47

PostPosted: Mon Jul 11, 2005 2:45 pm    Post subject: Reply with quote

I tryed to emerge wine-2005052..and get same error. I cant get past 5th configure line.. :o ... gues I stick with cedega...
I realy hoped wine-20050628 could fix evil genius and eve-online graphical bugs ( release notes ).
Back to top
View user's profile Send private message
madman2003
Apprentice
Apprentice


Joined: 20 Feb 2005
Posts: 178

PostPosted: Tue Jul 12, 2005 9:19 am    Post subject: Reply with quote

I just unmasked wine unstable and emerged it. I didn't do any extra patches, i simply wanted a working wine. (not for games)
Back to top
View user's profile Send private message
hulf
n00b
n00b


Joined: 09 Jun 2005
Posts: 47

PostPosted: Wed Jul 13, 2005 9:05 am    Post subject: Reply with quote

Ok..I know now the problem is
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find /usr/lib32/libc_nonshared.a
...related to this post:

    Compiling with the -m32 option generatest 32 bit binaries. To do so, 32 bit
    libraries are needed, too. The AMD roll provides several 32 bit libraries
    but not necessarily the ones you need to compile your test.c. Obviously, you
    have installed only a 64 bit version of the libstdc++ as it is skipped due
    to incompatibility.
    I had the same problem with some software. A work around to this problem is
    either to copy the needed libs from a 32 bit to a
    designated directory


Whats the easyest way to do that in gentoo ( pure 64 bit...till now ).
Back to top
View user's profile Send private message
dryadcito
Apprentice
Apprentice


Joined: 08 Oct 2004
Posts: 170
Location: Switzerland

PostPosted: Sat Jul 16, 2005 1:32 am    Post subject: Reply with quote

Could the black incos have something to do with this bug ?

https://bugs.gentoo.org/show_bug.cgi?id=96053


I had that problem with openoffice ( that bug report was started because of it ) but some people say there they have some issues with wine. I downgraded xorg-x11 and got rid of it. Good luck.
Back to top
View user's profile Send private message
superstoned
Guru
Guru


Joined: 17 Dec 2004
Posts: 432

PostPosted: Sun Jul 24, 2005 9:21 pm    Post subject: Reply with quote

according to http://winehq.org/?issue=284 we won't have to wait long until we have 64bit support, altough it'll take some time still.
Back to top
View user's profile Send private message
nly00471
n00b
n00b


Joined: 10 Aug 2004
Posts: 29
Location: Breda / Netherlands

PostPosted: Tue Aug 02, 2005 6:36 pm    Post subject: Reply with quote

Hello,

I've tried to emerge wine with

Code:
ACCEPT_KEYWORDS=~amd64 ABI=x86 USE=amd64 LDFLAGS=-m32 emerge --ask wine


but it fails, it ends with the following lines

Code:
>>> Source unpacked.
 * econf: updating wine-20050725/tools/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating wine-20050725/tools/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --build=x86_64-pc-linux-gnu CC=ccache gcc --sysconfdir=/etc/wine --with-curses --with-opengl --with-x --disable-trace --disable-debug
configure: WARNING: you should use --build, --host, --target
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for x86_64-pc-linux-gnu-gcc... ccache
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/wine-20050725/work/wine-20050725/config.log

!!! ERROR: app-emulation/wine-20050725 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.


and the config.log looks like

Code:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Wine configure 20050725, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/li$

## --------- ##
## Platform. ##
## --------- ##

hostname = localhost
uname -m = x86_64
uname -r = 2.6.12-gentoo-r4
uname -s = Linux
uname -v = #1 SMP Fri Jul 22 22:19:45 CEST 2005

/usr/bin/uname -p = AMD Opteron(tm) Processor 242
/bin/uname -X     = unknown

/bin/arch              = x86_64
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/lib/ccache/bin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib/portage/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3
PATH: /usr/qt/3/bin
PATH: /usr/kde/3.4/sbin
PATH: /usr/kde/3.4/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1424: checking build system type
configure:1442: result: x86_64-pc-linux-gnu
configure:1450: checking host system type
configure:1464: result: x86_64-pc-linux-gnu
configure:1504: checking whether make sets $(MAKE)
configure:1524: result: yes
configure:1541: checking for x86_64-pc-linux-gnu-gcc
configure:1567: result: ccache
configure:1849: checking for C compiler version
configure:1852: ccache --version </dev/null >&5
ccache: invalid option -- -
ccache, a compiler cache. Version 2.3
Copyright Andrew Tridgell, 2002

Usage:
        ccache [options]
        ccache compiler [compile options]
        compiler [compile options]    (via symbolic link)

Options:
-s                      show statistics summary
-z                      zero statistics
-c                      run a cache cleanup
-C                      clear the cache completely
-F <maxfiles>           set maximum files in cache
-M <maxsize>            set maximum size of cache (use G, M or K)
-h                      this help page
-V                      print version number
configure:1855: $? = 1
configure:1857: ccache -v </dev/null >&5
ccache: invalid option -- v
ccache, a compiler cache. Version 2.3
Copyright Andrew Tridgell, 2002

Usage:
        ccache [options]
        ccache compiler [compile options]
        compiler [compile options]    (via symbolic link)

Options:
-s                      show statistics summary
-z                      zero statistics
-c                      run a cache cleanup
-C                      clear the cache completely
-F <maxfiles>           set maximum files in cache
-M <maxsize>            set maximum size of cache (use G, M or K)
-h                      this help page
-V                      print version number
configure:1860: $? = 1
configure:1862: ccache -V </dev/null >&5
ccache version 2.3
Usage:
        ccache [options]
        ccache compiler [compile options]
        compiler [compile options]    (via symbolic link)

Options:
-s                      show statistics summary
-z                      zero statistics
-c                      run a cache cleanup
-C                      clear the cache completely
-F <maxfiles>           set maximum files in cache
-M <maxsize>            set maximum size of cache (use G, M or K)
-h                      this help page
-V                      print version number
configure:1860: $? = 1
configure:1862: ccache -V </dev/null >&5
ccache version 2.3
Copyright Andrew Tridgell 2002

Released under the GNU GPL v2 or later
configure:1865: $? = 0
configure:1888: checking for C compiler default output file name
configure:1891: ccache  -O3 -march=k8 -pipe  -m32 conftest.c  >&5
ccache: invalid option -- O
ccache, a compiler cache. Version 2.3
Copyright Andrew Tridgell, 2002

Usage:
        ccache [options]
        ccache compiler [compile options]
        compiler [compile options]    (via symbolic link)

Options:
-s                      show statistics summary
-z                      zero statistics
-c                      run a cache cleanup
-C                      clear the cache completely
-F <maxfiles>           set maximum files in cache
-M <maxsize>            set maximum size of cache (use G, M or K)
-h                      this help page
-V                      print version number
configure:1894: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "Wine"
| #define PACKAGE_TARNAME "wine"
| #define PACKAGE_VERSION "20050725"
| #define PACKAGE_STRING "Wine 20050725"
| #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:1933: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=x86_64-pc-linux-gnu
ac_cv_build_alias=x86_64-pc-linux-gnu
ac_cv_env_CC_set=set
ac_cv_env_CC_value=ccache
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value=' -O3 -march=k8 -pipe'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXFLAGS_set=set
ac_cv_env_CXXFLAGS_value=' -O3 -march=k8 -pipe'
ac_cv_env_CXX_set=set
ac_cv_env_CXX_value='ccache g++'
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value=-m32
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=x86_64-pc-linux-gnu
ac_cv_env_target_alias_set=set
ac_cv_env_target_alias_value=gcc
ac_cv_header_alsa_asoundlib_h=yes
ac_cv_header_audio_audiolib_h=no
ac_cv_header_audio_soundlib_h=no
ac_cv_header_cups_cups_h=yes
ac_cv_header_gif_lib_h=yes
ac_cv_header_jack_jack_h=no
ac_cv_header_jpeglib_h=yes
ac_cv_header_lcms_h=no
ac_cv_header_machine_soundcard_h=no
ac_cv_header_soundcard_h=no
ac_cv_header_sys_asoundlib_h=yes
ac_cv_header_sys_soundcard_h=no
ac_cv_host=x86_64-pc-linux-gnu
ac_cv_host_alias=x86_64-pc-linux-gnu
ac_cv_lib_asound_snd_pcm_open=yes
ac_cv_lib_glut_glutMainLoop=no
ac_cv_prog_CC=ccache
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ALLOCA=''
ALSALIBS=''
AR=''
ARTSCCONFIG=''
ARTSINCL=''
ARTSLIBS=''
AS='as --32'
AUDIOIOLIBS=''
BISON=''
CC='ccache'
CFLAGS=' -O3 -march=k8 -pipe'
COREFOUNDATIONLIB=''
CPP=''
CPPBIN=''
CPPFLAGS=''
CROSSCC=''
CROSSTEST=''
CROSSWINDRES=''
CRTLIBS=''
CURSESLIBS=''
CXX='ccache g++'
CXXFLAGS=' -O3 -march=k8 -pipe'
DEFS=''
DLLDEFS=' -DWINE_NO_DEBUG_MSGS -DWINE_NO_TRACE_MSGS'
DLLEXT=''
DLLFLAGS=''
DLLIBS=''
DLLTOOL=''
DLLWRAP=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
EXTRACFLAGS=''
FONTFORGE=''
FONTSSUBDIRS=''
FREETYPEINCL=''
FREETYPELIBS=''
GLU32FILES=''
GLUT32FILES=''
GLUT_LIBS=''
ICULIBS=''
IMPLIBEXT=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
IOKITLIB=''
LCMSLIBS=''
LD='ld -m elf_i386'
LDAPLIBS=''
LDCONFIG='/bin/true'
LDD=''
LDDLLFLAGS=''
LDEXECFLAGS=''
LDFLAGS='-m32'
LDLIBWINEFLAGS=''
LDPATH=''
LDSHARED=''
LEX=''
LEXLIB=''
LEX_OUTPUT_ROOT=''
LIBEXT=''
LIBOBJS=''
LIBPTHREAD=''
LIBS=''
LINT=''
LINTFLAGS=''
LN=''
LN_S=''
LTLIBOBJS=''
MAIN_BINARY=''
NASLIBS=''
OBJEXT=''
OPENGLFILES=''
OPENGL_LIBS=''
PACKAGE_BUGREPORT='wine-devel@winehq.org'
PACKAGE_NAME='Wine'
PACKAGE_STRING='Wine 20050725'
PACKAGE_TARNAME='wine'
PACKAGE_VERSION='20050725'
PATH_SEPARATOR=':'
RANLIB=''
SANEINCL=''
SANELIBS=''
SET_MAKE=''
SHELL='/bin/sh'
SOCKETLIBS=''
STRIP=''
TOOLSDIR=''
WIN16_FILES='$(WIN16_FILES)'
WIN16_INSTALL='$(WIN16_INSTALL)'
WINDRES=''
WINE_BINARIES=''
XFILES=''
XLEX=''
XLIB=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ac_ct_AR=''
ac_ct_AS=''
ac_ct_CC=''
ac_ct_CPPBIN=''
ac_ct_CXX=''
ac_ct_DLLTOOL=''
ac_ct_DLLWRAP=''
ac_ct_LD=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
ac_ct_WINDRES=''
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-pc-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
datadir='/usr/share'
exec_prefix='NONE'
ft_devel2=''
ft_devel=''
host='x86_64-pc-linux-gnu'
host_alias='x86_64-pc-linux-gnu'
host_cpu='i386'
host_os='linux-gnu'
host_vendor='pc'
includedir='${prefix}/include'
infodir='/usr/share/info'
libdir='/usr/lib32'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
oldincludedir='/usr/include'
prefix='/usr'
program_transform_name='s,x,x,'
sane_devel=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc/wine'
target_alias='gcc'

## ------------- ##
## Output files. ##
## ------------- ##

MAKE_DLL_RULES=''
MAKE_LIB_RULES=''
MAKE_PROG_RULES=''
MAKE_RULES=''
MAKE_TEST_RULES=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_BUGREPORT "wine-devel@winehq.org"
#define PACKAGE_NAME "Wine"
#define PACKAGE_STRING "Wine 20050725"
#define PACKAGE_TARNAME "wine"
#define PACKAGE_VERSION "20050725"

configure: exit 77


Can somebody give a bit of help
_________________
Tyan S2885ANRF, 2x opetron242, 2x 2x512MB (2GB total), Gainward 6800, 2x WD Raptor 36GB
Back to top
View user's profile Send private message
nly00471
n00b
n00b


Joined: 10 Aug 2004
Posts: 29
Location: Breda / Netherlands

PostPosted: Thu Aug 11, 2005 10:22 am    Post subject: Reply with quote

I got "wine-20050725" complied with

Code:

ACCEPT_KEYWORDS=~amd64 USE=amd64 emerge wine


after I corrected some links in ccache

more about that you can find in https://forums.gentoo.org/viewtopic-p-2640969.html#2640969
so al credits to Roguelazer
_________________
Tyan S2885ANRF, 2x opetron242, 2x 2x512MB (2GB total), Gainward 6800, 2x WD Raptor 36GB
Back to top
View user's profile Send private message
cwest
n00b
n00b


Joined: 13 Jun 2005
Posts: 72
Location: Oslo, Norway

PostPosted: Fri Aug 12, 2005 6:41 pm    Post subject: Reply with quote

Just dropping in to tell that the newest version in portage seems to build somewhat cleanly, and works (although some bugs, still, but no need to make bugzilla a deprecated feature? ;) )
Back to top
View user's profile Send private message
Enverex
Guru
Guru


Joined: 02 Jul 2003
Posts: 501
Location: Worcester, UK

PostPosted: Mon Aug 22, 2005 4:07 pm    Post subject: Reply with quote

I'm also getting the "checking whether the C compiler works... configure: error: cannot run C compiled programs." when I try and compile Wine. Did anyone manage to find a way around that? (nothing wrong with my CFLAGs or exporting).
Back to top
View user's profile Send private message
andrewd18
Guru
Guru


Joined: 11 Apr 2004
Posts: 364
Location: Wisconsin, USA

PostPosted: Tue Aug 23, 2005 2:07 am    Post subject: Reply with quote

NightShade737 wrote:
I'm also getting the "checking whether the C compiler works... configure: error: cannot run C compiled programs." when I try and compile Wine. Did anyone manage to find a way around that? (nothing wrong with my CFLAGs or exporting).


It's a FAQ.

Linky Dink

~~ Andrew D.
_________________
Keep Your Toolchain Stable! - emwrap.sh

There's no place like ::1
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Goto page Previous  1, 2, 3 ... 7, 8, 9, 10, 11  Next
Page 8 of 11

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum