Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Kimmo Hämäläinen 
On Wed, 2006-10-04 at 15:44, ext Guillem Jover wrote:
> On Wed, 2006-10-04 at 14:36:24 +0300, ext Kimmo Hämäläinen wrote:
> > On Wed, 2006-10-04 at 14:04, ext Murray Cumming wrote:
> > > On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
> > > > Yes, it does not tell the reasons for the changes (they are in
> > > > debian/changelog), but I'm too lazy to put those since you seem to be
> > > > the only one who is interested about Libosso changes ;)
> 
> I consider those two serve different purposes, ChangeLog (as in upstream)
> explains in detail up to the function and variable level what has been
> changed. And debian/changelog describes the packaging changes, and a
> summary of upstream changes if it's native package.

I knew this, but if I only edit one file, then it's debian/changelog.
There is no upstream in this case, not even other developers...

> > > At the moment, nobody (me included) knows what on earth libosso is. The
> > > README is empty, for instance.
> >
> > It's there just because automake complains otherwise.
> 
> That's because automake defaults to gnu strictness, if you are not
> following the GCS[0] you probably want:
> 
> AM_INIT_AUTOMAKE([foreign])
> 
> > 98% of Debian packages the README file is totally useless anyway.
> 
> On this one I disagree, if you have specific examples, please tell me
> or file bug reports.

I'm not that bored.

> > > ChangeLogs are one way to introduce people to what a module does and how
> > > it works, and how it is evolving. Not doing ChangeLogs because nobody
> > > cares about them would be almost a circular argument.
> 
> [ This snipped reordered ]
> > The code and API should be pretty self-explaining (yes, they're not,
> > that's why I'm working on new API).
> 
> > Well, just try to use the diff. The code is so simple that manually
> > writing some ChangeLog just seems stupid to me.
> 
> It's not about the code being simple, it's about having an offline
> history of what has been changed and how the code evolved. That's
> pretty useful when tracking down bugs for example.

I think this 'offline usage' is rare enough use case to ignore
(especially with Libosso). The bugs are pretty simple to spot if the
code is simple and short (especially if you have access to SVN).

BR; Kimmo

> 
> 
> [0] 
> 
> regards,
> guillem
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] WARNING: backups are broken with sardine

2006-10-04 Thread Koen Kooi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[EMAIL PROTECTED] schreef:
> Hi,
> 
> Same as extracting your IT-2006 backup on IT-2005 device - this will
> just not work - the backup is meant to work in the other direction.

I guess I read "Do not overwrite it with backups made with Sardine since these 
will not be
reliable" differently is you.

regards,

Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFI635MkyGM64RGpERAiPrAKCT4C85aSZ32tkBh5JhzLdAVDUrOQCffRvY
lVS/LXb9diL+EjrQuRD27mA=
=ejKF
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Guillem Jover 
On Wed, 2006-10-04 at 14:36:24 +0300, ext Kimmo Hämäläinen wrote:
> On Wed, 2006-10-04 at 14:04, ext Murray Cumming wrote:
> > On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
> > > Yes, it does not tell the reasons for the changes (they are in
> > > debian/changelog), but I'm too lazy to put those since you seem to be
> > > the only one who is interested about Libosso changes ;)

I consider those two serve different purposes, ChangeLog (as in upstream)
explains in detail up to the function and variable level what has been
changed. And debian/changelog describes the packaging changes, and a
summary of upstream changes if it's native package.

> > At the moment, nobody (me included) knows what on earth libosso is. The
> > README is empty, for instance.
>
> It's there just because automake complains otherwise.

That's because automake defaults to gnu strictness, if you are not
following the GCS[0] you probably want:

AM_INIT_AUTOMAKE([foreign])

> 98% of Debian packages the README file is totally useless anyway.

On this one I disagree, if you have specific examples, please tell me
or file bug reports.

> > ChangeLogs are one way to introduce people to what a module does and how
> > it works, and how it is evolving. Not doing ChangeLogs because nobody
> > cares about them would be almost a circular argument.

[ This snipped reordered ]
> The code and API should be pretty self-explaining (yes, they're not,
> that's why I'm working on new API).

> Well, just try to use the diff. The code is so simple that manually
> writing some ChangeLog just seems stupid to me.

It's not about the code being simple, it's about having an offline
history of what has been changed and how the code evolved. That's
pretty useful when tracking down bugs for example.


[0] 

regards,
guillem
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

RE: [maemo-developers] WARNING: backups are broken with sardine

2006-10-04 Thread Jakub.Pavelek 
Hi,

Same as extracting your IT-2006 backup on IT-2005 device - this will
just not work - the backup is meant to work in the other direction.

Br,

--jakub

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] On Behalf Of ext Koen Kooi
>Sent: 04 October, 2006 13:05
>To: maemo developers
>Subject: [maemo-developers] WARNING: backups are broken with sardine
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Hi,
>
>I just found out that backups made with sardine don't work 
>with IT2006. Great. Thank you.
>
>
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1.4.1 (Darwin)
>
>iD8DBQFFI4dbMkyGM64RGpERArFuAKC52tU9RdYoQBTY4Tx/EeVdB9lfywCfYbK3
>q87az/yUcj7X5mDT1mako8c=
>=UwjE
>-END PGP SIGNATURE-
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Kimmo Hämäläinen 
On Wed, 2006-10-04 at 14:58, ext Murray Cumming wrote:
...
> Could you at least put together a one sentence description of what this
> module does?

Ok, I'll put it to trunk. Damn, had to yield a little... :)

BR; Kimmo

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Murray Cumming 
On Wed, 2006-10-04 at 14:36 +0300, Kimmo Hämäläinen wrote:
> On Wed, 2006-10-04 at 14:04, ext Murray Cumming wrote:
> > On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
> > [snip]
> > > Yes, it does not tell the reasons for the changes (they are in
> > > debian/changelog), but I'm too lazy to put those since you seem to be
> > > the only one who is interested about Libosso changes ;)
> > > 
> > > > By the way, most projects that I work with in the GNOME world just
> > > > copy/paste their ChangeLog entry into the commit comment.
> > > 
> > > I'll do that if Libosso is in Gnome someday :)
> > > 
> > > Btw. I've had exactly one patch from outside Nokia for Libosso and it
> > > was from you. Many thanks.
> > 
> > At the moment, nobody (me included) knows what on earth libosso is. The
> > README is empty, for instance.
> 
> It's there just because automake complains otherwise. The code and API
> should be pretty self-explaining (yes, they're not, that's why I'm
> working on new API). 98% of Debian packages the README file is totally
> useless anyway.

Almost 98% of debian packages are useless, I guess. But really, I'll
take a description from anywhere - it doesn't have to be a README.

> > ChangeLogs are one way to introduce people to what a module does and how
> > it works, and how it is evolving. Not doing ChangeLogs because nobody
> > cares about them would be almost a circular argument.
> 
> Well, just try to use the diff. The code is so simple that manually
> writing some ChangeLog just seems stupid to me.
> 
> > It's your module, but it would help me.
> 
> Just ask me if you have questions (and I'll look the answers from the
> code).

Could you at least put together a one sentence description of what this
module does?

-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Kimmo Hämäläinen 
On Wed, 2006-10-04 at 14:04, ext Murray Cumming wrote:
> On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
> [snip]
> > Yes, it does not tell the reasons for the changes (they are in
> > debian/changelog), but I'm too lazy to put those since you seem to be
> > the only one who is interested about Libosso changes ;)
> > 
> > > By the way, most projects that I work with in the GNOME world just
> > > copy/paste their ChangeLog entry into the commit comment.
> > 
> > I'll do that if Libosso is in Gnome someday :)
> > 
> > Btw. I've had exactly one patch from outside Nokia for Libosso and it
> > was from you. Many thanks.
> 
> At the moment, nobody (me included) knows what on earth libosso is. The
> README is empty, for instance.

It's there just because automake complains otherwise. The code and API
should be pretty self-explaining (yes, they're not, that's why I'm
working on new API). 98% of Debian packages the README file is totally
useless anyway.

> ChangeLogs are one way to introduce people to what a module does and how
> it works, and how it is evolving. Not doing ChangeLogs because nobody
> cares about them would be almost a circular argument.

Well, just try to use the diff. The code is so simple that manually
writing some ChangeLog just seems stupid to me.

> It's your module, but it would help me.

Just ask me if you have questions (and I'll look the answers from the
code).

BR, Kimmo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Murray Cumming 
On Wed, 2006-10-04 at 13:04 +0200, Murray Cumming wrote:
> On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
> [snip]
> > Yes, it does not tell the reasons for the changes (they are in
> > debian/changelog), but I'm too lazy to put those since you seem to be
> > the only one who is interested about Libosso changes ;)
> > 
> > > By the way, most projects that I work with in the GNOME world just
> > > copy/paste their ChangeLog entry into the commit comment.
> > 
> > I'll do that if Libosso is in Gnome someday :)
> > 
> > Btw. I've had exactly one patch from outside Nokia for Libosso and it
> > was from you. Many thanks.
> 
> At the moment, nobody (me included) knows what on earth libosso is. The
> README is empty, for instance.
> 
> ChangeLogs are one way to introduce people to what a module does and how
> it works, and how it is evolving. Not doing ChangeLogs because nobody
> cares about them would be almost a circular argument.
> 
> It's your module, but it would help me.

Sorry to go on about this, but for people wishing to start enjoying the
wonders of ChangeLogs, this script is very useful. It creates a
ChangeLog entry that already lists the changed files and functions, so
you can just write the explanatory text:
http://www.gnome.org/~fherrera/patches/prepare-ChangeLog.pl
 
-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Hildon C++ bindings moved to garage

2006-10-04 Thread Murray Cumming 
The hildon C++ bindings (hildon-libsmm and hildon-widgetsmm) have been
moved from contrib to the garage SVN repository. I doubt that the
contrib SVN repository will be used for anything else in the future.

Among other things, this makes it easier to give write access to other
developers.

The project page:
https://garage.maemo.org/projects/maemomm/

The sources:
https://garage.maemo.org/svn/maemomm/trunk/

The current version is available from the garage debian repository, and
I have just confirmed that they build from source with jhbuild:
http://www.maemo.org/maemowiki/MaemoWithJhbuild

-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Murray Cumming 
On Wed, 2006-10-04 at 13:45 +0300, Kimmo Hämäläinen wrote:
[snip]
> Yes, it does not tell the reasons for the changes (they are in
> debian/changelog), but I'm too lazy to put those since you seem to be
> the only one who is interested about Libosso changes ;)
> 
> > By the way, most projects that I work with in the GNOME world just
> > copy/paste their ChangeLog entry into the commit comment.
> 
> I'll do that if Libosso is in Gnome someday :)
> 
> Btw. I've had exactly one patch from outside Nokia for Libosso and it
> was from you. Many thanks.

At the moment, nobody (me included) knows what on earth libosso is. The
README is empty, for instance.

ChangeLogs are one way to introduce people to what a module does and how
it works, and how it is evolving. Not doing ChangeLogs because nobody
cares about them would be almost a circular argument.

It's your module, but it would help me.

-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Reply to of this list is not maemo-developers@maemo.org

2006-10-04 Thread Guillem Jover 
On Tue, 2006-10-03 at 23:41:39 +0200, ext koos vriezen wrote:
> I keep forgetting the reply-to-all of my mailer for lists that don't
> set the ReplyTo or From to the list itself. Is that intentional (or
> otherwise can that be changed)?

Consider for example:

  

regards,
guillem
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Kimmo Hämäläinen 
On Wed, 2006-10-04 at 13:37, ext Murray Cumming wrote:
> On Wed, 2006-10-04 at 13:11 +0300, Kimmo Hämäläinen wrote:
> > On Wed, 2006-10-04 at 12:37, ext Murray Cumming wrote:
> > > Is the source in the maemo svn for libosso up to date?
> > 
> > Yes.
> > 
> > > I am surprised that there are no recent ChangeLog entries:
> > > https://stage.maemo.org/svn/maemo/projects/haf/trunk/libosso/ChangeLog
> > 
> > That's because I only use debian/changelog. ('svn diff' is enough, I
> > think.)
> 
> OK. Thanks. That is a little odd. Looking at debian/changelog, it would
> be nice if it mentioned what files and functions were changed, as you'll
> tend to see for projects such as GKT+.
> 
> I don't understand the comment about svn diff.

I meant that 'svn diff' allows you to see what files and functions were
changed. For example:
svn diff
https://stage.maemo.org/svn/maemo/projects/haf/tags/libosso/1.18-1/
https://stage.maemo.org/svn/maemo/projects/haf/tags/libosso/1.19-1/

Yes, it does not tell the reasons for the changes (they are in
debian/changelog), but I'm too lazy to put those since you seem to be
the only one who is interested about Libosso changes ;)

> By the way, most projects that I work with in the GNOME world just
> copy/paste their ChangeLog entry into the commit comment.

I'll do that if Libosso is in Gnome someday :)

Btw. I've had exactly one patch from outside Nokia for Libosso and it
was from you. Many thanks.

BR, Kimmo

> > 
> > > and I have a build error [1]:
> > > 
> > > osso-init.c: In function `add_to_if_hash':
> > > osso-init.c:519: warning: passing arg 2 of `g_list_append' discards
> > > qualifiers from pointer target type
> > > osso-init.c:538: warning: passing arg 2 of `g_list_append' discards
> > > qualifiers from pointer target type
> > > osso-init.c: In function `_msg_handler_rm_cb_f':
> > > osso-init.c:709: error: assignment of read-only member `handlers'
> > > osso-init.c:736: error: assignment of read-only member `handlers'
> > > make[2]: *** [osso-init.lo] Error 1
> > > make[2]: Leaving directory `/home/murrayc/cvs/maemo/libosso/src'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory `/home/murrayc/cvs/maemo/libosso'
> > > make: *** [all] Error 2
> > > *** error during stage build of libosso: Error running make   *** [6/8]
> > 
> > It compiled for me, but I have probably different environment...
> > Patches are welcome, as always! :)
> > 
> > BR; Kimmo
> > 
> > > [1] though my compiler might be different because I'm trying once more
> > > (stupidly) with scratchbox 1.0.5, because I need it for another
> > > codebase, and I can't have two scratchboxes on one PC.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Murray Cumming 
On Wed, 2006-10-04 at 13:11 +0300, Kimmo Hämäläinen wrote:
> On Wed, 2006-10-04 at 12:37, ext Murray Cumming wrote:
> > Is the source in the maemo svn for libosso up to date?
> 
> Yes.
> 
> > I am surprised that there are no recent ChangeLog entries:
> > https://stage.maemo.org/svn/maemo/projects/haf/trunk/libosso/ChangeLog
> 
> That's because I only use debian/changelog. ('svn diff' is enough, I
> think.)

OK. Thanks. That is a little odd. Looking at debian/changelog, it would
be nice if it mentioned what files and functions were changed, as you'll
tend to see for projects such as GKT+.

I don't understand the comment about svn diff.

By the way, most projects that I work with in the GNOME world just
copy/paste their ChangeLog entry into the commit comment.

> 
> > and I have a build error [1]:
> > 
> > osso-init.c: In function `add_to_if_hash':
> > osso-init.c:519: warning: passing arg 2 of `g_list_append' discards
> > qualifiers from pointer target type
> > osso-init.c:538: warning: passing arg 2 of `g_list_append' discards
> > qualifiers from pointer target type
> > osso-init.c: In function `_msg_handler_rm_cb_f':
> > osso-init.c:709: error: assignment of read-only member `handlers'
> > osso-init.c:736: error: assignment of read-only member `handlers'
> > make[2]: *** [osso-init.lo] Error 1
> > make[2]: Leaving directory `/home/murrayc/cvs/maemo/libosso/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/murrayc/cvs/maemo/libosso'
> > make: *** [all] Error 2
> > *** error during stage build of libosso: Error running make   *** [6/8]
> 
> It compiled for me, but I have probably different environment...
> Patches are welcome, as always! :)
> 
> BR; Kimmo
> 
> > [1] though my compiler might be different because I'm trying once more
> > (stupidly) with scratchbox 1.0.5, because I need it for another
> > codebase, and I can't have two scratchboxes on one PC.
-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Kimmo Hämäläinen 
On Wed, 2006-10-04 at 12:37, ext Murray Cumming wrote:
> Is the source in the maemo svn for libosso up to date?

Yes.

> I am surprised that there are no recent ChangeLog entries:
> https://stage.maemo.org/svn/maemo/projects/haf/trunk/libosso/ChangeLog

That's because I only use debian/changelog. ('svn diff' is enough, I
think.)

> and I have a build error [1]:
> 
> osso-init.c: In function `add_to_if_hash':
> osso-init.c:519: warning: passing arg 2 of `g_list_append' discards
> qualifiers from pointer target type
> osso-init.c:538: warning: passing arg 2 of `g_list_append' discards
> qualifiers from pointer target type
> osso-init.c: In function `_msg_handler_rm_cb_f':
> osso-init.c:709: error: assignment of read-only member `handlers'
> osso-init.c:736: error: assignment of read-only member `handlers'
> make[2]: *** [osso-init.lo] Error 1
> make[2]: Leaving directory `/home/murrayc/cvs/maemo/libosso/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/murrayc/cvs/maemo/libosso'
> make: *** [all] Error 2
> *** error during stage build of libosso: Error running make   *** [6/8]

It compiled for me, but I have probably different environment...
Patches are welcome, as always! :)

BR; Kimmo

> [1] though my compiler might be different because I'm trying once more
> (stupidly) with scratchbox 1.0.5, because I need it for another
> codebase, and I can't have two scratchboxes on one PC.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] WARNING: backups are broken with sardine

2006-10-04 Thread Koen Kooi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I just found out that backups made with sardine don't work with IT2006. Great. 
Thank you.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFI4dbMkyGM64RGpERArFuAKC52tU9RdYoQBTY4Tx/EeVdB9lfywCfYbK3
q87az/yUcj7X5mDT1mako8c=
=UwjE
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] libosso svn up-to-date?

2006-10-04 Thread Murray Cumming 
Is the source in the maemo svn for libosso up to date?

I am surprised that there are no recent ChangeLog entries:
https://stage.maemo.org/svn/maemo/projects/haf/trunk/libosso/ChangeLog

and I have a build error [1]:

osso-init.c: In function `add_to_if_hash':
osso-init.c:519: warning: passing arg 2 of `g_list_append' discards
qualifiers from pointer target type
osso-init.c:538: warning: passing arg 2 of `g_list_append' discards
qualifiers from pointer target type
osso-init.c: In function `_msg_handler_rm_cb_f':
osso-init.c:709: error: assignment of read-only member `handlers'
osso-init.c:736: error: assignment of read-only member `handlers'
make[2]: *** [osso-init.lo] Error 1
make[2]: Leaving directory `/home/murrayc/cvs/maemo/libosso/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/murrayc/cvs/maemo/libosso'
make: *** [all] Error 2
*** error during stage build of libosso: Error running make   *** [6/8]


[1] though my compiler might be different because I'm trying once more
(stupidly) with scratchbox 1.0.5, because I need it for another
codebase, and I can't have two scratchboxes on one PC.

-- 
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] compiling problems in scratchbox

2006-10-04 Thread Andrey Khurri 

Hi there,

I've got a problem with compiling some stuff in Scratchbox. It seems 
that compiler does not understand an option '-llibrary' when linking. It 
works elsewhere but in Scratchbox. I tried both sbox-i686-linux-gcc and 
sbox-arm-linux-gcc compilers. Both are 3.4.4 version (CodeSourcery ARM 
2005q3-2).


Do you know if this option is supported at all by sbox compilers or 
should it be invoked in some other way than '-llibrary' or '-l library'?


I checked that I have those libraries which I am trying to link 
installed so it shouldn't be a point (libraries are located under 
/usr/lib/ as a liblibrary.a)


The help messages for sbox compilers are not that helpful and contain 
nothing related to '-llibrary' option.


Below is an output of the error for PC target:

sbox-i686-linux-gcc: -lgthread-2.0: linker input file unused because 
linking not done
sbox-i686-linux-gcc: -lglib-2.0: linker input file unused because 
linking not done
sbox-i686-linux-gcc: -lgobject-2.0: linker input file unused because 
linking not done
sbox-i686-linux-gcc: -lglib-2.0: linker input file unused because 
linking not done
sbox-i686-linux-gcc: ../libinet6/.libs/libinet6.a: linker input file 
unused because linking not done
sbox-i686-linux-gcc: ../libhiptool/.libs/libhiptool.a: linker input file 
unused because linking not done

cc1: error: unrecognized command line option "-lgthread-2.0"
cc1: error: unrecognized command line option "-lglib-2.0"
cc1: error: unrecognized command line option "-lgobject-2.0"
cc1: error: unrecognized command line option "-lglib-2.0"

Would appreciate your help,

Andrey
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] high speed (52/48Mhz) MMC mode added

2006-10-04 Thread Kemal Hadimli 

works here too, with kingston 1gb mmcmobile (will get a 2gb later probably)
thanks!

Nokia770-26:~# time dd if=/dev/mmcblk0 of=/dev/null bs=8192 count=10240
10240+0 records in
10240+0 records out
real0m 15.42s
user0m 0.05s
sys 0m 2.03s

now if only they would make 4gb and 8gb mmcmobile cards. (samsung has
up to 8gb mmc's but no mmcmobile)

On 10/3/06, Koen Kooi <[EMAIL PROTECTED]> wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frantisek Dufka schreef:
> Hello,
>
> This kernel enables also 52Mhz high-speed MMC mode (works on Kingston
> 2GB MMCmobile). Complete summary of changes:
>
> 1. legacy MMC cards run at 16Mhz instead of original 12Mhz (1.3x
> speedup), my 64MB card included with N770 does not work with this,
> others do work (Sandisk 1GB). I suppose the card is buggy as max DTR in
> CSD is honored in MMC driver and card claims it can handle up to 20Mhz.
>
> 2. MMCplus/mobile cards run at 24 or 48Mhz only if cards claim to
> support v4 specs, report its speed in EXT_CSD structure (26 vs 52Mhz)
> and switch command to high-speed mode (CMD 6) worked.

With my 1GB sandisk RS-MMC:

time dd if=/dev/mmcblk0 of=/dev/null bs=8192
count=10240 # 44.13 seconds

Is that ~24MHz?


regards,

Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFInJ6MkyGM64RGpERAg/9AJ9W3E7XUNGk9dZUblK+0/JBT7KscgCgr+94
7tEDjRKX7sZ9x4Q5kFe2EvU=
=Sfsf
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers




--
Kemal
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers