Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Including wine package - Reg
Date: Mon, 8 Apr 2013 23:31:56 +0200	[thread overview]
Message-ID: <20130408233156.0ab27a38@skate> (raw)
In-Reply-To: <CAGK4xy5fzi5F0C_CaAq0e2JJmdUhNKD3ZuBqE8cBw8dsV+HQrw@mail.gmail.com>

Dear Arunkumar Vijayakumar,

On Tue, 9 Apr 2013 02:53:44 +0530, Arunkumar Vijayakumar wrote:

> Thanks for your quick reply.
> Im using i386 architecture and the variant to be i686 and creating a
> package wine with version 1.5.23. I also used the X Server package for GUI
> and followed steps as one in the below link
> http://agentoss.wordpress.com/2011/03/06/building-a-tiny-x-org-linux-system-using-buildroot/
> 
> 
> Please find the attachment for the config.in & wine.mk file for your
> reference.
> 
> Let me know if you need any additional details ?
> Also let me know why i couldn't able to use file, ldd, readelf commands in
> the prompt.

The problem is pretty clear in your wine.mk. You should use the
autotools-package infrastructure since Wine uses the autotools. This
will ensure the appropriate arguments and environment variables are
passed to the configure script. At the moment you're just calling it
using './configure --prefix=/usr', so it uses your glibc-based native
compiler to build wine... which generates a wine binary that cannot
work, because it doesn't match the C library you have on your target.

Could you submit a real patch for the wine package once you've made
some progress with this? Thanks!

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-04-08 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 19:49 [Buildroot] Including wine package - Reg Arunkumar Vijayakumar
2013-04-08 21:12 ` Thomas Petazzoni
2013-04-08 21:23   ` Arunkumar Vijayakumar
2013-04-08 21:31     ` Thomas Petazzoni [this message]
2013-04-08 21:44       ` Arunkumar Vijayakumar
2013-04-08 22:40         ` Arunkumar Vijayakumar
2013-04-09 18:16           ` Thomas Petazzoni
2013-04-09 21:19             ` Arunkumar Vijayakumar
2013-04-09 21:22               ` Thomas Petazzoni
2013-04-09 21:58                 ` Arnout Vandecappelle

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=20130408233156.0ab27a38@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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