Re: How to commit a new architecture like RISC-V

[zhangjialing <zhangjialing@loongson.cn>]

    Hi
    ,
    
    The upsteam work is working on, But it is slow ,We can provide the
    patch and the apt  repo.
    
    
    
    在 2021/5/11 下午6:36, Helmut Grohne 写道:
    
> Hi,
>       
>       
>       On Tue, May 11, 2021 at 05:41:35PM +0800, zhangjialing wrote:
>       
> >     We have a new
> >         architecture , We have compiled a lot of packages.Now the system
> >         can work normally .
> >         
> >         
> >             We want to submit to debian like RISC-V. Please What
> >         documents(or others) can we refer to.
> >         
> >       
>       I think that recent port bootstrapping efforts have been performed
>       using
>       
>       https://wiki.debian.org/HelmutGrohne/rebootstrap.
>       
>       
> >     I want to know
> >         the submission process and documents.I know RISC-V has done it
> >         ,but I do not know how to begain  and what can referance.
> >         
> >       
>       Please follow up on this email thread with the following
>       information:
>       
>       
>         * What is the gnu triplet used for the port?
>       
>     
    loongarch64-linux-gnu
    
>   * How many bits?
>       Endianess?
>       
>     
    64 bits,Little Endian
    
>   * What is the
>       state of binutils support?
>       
>     
      2.31.1-16 , patch can provide
    
>   * What is the
>       state of gcc support?
>       
>     
    gcc 4:8.3.0-1
    
    
    gcc-8  8.3.0-6
    
    
    patch can provide
    
    
>   * What is the
>       state of linux support?
>       
>     
    4.19.167,patch can provide
    
>   * What is the
>       state of glibc support
>       
>     
    2.28-10,patch can provide
    
>   * Do you have a
>       preferred architecture name already?
>       
>     
    loongarch64
    
    
    When describing "what is the state of ... support?", please tell:
    
      * If the support is upstreamed, since which version?
    
      * If not, are patches posted? Where?
    
      * If not, is support implemented in some fork? Where?
    
    
    Once we got answers to all these, I suppose that extending
    rebootstrap
    
    to support your architecture is the next step. Once finished, you
    get to
    
    manually fill in the gaps and roughly end up with something close to
    
    build-essential. Using that, you'll set up a native build system and
    
    build the rest of the archive. In the process, you'll break build
    
    dependency cycles using various means. The most common ones are
    nocheck
    
    builds and cross compilation.
    
    
    If you do irc, join #debian-bootstrap on oftc. Cross-bootstrap
    related
    
    matters are best directed at debian-cross@lists.debian.org.
    
    
    Helmut