[Cooker] cross-avr-gcc

View: New views
5 Messages — Rating Filter:   Alert me  

[Cooker] cross-avr-gcc

by yvanttt :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hello i would like to know how to get started to maintain that package.

am i on the correct mailing list?

currently there is a bug that prevent this package to be installed correctly and i want to contribute to correct it.

Thank you!

Re: [Cooker] cross-avr-gcc

by Christophe Fergeau-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

yvanttt@... a écrit :
> hello i would like to know how to get started to maintain that package.
>
> am i on the correct mailing list?
>
> currently there is a bug that prevent this package to be installed correctly and i want to contribute to correct it.
>  

Someone needs to figure out how to rebuild it I guess.. And potentially
to update it to the latest gcc version. This might be tricky, but is a
good learning experience :)

Thanks!

Christophe

Re: [Cooker] cross-avr-gcc

by Marcelo Ricardo Leitner-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm still pondering if it's worth using this cross- structure. Okay, I mean providing these toolchains via our distro. Currently there are tools that can build them very easily for you (like buildroot) with custom params and so on.

It tends to get too specific to each project, like building gcc to be used with uclibc or glibc. Would we provide cross-arm-gcc-uclibc and also cross-arm-gcc-glibc? and now -eglibc too?

Perhaps it would be simpler/easier/smarter to support these aux. tools to build them...

Cya!

On Fri, Oct 30, 2009 at 7:29 AM, Christophe Fergeau <cfergeau@...> wrote:
Hi,

yvanttt@... a écrit :
> hello i would like to know how to get started to maintain that package.
>
> am i on the correct mailing list?
>
> currently there is a bug that prevent this package to be installed correctly and i want to contribute to correct it.
>

Someone needs to figure out how to rebuild it I guess.. And potentially
to update it to the latest gcc version. This might be tricky, but is a
good learning experience :)

Thanks!

Christophe


Parent Message unknown Re: [Cooker] cross-avr-gcc

by Stéphane Téletchéa :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


----- yvanttt@... a écrit :

| hello i would like to know how to get started to maintain that
| package.
|
| am i on the correct mailing list?
|
| currently there is a bug that prevent this package to be installed
| correctly and i want to contribute to correct it.
|
| Thank you!

See

The overall "policy" to become a contributor is the starting message :
http://lists.mandriva.com/cooker/2009-05/msg00408.php

In short:
1) open a ticket on bugzilla, in category 'BS', with the following information:

- login
- public ssh key
- email address

2) get a mentor to approve this request.

More info on packaging (entry points), to ensure this is what you expect:

http://wiki.mandriva.com/en/Contributing_packages
http://wiki.mandriva.com/en/Development/Resources/Account
http://wiki.mandriva.com/en/Package_maintainer_tutorial

Welcome aboard,

Stéphane
(and no, for the moment i've no time to mentor you :-)

Re: [Cooker] cross-avr-gcc

by Marcelo Ricardo Leitner-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



On Fri, Oct 30, 2009 at 10:20 AM, Marcelo Ricardo Leitner <marcelo.leitner@...> wrote:
I'm still pondering if it's worth using this cross- structure. Okay, I mean providing these toolchains via our distro. Currently there are tools that can build them very easily for you (like buildroot) with custom params and so on.

It tends to get too specific to each project, like building gcc to be used with uclibc or glibc. Would we provide cross-arm-gcc-uclibc and also cross-arm-gcc-glibc? and now -eglibc too?

Perhaps it would be simpler/easier/smarter to support these aux. tools to build them...

 I mean, we could provide buildroot and some certified default configs (as it already ships some ones), for example.