This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RTEMS 4.10 Integration


Sebastien, All,

On Monday 01 November 2010 13:53:45 Sebastien Van Cauwenberghe wrote:
> I began the porting of RTEMS 4.10 for CTNG and I got some issues at
> the beginning.
> I added RTEMS to the menuconfig, and made the rtems.sh in the script dir.
> So that's OK, I added the necessary functions in the shell script.
> 
> Now I'm facing a little problem of unknown machine.
> --- Output of ./ct-ng build only with the problems
> [00:00] / Invalid configuration `arm-unknown-rtems4.10-gnueabi':
> machine `arm-unknown-rtems4.10' not recognized
> [ERROR]  Build failed in step '<none>'
> [ERROR]  Error happened in
> '/home/seb/devel/crosstool-ng/scripts/functions' in function
> 'CT_DoBuildTargetTuple' (line unknown, sorry)
> [ERROR]        called from
> '/home/seb/devel/crosstool-ng/scripts/crosstool-NG.sh' at line # 134
> in function 'main'
> [ERROR]  Look at '' for more info on this error.
> [ERROR]  (elapsed: 0:00.18)
> ---
> I don't understand where this comes from... Can you give me some hints...

You can look in the current directoy for a file named log.XXX (where XXX
is the pid of the process).

Normally the log file would be stored in the toolchain directory, but that
is known only after we have setup a few things, of which the tuple. As it
fails computing the tuple in your case, the initial log file is still in
the build directory.

> Another question, in menuconfig, how do you hide the whole RTEMS entry
> in the case we aren't using the EXPERIMENTAL mode

    config KERNEL_rtems
        depends on EXPERIMENTAL

> or we are using an unsupported architecture...

    config KERNEL_rtems
        depends on ARCH_x86 || ARCH_mips  (select approriate arch, of course)

> I suppose hiding the C libs will be exactly the same... 

For now, this is not really straightforward. In the libc config file, you
can add a comment that is a depend option. For example, glibc currently
has this:

    # glibc options
    # depends on ! MINGW32 && ! BARE_METAL && ARCH_USE_MMU

You could either append:  && ! KERNEL_rtems
Or you could add another line:

    # depends on ! KERNEL_rtems

Do not hesitate to post your patches early, even if they are not finished,
so we can review them and bash out issues early. I think you could post them
right now, so we see what the failure above is.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]