Active Topics
-
Maemo repository (8)
to Community by Maemish - 1 day, 18 hrs ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 23 hrs ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 20 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days, 18 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days, 18 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 6 days ago - more...
|
2007-11-19
, 14:46
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#2
|
trying to lie to dpkg-buildpackage doesn't work
That's always worked for me, so in that case I don't know I'm afraid.
 |
|
2007-11-19
, 15:33
|
|
Posts: 696 |
Thanked: 1,012 times |
Joined on Mar 2006
@ Asturies, Spain
|
#3
|
Or trying to do "dpkg-buildpackage -d"
It will ignore the build dependencies and will continue. And you might haven't problems after.
It will ignore the build dependencies and will continue. And you might haven't problems after.
|
|
2007-11-19
, 16:22
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#4
|
Even with -d mine sometimes collapses (i.e. it's not just checked at the dependency checking stage) so I have to do the compat edit.
 |
|
2007-11-20
, 11:20
|
|
Posts: 739 |
Thanked: 159 times |
Joined on Sep 2007
@ Germany - Munich
|
#5
|
Thanks for the answers.
No it's not linked with dependencies.
These are my first packages I'm doing for debian so I'm in my discovery phase ..
I'm only _thinking_ it comes from debhelper 5 not present, not really sure.
It fails with a nice message:
Anybody already seen this message? That's a funny one I have to say. (yes, yes, debian/rules is present _from the root tree of libqt_)
I thought the dependencies would be handled on the fly depending of what compile options you use.
Also I thought compile options should be passed to DEB_BUILD_OPTIONS but for qt4.3 they use another variable. <-- I'm fussy on this one, I don't know if it's part of the debian policy (dictatorship? lol ). I'll submit a bug report!! No just kidding.
So I guess that I'll handle my dependencies myself and make a private "fork" (or NMU whatever) of the libqt4.3 (not sure about legal stuffs with the trolltech mess).
I will try again and again to make a qt4.3.2 package, next days.
In my impatience, I tried checkinstall ( a big intelligent hack for creating packages ). This is definetly something to try to integrate, unless something already exist for scratchbox and arm ??
Buuuutttt I doesn't play well with scratchbox. Maybe I should contact scratchbox devs. I only tried an aggressive method yesterday and stopped after 2hours of trying to debug checkinstall.. So I didn't try that hard.
Then I did the targz method
For the details (and could be usefull to someone):
It's full of soft links (/lib) and my external card was formatted in fat (bad idea). I was surprised that tar didn't want to keep my links.. yep I had forgotten how primitive fat is :/ Card contained 3Gb of data already, reformating was not an option... so I did a loopback partition:
It's awfull but does the trick (tm)
And this is my first qt4.3.2 app running, penguinbait what's with kde4?
Last edited by free; 2007-11-20 at 16:46.
No it's not linked with dependencies.
These are my first packages I'm doing for debian so I'm in my discovery phase ..
I'm only _thinking_ it comes from debhelper 5 not present, not really sure.
It fails with a nice message:
Code:
[sbox-SDK_ARMEL: ~/src/qt-x11-opensource-src-4.3.1] > fakeroot dpkg-buildpackage -d -us -uc dpkg-buildpackage: source package is qt4-x11 dpkg-buildpackage: source version is 4.3.1-2 dpkg-buildpackage: source changed by Sune Vuorela <debian@pusling.com> dpkg-buildpackage: host architecture armel dpkg-buildpackage: source version without epoch 4.3.1-2 debian/rules clean test -x debian/rules make: *** [testdir] Error 1
I thought the dependencies would be handled on the fly depending of what compile options you use.
Also I thought compile options should be passed to DEB_BUILD_OPTIONS but for qt4.3 they use another variable. <-- I'm fussy on this one, I don't know if it's part of the debian policy (dictatorship? lol ). I'll submit a bug report!! No just kidding.
So I guess that I'll handle my dependencies myself and make a private "fork" (or NMU whatever) of the libqt4.3 (not sure about legal stuffs with the trolltech mess).
I will try again and again to make a qt4.3.2 package, next days.
In my impatience, I tried checkinstall ( a big intelligent hack for creating packages ). This is definetly something to try to integrate, unless something already exist for scratchbox and arm ??
Buuuutttt I doesn't play well with scratchbox. Maybe I should contact scratchbox devs. I only tried an aggressive method yesterday and stopped after 2hours of trying to debug checkinstall.. So I didn't try that hard.
Then I did the targz method
For the details (and could be usefull to someone):
It's full of soft links (/lib) and my external card was formatted in fat (bad idea). I was surprised that tar didn't want to keep my links.. yep I had forgotten how primitive fat is :/ Card contained 3Gb of data already, reformating was not an option... so I did a loopback partition:
Code:
1)on my linux pc: #Create a file of 100Meg dd if=/dev/zero of=qt.img bs=1k count=100000 #Assign the file to a partition (the magic of linux) losetup /dev/loop0 qt.img #Format it as ext2 mkfs.ext2 /dev/loop0 # Mount the loopback mkdir /mnt/x ; mount /dev/loop0 /mnt/x # Copy my tar inside cd /mnt/x tar xvzf ~/qt4.tgz # Umount, copy to the n800 umount /mnt/x scp qt.img user@n800:/media/mmc2/ 2) On the n800 sudo gainroot #mkdir /mnt/lo #mount /media/mmc2/qt.img /mnt/lo -o loop Now /mnt/lo is an ext2 partition containing my extracted tar 3) Running qt4.3.2 demo: $export LD_LIBRARY_PATH=/mnt/lo/TrollTech/qt4.3.2/lib $/mnt/lo/TrollTech/qt4.3.2/demos/spreadsheet/spreadsheet (takes 3 seconds to start, dynamic version, no prelinking yet)
And this is my first qt4.3.2 app running, penguinbait what's with kde4?
Last edited by free; 2007-11-20 at 16:46.
I'm trying to package qt4.3.1.
It really needs deb-helper version 5, trying to lie to dpkg-buildpackage doesn't work
So I have several choices..
* Do it the clean way and then I need deb-helper 5 (and a lot of other things btw..). That would be perfect.
* DIM (Do It Myself doh!) in a more dirty way.
-> Would mud-builder be helpful?
-> Checkinstall?
-> pypackager?
-> tar+ ar ?
It builds well under scratchbox with standard ./configure, make, make install.
Any idea appreciated..
Meanwhile I'll try the second choice...
Last edited by free; 2007-11-20 at 19:47.