Re: [Crosstool-NG] Blackfin support, RFC

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Thomas, All,

On Wednesday 07 April 2010 10:33:49 Thomas Petazzoni wrote:
> I've recently started adding Blackfin support to Crosstool-NG. On
> Blackfin, there are typically 3 toolchains available :
>  * bfin-elf, a bare-metal toolchain using newlib
>  * bfin-uclinux, a Linux toolchain that generates flat binaries (no
>    shared libaries)
>  * bfin-linux-uclibc, a Linux toolchain that generates FDPIC ELF
>    binaries (shared libraries are possible)
> I've focused on the latest one for the moment, and I've reached the
> point where I can compile a small Hello World application, both dynamic
> and static and run it on the target. I haven't tried more complicated
> examples at the moment.

Yeah! Nice! :-)

> However, in addition to these patches, I had to make a very ugly
> modification :
> 
> diff -r e4d7a4cd72cc scripts/build/kernel/linux.sh
> --- a/scripts/build/kernel/linux.sh	Wed Apr 07 09:26:12 2010 +0200
> +++ b/scripts/build/kernel/linux.sh	Wed Apr 07 10:30:07 2010 +0200
> @@ -6,7 +6,7 @@
>      if [ "${CT_ARCH_USE_MMU}" = "y" ]; then
>          CT_TARGET_KERNEL="linux"
>      else
> -        CT_TARGET_KERNEL="uclinux"
> +        CT_TARGET_KERNEL="linux"
>      fi
>  }
> 
> This is because Crosstool-NG assumes that when the architecture has
> no-mmu, the kernel part of the tuple must be "uclinux". However, in the
> case of Blackfin toolchains, it seems that the tradition is
> bfin-uclinux for FLAT toolchains and bfin-linux-uclibc for FDPIC
> toolchains. Therefore, I had to hack this part of Crosstool-NG code.
> 
> Obviously, this is not the right way to do it, and that's why I'm
> requesting for your comments on how to implement this properly.

I'd say that, as of today, crosstool-NG does not build any single toolchain
that targets Linux/noMMU. This code was just a plan for the future.

Blackfin is the first arch that can build a Linux/noMMU toolchain, so let's
adapt and match that. I'm not sure how other archs work, either.

I will handle the patchset a bit later, after dinner...

> On a side note, when is Crosstool-NG switching to git ? When you're
> used to Git with all the other open-source projects, switching to
> Mercurial just for Crosstool-NG is kind of painful.

Short answer: not interested, not planned.

Long answer:

No, I am not switching crosstool-NG to git. _I_ am not used to using git
on a daily basis, except for the usual git clone/pull dance; for anything
more, _I_ find git to be a real *pain* to work with on a daily basis [*],
while _I_ find hg very easy to use.

And switching to git for the occasional patch is just painful for me as
well, and I'm not asking other projects to switch to Mercurial just
because _I_ find it easier to use than git. ;-)

And I am tired of the argument, sorry. :-/

And Linus is not my All-Mighty Deity, sorry. :-]

So, there is no switch in sight. End of argument. Period.

Don't take me wrong: I am not arguing wether git or Hg is better than
the alternative. Just that, when switching out of SVN, I made a choice,
based on some experiments I did on both solutions (and even a third one),
and it appeared to me that Mercurial was easier to use, for me, on a daily
basis (imagine: just two hours, and I was ready! When two years later, I
am not yet ready to properly work with git without resorting to Google).

And, please, don't take this personnaly, Thomas! :-)

Regards,
Yann E. MORIN.

[*] Praise to stgit for the end user! Alas, as maintainer, I don't want to
    battle with git every time I have to merge/pull/etc...
YEM.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq