Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: sh-elf-objcopy creates _large_ archos.bin output
From: Matthias Wächter (matthias_at_waechter.wiz.at)
Date: 2002-09-07


On Sat, 7 Sep 2002, Linus Nielsen Feltzing wrote:

> > (Then maybe we should note this in the docs explicitly)
>
> We could mention that. Or you can just download the versions that the
> instructions tell you to.

Hmmm. When you download a tool stating it needed Win32s for proper
operation I assume you won't dig your floppy disc heap to find the dusty
Dos 6.2 + Win 3.11 + Win32s compatibility layer installation media, will
you? You will try your current operating system version first and fight
all upcoming compatibility issues (f.e. contacting the author).

My interpretation of docs' versioning is as follows:

a) The docs say: Use 'linux'

   --> Means: Take the latest release (of the best OS. :-)

b) The docs say: Use 'linux v2.0.12'

   --> Means: Take the latest release but at least v2.0.12

c) The docs say: Use 'linux v2.0.12' but not newer because they introduce
   trouble

   --> Means: Take v2.0.12 and be happy or find out what causes trouble,
       fix it, report it and make this limitation go away. Should lead to
       _d_

c1) The docs say: Use 'linux v2.0.12' but not newer because they introduce
    trouble. The problem was observed last with v2.0.17.

    --> Means: Just like _c1_ but makes debugging the problem a lot
    easier.

d) The docs say: Use linux up to v2.0.12 or v2.2.0 upwards

   --> Means: Somehow a bug was introduced after v2.0.12 which was removed
       by someone searching for the reasons for the bug. So take the current
       release.

> You are very welcome to try to figure out what the problem might be,
> and then we can either fix it, or add some info on the instruction
> page.

OK, but the first conclusion is to do _c_ in the docs (or even better with
_c1_). Then anyone can choose to concentrate on developing Rockbox or
finding this compiler/linker bug. And everyone not in the mood for
searching bugs in gcc or guessing the best version knows about the
limitations.

> Why do you call it an 'intermediate' solution? That version works,
> and we haven't had any problems with it. I say stick with it and be
> happy. :-)

For Rockbox, of course, that's _the_ solution. The term 'intermediate' was
used in conjunction with the docs and the compiler problem.

Sehr Wus,
- Matthias

-- 
                    "To get control over people, make them trust you.
                                            To make people trust you
                      don't try to tell them the truth about history
                 but make happen what you told them about the future."



Page was last modified "Jan 10 2012" The Rockbox Crew
aaa