Flyspray:: http://www.rockbox.org/tracker/ Flyspray:: Rockbox: Recently opened tasks 2014-09-22T15:21:44Z FS#13002: Fails to build from source under long build path with "execvp: /bin/sh: Argument list too long". http://www.rockbox.org/tracker/task/13002 2014-09-22T15:21:44Z Oid Maps When I try to build rockbox, I get the following error: ==> make: execvp: /bin/sh: Argument list too long <== My build path is a fairly long path. Building it at a location with shorter path it works. Details: Steps to reproduce: * Create a location where you want to have the sources; use a fairly long path name, e.g. mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/ * Change to that directory: cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/ * Download git sources (Tried with version from 2014-09-22, 10:55:11 GMT+1, Commit by "Marcin Bukat <marcin.bukat@gmail.com>", Change-Id: "Ie3aa9b208e3f4f17d4d02f11f69839e9b381217d") to a long path: git clone git://git.rockbox.org/rockbox * Make a build directory and change into it: mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2 cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2 * Configure the build: ../rockbox/tools/configure --target=63 --type=N prodces the output ==> Using temporary directory /tmp Platform set to sansafuzev2 Normal build selected Using source code root directory: /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/rockbox Using arm-elf-eabi-gcc 4.4.4 (404) Using arm-elf-eabi-ld 2.20.1.20100303 Found and uses ccache (/sbin/ccache) Automatically selected arch: arm (ver 5) Created Makefile <== * Running "make": make produces the output ==> Generating dependencies make: execvp: /bin/sh: Argument list too long make: *** No rule to make target '/home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2/make.dep', needed by 'all'. Stop. <== and returns with exit code 2. Workaround: Building it in a directory with shorter path, e.g. doing everything in "/tmp", works. But that is only a workaround; it should not fail when building in arbitrary locations, and especially not with a message not making it clear _what_ the underlying problem ist. (I had to do a long internet search to get to the idea that the build place can be the problem).
==>
make: execvp: /bin/sh: Argument list too long
<==

My build path is a fairly long path. Building it at a location with shorter path it works. Details:


Steps to reproduce:

* Create a location where you want to have the sources; use a fairly long path name, e.g.

mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/

* Change to that directory:

cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/

* Download git sources (Tried with version from 2014-09-22, 10:55:11 GMT+1, Commit by "Marcin Bukat <marcin.bukat@gmail.com>", Change-Id: "Ie3aa9b208e3f4f17d4d02f11f69839e9b381217d") to a long path:

git clone git://git.rockbox.org/rockbox

* Make a build directory and change into it:

mkdir -p /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2
cd /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2

* Configure the build:

../rockbox/tools/configure --target=63 --type=N

prodces the output

==>
Using temporary directory /tmp
Platform set to sansafuzev2
Normal build selected
Using source code root directory: /home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/rockbox
Using arm-elf-eabi-gcc 4.4.4 (404)
Using arm-elf-eabi-ld 2.20.1.20100303
Found and uses ccache (/sbin/ccache)
Automatically selected arch: arm (ver 5)
Created Makefile
<==

* Running "make":

make

produces the output

==>
Generating dependencies
make: execvp: /bin/sh: Argument list too long
make: *** No rule to make target '/home/myuser/download/mediaplayer_hardware/SanDisk/Sansa_Fuze_v2/rockbox/firmware/source/build_FuzeV2/make.dep', needed by 'all'. Stop.
<==

and returns with exit code 2.



Workaround:

Building it in a directory with shorter path, e.g. doing everything in "/tmp", works.

But that is only a workaround; it should not fail when building in arbitrary locations, and especially not with a message not making it clear _what_ the underlying problem ist. (I had to do a long internet search to get to the idea that the build place can be the problem).
]]>
FS#13001: Portugal Portuguese Update http://www.rockbox.org/tracker/task/13001 2014-09-21T22:37:33Z Tiago Medeiros Attached you&#039;ll find a DIFF for Portugal Portuguese. Cheers!
Cheers!]]>
FS#13000: Audio drop-out with hi-res file playback http://www.rockbox.org/tracker/task/13000 2014-09-19T20:47:11Z Aaron Tate I have a couple of hi-res files (24/44) that seems to have audio volume drop-outs at certain points, as if it is an over-reacting dynamic clip prevention. If I try the same file in Foobar 2000, I do not get the sound drop-outs. Dithering is turned on, ReplayGain is on &quot;album&quot;, and I tried it both with and without clipping prevention, but both times I got the drop-outs. The file is too large to attach here, but I can provide it via other means. They are tracks from Steven Wilson - The Raven That Refused to Sing. I resampled and dithered the official 24/96 release to 24/44 using iZotope RX 3 Advanced. I can provide both resampler and dither settings if desired, or I can just provide the effected tracks (title track, &quot;The Watchmaker&quot;, both near the end), or the files themselves.
The file is too large to attach here, but I can provide it via other means. They are tracks from Steven Wilson - The Raven That Refused to Sing. I resampled and dithered the official 24/96 release to 24/44 using iZotope RX 3 Advanced. I can provide both resampler and dither settings if desired, or I can just provide the effected tracks (title track, "The Watchmaker", both near the end), or the files themselves.]]>
FS#12999: Manual says there are 2 different builds of iPod 5G http://www.rockbox.org/tracker/task/12999 2014-09-16T19:29:39Z Arthur Ferrai Getting last iPod 5G manual (found here: http://download.rockbox.org/daily/manual/rockbox-ipodvideo-20140916.pdf page 17), it says there are two different versions of Rockbox for this player. It was true some time ago, but now (even in release page), there are only one version that works with any model of iPod 5G. http://download.rockbox.org/daily/manual/rockbox-ipodvideo-20140916.pdf page 17), it says there are two different versions of Rockbox for this player. It was true some time ago, but now (even in release page), there are only one version that works with any model of iPod 5G.]]> FS#12998: Vertical progress bar (%pb) glitches at the start of a song http://www.rockbox.org/tracker/task/12998 2014-09-16T17:12:26Z Guillaume Cocatre-Zilgien Consider the following theme markup: %Vl(progressbar,306,156,10,80,-) %pb(0,0,10,80,progressbar.bmp,vertical) That draws a vertical progress bar that will get filled from bottom to top. When a song starts to play, the progress bar is one pixel high, at the correct position (at the bottom of the viewport). That 1px-high image quickly jumps up one pixel (moves up by one pixel), then comes back down one pixel (at the correct position) whenever the progress percentage is high enough. The progress bar then displays normally and grows as the song is playing. See attached screenshots. Expected behavior: the position of the progress bar (relative to the viewport) should not change. The bug has been observed in the iPod Classic and Clip Zip sims (builds 1bc89bd and 77bfff5) as well on the actual devices. Inverting the progress bar (with the &quot;invert&quot; parameter) shows the correct behavior (inverted bar with no such glitch). Affected themes: Ash (iPod Classic), SugarBrown (Clip Zip).
%Vl(progressbar,306,156,10,80,-)
%pb(0,0,10,80,progressbar.bmp,vertical)

That draws a vertical progress bar that will get filled from bottom to top. When a song starts to play, the progress bar is one pixel high, at the correct position (at the bottom of the viewport). That 1px-high image quickly jumps up one pixel (moves up by one pixel), then comes back down one pixel (at the correct position) whenever the progress percentage is high enough. The progress bar then displays normally and grows as the song is playing. See attached screenshots.

Expected behavior: the position of the progress bar (relative to the viewport) should not change. The bug has been observed in the iPod Classic and Clip Zip sims (builds 1bc89bd and 77bfff5) as well on the actual devices. Inverting the progress bar (with the "invert" parameter) shows the correct behavior (inverted bar with no such glitch).

Affected themes: Ash (iPod Classic), SugarBrown (Clip Zip).]]>
FS#12997: Gather Runtime Data causes playback issues http://www.rockbox.org/tracker/task/12997 2014-09-16T11:02:10Z Thomas Martitz It was reported on IRC (http://www.rockbox.org/irc/log-20140916#03:37:18) that there are playback problems (e.g. gaps between gapless songs) if/when Gather Runtime Data is active and playback is started via database. FS#12996: path_trim_whitespace() shouldn't trim the start of a filename http://www.rockbox.org/tracker/task/12996 2014-09-15T22:34:10Z Frank Gevaerts Filenames can legally start with space characters. This was supported before 7d1a47cf. The new path_trim_whitespace() trims both the start and end of filenames. FS#12995: path_trim_whitespace() assumes unsigned char http://www.rockbox.org/tracker/task/12995 2014-09-16T03:15:27Z Frank Gevaerts path_trim_whitespace() (introduced in 7d1a47cf) assumes unsigned char (things like c &lt;= &#039; &#039;). This makes it break on some platforms (including the simulator on x86/amd64). I don&#039;t know if that commit has other similar issues. FS#12994: Bacon http://www.rockbox.org/tracker/task/12994 2014-09-04T09:35:48Z activeminds [[http://www.bacon.com/|Bacon]] may be eaten smoked, boiled, fried, baked, or grilled, or used as a minor ingredient to flavour dishes. Bacon is also used for barding and larding roasts, especially game, including venison and pheasant. The word is derived from the Old High German bacho, meaning &quot;buttock&quot;, &quot;ham&quot; or &quot;side of bacon&quot;, and cognate with the Old French bacon.[5][6] In continental Europe, part of the pig is not usually smoked like bacon is in the United States; it is used primarily in cubes (lardons) as a cooking ingredient, valued both as a source of fat and for its flavour. In Italy, this is called pancetta and is usually cooked in small cubes or served uncooked and thinly sliced as part of an antipasto. Meat from other animals, such as beef, lamb, chicken, goat, or turkey, may also be cut, cured, or otherwise prepared to resemble bacon, and may even be referred to as &quot;bacon&quot;.[7] Such use is common in areas with significant Jewish and Muslim populations, both of which prohibit the consumption of pig.[8] The USDA defines bacon as &quot;the cured belly of a swine carcass&quot;; other cuts and characteristics must be separately qualified (e.g., &quot;smoked pork loin bacon&quot;). For safety, bacon may be treated to prevent trichinosis,[9] caused by Trichinella, a parasitic roundworm which can be destroyed by heating, freezing, drying, or smoking.[10] Bacon is distinguished from salt pork and ham by differences in the brine (or dry packing). Bacon brine has added curing ingredients, most notably sodium nitrite, and occasionally potassium nitrate (saltpeter); sodium ascorbate or erythorbate are added to accelerate curing and stabilise colour. Flavourings such as brown sugar or maple are used for some products. Sodium polyphosphates, such as sodium triphosphate, may be added to make the produce easier to slice and to reduce spattering when the bacon is pan-fried. Today, a brine for ham, but not bacon, includes a large amount of sugar. Historically, &quot;ham&quot; and &quot;bacon&quot; referred to different cuts of meat that were brined or packed identically, often together in the same barrel.
In continental Europe, part of the pig is not usually smoked like bacon is in the United States; it is used primarily in cubes (lardons) as a cooking ingredient, valued both as a source of fat and for its flavour. In Italy, this is called pancetta and is usually cooked in small cubes or served uncooked and thinly sliced as part of an antipasto.

Meat from other animals, such as beef, lamb, chicken, goat, or turkey, may also be cut, cured, or otherwise prepared to resemble bacon, and may even be referred to as "bacon".[7] Such use is common in areas with significant Jewish and Muslim populations, both of which prohibit the consumption of pig.[8] The USDA defines bacon as "the cured belly of a swine carcass"; other cuts and characteristics must be separately qualified (e.g., "smoked pork loin bacon"). For safety, bacon may be treated to prevent trichinosis,[9] caused by Trichinella, a parasitic roundworm which can be destroyed by heating, freezing, drying, or smoking.[10]

Bacon is distinguished from salt pork and ham by differences in the brine (or dry packing). Bacon brine has added curing ingredients, most notably sodium nitrite, and occasionally potassium nitrate (saltpeter); sodium ascorbate or erythorbate are added to accelerate curing and stabilise colour. Flavourings such as brown sugar or maple are used for some products. Sodium polyphosphates, such as sodium triphosphate, may be added to make the produce easier to slice and to reduce spattering when the bacon is pan-fried. Today, a brine for ham, but not bacon, includes a large amount of sugar. Historically, "ham" and "bacon" referred to different cuts of meat that were brined or packed identically, often together in the same barrel.]]>
FS#12993: removing the lock form my FBOP purchased Sandisk MP3 player http://www.rockbox.org/tracker/task/12993 2014-08-26T09:02:25Z Johnathan Simpson I bought the sandisk MP3 player while in the FBOP and it came with a lock that has to be revalidated every two weeks. Now that I have been released, the player has &quot;expired&quot; and Im wondering if I can remove the lock, or de-institutionalize it myself because the company has had a few problems with the money, based on what I have seen from others who sent their players out.