It seems like every time I start Rockbox these days it does a re-scan
of my disk and then spends a minute or two committing the database.
This is very frustrating when you just want to start listening
straight away. Usually I've only updated a few podcasts on the file
system so why does this stage
2009/6/11 Alex Bennee kernel-hac...@bennee.com
It seems like every time I start Rockbox these days it does a re-scan
of my disk and then spends a minute or two committing the database.
This is very frustrating when you just want to start listening
straight away. Usually I've only updated a
2009/6/11 Bryan Childs godea...@gmail.com:
2009/6/11 Alex Bennee kernel-hac...@bennee.com
Usually I've only updated a few podcasts on the file
system so why does this stage take so long?
Why have you sent this to the development list ?
Well I thought the developers would probably have a
Alex Bennee wrote:
Well I thought the developers would probably have a better idea
It's the development list, not the developer list. It's for discussing
Rockbox development, not contacting the developers. ALL support
questions, even ones where you expect the developers are likely to know
the
2009/6/11 Paul Louden paulthen...@gmail.com:
Alex Bennee wrote:
Well I thought the developers would probably have a better idea
It's the development list, not the developer list. It's for discussing
Rockbox development, not contacting the developers. ALL support questions,
even ones where
Alex Bennee wrote:
Fair enough, I was just curious and looking for pointers for development.
Pointers for development on what? Maybe if you stated where you're at or
what you're working on, it might be more clear what you're asking. The
original question looked like a simple database
2009/6/11 Paul Louden paulthen...@gmail.com:
Alex Bennee wrote:
Fair enough, I was just curious and looking for pointers for development.
Pointers for development on what?
How to speed up the database updates?
Maybe if you stated where you're at or
what you're working on, it might be
Alex Bennee wrote:
Pointers for development on what?
How to speed up the database updates?
Maybe you should've mentioned that in your original question then,
instead of simply asking about it being slow.
I seem to be stuck between a support observation and desire to know the
Hi all,
building the ipodpatcher, I get the following error:
gcc -Wall -W -o ipodpatcher main.c ipodpatcher.c fat32format.c arc4.c
ipodio-posix.c
fat32format.c:59: error: expected ) before x
fat32format.c:72: error: expected ) before x
make: *** [ipodpatcher] Errore 1
It seems that the
On Thu, Jun 11, 2009 at 6:49 PM, asetticoasett...@rossomaltese.it wrote:
building the ipodpatcher, I get the following error:
building works fine for me. Maybe you should tell use about your build
environment? What OS / distro, what compiler (version) and similar.
- Dominik
*In data 11/06/2009 19:10, Dominik Riebeling ha scritto*:
On Thu, Jun 11, 2009 at 6:49 PM, asetticoasett...@rossomaltese.it wrote:
building the ipodpatcher, I get the following error:
building works fine for me. Maybe you should tell use about your build
environment? What OS / distro, what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le Thu, 11 Jun 2009 19:41:27 +0200,
asettico asett...@rossomaltese.it a écrit :
ld: GNU ar 2.16.1
Host gcc: gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
I use ubuntu as well and I can confirm fat32format.c fails to build.
The problem is htole16 and htole32
Rafaël Carré wrote:
The problem is htole16 and htole32 are defined in endian.h (under ifdef
__USE_BSD)
I believe this is a bug in Ubuntu, but if other OS (BSD?) provide these
functions they should be under #ifndef htole16 ?
I don't think this is a Ubuntu problem - those macros were added with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le Thu, 11 Jun 2009 22:20:29 +0100,
Dave Chapman d...@dchapman.com a écrit :
Rafaël Carré wrote:
The problem is htole16 and htole32 are defined in endian.h (under
ifdef __USE_BSD)
I believe this is a bug in Ubuntu, but if other OS (BSD?)
Hi,
I've just created the 3.3 release branch. To check it out, run:
svn co svn://svn.rockbox.org/rockbox/branches/v3_3 rockbox-3.3
This means that trunk is again free for regular development. However,
please don't be afraid to concentrate on bugs for the time being, and
maybe don't do invasive
15 matches
Mail list logo
