[Q] Dependancy errors trying to install heimdall on Fedora 18

Search This thread

banjo67xxx

Member
Jun 25, 2013
12
0
Hi,

I'm about to use Chainfire's CF-Auto-Root on my SIII GT-I9300 running 4.1.2 build JZO54K.I9300XXEMC2

One of the pre-reqs is to download heimdall as my IBM Lenovo T510 is running Fedora 18 x86_64, so I went to
h ttp s bit bucket .org/benjamin_dobell/heimdall/downloads

and downloaded
fedora18-heimdall-1.4.0-44.1.x86_64.rpm
fedora18-heimdall-frontend-1.4.0-17.1.x86_64.rpm

but when I try to install them I get the error

Code:
# yum localinstall fedora18-heimdall-1.4.0-44.1.x86_64.rpm fedora18-heimdall-frontend-1.4.0-17.1.x86_64.rpm
Loaded plugins: langpacks, presto, refresh-packagekit
Examining fedora18-heimdall-1.4.0-44.1.x86_64.rpm: heimdall-1.4.0-44.1.x86_64
Marking fedora18-heimdall-1.4.0-44.1.x86_64.rpm to be installed
Examining fedora18-heimdall-frontend-1.4.0-17.1.x86_64.rpm: heimdall-frontend-1.4.0-17.1.x86_64
Marking fedora18-heimdall-frontend-1.4.0-17.1.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package heimdall.x86_64 0:1.4.0-44.1 will be installed
--> Processing Dependency: libusb1.0 >= 1.0.8 for package: heimdall-1.4.0-44.1.x86_64
fedora/18/x86_64/metalink                                                                                                                                                |  20 kB  00:00:00     
google-chrome                                                                                                                                                            |  951 B  00:00:00     
rpmfusion-free-updates                                                                                                                                                   | 3.3 kB  00:00:00     
rpmfusion-nonfree-updates                                                                                                                                                | 3.3 kB  00:00:00     
updates/18/x86_64/metalink                                                                                                                                               |  14 kB  00:00:00     
---> Package heimdall-frontend.x86_64 0:1.4.0-17.1 will be installed
--> Processing Dependency: libqt4-xml >= 4.6 for package: heimdall-frontend-1.4.0-17.1.x86_64
--> Processing Dependency: libqtcore4 >= 4.6 for package: heimdall-frontend-1.4.0-17.1.x86_64
--> Processing Dependency: libqtgui4 >= 4.6 for package: heimdall-frontend-1.4.0-17.1.x86_64
--> Finished Dependency Resolution
Error: Package: heimdall-frontend-1.4.0-17.1.x86_64 (/fedora18-heimdall-frontend-1.4.0-17.1.x86_64)
           Requires: libqtcore4 >= 4.6
Error: Package: heimdall-1.4.0-44.1.x86_64 (/fedora18-heimdall-1.4.0-44.1.x86_64)
           Requires: libusb1.0 >= 1.0.8
Error: Package: heimdall-frontend-1.4.0-17.1.x86_64 (/fedora18-heimdall-frontend-1.4.0-17.1.x86_64)
           Requires: libqtgui4 >= 4.6
Error: Package: heimdall-frontend-1.4.0-17.1.x86_64 (/fedora18-heimdall-frontend-1.4.0-17.1.x86_64)
           Requires: libqt4-xml >= 4.6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Searching on Google I found this comment on stackoverflow h tt p stac koverflow. com/questions/4586431/fedora-qt-runtime-packages which says the packages are named wrong

So I checked ...

Code:
# rpm -qa | grep qt
qt-settings-4.9-21.fc18.noarch
ibus-qt-1.3.2-2.fc18.x86_64
pinentry-qt-0.8.1-8.fc18.x86_64
qt-mobility-1.2.2-0.3.20120224git.fc18.x86_64
qt-mysql-4.8.4-17.fc18.x86_64
qtscriptbindings-0.2.0-4.fc18.x86_64
dbusmenu-qt-0.9.2-2.fc18.x86_64
polkit-qt-0.103.0-4.fc18.x86_64
telepathy-logger-qt-0.6.2-1.fc18.x86_64
qt-4.8.4-17.fc18.x86_64
qt-x11-4.8.4-17.fc18.x86_64
qt-config-4.8.4-17.fc18.x86_64
qt3-3.3.8b-43.fc18.x86_64
telepathy-qt4-farstream-0.9.3-5.fc18.x86_64
poppler-qt-0.20.2-15.fc18.x86_64
qtwebkit-2.3.1-1.fc18.x86_64
qt-gstreamer-0.10.2-2.fc18.x86_64
telepathy-qt4-0.9.3-5.fc18.x86_64
libmygpo-qt-1.0.6-1.fc18.x86_64
qtsoap-2.7-4.fc18.x86_64
[root@banjo Downloads]# rpm -qa | grep usb
libusbx-1.0.14-1.fc18.x86_64
usbredir-0.6-1.fc18.x86_64
libertas-usb8388-firmware-20130418-0.1.gitb584174.fc18.noarch
liveusb-creator-3.11.8-1.fc18.noarch
libgusb-0.1.6-1.fc18.x86_64
usb_modeswitch-1.2.5-1.fc18.x86_64
usb_modeswitch-data-20121109-1.fc18.noarch
usbutils-006-4.fc18.x86_64
libusb-0.1.3-11.fc18.x86_64
usbmuxd-1.0.8-5.fc18.x86_64

So should I just install heimdall with --nodeps or do I have to recompile from source?

I'm afraid to do the wrong thing just in case heimdall crashes mid-download and bricks the phone.

Thx,
Banjo
 

Benjamin Dobell

Inactive Recognized Developer
Jul 1, 2010
843
600
Melbourne
www.glassechidna.com.au
Hmmm, it looks like Qt 4.6 (or later) isn't available for you system from Yum. Which is a bit strange because the Open Build Service seems to think it is. Maybe you need to add another repository. I suggest asking on some Fedora forums.

However if you can't find it you could compile Qt 4.6-4.8 (not 5.x) from source then install with no-deps. But compiling from source tasks ages so I'd suggest trying to find binary packages/repositories first.
 
  • Like
Reactions: banjo67xxx

banjo67xxx

Member
Jun 25, 2013
12
0
[SOLVED] Recompliled from source

Hmmm, it looks like Qt 4.6 (or later) isn't available for you system from Yum. Which is a bit strange because the Open Build Service seems to think it is. Maybe you need to add another repository. I suggest asking on some Fedora forums.

However if you can't find it you could compile Qt 4.6-4.8 (not 5.x) from source then install with no-deps. But compiling from source tasks ages so I'd suggest trying to find binary packages/repositories first.

Hi Benjamin,

I checked again and the require libusb and qt packages were already there.

Code:
libusbx-1.0.14-1.fc18.x86_64
qt-4.8.4-17.fc18.x86_64
qt-x11-4.8.4-17.fc18.x86_64
qt-config-4.8.4-17.fc18.x86_64

When I tried recompiling from source, all I needed to do was add 2 more packages ...

Code:
# yum install qt-devel
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package qt-devel.x86_64 1:4.8.4-17.fc18 will be installed
--> Processing Dependency: pkgconfig(xv) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xt) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xrender) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xrandr) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xproto) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xinerama) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xi) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xft) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xfixes) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xext) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(xcursor) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(x11) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(sm) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(ice) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(glu) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Processing Dependency: pkgconfig(gl) for package: 1:qt-devel-4.8.4-17.fc18.x86_64
--> Running transaction check
---> Package libICE-devel.x86_64 0:1.0.8-2.fc18 will be installed
---> Package libSM-devel.x86_64 0:1.2.1-2.fc18 will be installed
---> Package libX11-devel.x86_64 0:1.5.99.901-3.20130524gita3bdd2b09.fc18 will be installed
--> Processing Dependency: pkgconfig(xcb) >= 1.1.92 for package: libX11-devel-1.5.99.901-3.20130524gita3bdd2b09.fc18.x86_64
--> Processing Dependency: pkgconfig(xcb) for package: libX11-devel-1.5.99.901-3.20130524gita3bdd2b09.fc18.x86_64
---> Package libXcursor-devel.x86_64 0:1.1.13-5.20130524git8f677eaea.fc18 will be installed
---> Package libXext-devel.x86_64 0:1.3.1-3.20130524gitdfe6e1f3b.fc18 will be installed
---> Package libXfixes-devel.x86_64 0:5.0-6.20130524gitc480fe327.fc18 will be installed
---> Package libXft-devel.x86_64 0:2.3.1-2.fc18 will be installed
--> Processing Dependency: pkgconfig(freetype2) for package: libXft-devel-2.3.1-2.fc18.x86_64
--> Processing Dependency: pkgconfig(fontconfig) for package: libXft-devel-2.3.1-2.fc18.x86_64
---> Package libXi-devel.x86_64 0:1.6.2.901-1.fc18 will be installed
---> Package libXinerama-devel.x86_64 0:1.1.2-5.20130524git99c644fc8.fc18 will be installed
---> Package libXrandr-devel.x86_64 0:1.4.0-4.20130524gitc90f74497.fc18 will be installed
---> Package libXrender-devel.x86_64 0:0.9.7-5.20130524git786f78fd8.fc18 will be installed
---> Package libXt-devel.x86_64 0:1.1.3-4.20130524git1f4802b74.fc18 will be installed
---> Package libXv-devel.x86_64 0:1.0.7-5.20130524git50fc4cb18.fc18 will be installed
---> Package mesa-libGL-devel.x86_64 0:9.2-0.7.20130528.fc18 will be installed
--> Processing Dependency: pkgconfig(libdrm) >= 2.4.24 for package: mesa-libGL-devel-9.2-0.7.20130528.fc18.x86_64
--> Processing Dependency: pkgconfig(xxf86vm) for package: mesa-libGL-devel-9.2-0.7.20130528.fc18.x86_64
--> Processing Dependency: pkgconfig(xdamage) for package: mesa-libGL-devel-9.2-0.7.20130528.fc18.x86_64
--> Processing Dependency: gl-manpages for package: mesa-libGL-devel-9.2-0.7.20130528.fc18.x86_64
---> Package mesa-libGLU-devel.x86_64 0:9.0.0-1.fc18 will be installed
---> Package xorg-x11-proto-devel.noarch 0:7.6-24.fc18 will be installed
--> Running transaction check
---> Package fontconfig-devel.x86_64 0:2.10.2-2.fc18 will be installed
---> Package freetype-devel.x86_64 0:2.4.10-4.fc18 will be installed
--> Processing Dependency: zlib-devel for package: freetype-devel-2.4.10-4.fc18.x86_64
---> Package gl-manpages.noarch 0:1.1-5.20130122.fc18 will be installed
---> Package libXdamage-devel.x86_64 0:1.1.3-4.fc18 will be installed
---> Package libXxf86vm-devel.x86_64 0:1.1.2-5.20130524git4c4123441.fc18 will be installed
---> Package libdrm-devel.x86_64 0:2.4.45-1.fc18 will be installed
---> Package libxcb-devel.x86_64 0:1.9-3.fc18 will be installed
--> Processing Dependency: pkgconfig(xau) >= 0.99.2 for package: libxcb-devel-1.9-3.fc18.x86_64
--> Running transaction check
---> Package libXau-devel.x86_64 0:1.0.6-4.fc18 will be installed
---> Package zlib-devel.x86_64 0:1.2.7-9.fc18 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

...

Installed:
  qt-devel.x86_64 1:4.8.4-17.fc18                                                                                                                                                                

Dependency Installed:
  fontconfig-devel.x86_64 0:2.10.2-2.fc18                        freetype-devel.x86_64 0:2.4.10-4.fc18                           gl-manpages.noarch 0:1.1-5.20130122.fc18                       
  libICE-devel.x86_64 0:1.0.8-2.fc18                             libSM-devel.x86_64 0:1.2.1-2.fc18                               libX11-devel.x86_64 0:1.5.99.901-3.20130524gita3bdd2b09.fc18   
  libXau-devel.x86_64 0:1.0.6-4.fc18                             libXcursor-devel.x86_64 0:1.1.13-5.20130524git8f677eaea.fc18    libXdamage-devel.x86_64 0:1.1.3-4.fc18                         
  libXext-devel.x86_64 0:1.3.1-3.20130524gitdfe6e1f3b.fc18       libXfixes-devel.x86_64 0:5.0-6.20130524gitc480fe327.fc18        libXft-devel.x86_64 0:2.3.1-2.fc18                             
  libXi-devel.x86_64 0:1.6.2.901-1.fc18                          libXinerama-devel.x86_64 0:1.1.2-5.20130524git99c644fc8.fc18    libXrandr-devel.x86_64 0:1.4.0-4.20130524gitc90f74497.fc18     
  libXrender-devel.x86_64 0:0.9.7-5.20130524git786f78fd8.fc18    libXt-devel.x86_64 0:1.1.3-4.20130524git1f4802b74.fc18          libXv-devel.x86_64 0:1.0.7-5.20130524git50fc4cb18.fc18         
  libXxf86vm-devel.x86_64 0:1.1.2-5.20130524git4c4123441.fc18    libdrm-devel.x86_64 0:2.4.45-1.fc18                             libxcb-devel.x86_64 0:1.9-3.fc18                               
  mesa-libGL-devel.x86_64 0:9.2-0.7.20130528.fc18                mesa-libGLU-devel.x86_64 0:9.0.0-1.fc18                         xorg-x11-proto-devel.noarch 0:7.6-24.fc18                      
  zlib-devel.x86_64 0:1.2.7-9.fc18                              

Complete!
[root@banjo ~]# yum install libusbx-devel
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package libusbx-devel.x86_64 0:1.0.14-1.fc18 will be installed
--> Processing Dependency: libusbx-devel-doc = 1.0.14-1.fc18 for package: libusbx-devel-1.0.14-1.fc18.x86_64
--> Running transaction check
---> Package libusbx-devel-doc.noarch 0:1.0.14-1.fc18 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=================================================================================================================================================================================================
 Package                                              Arch                                      Version                                          Repository                                 Size
=================================================================================================================================================================================================
Installing:
 libusbx-devel                                        x86_64                                    1.0.14-1.fc18                                    fedora                                     17 k
Installing for dependencies:
 libusbx-devel-doc                                    noarch                                    1.0.14-1.fc18                                    fedora                                    153 k

Transaction Summary
=================================================================================================================================================================================================
Install  1 Package (+1 Dependent package)

Total download size: 170 k
Installed size: 1.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): libusbx-devel-1.0.14-1.fc18.x86_64.rpm                                                                                                                             |  17 kB  00:00:00     
(2/2): libusbx-devel-doc-1.0.14-1.fc18.noarch.rpm                                                                                                                         | 153 kB  00:00:10     
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                             17 kB/s | 170 kB     00:10     
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : libusbx-devel-doc-1.0.14-1.fc18.noarch                                                                                                                                        1/2 
  Installing : libusbx-devel-1.0.14-1.fc18.x86_64                                                                                                                                            2/2 
  Verifying  : libusbx-devel-1.0.14-1.fc18.x86_64                                                                                                                                            1/2 
  Verifying  : libusbx-devel-doc-1.0.14-1.fc18.noarch                                                                                                                                        2/2 

Installed:
  libusbx-devel.x86_64 0:1.0.14-1.fc18                                                                                                                                                           

Dependency Installed:
  libusbx-devel-doc.noarch 0:1.0.14-1.fc18                                                                                                                                                       

Complete!

Everything compiled from source within less than 2 minutes, so I presume their is just some sort of naming issue in the dependancy list.

Thx,
Banjo.
 

fjb3

Member
Aug 18, 2014
8
0
Same dependency errors installing heimdall on Fedora 20 and CentOS 7

Hi Benjamin,
(...snip...)

Everything compiled from source within less than 2 minutes, so I presume their is just some sort of naming issue in the dependancy list.

Thx,
Banjo.

Hi all,

I've encountered exactly the same problem trying to install heimdall on both CentOS 7 and Fedora 20 (Live DVD / USB).
Can you please clarify what you meant by "Everything"? Did you recompile heimdall from source or something else?
Need to flash back stock NCG rom on my SM-G900V ASAP!

Thanks,
-fjb3
 

VelosterM14

Senior Member
Going to take a look at the source tarball and see if there is by chance an RPM spec file in it, if there is I will see what I can do about the BuildRequires and Requires to update the names of the packages and do some build work. I didn't see the .src.rpm over at the download site.

Not finding spec file. IIRC there is a way to get it out of the binary RPM but will have to startpage for that.

---------- Post added at 03:25 PM ---------- Previous post was at 03:18 PM ----------

BTW I'm on Fedora 19 but assuming I get good working RPM's (probably will) we'll have .src.rpm's that can be worked from to build on newer Fedora releases. Unless something has changed with package names etc. (kind of like how we may have gotten into this boat with the qt-devel and libuxbx-devel packages) you would probably be able to just rebuild the .src.rpm on F20.

PS: Anyone recommend a good file host to post to? I'm sorta new to involvement here and not sure what all is involved with posting to AFH for example. Technically though I think the only thing we're really going to need to post is the updated .spec file and any patches that might be used. I don't want to start redistributing Benjamin's work. :)

---------- Post added at 03:40 PM ---------- Previous post was at 03:25 PM ----------

hmm, evidently you can't get the spec out of the binary rpm. I could almost swear I saw this done once.

Benjamin could you post the RPM .spec file you're building the RPM's with somewhere, or point us in the right direction of where it already is posted? I can fix the package names etc. if I can just get the .spec file. :)

---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------

FWIW on Fedora 19 x86_64, the Fedora 18 x86_64 packages installed OK for me using 'rpm -Uvh --nodeps <package-names-and-paths>'. I already had libusbx and qt installed, and heimdall-frontend starts up just fine.

libusbx is stated to be API compatible with stuff that wants libusb1 functions. So it would probably work fine. I've not used Heimdall before but was looking for a linux solution so I wouldn't have to reboot into that "other" OS to Odin-ate...

---------- Post added at 04:08 PM ---------- Previous post was at 03:54 PM ----------

heimdall-frontend from the fedora 18 x86_64 packages appears to be able to communicate fine with my VZW Galaxy S4 (i545) - I was able to get it to print the PIT under the utilities tab with no errors noted. So if you're in a pinch (as it sounds like previous poster is), you can probably download the 2 fedora 18 rpm's from the download link, use 'rpm -Uvh --nodeps package1 package2' to install them, then make sure you have qt and libusbx packages installed.

I have more reading to do about the file formats heimdall can flash before I try it on mine, not sure if i can just use the official VZW OTA NC5 files directly or not. For right now I'm just experimenting with heimdall to be able to stay in Linux if I mess up while I'm rom'ing and modding around and need to flash back a stock OTA load.
 

fjb3

Member
Aug 18, 2014
8
0
Thanks Veloster.

I was looking for a .spec file too, but I downloaded heimdall-suite-1.4.0.tar.gz which contains the complete source for heimdall in GNU-style autoconf distro format. There isn't a spec file per se, but you can pretty much build and configure everything once you've got the full source tree. As I mentioned, I'm running Fedora20 and CentOS7 off of USB LiveDVD-to-USBflashdrive burns a.t.m., with NFS mounted fs to provide space for a build. I may break down and install VirtualBox, I'm happy with my older non-systemd-based linux distro for now and don't want to break my whole dev environment just to be able to flash my phone every once in a while.

Going to take a look at the source tarball and see if there is by chance an RPM spec file in it, if there is I will see what I can do about the BuildRequires and Requires to update the names of the packages and do some build work. I didn't see the .src.rpm over at the download site.

Not finding spec file. IIRC there is a way to get it out of the binary RPM but will have to startpage for that.

FWIW, I have been reading a lot on the xda forums for several years, and after a few months studying the S5 I finally broke down and bought a Samsung Galaxy S5 to replace my ancient Motorola Droid 3 (which I rooted the day I got it from a command line under ConnectBot). Anyway, I decided to purchase the S5 after I saw it had been successfully rooted (towelroot), as I didn't want to be trapped inside "Android: Linux with the hood welded shut!" [And BTW, what sort of twisted world have we found ourselves in, where we've gone through _THIS_ completely moronic circle? ;) ] I've been really frustrated at the limited nmber of discussions of using Linux-based tools, since I proudly do not own or use any machines running "that other operating system". I usually lurk in the shadows (this being my second post on xda-developers after years of reading) on forums, but I hope to see more linux-based tools and discussions here in the future.

-fjb3
 
Last edited:

VelosterM14

Senior Member
Thanks Veloster.

I was looking for a .spec file too, but I downloaded heimdall-suite-1.4.0.tar.gz which contains the complete source for heimdall in GNU-style autoconf distro format. There isn't a spec file per se, but you can pretty much build and configure everything once you've got the full source tree.

True. It's not really required to build RPM's for stuff. But I do like the convenience of it at least once you've got a good RPM built.

As I mentioned, I'm running Fedora20 and CentOS7 off of USB LiveDVD-to-USBflashdrive burns a.t.m., with NFS mounted fs to provide space for a build. I may break down and install VirtualBox, I'm happy with my older non-systemd-based linux distro for now and don't want to break my whole dev environment just to be able to flash my phone every once in a while.

*nod* - tends to be a chore when you update the OS.

FWIW, I have been reading a lot on the xda forums for several years, and after a few months studying the S5 I finally broke down and bought a Samsung Galaxy S5 to replace my ancient Motorola Droid 3 (which I rooted the day I got it from a command line under ConnectBot). Anyway, I decided to purchase the S5 after I saw it had been successfully rooted (towelroot), as I didn't want to be trapped inside "Android: Linux with the hood welded shut!"

Good deal! I was looking pretty hard at the S5 when I got the S4 a couple weeks ago. It's really nice - especially since they have 32GB of onboard storage (IIRC). The size ended up being the main factor against it for me, preferring one a little smaller and easier to get in/out of my pocket. But they're nice. Congratulations on the new phone.

[And BTW, what sort of twisted world have we found ourselves in, where we've gone through _THIS_ completely moronic circle? ;) ] I've been really frustrated at the limited nmber of discussions of using Linux-based tools, since I proudly do not own or use any machines running "that other operating system".

I hear ya. I am a Linux guy by trade (and bigotry) and really try not to run Windows if I can help it. Only when I have to.

I usually lurk in the shadows (this being my second post on xda-developers after years of reading) on forums, but I hope to see more linux-based tools and discussions here in the future.

Me too. :)

Take care!
 
Last edited:
  • Like
Reactions: fjb3

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hmmm, it looks like Qt 4.6 (or later) isn't available for you system from Yum. Which is a bit strange because the Open Build Service seems to think it is. Maybe you need to add another repository. I suggest asking on some Fedora forums.

    However if you can't find it you could compile Qt 4.6-4.8 (not 5.x) from source then install with no-deps. But compiling from source tasks ages so I'd suggest trying to find binary packages/repositories first.
    1
    Thanks Veloster.

    I was looking for a .spec file too, but I downloaded heimdall-suite-1.4.0.tar.gz which contains the complete source for heimdall in GNU-style autoconf distro format. There isn't a spec file per se, but you can pretty much build and configure everything once you've got the full source tree.

    True. It's not really required to build RPM's for stuff. But I do like the convenience of it at least once you've got a good RPM built.

    As I mentioned, I'm running Fedora20 and CentOS7 off of USB LiveDVD-to-USBflashdrive burns a.t.m., with NFS mounted fs to provide space for a build. I may break down and install VirtualBox, I'm happy with my older non-systemd-based linux distro for now and don't want to break my whole dev environment just to be able to flash my phone every once in a while.

    *nod* - tends to be a chore when you update the OS.

    FWIW, I have been reading a lot on the xda forums for several years, and after a few months studying the S5 I finally broke down and bought a Samsung Galaxy S5 to replace my ancient Motorola Droid 3 (which I rooted the day I got it from a command line under ConnectBot). Anyway, I decided to purchase the S5 after I saw it had been successfully rooted (towelroot), as I didn't want to be trapped inside "Android: Linux with the hood welded shut!"

    Good deal! I was looking pretty hard at the S5 when I got the S4 a couple weeks ago. It's really nice - especially since they have 32GB of onboard storage (IIRC). The size ended up being the main factor against it for me, preferring one a little smaller and easier to get in/out of my pocket. But they're nice. Congratulations on the new phone.

    [And BTW, what sort of twisted world have we found ourselves in, where we've gone through _THIS_ completely moronic circle? ;) ] I've been really frustrated at the limited nmber of discussions of using Linux-based tools, since I proudly do not own or use any machines running "that other operating system".

    I hear ya. I am a Linux guy by trade (and bigotry) and really try not to run Windows if I can help it. Only when I have to.

    I usually lurk in the shadows (this being my second post on xda-developers after years of reading) on forums, but I hope to see more linux-based tools and discussions here in the future.

    Me too. :)

    Take care!