LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-28-2017, 08:09 PM   #16
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,890

Rep: Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905Reputation: 1905

Did you specify -i for the input package? If I leave it out, it gives me the same error.

Code:
jbhansen@craven-moorhead:~$ convertpkg-compat32 libpng-1.4.20-i486-1_slack14.1.txz
** Please supply a valid input package! **

Usage: /usr/sbin/convertpkg-compat32 <-i input_package_file_name> [-o output_package_file_name] [-d output_directory] [-s custom_slack_desc] [-e custom_package_extension]

convertpkg-compat32 is used to convert a 32-bit Slackware package
into a '32-bit compatibility' package, for installion on 64-bit Slackware.

required parameters::
  -i input_package_file_name     : 32-bit package to convert
optional parameters::
  -d destination_directory       : create package in this directory
  -e extension                   : use another valid extension instead of 'txz'
  -o output_package_file_name    : use custom output package filename
  -s output_slack_desc           : custom slack-desc file to use for new package

environment variables:
  ARCH   (target architecture; defaults to $(uname -m))
  BUILD  (build number for output package; defaults to same as input package.
          output_package_file_name overrides this value)
  TAG    (build tag, defaults to compat32))
  OUTPUT (location to create the package; defaults to /tmp)
  TMP    (location for temporary files; defaults to /tmp)

jbhansen@craven-moorhead:~$ convertpkg-compat32 -i libpng-1.4.20-i486-1_slack14.1.txz
Converting package libpng (version 1.4.20) to libpng-compat32-1.4.20-x86_64-1_slack14.1compat32.txz (libpng-compat32)
Exploding package /home/jbhansen/libpng-1.4.20-i486-1_slack14.1.txz in current directory:
--cut--
 
Old 03-29-2017, 09:03 AM   #17
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Once again, Bassmadrigal, I am in your debt as I did indeed assume the Help file was indicating an identifier not required in the command. That did build the proper compat32 package which I can see since now wine reports it as the library being used. Unfortunately for me it still says 1.4.x is incompatible with the 1.2.50 required. Maybe I'm just getting old (new tricks?) but it took me awhile to be dead certain exactly what had been compiled with 1.2.50 and now it looks as if that refers to WoW, itself. So next is attempting to build a compat32 pkg for that exact libpng version and dumping 1.4-legacy.

FWIW this isn't some frivolous thing to me as I use this game as post stroke therapy for language, problem solving, and eye/hand coordination. So my thanks for all who have helped is not only sincere, but quite important to me.

Wish me luck
 
Old 03-30-2017, 08:00 AM   #18
GreenFireFly
Member
 
Registered: Jul 2013
Posts: 181

Rep: Reputation: Disabled
Hello Everyone,

I use wine 64bit from winehq.org with multilib. I heard someone mention in a previous post that the wine 64bit version has stability issues. Can anyone explain what stability issues wine 64bit has?
 
Old 04-12-2017, 12:30 PM   #19
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
OK It's Hair Pulling time as this make zero sense to me now. No matter what I do I still get that damned "fixme libpng" error even though the app seems to work just fine. The reason I want to fix it is it seems the app gets obsessed with the error and logging in or out takes a very long time when it used to be very fast. Ive even tried turning off all fixme messages both with the command

Code:
  WINEDEBUG=fixme-all
and when that didn't do the job

Code:
 wine SET WINEDEBUG=fixme-all
AND when that also did not do the job

running wine regedit and adding
Code:
HKEY_CURRENT_USER
Environment
WINEDEBUG        default     "fixme-all"
and still error reporting persists and seems to hang the system up with wait times that never used to occur. At this point it is probably me, so please help, what am I doing wrong?

PS - Sorry GreenFireFly I'm not privy to 64 bit Wine issues, good or bad.

PPS - For reference, the libpng error is
Code:
libpng warning: Application was compiled with png.h from libpng-1.6.23
libpng warning: Application  is  running with png.c from libpng-1.4.20

Last edited by enorbet; 04-12-2017 at 12:39 PM.
 
Old 04-13-2017, 05:27 PM   #20
GreenFireFly
Member
 
Registered: Jul 2013
Posts: 181

Rep: Reputation: Disabled
Hello Everyone,

@enorbet My guess is that when wine was compiled you had 2 libpng installed so when you
you run the program is still looking for the missing libpng.

BTW: Try WINEDEBUG=-all.

Last edited by GreenFireFly; 04-13-2017 at 05:57 PM.
 
Old 04-14-2017, 02:15 PM   #21
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Well I have the following libpng packages installed now and at the time of the latest wine compile

*libpng-1.6.23-x86_64-1
*libpng-compat32-1.4.20-x86_64-1Slack14.1compat32
*libpng-compat32-1.6.23-x86_64-1compat32

One of the puzzling factors that I don't understand at all is that I see png.h in "/usr/include/libpng16" but though the apps error messages say it is "running with png.c from libpmg-1.4.20" I can't find any file named png.c anywhere of any version. What's messing me up on top of that is that I've tried installing four different earlier versions and the version numbers change but it always says it's running with some png.c I can't find. I still have a pure 32bit 14.0 system installed on another partition and it also has png.h (no png.c) in "/usr/include/libpng14" so I suppose my main problem is that I really don't understand what the error messages are trying to tell me and I doubt that it really matters other than wasting resources with voluminous error reporting.
 
Old 04-14-2017, 02:28 PM   #22
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,511

Rep: Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741
Why do you have two versions of libpng-compat32 installed? Recipe for disaster.
 
1 members found this post helpful.
Old 04-14-2017, 07:39 PM   #23
GreenFireFly
Member
 
Registered: Jul 2013
Posts: 181

Rep: Reputation: Disabled
Hello Enorbet,

Some applications come with a version libpng like opencv. If you have that installed you will need to recompile. Not sure if wine comes with it's own version of libpng but if it does then you will need turn one of too.

Add flag BUILD_PNG=OFF to cmake. On the cmake results you'll see under Media I/O, PNG: "path to your libpng.so" instead of Build.

For wine i think it's this.
PNG_CFLAGS="-I /usr/include/libpng16"
PNG_LIBS="-L /usr/lib/"

Here is an article on using cflags.
https://unix.stackexchange.com/quest...s-to-configure

Here are few articles with similiar problem to yours just incase you need more info.

http://stackoverflow.com/questions/5...on-and-library

http://stackoverflow.com/questions/4...ary-in-rstudio

Last edited by GreenFireFly; 04-14-2017 at 08:29 PM.
 
Old 04-15-2017, 04:39 PM   #24
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 759
Blog Entries: 2

Rep: Reputation: 246Reputation: 246Reputation: 246
enorbet,
As Alien Bob mentioned, you really do not want multiple versions of libpng floating around your system. For 14.2, you should ONLY have libpng-1.6.27 (and for 64-bit multilib, libpng-compat32-1.6.2 from Alien Bob's multilib packages), as well as any other /patches releases for 14.2 since last Summer!

I recommend that you compile wine-2.0 exactly AS-IS from Slackbuilds.org. A lot of work has gone into making sure that script works. I would avoid wine-staging until you get wine-2.0 working. If configure or make fails, do NOT modify the script but rather FIX your system. Your libpng errors are YOUR fault, not wine's. You will need a FULL installation of Alien Bob's multilib packages. He provides detailed instructions. You can NOT pick and choose what to install. Wine has a lot of dependencies with and without autodetection, so be sure you have a FULL, STOCK Slackware with full multilib installation. Or compile in a VM if you current system is buggered up with customizations (which some call "optimizations").

Like I said in a post above, I've been running wine since, heck, 0.9x something, long before 1.0, on Slackware for a very wide variety of software. I'm running Skyrim on wine-2.0 now. Any libpng errors in wine where fixed a very long time ago.

Have fun !

Greenfly, PNG_CFLAGS and PNG_LIBS are not required to build wine.
 
1 members found this post helpful.
Old 04-16-2017, 01:12 PM   #25
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Quote:
Originally Posted by Alien Bob View Post
Why do you have two versions of libpng-compat32 installed? Recipe for disaster.
Hello Alien Bob. This is just the recent setup. I have tried having just the 1.6x and the 1.4x as compat32 to no avail and if it isn't obvious already I have fallen back (down?) to ye olde Shotgun Approach because I really do not understand the problem. The app in question seems to run fine with the exception of some rather long delays in some processes like logging in and out that never existed before but I don't see how libpng has anything to do with that. Wine also reports wininet issues (it is not installed nor do I want to install it) vut connection seems quite normal. I also get rare crashes (maybe 2 per 40 hours of runtime) but I'm pretty certain that is just LUA errors in private server WoW.

Any suggestions?
 
Old 04-16-2017, 01:22 PM   #26
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Quote:
Originally Posted by kingbeowulf View Post
enorbet,
As Alien Bob mentioned, you really do not want multiple versions of libpng floating around your system. For 14.2, you should ONLY have libpng-1.6.27 (and for 64-bit multilib, libpng-compat32-1.6.2 from Alien Bob's multilib packages), as well as any other /patches releases for 14.2 since last Summer!

I recommend that you compile wine-2.0 exactly AS-IS from Slackbuilds.org. A lot of work has gone into making sure that script works. I would avoid wine-staging until you get wine-2.0 working. If configure or make fails, do NOT modify the script but rather FIX your system. Your libpng errors are YOUR fault, not wine's. You will need a FULL installation of Alien Bob's multilib packages. He provides detailed instructions. You can NOT pick and choose what to install. Wine has a lot of dependencies with and without autodetection, so be sure you have a FULL, STOCK Slackware with full multilib installation. Or compile in a VM if you current system is buggered up with customizations (which some call "optimizations").

Like I said in a post above, I've been running wine since, heck, 0.9x something, long before 1.0, on Slackware for a very wide variety of software. I'm running Skyrim on wine-2.0 now. Any libpng errors in wine where fixed a very long time ago.

Have fun !
Thank you, kingbeowulf, for your considered reply. Just FTR I suffer no illusions about fault which I KNOW are my own which is exactly why I have stuck with Slackware since version 6. Does software sometimes present "interesting" problems? Of course some does, but if I wasn't confidant that, with a little help, could sort it out, I wouldn't be posting here accepting the responsibility of properly administering my system. I am new to 64bit Multilib and still don't see any major advantage and it comes at a steep increase in complexity, so I am likely not AS confidant as I am in 32 bit.

It is my intention to struggle with wine-staging a little longer as I do see benefits to it. That said, you have given me good instructions for a "safety net" if I am unsuccessful. Thanks again.
 
Old 04-16-2017, 01:54 PM   #27
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,511

Rep: Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741Reputation: 3741
Quote:
Originally Posted by kingbeowulf View Post
Alien Bob's usually will work fine but you have no control over what he had installed when he compiled it.
To the contrary. It is very clear what I have installed when I compile software. I always compile on a full installation of Slackware. The only 3rd party packages that are added before I start compiling are documented in the header section of my SlackBuild script. The runtime dependencies of the resulting package are documented in the slack-required file inside the 'build' directory.

Quote:
I highly recommend using the build scripts from SBo, with a few modifications, for example:
Code:
if [ "$ARCH" = "x86_64" ]; then
  . /etc/profile.d/32dev.sh
fi

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --mandir=/usr/man \
  --docdir=/usr/doc/$PRGNAM-$VERSION \
  --disable-tests \
  --with-x \
  --with-opengl \
  --with-gnutls=yes \
  --build=$ARCH-slackware-linux
'32dev.sh' sets up a 32-bit environment for the compile. '--disable-tests' can provide a BIG performance improvement.
There is no need to run ". /etc/profile/32dev.sh" when compiling wine on Slackware 32. Also, there is no need to re-define ARCH. On 64bit, you can keep ARCH at "x86_64". This sets wine apart from other software which you want to compile into 32bit binaries on a 64bit (multilib) system.

My script at http://www.slackware.com/~alien/slackbuilds/wine/build/ builds 32bit wine as well as 64bit wine by default (you can disable wine64 by changing a variable "DO_WINE64"). My script also applies the wine-staging patches always.
I do not have libpng issues with this package.
 
1 members found this post helpful.
Old 04-21-2017, 01:26 PM   #28
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Just a few FTRs. I have always installed Full Recommended Install. I do build custom kernels (basically using Bob's method these days) and I do always pay attention to the dependencies listed by Slackbuilds.org and I never rely on any automatics, greatly preferring to take the time to do each one manually myself. Any optional addons I have in this first (to me) 64bit multilib system are all from Alien Bob with only three exceptions, Aqualung media player, and wine, and technically Discord (com app) though it is a drop in binary not a native compile now. For wine I have been using Dugan's wine-staging script since it does provide me with improvements in performance that I wish to employ and also support by use, kudos and bugreporting.

As I have said I have yet to satisfy the libpng errors but the app seems to work fine in that regard.

So once again, Thank You Eric for all your great and highly appreciated work. For now and the foreseeable future I will struggle along with wine-staging. Anything earth-shaking I will post here.
 
Old 04-21-2017, 04:12 PM   #29
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,075
Blog Entries: 2

Rep: Reputation: 128Reputation: 128
Thumbs up

IMHO, aside for latest bug fixes for some most recent game, I see no reason going for any multilib Wine but Alien's packages?
1. has both binaries (both 32 and 64 bit work good for me?)
2. has decent performance (outperforms native OS/apps somehow?)
3. has little or no issues with AMD/Radeon HW out of the box)
And i did try run any Wine available at the time and found only Alien's package to satisfy all my ambitions?

Is it an Intel HD graphics system?

other than that, i highly recommend trying the sbotools since they provide an most elegant solution to compat32 packages:
Code:
sboinstall -p <package>
makes an compat32 one, yes a mere -p command line switch
 
Old 04-21-2017, 10:29 PM   #30
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,291

Original Poster
Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Thanks for your assessment and responses, SCerovec.

I am a confirmed nVidia Loyalist and am currently using a GTX-760. Since the bulk of my current concerns seem to be error reporting that is both unnecessary as everything works to my satisfaction except some timeouts and delays often a function of the error reporting itself and seemingly unresponsive to attempts to shut the reporting off. One example is the libpng issue of which I can see nothing improperly rendered. In fact I enjoy VERY high graphics settings as well as low latency and FPS. Another example is

Code:
fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
fixme:service:svcctl_EnumServicesStatusW resume index not supported
The app is connected and obviously by LAN (I have no other connection setup) so why the error for wininet/winsock ? I could simply ignore this since it works decently and in some cases, excellently, but the delays are annoying and I think can be eliminated. I just haven't learned how yet as neither WINEDEBUG=fixme-all or WINEDEBUG=-ALL seem to produce that condition.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LoL in wine not running on Slackware 14.2 Multilib EzAcc Slackware 5 12-21-2016 07:22 AM
[SOLVED] trying to install Wine with multilib Knightron Slackware 5 10-23-2012 04:58 AM
Gstreamer errors in 13.37 multilib + wine quiescere Slackware 5 11-07-2011 09:06 AM
[SOLVED] Installing wine in -current,multilib TSquaredF Slackware 3 12-20-2010 12:34 PM
Building WINE on Slackware64 multilib? Lufbery Slackware 12 07-19-2010 06:22 PM


All times are GMT -5. The time now is 09:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration