SliTaz SliTaz Forum

You are not logged in.

#1 2012-10-16 08:20:03

SSamiK
Member
Registered: 2012-10-16
Posts: 2

Compile wine from source

The version of wine in tazpkg dosent quite fill my needs, so I try to compile it from source. however, I'm having some trouble getting ./configure to pickup on packages installed on the system.

Btw - i runt Slitaz 4

This is the tail of ./configure --prefix=/usr --without-freetype --verbose

configure: WARNING: prelink not found, base address of core dlls won't be set correctly.

configure: WARNING: libxrender development files not found, XRender won't be supported.

configure: WARNING: OpenGL development headers not found.

OpenGL and Direct3D won't be supported.

configure: WARNING: libxslt development files not found, xslt won't be supported.

configure: WARNING: OpenSSL development files not found, SSL won't be supported.

configure: WARNING: libjpeg development files not found, JPEG won't be supported.

configure: WARNING: libpng development files not found, PNG won't be supported.

configure: Finished.  Do 'make' to compile Wine.

Lets break it down: Prelink - no package in tazpkg?

libjpg, libpng, openssl - and most of the othes are installed with dev-packages.

f.eks:

tazpkg get-install openssl-dev --forced

openssl-dev-1.0.0g already in the cache : /var/cache/tazpkg/4.0/packages

Installation of : openssl-dev

================================================================================

Copying openssl-dev...                                               [ OK ]

Extracting openssl-dev...                                            [ OK ]

Extracting the pseudo fs... (lzma)                                   [ OK ]

Installing openssl-dev...                                            [ OK ]

Removing all tmp files...                                            [ OK ]

================================================================================

openssl-dev (1.0.0g) is installed.

now, what to do? I've never experienced that the system wont pickup on installed packages.. Any hints on how to solve would be great.

Offline

#2 2012-10-16 08:46:43

lexeii
Administrator
Registered: 2012-03-21
Posts: 1,853

Re: Compile wine from source

Hi SSamiK,

Execuse me, but I have no time to repeat your experience. I only want to say that the better way to compile packages under SliTaz is using cook and receipts.

Read local Cookutils documentation (under SliTaz menu - Documentation), search http://doc.slitaz.org for cooking receipts, pick existing wine receipt from wok http://hg.slitaz.org and iterate to edit it and compile until you have all you need.

Offline

#3 2012-10-16 09:33:27

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Compile wine from source

you should check the recent post,someone, i think mojo, has given a link to a more recent version (i think it is 1.4.1 but this is a month old and i am not using slitas at this time)

That last version is very good.

Offline

#4 2012-10-16 11:11:39

SSamiK
Member
Registered: 2012-10-16
Posts: 2

Re: Compile wine from source

Yeah... I found the cooking and receipts to be a bit comprehensive and unnecessary to learn for my needs. I prefer doing things the generic-source-code-way, to keep the changes between distros as small as possible. I'm still having a hard time figuring out how things are normally done here in Slitaz though, so I might be wrong. But as this just is a old computer that my dad uses to browse the web, I don't really want to spend time learning a new way of doing things just to install a few packages. 

All I really want is my system to recognize the installed packages so that I can install source code in the traditional way. In my head, that should not be that hard - if Slitaz works as a normal linux distro.

Thanks for your input, though!

Offline

#5 2012-10-16 15:38:57

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: Compile wine from source

Hi SSamiK

Yes slitaz work exact an another normal distro, but only if you add source and total dependency request step by step. I have compiled various packages on external installation at normal use, but the complete final distro is very big, a way to reduce it is to carry the only application created, or repack and reinstall in to original the result.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]