Rockbox Development > Starting Development and Compiling
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:
--- Quote from: mcc01 on May 07, 2014, 01:34:23 PM ---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...
--- End quote ---
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.
--- Quote from: mcc01 on May 07, 2014, 01:57:27 PM ---Version: r Unversioned directory-140507
--- End quote ---
Did you get this source from git?
Navigation
[0] Message Index
[#] Next page
Go to full version