Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH try 4] wine: New package
Date: Thu, 22 Jan 2015 00:20:02 +0100	[thread overview]
Message-ID: <54C03422.8050500@dawncrow.de> (raw)
In-Reply-To: <54C03142.4010105@openwide.fr>

Am 22.01.2015 um 00:07 schrieb Romain Naour:
> I'm building your wine package on my 64bits host and the build fail
> because freetype library in HOST_DIR is build for it, but wine is
> build for 32bits host.
> 
> see my config.log output:
> configure:10886: checking for -lfreetype
> configure:10911: /usr/bin/gcc -m32 -o conftest -O2 -I/home/naourr/git/buildroot/test/wine/host/usr/include -I/home/naourr/git/buildroot/test/wine/host/usr/include -I/home/naourr/git/buildroot/test/wine/host/usr/include/freetype2   -L/home/naourr/git/buildroot/test/wine/host/lib -L/home/naourr/git/buildroot/test/wine/host/usr/lib -Wl,-rpath,/home/naourr/git/buildroot/test/wine/host/usr/lib conftest.c -lfreetype -L/home/naourr/git/buildroot/test/wine/host/usr/lib -lfreetype    >&5
> /usr/bin/ld: skipping incompatible /home/naourr/git/buildroot/test/wine/host/usr/lib/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: skipping incompatible /home/naourr/git/buildroot/test/wine/host/usr/lib/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: skipping incompatible /usr/lib64/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: cannot find -lfreetype
> /usr/bin/ld: skipping incompatible /home/naourr/git/buildroot/test/wine/host/usr/lib/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: skipping incompatible /home/naourr/git/buildroot/test/wine/host/usr/lib/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: skipping incompatible /usr/lib64/libfreetype.so when searching for -lfreetype
> /usr/bin/ld: cannot find -lfreetype
> collect2: error: ld returned 1 exit status
> 
> It seems that --enable-win64 must be added to HOST_WINE_CONF_OPTS
> for 64bits host.

Wow, good catch, thanks!
Guess it didn't failed on my machine because i also have 32-bit freetype installed on the host.

  reply	other threads:[~2015-01-21 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 22:09 [Buildroot] [PATCH try 4] wine: New package André Hentschel
2015-01-21 23:07 ` Romain Naour
2015-01-21 23:20   ` André Hentschel [this message]
2015-01-21 23:35 ` Yann E. MORIN
2015-01-22 22:13   ` André Hentschel

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=54C03422.8050500@dawncrow.de \
    --to=nerv@dawncrow.de \
    --cc=buildroot@busybox.net \
    /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