Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 3 days, 10 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 5 days, 7 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 6 days, 4 hrs ago - more...
Yana |
2010-12-06
, 15:53
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Dec 2010
|
#111
|
Originally Posted by egoshin
I try to install libqt4-dev-arm_4.7.0~git20100909_armel.deb from https://garage.maemo.org/frs/?group_...elease_id=4213 - but the Application Manager gives me the following error: "Cannot install 'libqt4-dev'. Incompatible application package". (My N900 has Russian as the default language, so I've translated the error message from Russian to English).
 |
|
2011-02-06
, 15:09
|
|
Posts: 191 |
Thanked: 46 times |
Joined on Jun 2010
@ NanJing China
|
#112
|
does it come any updatel to the pr1.3???
I am not a developer , konw nothing but C .
However, I want to have it a try on my N900. Mine is Pr1.3 and the image is 1.2 so iam waiting for a update......
I am not a developer , konw nothing but C .
However, I want to have it a try on my N900. Mine is Pr1.3 and the image is 1.2 so iam waiting for a update......
|
|
2011-02-06
, 15:10
|
|
Posts: 191 |
Thanked: 46 times |
Joined on Jun 2010
@ NanJing China
|
#113
|
Originally Posted by Khertan
but I doesn't use python , er......
Personnally i use KhtEditor as editor, maybe because i'm the author
|
|
2012-07-09
, 13:15
|
|
Posts: 1,163 |
Thanked: 1,873 times |
Joined on Feb 2011
@ The Netherlands
|
#114
|
I tried to make my own sdkimage of PR1.3, but I have a broken package system. I can't install the nokia-binaries.
Don't understand where in the process I have gone wrong
Looks like I'm missing some repository or something like that
log
Don't understand where in the process I have gone wrong
Looks like I'm missing some repository or something like thatlog
Code:
[root@maemo-sdk-v1_3: /]apt-get install nokia-binaries Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nokia-binaries: Depends: calendar-backend but it is not going to be installed Depends: calendar-backend-dev but it is not going to be installed Depends: calendar-backend-doc but it is not going to be installed Depends: clockd but it is not going to be installed Depends: csd-base but it is not going to be installed Depends: evolution-data-server-addressbook-backend-sim but it is not going to be installed Depends: fmtx-middleware but it is not going to be installed Depends: hald-addon-bme but it is not going to be installed Depends: hildon-im-common-virtual-settings but it is not going to be installed Depends: hildon-im-fkb but it is not going to be installed Depends: hildon-input-method-configurator but it is not going to be installed Depends: hildon-plugins-notify-sv but it is not going to be installed Depends: hildon-status-menu but it is not installable Depends: hildon-theme-alpha but it is not going to be installed Depends: icd2 but it is not going to be installed Depends: icd2-dev but it is not going to be installed Depends: icd2-settings-default but it is not going to be installed Depends: libaccounts0 but it is not going to be installed Depends: libaccounts-dev but it is not going to be installed Depends: libaccounts-glade but it is not going to be installed Depends: libcityinfo0-0 but it is not going to be installed Depends: libcityinfo-dev but it is not going to be installed Depends: libclockcore0-0 but it is not going to be installed Depends: libcodelockui1 but it is not going to be installed Depends: libcodelockui1-dev but it is not going to be installed Depends: libcumulus0 but it is not going to be installed Depends: libdevlock1 but it is not going to be installed Depends: libdevlock-bin but it is not going to be installed Depends: libgles1 but it is not going to be installed Depends: libgles1-sgx-img but it is not going to be installed Depends: libgles1-sgx-img-dev but it is not going to be installed Depends: libgles2 but it is not going to be installed Depends: libgles2-sgx-img but it is not going to be installed Depends: libgles2-sgx-img-dev but it is not going to be installed Depends: libhildon-im-vkbrenderer3 but it is not going to be installed Depends: libhildon-im-western-plugin-common3 but it is not going to be installed Depends: libhildon-time-zone-chooser0-0 but it is not going to be installed Depends: libicd2 but it is not going to be installed Depends: liblocation0 but it is not going to be installed Depends: liblocation-dev but it is not going to be installed Depends: liblomesa0 but it is not going to be installed Depends: libnavigation0 but it is not going to be installed Depends: libnavigation-dev but it is not going to be installed Depends: libosso-abook but it is not going to be installed Depends: libosso-abook-dev but it is not going to be installed Depends: libplayback-1-0 but it is not going to be installed Depends: libprofile0 but it is not going to be installed Depends: librtcom-accounts-ui-client0 but it is not going to be installed Depends: librtcom-accounts-ui-client-dev but it is not going to be installed Depends: librtcom-accounts-ui-dev but it is not going to be installed Depends: librtcom-accounts-widgets0 but it is not going to be installed Depends: librtcom-accounts-widgets-dev but it is not going to be installed Depends: librtcom-eventlogger0 but it is not installable Depends: librtcom-eventlogger-dev but it is not installable Depends: librtcom-eventlogger-plugins0 but it is not installable Depends: librtcom-eventlogger-plugins-dev but it is not installable Depends: librtcom-eventlogger-ui0 but it is not installable Depends: librtcom-eventlogger-ui-dev but it is not installable Depends: libsharing0 but it is not going to be installed Depends: libsharing-plugin-dev but it is not going to be installed Depends: libsignon-glib0 but it is not going to be installed Depends: libsignon-glib-dev but it is not going to be installed Depends: libsimpb0 but it is not going to be installed Depends: libtime0 but it is not going to be installed Depends: libtime-dev but it is not going to be installed Depends: location-daemon but it is not going to be installed Depends: mce but it is not going to be installed Depends: opengles-sgx-img-common but it is not going to be installed Depends: opengles-sgx-img-common-dev but it is not going to be installed Depends: osso-applet-textinput but it is not going to be installed Depends: osso-bookmark-engine but it is not going to be installed Depends: osso-bookmark-engine-dev but it is not going to be installed Depends: osso-mission-control but it is not going to be installed Depends: osso-systemui but it is not going to be installed Depends: osso-systemui-alarm but it is not going to be installed Depends: profiled but it is not going to be installed Depends: rtcom-accounts-ui but it is not going to be installed Depends: sharing-account-manager but it is not going to be installed Depends: sharing-dialog but it is not going to be installed Depends: sharing-manager but it is not going to be installed Depends: sharing-service-flickr but it is not going to be installed Depends: sharing-service-ovi but it is not going to be installed Depends: signon-utils but it is not going to be installed Depends: signond-dev but it is not going to be installed Depends: signond0 but it is not going to be installed Depends: ui-fonts but it is not going to be installed Depends: fakeroot-net but it is not installable Depends: hildon-theme-devel but it is not installable Depends: libhildon-thumbnail-dev but it is not installable Depends: libhildon-thumbnail0-dbg but it is not installable Depends: hildon-thumbnail but it is not installable Depends: libhildondesktop1-dev but it is not installable Depends: hildon-home but it is not installable Depends: hildon-control-panel-dev but it is not installable Depends: hildon-control-panel-dbg but it is not installable Depends: hildon-control-panel but it is not installable Depends: hildon-application-manager-dbg but it is not installable Depends: hildon-application-manager but it is not installable Depends: hildon-desktop but it is not installable Depends: libloudmouth1-0-dbg but it is not installable Depends: libloudmouth1-dev but it is not installable Depends: telepathy-gabble but it is not installable Depends: tracker but it is not installable Depends: osso-af-sb-startup but it is not installable E: Broken packages
__________________
N900 loaded with:
CSSU-T (Thumb)
720p recording,
Pierogi, Lanterne, Cooktimer, Frogatto
N9 16GB loaded with:
Kernel-Plus
--
[TCPdump & libpcap | ngrep]
--
donate
N900 loaded with:
CSSU-T (Thumb)
720p recording,
Pierogi, Lanterne, Cooktimer, Frogatto
N9 16GB loaded with:
Kernel-Plus
--
[TCPdump & libpcap | ngrep]
--
donate
 |
|
2014-04-21
, 11:24
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#115
|
I have a question about using automake on the N900. It did not work at all to start with as all the scripts had hard-coded paths to /scratchbox/tools/bin. Having changed them to /usr/bin has made a big progress but I am still getting this for pretty much every random package I get from the source repos:
I can't believe it's the package as it is perfectly reproducable for any package built with autotools.
Sure thing, I've found a few sources complaining about the same thing in automake 1.10 (which is what I am using):
https://www.mail-archive.com/bug-aut.../msg01590.html
http://gnu-automake.7480.n7.nabble.c...on-td8782.html
https://duckduckgo.com/?q=requires%20AM_PROG_CC_C_O
However I am not very experienced with autotools and do not fully understand the implications or how to fix it. Any ideas?
Code:
<subdir>/Makefile.am:NN: compiling `foo.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.ac'
Sure thing, I've found a few sources complaining about the same thing in automake 1.10 (which is what I am using):
https://www.mail-archive.com/bug-aut.../msg01590.html
http://gnu-automake.7480.n7.nabble.c...on-td8782.html
https://duckduckgo.com/?q=requires%20AM_PROG_CC_C_O
However I am not very experienced with autotools and do not fully understand the implications or how to fix it. Any ideas?
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
|
|
2014-04-23
, 23:18
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#116
|
I've fixed the above problem by adding AM_PROG_CC_C_O to configure.ac. It took some fiddling as it could not go on just any line without more errors, but it works now. I am still not convinced that I should have to do that at all; a source taken from repos should work out of the box, without alterations. In other words, the problem must be in my environment.
But now I am stumbling on the next hurdle. I get past autoconf, autoheader and auomake, only to get the following from ./configure.
Indeed, that package is nowhere to be found. A forum search for hildon-1 brings up a bunch of results, all suggesting that it should magically work in the scratchbox. Is that really the case? Is there no escape from using the scratchbox? Do I need that package if developing on the device itself?
But now I am stumbling on the next hurdle. I get past autoconf, autoheader and auomake, only to get the following from ./configure.
Code:
checking for HILDON... configure: error: Package requirements (hildon-1 >= 2.1.0) were not met: No package 'hildon-1' found
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
|
|
2014-04-24
, 08:13
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#117
|
Originally Posted by pichlo
What program are you trying to compile?
Indeed, that package is nowhere to be found. A forum search for hildon-1 brings up a bunch of results, all suggesting that it should magically work in the scratchbox. Is that really the case? Is there no escape from using the scratchbox? Do I need that package if developing on the device itself?
I guess many Maemo source debs are patched to work with Maemo's autobuilder (scratchbox).
|
|
2014-04-24
, 08:46
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#118
|
Originally Posted by reinob
I've tried scv-reader and tunertool, both exhibiting the same problem. I have tried a few more but not all of them use autotools. The newer packages generally tend to use Qt which builds better on the device itself.
What program are you trying to compile?
EDIT: This time I am not planning any updates to the mentioned packages. I am building some random packages to learn from them.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
Last edited by pichlo; 2014-04-24 at 08:50.
|
|
2014-04-30
, 07:37
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#119
|
Err, problem solved. It turned out that missing hildon-1 was actually libhildon1-dev found in cssu-(thumb|testing|devel). I really hate it when things like that happen. Why on earth do they have to confuse people like that? Also, someone could have told me
But hey, that means that I can now build GTK packages on my phone as well as Qt ones. Yey!
EDIT: Oh, and by the way, some repositories look inconsistent
Last edited by pichlo; 2014-04-30 at 07:46.
But hey, that means that I can now build GTK packages on my phone as well as Qt ones. Yey!
EDIT: Oh, and by the way, some repositories look inconsistent
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
Last edited by pichlo; 2014-04-30 at 07:46.
|
|
2014-04-30
, 11:54
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#120
|
Originally Posted by pichlo
I think it was Debian
Why on earth do they have to confuse people like that? Also, someone could have told me
(but I'm not sure). In the old days there were no "packages" in the modern sense of the word, a package was a program.tar.gz, and always included not only the source but also (if it was or included a library) the headers and everything related to the program.This was (and still is AFAIK) used consistently by the only sane Linux distribution (Slackware, which unfortunately I don't use anymore).
Debian, Redhat & Co. decided that users should not have to bother with .h files, so from "package1" they split the files into "package1" (only user-executable stuff) and "libpackage1-dev" (others use "-devel" with or without the "lib" prefix).
This seems to break stuff, as the over-complicated ./configure mess should at least manage to report the correct "package", but since the package name is distribution-dependent it, apparently, cannot.
But hey, the less .h files you have on your PC, the more pr0n you can have on it
| The Following User Says Thank You to reinob For This Useful Post: | ||