Re: [PATCH v3 5/5] automation: Add container for riscv64 builds

[Connor Davis <connojdavis@xxxxxxxxx>]

On 5/14/21 3:01 PM, Bob Eshleman wrote:
> On 5/14/21 11:53 AM, Connor Davis wrote:
> > +
> > +# There is a regression in GDB that causes an assertion error
> > +# when setting breakpoints, use this commit until it is fixed!
> > +RUN git clone --recursive -j$(nproc) --progress 
> > https://github.com/riscv/riscv-gnu-toolchain && \
> > +    cd riscv-gnu-toolchain/riscv-gdb && \
> > +    git checkout 1dd588507782591478882a891f64945af9e2b86c && \
> > +    cd  .. && \
> > +    ./configure --prefix=/opt/riscv && \
> > +    make linux -j$(nproc) && \
> > +    rm -R /riscv-gnu-toolchai
> What do you think about using the RISCV tool chain from the Arch
> repos now?
That sounds much better, will update
> I've also discovered that the sym table error avoided by the commit
> pin can be worked around by removing already loaded symbols with
> `file` (no args) prior to calling `file path/to/file` to load new
> ones.  So if people did still want to use the container for
> development, they could still use the gdb installed by pacman
> (with the symbols caveat).
Thanks,

Connor