[SOLVED] i7z qmake compile woes

enorbet · 08-15-2015, 11:04 PM

Greetings
Ultimately I wish to be able to install and run i7z and i7z_GUI, a potent monitoring app specific to i3, i5, and i7 CPUs.. I'm using 32bit Slackware v14.0 full install (and then some) which includes qt-4.8.2-i486-4 but not the devtools. I have qmake but seem to have 2 problems

1) i7z seeks several qt libraries in /usr/share/qt4 but all mine are in /usr/lib/qt4 with the exception of icons and a few .desktop app launcher links.

2) Among those i7z seeks qmake.conf of which there are many (over a dozen) but also in /usr/share/... instead of /usr/lib/... so in addition to mismatch in location I'm wondering if one of those needs to be linked to what I want the system's default qmake.conf to be.

Additionally the Trolltech site seems to be down (at least for now) so I have no way to get qt-devtools. AFAIK for i7z all I really need is libqt4-dev and qmake-qt4 according to the readme.

Any help or suggestions appreciated.

ml4711 · 08-16-2015, 04:54 AM

Ok - tried on slackware 14.1

First suggestions :-)

read this GUI/README_GUI.txt

In short:

Code:

qmake
make clean
make

Quote:

1) i7z seeks several qt libraries in /usr/share/qt4 but all...

This because you did not run qmake

cheers

enorbet · 08-16-2015, 12:47 PM

Hello and TY for your effort. We must have different versions since this is my Readme_GUI.txt in total

Quote:

Originally Posted by Readme.GUI.txt

By Abhishek Jaiantilal
Under GPL v2

#to make the gui working you will need qt4 installed.
libqt4-dev, qmake-qt4 should be enough i think

running the Makefile should be enough

svn-r43
Wworks for Dual Socket Boards but wont work if core is taken offline while the tool is running.

This is the i7z Readme in the parent directory

Quote:

Originally Posted by Readme.txt

license: My code is GPLv2
Current Version: svn-31 (17/May/2010)

Compiling:
32/64-bit linux:
make

Running:
sudo ./i7z

needs sudo as MSR are usually only superuser readable/writeable. or if the device nodes
are readable under your account then they will work out fine without the sudo

need ncurses library: usually something like libncurses on debian.
also needs support of MSR (model specific register) in kernel. Usually most kernels
have it. Else run the MAKEDEV file. I do modprobing of msr within the C-program.

I added in new code that shows a nice GUI.
The Makefile for that is in GUI/ subdirectory. Just install a couple of qt packages
and you should be all set to run it. There is a README file that lists those packages

Running GUI:
sudo ./i7z_GUI

Installation
sudo make install

As you can see qmake is not mentioned in my Readmes. That said I did run qmake in the GUI directory and now terminal text i7z works but GUI still does not. If I run it w/ kdesu I get a kdesu stub. If I run it as User, I get a segfault.

Any ideas?

ml4711 · 08-16-2015, 01:23 PM

Your version seems to be rather old

I used i7z-0.27.2 from
https://code.google.com/p/i7z/

it says i7z version: svn-r77-(20-Nov-2011)

It asks to be run as root, And the GUI works on
my main desktop (slackware64 14.1, cpu i5-2500)

On Slackware 14.0 it starts,
but exits after some seconds, since the cpu is far too old

Cheers

enorbet · 08-16-2015, 10:19 PM

@ m14711 THANK YOU! That version actually has readable Readmes AND worked a treat first shot!.... and this is 32bit 14.0. I'm very pleased.

i7z_GUI In Action screenie

John VV · 08-16-2015, 11:44 PM

google code is basically dead and not used any more
on the page
https://code.google.com/p/i7z/
you DID notice the NOTICE at the top of the page

Quote:

Summary says all: A better i7 (and now i3, i5) reporting tool for Linux. Source and makefiles inside the download OR sync in the Source Tab OR sync @ http://github.com/ajaiantilal/i7z (git://github.com/ajaiantilal/i7z.git)

use the newer code on Github

the google-code file" i7z-0.27.2.tar.gz" is from 2012

https://github.com/ajaiantilal/i7z
is the newer 2013 code

enorbet · 08-17-2015, 07:06 AM

Thanks JohnW. I actually had read the notice but didn't choose to make that leap first. I prefer small steps and in this case, since my mobo is slightly older than 2012, it seemed a safe bet to give it a shot before I tried the 2013 version. I since have compiled the 2013 version (one of the wonderful things about Linux is multiple versions, right?) and it runs fine, looks a little better and has slightly more info in the GUI though still not up to CLI par. It still doesn't show core voltage and temps yet but I plan to try to pipe it into Conky and see if I can replace the existing reporting code in Conky with i7z which has several benefits, speed and accuracy among them. Then comparing to STDIN STDOUT data through KDE Plasmoids should be interesting.