[Buildroot] Including wine package - Reg

[Buildroot] Including wine package - Reg

[Arunkumar Vijayakumar]

Dear Team,

I'm including wine package in buildroot to run my windows application. But
after building and testing with Qemu, when i type the command wine, its says

-sh: wine: not found, even though the wine binaries are in /usr/bin

Can you please help me with the solution.


Thanks
Arun Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/f82c365a/attachment.html>

[Buildroot] Including wine package - Reg

[Thomas Petazzoni]

Dear Arunkumar Vijayakumar,

On Tue, 9 Apr 2013 01:19:42 +0530, Arunkumar Vijayakumar wrote:

> I'm including wine package in buildroot to run my windows
> application. But after building and testing with Qemu, when i type
> the command wine, its says
> 
> -sh: wine: not found, even though the wine binaries are in /usr/bin
> 
> Can you please help me with the solution.

Could you submit your wine package so that we can try to reproduce the
problem?

Which architecture are you targeting? What is the output of "file
output/target/usr/bin/wine" ?

Best regards,

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

[Buildroot] Including wine package - Reg

[Arunkumar Vijayakumar]

Hello Thomas

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.

Thanks & Regards
Arun Kumar



On Tue, Apr 9, 2013 at 2:42 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Arunkumar Vijayakumar,
>
> On Tue, 9 Apr 2013 01:19:42 +0530, Arunkumar Vijayakumar wrote:
>
> > I'm including wine package in buildroot to run my windows
> > application. But after building and testing with Qemu, when i type
> > the command wine, its says
> >
> > -sh: wine: not found, even though the wine binaries are in /usr/bin
> >
> > Can you please help me with the solution.
>
> Could you submit your wine package so that we can try to reproduce the
> problem?
>
> Which architecture are you targeting? What is the output of "file
> output/target/usr/bin/wine" ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/eca589d6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine.rar
Type: application/rar
Size: 627 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/eca589d6/attachment-0001.rar>

[Buildroot] Including wine package - Reg

[Thomas Petazzoni]

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

[Buildroot] Including wine package - Reg

[Arunkumar Vijayakumar]

Thomas,

Initially I tried with the autotools type, but it throwed a lot of errors
hence I switched to generic one. Let me post the error details when
autotools used.


Many Thanks
Arun Kumar


On Tue, Apr 9, 2013 at 3:01 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/bef1cb86/attachment.html>

[Buildroot] Including wine package - Reg

[Arunkumar Vijayakumar]

Hello Thomas,

I tried with the autotools options as per your suggestion and got the
error, please find the attached config.log for your kind reference.

Kindly advice me where Im making mistakes ?

Thanks
Arun Kumar




On Tue, Apr 9, 2013 at 3:14 AM, Arunkumar Vijayakumar <
arun.magzion@gmail.com> wrote:

> Thomas,
>
> Initially I tried with the autotools type, but it throwed a lot of errors
> hence I switched to generic one. Let me post the error details when
> autotools used.
>
>
> Many Thanks
> Arun Kumar
>
>
> On Tue, Apr 9, 2013 at 3:01 AM, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/cc2e4cc0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 9003 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130409/cc2e4cc0/attachment-0001.obj>

[Buildroot] Including wine package - Reg

[Thomas Petazzoni]

Dear Arunkumar Vijayakumar,

On Tue, 9 Apr 2013 04:10:04 +0530, Arunkumar Vijayakumar wrote:

> I tried with the autotools options as per your suggestion and got the
> error, please find the attached config.log for your kind reference.
> 
> Kindly advice me where Im making mistakes ?

It doesn't find the cross-compiler, so something looks really wrong in
your Buildroot build.

Can you do:

	make clean
	make 2>&1 | tee build.log

Put the contents of build.log on some pastebin site, and give us the
URL?

Please also pastebin your Buildroot .config file.

Thanks,

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

[Buildroot] Including wine package - Reg

[Arunkumar Vijayakumar]

Dear Thomas,

I found the issue with the cross compiler and fixed it. Now when I tried
executing wine package using
$ make wine v=1 in buildroot

It throwed an error stating to use --with-wine-tools for cross compiling,
hence I used
WINE_CONF_OPT = --with-wine-tools=$(BUILD_DIR)/wine-$(WINE_VERSION)

Again I got an error of missing Xlib/Xfree86 package, though I have
installed those using apt-get install xorg xorg-dev *libx*11-dev in my
ubuntu 12.04 desktop system.

But it didnt work hence i forced to use the following line in .mk file and
it got worked.
WINE_CONF_OPT += --x-libraries=/usr/lib/X11
WINE_CONF_OPT += --x-includes=/usr/include/X11
WINE_CONF_OPT += --with-x

My point is,
1. Will including the path in .mk file (--x-libraries=/usr/lib/X11)  while
compiling for embedded system require the same folders in the Initrd and
binaries?
2. Do I need to include xorg graphics package for the same and if so, will
it be created in the same path like the above one ?

Thanks
Arun Kumar

On Tue, Apr 9, 2013 at 11:46 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Arunkumar Vijayakumar,
>
> On Tue, 9 Apr 2013 04:10:04 +0530, Arunkumar Vijayakumar wrote:
>
> > I tried with the autotools options as per your suggestion and got the
> > error, please find the attached config.log for your kind reference.
> >
> > Kindly advice me where Im making mistakes ?
>
> It doesn't find the cross-compiler, so something looks really wrong in
> your Buildroot build.
>
> Can you do:
>
>         make clean
>         make 2>&1 | tee build.log
>
> Put the contents of build.log on some pastebin site, and give us the
> URL?
>
> Please also pastebin your Buildroot .config file.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130410/5f64cbb8/attachment.html>

[Buildroot] Including wine package - Reg

[Thomas Petazzoni]

Dear Arunkumar Vijayakumar,

On Wed, 10 Apr 2013 02:49:24 +0530, Arunkumar Vijayakumar wrote:

> I found the issue with the cross compiler and fixed it. Now when I tried
> executing wine package using
> $ make wine v=1 in buildroot
> 
> It throwed an error stating to use --with-wine-tools for cross compiling,
> hence I used
> WINE_CONF_OPT = --with-wine-tools=$(BUILD_DIR)/wine-$(WINE_VERSION)

This looks odd. Why would the wine package require a reference to its
own source directory? Doesn't sound correct.

> Again I got an error of missing Xlib/Xfree86 package, though I have
> installed those using apt-get install xorg xorg-dev *libx*11-dev in my
> ubuntu 12.04 desktop system.
> 
> But it didnt work hence i forced to use the following line in .mk file and
> it got worked.
> WINE_CONF_OPT += --x-libraries=/usr/lib/X11
> WINE_CONF_OPT += --x-includes=/usr/include/X11
> WINE_CONF_OPT += --with-x

Do you realize that Buildroot is used for *cross* compilation?
Therefore pointing the compilation to /usr/lib or /usr/include is just
plain wrong, and is precisely what Buildroot avoids everywhere. What
you're doing here is completely incorrect and has absolutely no chance
of working.

If wine depends on X11 libraries, then your wine package must depend on
the appropriate X11 Buildroot packages.

Best regards,

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

[Buildroot] Including wine package - Reg

[Arnout Vandecappelle]

On 09/04/13 23:22, Thomas Petazzoni wrote:
>> It throwed an error stating to use --with-wine-tools for cross compiling,
>> >hence I used
>> >WINE_CONF_OPT = --with-wine-tools=$(BUILD_DIR)/wine-$(WINE_VERSION)
> This looks odd. Why would the wine package require a reference to its
> own source directory? Doesn't sound correct.
>

  wine-tools is a separate (host) package. Quick web search doesn't turn 
up any archives, just git://source.winehq.org/git/tools.git


  Arunkumar, I'm afraid integrating wine in buildroot will turn out to be 
quite ambitious... I don't know what you are trying to do, but if it is 
just a matter of building a very customized system and you don't really 
care about cross-compilation, then you may be better off with e.g. Gentoo.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F