05-02-2012, 07:46 PM | #151 | ||
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Sure... if you tell me what pull requests actually are, how they work, and what I am supposed to do with them.
I already admitted in some other thread that I am quite an idiot concerning git. I do clearly see the benefits of a DVCS, but I just didn't gain any experience with it yet. Please enlighten me! Quote:
Quote:
The workaround that I created has been working for me for everything I released so far. But I know it's not a real solution. Then again, the current solution works for everything that I personally need right now, so there is no urgent need from my (personal) perspective. |
||
05-02-2012, 07:50 PM | #152 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Thanks for the hint. I'll take it into account for the next release. Until then, it doesn't seem to hurt and can trivially be disabled.
|
Advert | |
|
05-02-2012, 09:26 PM | #153 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@JustAMan: You're welcome to try my KindleTool fork, if you're on a Linux box, it should (hopefully) work, and if it doesn't, I'll try to fix it . I haven't checked K4/K5 packages yet, but I've successfully built (and ran) my old K2/K3 stuff with it, so, either way, I'd be glad for some feedback .
Last edited by NiLuJe; 05-02-2012 at 09:31 PM. |
05-05-2012, 11:37 AM | #154 | |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
I'm on Ubuntu 10.4.2 64-bit. First: version.sh throws loads of errors because of "[[" syntax. I tried changing #!/bin/sh to #!/bin/bash, but that doesn't help either. So I replaced these double-brackets by single-brackets, and at least that stage goes through without errors. I'm attaching a diff, but please verify that the result is actually sensible. What is that "[[" thing about anyway? Second: even after applying that, I get the following errors when running "make": Code:
$ make KT_VERSION = v0.5-9-g7db0dfa-dirty (GCC 4.4.3) mkdir -p Release gcc -Llib -Iincludes -O2 -fomit-frame-pointer -march=native -pipe -Wall -D_FILE_OFFSET_BITS=64 -DKT_VERSION='"v0.5-9-g7db0dfa-dirty (GCC 4.4.3)"' -o Release/kindle_tool.o -c kindle_tool.c gcc -Llib -Iincludes -O2 -fomit-frame-pointer -march=native -pipe -Wall -D_FILE_OFFSET_BITS=64 -DKT_VERSION='"v0.5-9-g7db0dfa-dirty (GCC 4.4.3)"' -o Release/create.o -c create.c create.c: In function ‘kindle_create_package_archive’: create.c:119: warning: implicit declaration of function ‘archive_write_set_format_gnutar’ create.c:133: warning: implicit declaration of function ‘archive_read_disk_open’ create.c:188: warning: implicit declaration of function ‘archive_read_disk_descend’ create.c:247: warning: format ‘%lld’ expects type ‘long long int’, but argument 6 has type ‘__off_t’ create.c:352: warning: implicit declaration of function ‘archive_read_free’ create.c: In function ‘kindle_create_main’: create.c:897: warning: format ‘%llu’ expects type ‘long long unsigned int’, but argument 3 has type ‘uint64_t’ create.c:897: warning: format ‘%llu’ expects type ‘long long unsigned int’, but argument 4 has type ‘uint64_t’ gcc -Llib -Iincludes -O2 -fomit-frame-pointer -march=native -pipe -Wall -D_FILE_OFFSET_BITS=64 -DKT_VERSION='"v0.5-9-g7db0dfa-dirty (GCC 4.4.3)"' -o Release/convert.o -c convert.c convert.c: In function ‘kindle_convert_ota_update_v2’: convert.c:97: warning: format ‘%llu’ expects type ‘long long unsigned int’, but argument 3 has type ‘uint64_t’ convert.c:100: warning: format ‘%llu’ expects type ‘long long unsigned int’, but argument 3 has type ‘uint64_t’ convert.c: In function ‘libarchive_extract’: convert.c:491: warning: implicit declaration of function ‘archive_read_free’ convert.c:493: warning: implicit declaration of function ‘archive_write_free’ gcc -Llib -Iincludes -O2 -fomit-frame-pointer -march=native -pipe -Wall -D_FILE_OFFSET_BITS=64 -DKT_VERSION='"v0.5-9-g7db0dfa-dirty (GCC 4.4.3)"' -Wl,-O1 -Wl,--as-needed Release/kindle_tool.o Release/create.o Release/convert.o -lcrypto -larchive -oRelease/kindletool Release/create.o: In function `kindle_create_package_archive': create.c:(.text+0x4f6): undefined reference to `archive_write_set_format_gnutar' create.c:(.text+0x560): undefined reference to `archive_read_disk_open' create.c:(.text+0x6e8): undefined reference to `archive_read_disk_descend' create.c:(.text+0x97f): undefined reference to `archive_read_disk_open' create.c:(.text+0xa68): undefined reference to `archive_read_disk_descend' create.c:(.text+0xc42): undefined reference to `archive_read_free' Release/convert.o: In function `libarchive_extract': convert.c:(.text+0x30e): undefined reference to `archive_read_free' convert.c:(.text+0x320): undefined reference to `archive_write_free' collect2: ld returned 1 exit status make: *** [kindletool] Fehler 1 Code:
$ apt-cache policy libarchive-dev libarchive-dev: Installiert: 2.8.0-2ubuntu0.1 Kandidat: 2.8.0-2ubuntu0.1 Versions-Tabelle: *** 2.8.0-2ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2.8.0-2 0 500 http://ch.archive.ubuntu.com/ubuntu/ lucid/main Packages Could you look into that please? |
|
05-05-2012, 01:51 PM | #155 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Ubuntu Compile problems
The first /bin/sh and/or /bin/bash is the result of /bin/dash -
Say: "Thank You, Canonical" Under 10.4 you may have to explicitly install bash (apt-get install bash). It is certainly the /bin/sh problem (linked to /bin/dash) and from your report, I would say that your 10.4 also has /bin/bash linked to /bin/dash. - - - - The "warning implicate defination..." errors come from one or more missing header files. "gcc -E " might give you some help in spotting the missing header(s). |
Advert | |
|
05-05-2012, 01:55 PM | #156 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
And a quick reference to the extended test __keyword__:
http://tldp.org/LDP/abs/html/testconstructs.html |
05-05-2012, 02:36 PM | #157 | |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
I'm aware of Ubuntu's "dash initiative", or whatever you want to call it, and I don't fully understand it either. But in any case, if at all, it was only ever advocated as a replacement for sh, not for bash. Code:
~$ ls -la `which sh` lrwxrwxrwx 1 root root 4 2010-11-17 21:41 /bin/sh -> dash ~$ ls -la `which bash` -rwxr-xr-x 1 root root 934336 2010-04-19 04:16 /bin/bash PS: I keep misspelling NiLuJe's username. Everytime. Sorry... Last edited by ixtab; 05-05-2012 at 05:07 PM. |
|
05-06-2012, 02:14 AM | #158 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@ixtab: Huh, I've been using double brackets tests for a good while, never thought there'd be such an issue, I knew it wasn't the most portable syntax, but still... Will keep it in mind in the future .
As for the libarchive stuff, yep, apparently some stuff, most notably a good part of the the *disk stuff was added in libarchive 3... I'll make that more clear in the readme, and kill some useless ifdef I had for some other libarchive 2 stuff . (FYI, that's also most likely the cause of the implicit declaration warnings). Also, what in the hell is happening with the LFS handling on Ubuntu? All those lli arg type mismatch warnings should not be here with the _FILE_OFFSET_BITS define, especially on an amd64 system, where it should be the default anyway, so I'll look into that as well... EDIT: Well, the first one at least, stat/lstat should be pulling *stat64 symbols, not *stat, and that should be an __off64_t... What does your features/stdio header files look like, and what would seem to be needed to get proper LFS support? EDIT²: Oops, my bad, don't bother, I can (of course) reproduce this on my amd64 box... That'll teach me to try to understand/explain stuff while slightly drunk . Thanks for the feedback . Last edited by NiLuJe; 05-06-2012 at 03:56 AM. |
05-06-2012, 02:50 AM | #159 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
|
05-06-2012, 03:33 AM | #160 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Ah, thanks geekmaster, I indeed dimly remember starting using double brackets everywhere to save some forks .
On another note, the type mismatch warnings should now be fixed on x86_64 . (And I'm building against libarchive-3.0.3 or 3.0.4 here, and the first 3.x release is only 6 months old, huh). Last edited by NiLuJe; 05-06-2012 at 03:58 AM. |
05-06-2012, 07:50 AM | #161 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
For projects too small for a build system or even for a configure script (which could either supply or at least test for required version dependencies)... My personal policy is to try to stay compatible with the "oldest, common, stable" development environment likely to be encountered. I.E: The oldest Debian or Ubuntu release still "actively supported". This problem report was from a user of Ubuntu LTS 10.4 which is a fairly old software version environment in the Linux world but still "actively supported". How the "small project developer" chooses to deal with the situation is up to them, I only offered my choice as one example. I also think that this comment applies here: https://www.mobileread.com/forums/sho...1&postcount=42 |
|
05-06-2012, 11:16 AM | #162 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Last edited by geekmaster; 05-06-2012 at 11:30 AM. |
|
05-06-2012, 11:25 AM | #163 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
The problem in this thread came about from off-kindle builds using something other than Bash (specifically here, sh is linked to dash rather than bash). Developers here just need to know that sometimes they have to populate a chroot or linux-vserver instance with the things a development script expects. (I.E: Not everything "sh" will work under "dash" and not everything Bash-3 will work under Bash-4.) Hmm... Where did I put my Linux Poker link? |
|
05-06-2012, 11:35 AM | #164 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Last edited by geekmaster; 05-06-2012 at 08:26 PM. |
|
05-06-2012, 08:22 PM | #165 |
Connoisseur
Posts: 65
Karma: 20728
Join Date: Jan 2010
Device: K2i, K3(B006), KT(WiFi)
|
Could you post a binary for this?
I see this was committed a couple of days ago into to git Could you post a binary for this, ixtab?
|
Tags |
kindle touch hacks |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Extended Linux Functionality - GUI Launcher Kindle Touch | dasmoover | Kindle Developer's Corner | 41 | 02-11-2013 06:05 PM |
Removing Ads with the GUI Launcher | vaniaspeedy | Kindle Developer's Corner | 54 | 01-23-2013 08:47 PM |
Image Viewer: An extension for GUI Launcher on Kindle Touch 5.1 | starsy | Kindle Developer's Corner | 20 | 08-04-2012 04:15 PM |
Installing Yifan Lu's Launcher on Kindle Touch 5.03 | pwright2 | Amazon Kindle | 2 | 02-12-2012 10:13 PM |