Closed GoogleCodeExporter closed 9 years ago
Are you setting environment variables to look in the Wine lib directory:
export
DYLD_FALLBACK_LIBRARY_PATH="${HOME}/wine/wine-1.1.36/lib:/usr/X11/lib:/usr/lib"
export PATH="${HOME}/wine/wine-1.1.36/bin:${PATH}"
These must be in place every time Wine is run. You can add them to a shell
startup
file as well - use ~/.profile, ~/.bash_profile, ~/.bashrc if you're using
sh/bash, or
a ~/.cshrc, etc., for csh/tcsh.
Original comment by rwoodsm...@gmail.com
on 18 Jan 2010 at 10:08
Hmmm. I just tried that, but i'm still getting the freetype error.
Original comment by fbig...@gmail.com
on 20 Jan 2010 at 3:51
Can you send the output of the "env" command run from a terminal?
Do you have a file called ~/.MacOSX/environment.plist? This can also be
verified
with a terminal; it may override shell environment settings. This is a Mac OS
X-specific property list that can override shell settings.
Do you have anything in any of the following files:
~/.bash_profile
~/.bashrc
~/.profile
~/.shrc
~/.cshrc
~/.tcshrc
Trunk was updated to Wine 1.1.37 today, but there were no changes to
freetype/fontconfig. I've not encountered this error before, either on
machines with
or without MacPorts, Fink, Gentoo, homebrew, etc. I'm a bit stumped as to
what's
causing this, or if it's even a run-time or compile-time error. Paths are
explicitly
set in the build script, so it should find the custom-built versions of any
packages
in ~/wine/wine-X.X.XX before any other builds of freetype/fontconfig.
Original comment by rwoodsm...@gmail.com
on 23 Jan 2010 at 1:53
Sorry it took so long to get back. I was busy with some other school stuff.
The output of env is :
Juliet:~ AndyBob$ env
MANPATH=/opt/local/man:
TERM_PROGRAM=Apple_Terminal
TERM=xterm-color
SHELL=/bin/bash
TMPDIR=/var/folders/Yk/Ykdwq7iNHbmhq3cYLjAAUE+++TI/-Tmp-/
Apple_PubSub_Socket_Render=/tmp/launch-xYSqNo/Render
TERM_PROGRAM_VERSION=272
USER=AndyBob
COMMAND_MODE=unix2003
SSH_AUTH_SOCK=/tmp/launch-Hi8h58/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:0:0
PATH=/opt/local/bin:/opt/local/sbin:/Library/Frameworks/Python.framework/Versio
ns/Current/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr
/loc
al/bin:/usr/X11/bin
PWD=/Users/AndyBob
LANG=en_US.UTF-8
SHLVL=1
HOME=/Users/AndyBob
LOGNAME=AndyBob
DISPLAY=/tmp/launch-NgLGyv/:0
_=/usr/bin/env
Juliet:~ AndyBob$
And no, i do not have a file located in the .MacOSX folder called
environment.plist. I
don't even have a folder called .MacOSX.
In the .bash_profile:
# Setting PATH for MacPython 2.6
# The orginal version is saved in .bash_profile.pysave
PATH="/Library/Frameworks/Python.framework/Versions/Current/bin:${PATH}"
export PATH
##
# Your previous /Users/AndyBob/.bash_profile file was backed up as
/Users/AndyBob/.bash_profile.macports-saved_2010-01-12_at_14:18:14
##
# MacPorts Installer addition on 2010-01-12_at_14:18:14: adding an appropriate
PATH variable for use with MacPorts.
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
# Finished adapting your PATH environment variable for use with MacPorts.
in the .bashrc:
xhost +
in the .profile:
export PATH=`pwd`/depot_tools:"$PATH"
export DYLD_FALLBACK_LIBRARY_PATH="${HOME}/wine/wine-
1.1.36/lib:/usr/X11/lib:/usr/lib"
export PATH="${HOME}/wine/wine-1.1.36/bin:${PATH}"
And i don't have either .shrc, cshrc, or tcshrc.
Original comment by fbig...@gmail.com
on 30 Jan 2010 at 11:18
[deleted comment]
Also, trying to upgrade to the newest version of wine, here's what I get:
Juliet:wine-1.1.37 AndyBob$ ./configure
checking build system type... i386-apple-darwin10.2.0
checking host system type... i386-apple-darwin10.2.0
checking whether make sets $(MAKE)... yes
checking for gcc... 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... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for cpp... cpp
checking for the directory containing the Wine tools... $(TOPOBJDIR)
checking for flex... flex
checking whether flex is recent enough... yes
...
...
...
checking gnutls/gnutls.h usability... no
checking gnutls/gnutls.h presence... no
checking for gnutls/gnutls.h... no
checking for -lncurses... libncurses.5.4.dylib
checking for mousemask... yes
checking for sane-config... no
checking sane/sane.h usability... no
checking sane/sane.h presence... no
checking for sane/sane.h... no
checking for gphoto2-config... no
checking for gphoto2-port-config... no
checking gphoto2-camera.h usability... no
checking gphoto2-camera.h presence... no
checking for gphoto2-camera.h... no
checking for freetype-config... freetype-config
checking for -lfreetype... not found
configure: error: FreeType 32-bit development files not found. Fonts will not
be
built.
Use the --without-freetype option if you really want this.
Juliet:wine-1.1.37 AndyBob$
It's seeing there's something wrong with freetype here too
Original comment by fbig...@gmail.com
on 31 Jan 2010 at 12:04
You'll need to move the contents of your .profile to the *end* of your
.bash_profile
file and restart your terminal. MacPorts is placing itself in your path before
the
Wine install in ~/wine/wine-1.1.36. You can see this in the output of the env
command - the PATH variable lists /opt/local before anything else. Shell
startup
file processing is described here:
http://www.comptechdoc.org/os/linux/howlinuxworks/linux_hlbash.html
Please also note that you can't simply download Wine source code and run
configure;
you'll need to run through the entire build script again, and the installation
for
1.1.37 will be put into ~/wine/wine-1.1.37.
Let me know if this helps with the FreeType issue you're seeing!
Original comment by rwoodsm...@gmail.com
on 31 Jan 2010 at 8:55
Excellent. So far so good. I think we have a go! Thanks for the help.
I'll update if something goes wrong.
Original comment by fbig...@gmail.com
on 31 Jan 2010 at 7:09
Closing - seems like this is working as expected.
Original comment by rwoodsm...@gmail.com
on 24 Feb 2010 at 2:29
Original issue reported on code.google.com by
fbig...@gmail.com
on 15 Jan 2010 at 2:35