Ensureing that a build is correct

[mcc01]

Hi,

(I am doing all this on Linux...)

I am currently struggling to create my own "stable build" (3.13)
of rockbox for my Sansa Clip ZIP.

At the moment my rockbox-builds crash the player while playing a mp3
file ( there are others which also crash the player), which plays nice with
the original firmware.

Unfortunately these crashes had corrupted the filesystem of the internal flash (see my other
posting).

I built the crosscompiler-chain with the buildscript of the rockbox source tree.

What may be the reason, that obviously the cross compiler does something wrong here?

By the way: the mp3 file can downloaded completly legally here:
https://archive.org/details/SecondsBeforeAwakening-One
It is called "One-2" and is the 320Kbps-mp3-version from here:
https://archive.org/download/SecondsBeforeAwakening-One/02One2.mp3
If someone wants to try it by oneself...

How should I proceed?

Best regards,
mcc

[saratoga]

Why are you building 3.13?

Anyway, post your rockbox-info.txt from the build you just compiled that doesn't work.  Might give a clue if something is wrong with your build tools.

[mcc01]

Hi Saratoga,

thanks for your quick reply !

I am building "my own 3.13" to have a stable starting point.
If my buildprocess will be able to create stable builds of the
quality of the official stable 3.13 I will ensure that -- if I am
hunting errors later on -- they will more likely be caused of
my own programming than on bugs in my buildchain...

I will start with a fresh compilation of 3.13 and post the
file than...
A minute (or so)...please...

Best regards,
mcc

[mcc01]

Hi Saratiga,

here is the contents of the rockbox-info.txt:

computer:rockbox-3.13/build>cat rockbox-info.txt
Target: sansaclipzip
Target id: 68
Target define: -DSANSA_CLIPZIP
Memory: 8
CPU: arm
Manufacturer: as3525
Version: rUnversioned directory-140507
Binary: rockbox.sansa
Binary size: 621440
Voice format: 400
Actual size: 621432
RAM usage: 948152
Features: alarm:backlight_brightness:crossfade:dircache:flash_storage:lcd_bitmap:lcd_non-mono:lcd_color:pitchscreen:multivolume:multidrive_usb:quickscreen:radio:recording:recording_swcodec:recording_mic:rtc:swcodec:tagcache:tc_ramcache:charging:large_plugin_buffer:ab_repeat_buttons:albumart:usb_power:usbstack
gcc: arm-elf-eabi-gcc (GCC) 4.4.4
ld: GNU ld (GNU Binutils) 2.20.1.20100303
Host gcc: gcc (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) 4.7.3

Best regards,
mcc

[saratoga]

I am building "my own 3.13" to have a stable starting point.
If my buildprocess will be able to create stable builds of the
quality of the official stable 3.13 I will ensure that -- if I am
hunting errors later on -- they will more likely be caused of
my own programming than on bugs in my buildchain...

This is not a good idea.  You should be using the current build, because that is what everyone else as well as the build system is using.

Version: r Unversioned directory-140507

Did you get this source from git? 

[mcc01]

Hi Saratoga,

uummm....no, I fetched the source from here:
http://download.rockbox.org/release/3.13/rockbox-3.13.7z

I am only using 3.13 to verify, that my build system is ok,
Saratoga. NOT as a code base for further development...

...the """problem""" with the current build is, that it is
not stable...and if my player crashes it could be based
on my build system AND programming bugs...
Or get I something wrong here...

Is there something else in the info txt file, that indicates
problems with my build chain?

Best regards,
mcc

[saratoga]

Hi Saratoga,

uummm....no, I fetched the source from here:
http://download.rockbox.org/release/3.13/rockbox-3.13.7z

If you insist on this (which I do not recommend), I would check it out from git and see if that works. 

[[Saint]]

It is very much worth noting that compared to git head, 3.13 almost certainly isn't "stable".

You're throwing away over a year's worth of bug fixes and improvements because of an essentially arbitrary build classification.


[Saint]

[mcc01]

Hi Saint,

ok... I see... "stable" doesn't mean to be stable...

Ok, I installed the "current build" (that was is linked via "dev builds" in the menu
at the upper left of the web page).
Now I cannot use usb anymore.
Attaching works. But as soon as there is an access
to the device (via mount), rockbox
crashes. USB via the original firmware works
fine.

How can I ensure, that my cross compiler and my build chain works
fine before I start modifying the code?

Best regards
mcc

PS: How can I check out exactly the same code, which was used to
create the build I have now installed on my Sansa Clip ZIP?

[[Saint]]

How can I ensure, that my cross compiler and my build chain works
fine before I start modifying the code?

By using our toolchain instead.

PS: How can I check out exactly the same code, which was used to
create the build I have now installed on my Sansa Clip ZIP?

http://www.rockbox.org/wiki/UsingGit


[Saint]

[gevaerts]

ok... I see... "stable" doesn't mean to be stable...

It does. You might however have picked the wrong meaning of the word "stable"

[mcc01]

Hi Saint,

By using our toolchain instead.

I do !
But experiences with other embedded systems
(mainly Centipad, Beaglebone and Beaglebone black)
gave me the impression, that compiling the same cross
compiler toolchain on two systems can -- even by using
the same software versions -- let to different results.
Better safe than sorry...

http://www.rockbox.org/wiki/UsingGit

Oh YEAH! Good link! Thanks! Did overlooked that one,
sorry!

Best regards
mcc

[mcc01]

Hi Gevaerts

ok... I see... "stable" doesn't mean to be stable...

It does. You might however have picked the wrong meaning of the word "stable"

So...is there a difference in stability between the so called stable version
and the current development version?
And: If the current is more stable than the stable one...why not to release
a new stable version then?

Best regards,
mcc

[saratoga]

We've been meaning to release a new stable build for a year now.

The builds we distribute are actually compiled by individual user and developer machines via our build system. If you use our toolchain you should build the same as everyone else.

[mcc01]

Ok, I see...

I will carefully recompile everything and may be I am able then
to pinpoint the problems I have...with the kind help of this forum may be

Thanks again for help and understanding !

Best regards,
mcc