sunhaiyong1978 / clfs-for-loongarch Goto Github PK

View Code? Open in Web Editor NEW

177.0 177.0 58.0 1.14 MB

如何交叉编译一个基于LoongArch架构的LFS（Linux From Scratch）系统。

Shell 100.00%

clfs-for-loongarch's People

Contributors

Stargazers

Watchers

clfs-for-loongarch's Issues

是否可以提供服务器版本的initrd

我尝试了一下发现服务器版本的可能需要其他acpi相关的aml文件
现在启动之后显示只有4核心

404 not found of binutils

CLFS-for-LoongArch/CLFS_For_LoongArch64-20220108.md

Line 235 in 8b76ff1

 　　**Binutils:** ```https://github.com/loongarch/binutils-gdb.git 分支名“loongarch/upstream_v6_a1d65b3”``` 

gcc 编译器问题 internal compiler error: in output_constructor_regular_field, at varasm.c:5512

孙老师，您好！我在用您的2.3版CLFS的GCC 编译 poppler时，会出错，编译QT5.15也报同样的错误。麻烦看看是什么原因。谢谢！

g++ poppler_Decrypt_preprocessed.cc -c
/var/tmp/portage/app-text/poppler-21.12.0/work/poppler-21.12.0/poppler/Decrypt.cc:1826:1: 编译器内部错误：在 output_constructor_regular_field 中，于 varasm.c:5512
1826 | }
| ^
0x1134277 internal_error(char const*, ...)
???:0
0x1a2887 fancy_abort(char const*, int, char const*)
???:0
0xbdecbf assemble_variable(tree_node*, int, int, int)
???:0
0xbe24ab varpool_node::assemble_decl()
???:0
0x4c2067 symbol_table::finalize_compilation_unit()
???:0
请提交一份完整的错误报告，
如有可能请附上经预处理后的源文件。
Please include the complete backtrace with any bug report.

20220108日文档中一点笔误，285行的Intltool写成了Inih

loongarch仓库地址是否已迁移到loongson仓库中？

loongarch仓库已经没东西了QAQ

Update to OpenSSL-1.1.1l for CVE-2021-3711

OpenSSL-1.1.1k 中存在一个影响 SM2 的高级别安全缺陷。

SM2 是我国国家标准，由于龙芯平台常用在信控领域，这个问题对龙芯用户的影响可能比一般人更为严重。

使用3.20中的python3.10.4编译3.21 Jinja时报缺少setuptools

孙老师好，按照您的文档编译3.21 Jinja时，使用的是3.20中编译的python3.10.4,然后报缺少setuptools

Traceback (most recent call last): File "/opt/mylaos/build/chp03/python-jinja2/Jinja2-3.0.3/setup.py", line 1, in <module> from setuptools import setup ModuleNotFoundError: No module named 'setuptools'

请教下，您这步用到的setuptools是来自之前的哪个步骤？

dnf生成基础chroot环境缺软件包

建议dnf生成基础软件环境中增加cmake软件包，因为在编译cmake软件包时会需要本地的cmake。

3.17节perl源码的下载链接最后多个一个"z"

如题

请求Linux内核头文件版本

在龙芯社区发现gcc8.3 rc1.2的交叉编译版本，使用社区的代码编译一直失败。请问应该使用哪个版本的内核头文件？

编译Thunderbird100时补丁缺少

您好，我看见在编译Thunderbird100的时候用上了一个补丁包 firefox-100-l10.zip，但是我并没有在仓库里找全所需要的补丁文件。请问这可以在哪找到呢

3.7 Automake : 没看到补丁

这节说要打补丁，但是没有看到补丁以及打补丁的命令。

What is official QEMU port for LoongArch

I see that in your document references https://github.com/gaosong-loongson/qemu
and there https://github.com/loongson/qemu which seems quite close to master. Can you tell what's the differences?

20220108文档，Binutils分支问题

使用 upstream_v3.1 分支在执行 ./configure 时会有无法识别loongarch架构的问题

切换为 upstream_v3 则没有问题，不清楚是什么原因QAQ

请求glibc2.28的补丁

最近在做某些软件向龙芯服务器版本的移植，按照您的交叉编译工具集制作了相对应的二进制包，但其中一些动态链接库需要glibc的2.35版本但实际上服务器只有2.28版本
所以想和您要2.28版本的补丁制作交叉编译器
感谢

制作docker镜像时遇到的问题

FROM ubuntu:16.04
LABEL author maikebing <[email protected]>
# docker run -ti   --net=host --rm -e DISPLAY=host.docker.internal:0 -v /tmp/.X11-unix:/tmp/.X11-unix  x11ubuntu   --gpus
ENV DEBIAN_FRONTEND noninteractive
# RUN apt-get -y   -q   update && apt-get  install  -y   -q  apt-transport-https ca-certificates  
RUN echo "deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial main restricted universe multiverse " > /etc/apt/sources.list && \
    echo "deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-updates main restricted universe multiverse" >> /etc/apt/sources.list && \
    echo "deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-backports main restricted universe multiverse" >> /etc/apt/sources.list && \
    echo "deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-security main restricted universe multiverse" >> /etc/apt/sources.list && \
    apt-get -yq update &&  apt-get install  -y   -q   ca-certificates  wget bzip2  && \
    apt-get clean && apt-get autoremove   && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*	

RUN wget -c  https://github.com/sunhaiyong1978/CLFS-for-LoongArch/releases/download/20210903/qemu-x86_64-to-loongarch64 && cp qemu-x86_64-to-loongarch64 /bin/qemu-loongarch64
RUN cd /tmp && wget  -cq https://github.com/sunhaiyong1978/CLFS-for-LoongArch/releases/download/20210903/loongarch64-clfs-system-20210903.tar.bz2 && \
    cd /opt  &&  mkdir clfs-os &&  cd clfs-os  && tar xvpf /tmp/loongarch64-clfs-system-20210903.tar.bz2 && rm  /tmp/loongarch64-clfs-system-20210903.tar.bz2
RUN echo  "none  /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0" >> /etc/fstab && \
    mount -t binfmt_misc none /proc/sys/fs/binfmt_misc && \
    echo ":qemu-loongarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x02\x01:\xff\xff\xff\xff\xff\xfe\xfe\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/bin/qemu-loongarch64:" > /proc/sys/fs/binfmt_misc/register    
RUN  ls /proc/sys/fs/binfmt_misc/ &&  cat /proc/sys/fs/binfmt_misc/status  
RUN cp /bin/qemu-loongarch64 /opt/clfs-os/bin/
RUN chroot /opt/clfs-os

qemu的源码可以提供吗？

缺少 libffi-3.3-add-loongarch.patch

在提交的库里面没有找到这个patch文件

3.21节qemu编译缺少*-static包

简述

.编译qemu需要依赖glibc-static、glib2-static、pcre-static、zlib-static，建议在2.1节创建la-clfs环境时安装

具体信息

configure阶段：

首先出现big/little test failed, 查看build/config.log，提示 ld找不到 -lc , 确认是缺少 libc.a，在la-clfs的chroot环境中安装glibc-static解决
出现“sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T. You probably need to set PKG_CONFIG_LIBDIR to point to the right pkg-config files for your build target””，与第1步问题类似，config.log提示ld找不到 -lgthread-2.0、-lglib-2.0，确认是缺少libgthread-2.0.a和libglib-2.0.a，安装glib2-static解决
再次出现第2步同样的“sizeof……”错误，config.log提示ld找不到-lpcre，确认是缺少ibpcre.a，安装pcre-static解决

ninja阶段：
.执行ninja报错，ld找不到-lz ，确认缺少libz.a，安装zlib-static解决

libcap 版本号不一致

孙老师您好，

libcap 在下载链接里版本号是 2.50 ，在解压的时候是 2.49

望修复

关于LoongArch版Binutils与GCC的源码

孙老师您好。

我现在正在尝试根据您写的这篇教程编译交叉工具链，卡在了Binutils和GCC的编译上。从GNU官方repo上下载的Binutils和GCC源码尚未提供LoongArch的支持，编译时直接报错。
同时，我从龙芯开源社区官网关注到，基于LoongArch64的一系列系统和软件早已发布，但我在任何渠道都无法获取支持该架构的新版GCC。

就这一问题想特地向您请教。

注：GCC根据GPL开源。理论上龙芯社区所做的完善均应当公开，并回馈给上游。

3.2节有一处笔误

代码准备
tar -czf ${DOWNLOADDIR}/binutils-2.37.tar.gz binutils-2.37

制作步骤
tar xvf ${DOWNLOADDIR}/binutils-2.37.tar.xz -C ${BUILDDIR}

这里文件后缀应该是gz
-> tar xvf ${DOWNLOADDIR}/binutils-2.37.tar.gz -C ${BUILDDIR}

8.0工具链std::function无法使用

使用8.0工具链时，哪怕#include 也会提示找不到std::function，并给出令人哭笑不得的修复建议。

使用6.0版本不会有此问题。

缺少补丁文件

没有找到文档中提到的如下补丁文件：

guile-3.0.8-add-loongarch64.patch
rustc-1.65.0-add-loongarch-support.patch
cmake-3.22.3-add-loongarch64-to-checktypesize.patch
cmake-3.22.3-add-loongarch64-to-checktypesize.patch
0001-gdb-gdbserver-LoongArch-Improve-implementation-of-fc.patch
userspace-rcu-0.13.1-add-loongarch64.patch
0001-Rustc-1.67.1-vendor-linux-raw-sys-add-loongarch64.patch
xorg-server-21.1.3-fix-x11perf-segment-fault.patch
gstreamer-1.20.0-add-loongarch64.patch
0001-librsvg-2.54.5-fix-loongarch64-support.patch
0001-mozjs-91-add-loongarch64-supprot.patch
qt-everywhere-src-5.15.2-add-loongarch-config.patch
qt-everywhere-src-5.15.6-fix-for-gcc13.patch
0001-QT-5.15.8-add-loongarch64-support.patch
sip-add-loongarch64.patch
pyqt-5.15.6-cross_compiler.patch
pyqt-5.15.6-fix-sip.patch
0001-ibus-1.5.28-change-for-cross-compiler.patch
firefox-100-add-loongarch.patch
firefox-110-fix-rust.patch
firefox-100-xpcom-add-loongarch.patch
firefox-100-for-clfs.patch
firefox-105-fix-for-gcc13.patch
firefox-105-fix-jit-for-loongarch64.patch

Correct-incorrect-inputs-provided-to-the-CRC-functio.patch没有提供下载地址

zlib的Correct-incorrect-inputs-provided-to-the-CRC-functio.patch没有提供下载地址

4.3 missing perl-5.38.0-loongarch64-config.sh

In section 4.3 Perl5,missing perl-5.38.0-loongarch64-config.sh file,the patch in patches is 5.36 ver.

link:https://github.com/sunhaiyong1978/CLFS-for-LoongArch/blob/main/CLFS_For_LoongArch64.md#perl5

20220108 linux kernel 使用的 commit 是哪个您好记得吗？

https://github.com/sunhaiyong1978/CLFS-for-LoongArch/blob/main/CLFS_For_LoongArch64-20220108.md

还记得 20220108 linux kernel 使用的 commit 是哪个？

按照 https://bbs.loongarch.org/d/45-loongarch-next-linux 中的说法，最新版本的 loongarch-next 会有问题。

能方便提供一下当时您所用的 linux commit 是哪个？

催更了催更了

创建目标系统的目录结构小节ln命令的路径问题

ln -sfv usr/{lib{,64},bin,sbin} ./

在fedora35上尝试不成功，需要写明 /usr
即

ln -sfv /usr/{lib{,64},bin,sbin} ./

V20220108 biwu

tar xvf ${DOWNLOADDIR}/binutils-2.37.tar.xz -C ${BUILDDIR}

tar xvf ${DOWNLOADDIR}/binutils-2.37.tar.gz -C ${BUILDDIR}

Are some commands needed?

This command seems to be already applied to source code.
sed -i 's@"loongarch"@"loongarch64"@g' linux-user/loongarch64/target_syscall.h

Similar to sed -i '/compile_prog/s@"\$glib_cflags"@"\$glib_cflags -Werror"@g' configure because later for building passed --disable-werror which seems to be serving same purposes.

Am I miss something?

grub生成efi文件参数缺少fat模块

${CROSS_TARGET}-grub-mkimage \
          --directory "${SYSDIR}/sysroot/usr/lib64/grub/loongarch64-efi" \
          --prefix '(,gpt2)/boot/grub' \
          --output "${SYSDIR}/sysroot/boot/efi/EFI/BOOT/BOOTLOONGARCH.EFI" \
          --format 'loongarch64-efi' \
          --compression 'auto' \
          'ext2' 'part_gpt'

只默认打入了 ext2 和part_gpt
没有efi分区的fat，会导致grub 启动以后无法载入efi分区（fat格式）的各个mod
进入rescue模式

请考虑增加license信息

孙老师，注意到已经有合作者在翻译本文档了。如果有明确的许可协议，对于贡献者提交issue或者翻译者发布作品会更放心，长远看也利于增加loongarch平台的使用，请酌情考虑。
从github在issue页面提供的链接里，看到有一个协议按照说明和我自己的理解是适合教程类使用的。因为不指定授权的内容是创作者拥有版权的，所以添加协议可能需要取得提交过pull request的朋友们的同意。

github推荐的参考信息，可切换多语言版
https://opensource.guide/
授权协议地址
https://choosealicense.com/licenses/cc-by-sa-4.0/

Does autodetection failure means that sometihng should be upstreamed too

I notice that you suggest changing cached configuration values due to detection logic errors. Like this

CLFS-for-LoongArch/CLFS_For_LoongArch64-20210903.md

Lines 803 to 808 in cfffcf0

 ```sh 

 cat > config.cache << "EOF" 

  ac_cv_func_mmap_fixed_mapped=yes 

  ...... 

 EOF 

 ```

Isn't this means that some configuration logic should be upstreamed first? That way for building LoongArch64 applications you don't have to make these changes everywhere.

ELF relocation 问题

孙老师您好，我在使用您2021/6的工具链编译其他软件时遇到了如下问题：

Dump relocate record:
stack top		relocation name		symbol
at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf4b8):
...
0x000000000000482c R_LARCH_SOP_POP_32_S_5_20	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf4bc):
0x000000000006b528 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 4(0x4)
0x00000000047c0fd0 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482c4f8 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2052(0x804)
0x00000000047c17d0 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482ccf8 R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SL	`<nameless>'
0x000000000482c000 R_LARCH_SOP_SUB	`<nameless>'
0x00000000000004f8 R_LARCH_SOP_POP_32_S_10_12	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf530):
0x000000000004b490 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2048(0x800)
0x00000000047c1758 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc80 R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_POP_32_S_5_20	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf534):
0x000000000004b490 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 4(0x4)
0x00000000047c0f58 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482c480 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2052(0x804)
0x00000000047c1758 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc80 R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SL	`<nameless>'
0x000000000482c000 R_LARCH_SOP_SUB	`<nameless>'
0x0000000000000480 R_LARCH_SOP_POP_32_S_10_12	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf544):
0x0000000000072ee8 R_LARCH_SOP_PUSH_PCREL	`.L12063'
0x0000000000000014 R_LARCH_SOP_POP_32_S_10_16_S2	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf548):
0x000000000006b528 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2048(0x800)
0x00000000047c1740 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc68 R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_POP_32_S_5_20	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf54c):
0x000000000006b528 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 4(0x4)
0x00000000047c0f40 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482c468 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2052(0x804)
0x00000000047c1740 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc68 R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SL	`<nameless>'
0x000000000482c000 R_LARCH_SOP_SUB	`<nameless>'
0x0000000000000468 R_LARCH_SOP_POP_32_S_10_12	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf564):
0x000000000006b528 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2048(0x800)
0x00000000047c1724 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc4c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_POP_32_S_5_20	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf568):
0x000000000006b528 R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 4(0x4)
0x00000000047c0f24 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482c44c R_LARCH_SOP_PUSH_PCREL	`_GLOBAL_OFFSET_TABLE_' + 2052(0x804)
0x00000000047c1724 R_LARCH_SOP_PUSH_GPREL	`MainCapability'
0x000000000006b528 R_LARCH_SOP_ADD	`<nameless>'
0x000000000482cc4c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SR	`<nameless>'
0x000000000000482c R_LARCH_SOP_PUSH_ABSOLUTE	`<nameless>' + 12(0xc)
0x000000000000000c R_LARCH_SOP_SL	`<nameless>'
0x000000000482c000 R_LARCH_SOP_SUB	`<nameless>'
0x000000000000044c R_LARCH_SOP_POP_32_S_10_12	`<nameless>'

at compiler/stage2/build/GHC/Rename/Expr.dyn_o(.text+0xcf578):
0x000000000006b528 R_LARCH_SOP_PUSH_PLT_PCREL	`newCAF'
0xfffffffff7f357d8 R_LARCH_SOP_POP_32_S_0_10_10_16_S2	`<nameless>'

/home/hiropoi/Desktop/GHCtime/CrossCPS/cross-tools/bin/../lib/gcc/loongarch64-linux-gnu/8.3.0/../../../../loongarch64-linux-gnu/bin/ld: compiler/stage2/build/GHC/Rename/Expr.dyn_o: in function `.L12063':
(.text+0xcf578): relocation truncated to fit: R_LARCH_SOP_POP_32_S_0_10_10_16_S2 against `<nameless>'
/home/hiropoi/Desktop/GHCtime/CrossCPS/cross-tools/bin/../lib/gcc/loongarch64-linux-gnu/8.3.0/../../../../loongarch64-linux-gnu/bin/ld: final link failed: symbol needs debug section which does not exist
collect2: error: ld returned 1 exit status
-- Record dump end --

`loongarch64-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)

我完全无法解决这个问题。它似乎有点过于底层，而且是由目标软件编译过程中一个非常非常庞大的命令引发的，因此它变得十分不可控……希望您能以专业人士的视点给出一些建议，不胜感激。

3.6 交叉编译器之GCC：编译得到的loongarch64-unknown-linux-gnu-gcc运行出错

Anybodysuggestion？

lauser:/opt/mylaos/downloads$ loongarch64-unknown-linux-gnu-gcc wen1.c
/opt/mylaos/cross-tools/lib/gcc/loongarch64-unknown-linux-gnu/13.0.0/../../../../loongarch64-unknown-linux-gnu/bin/ld: cannot find Scrt1.o: No such file or directory
/opt/mylaos/cross-tools/lib/gcc/loongarch64-unknown-linux-gnu/13.0.0/../../../../loongarch64-unknown-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
/opt/mylaos/cross-tools/lib/gcc/loongarch64-unknown-linux-gnu/13.0.0/../../../../loongarch64-unknown-linux-gnu/bin/ld: cannot find -lc: No such file or directory
/opt/mylaos/cross-tools/lib/gcc/loongarch64-unknown-linux-gnu/13.0.0/../../../../loongarch64-unknown-linux-gnu/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status

关于目标系统 GCC 的链接问题

孙老师你好，
在为目标系统编译安装GCC后，有这么一行命令：

ln -sv /usr/bin/cpp ${SYSDIR}/sysroot/lib

个人认为这是笔误，还望指正。

V20220108 have no package address of file Jinja2-3.0.3 in file list

如题。

20220108文档，4.1小节方法2路径问题

在文档给出的路径并未找到automake的文件夹

路径是否在 ${SYSDIR}/cross-tools/automake-1.16 ？

3.15和3.20节Jinja问题

Jinja2-3.0.3.tar.gz的源码包下载链接在2.3节和3.15节都没有列出；
执行“python3 setup.py install --optimize=1”时出错，当时没有及时记录具体错误提示，但大体意思是xxx/python3.9/xxx目录不存在，因为按文档之前步骤操作创建lauser没有sudo权限也没有设置密码，因此手动用root用户通过mkdir -p创建相关目录，并用root用户执行"python3……"命令完成安装（lauser用户没有python3.9相关目录的权限，因此执行安装会报错）；
执行第2步后，再执行3.20节的操作，会提示“error: [Errno 1] Operation not permitted: 'build/lib/jinja2/py.typed'”
3.15节和3.20节的内容是否重复了？

configure: error: Unable to determine floating-point ABI!!

孙老师你好，有这么个问题想请教您。
问题描述：我在loongarch架构的linux系统上源码编译glibc，升级glibc到2.36版本。在glibc源码目录运行mkdir build && cd build && ../configure时，报如下错误:
checking build system type... loongarch64-unknown-linux-gnu
checking host system type... loongarch64-unknown-linux-gnu
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for readelf... readelf
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether g++ can link programs... yes
checking for sysdeps preconfigure fragments... aarch64 alpha arc arm csky hppa i386 loongarch configure: error: Unable to determine floating-point ABI!!

我的一些排查点：

在glibc源码的README中看到如下内容，按理说glibc2.36版本应该支持loongarch架构了。
aarch64*--linux-gnu
alpha--linux-gnu
arc--linux-gnu
arm--linux-gnueabi
csky--linux-gnuabiv2
hppa--linux-gnu
i[4567]86--linux-gnu
x86_64--linux-gnu Can build either x86_64 or x32
ia64--linux-gnu
loongarch64--linux-gnu Hardware floating point, LE only.
m68k--linux-gnu
microblaze--linux-gnu
mips--linux-gnu
mips64--linux-gnu
or1k--linux-gnu
powerpc--linux-gnu Hardware or software floating point, BE only.
powerpc64--linux-gnu Big-endian and little-endian.
s390--linux-gnu
s390x--linux-gnu
riscv32--linux-gnu
riscv64--linux-gnu
sh[34]--linux-gnu
sparc*--linux-gnu
sparc64-*-linux-gnu
gcc版本信息如下内容。
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/loongarch64-linux-gnu/8/lto-wrapper
Target: loongarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Loongnix 8.3.0-6.lnd.vec.24' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,c++,fortran --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libsanitizer --disable-libquadmath --disable-libquadmath-support --enable-plugin --with-system-zlib --enable-multiarch --disable-werror --with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array --enable-gnu-indirect-function --disable-host-shared --disable-emultls --with-fix-loongson3-llsc --enable-checking=release --build=loongarch64-linux-gnu --host=loongarch64-linux-gnu --target=loongarch64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Loongnix 8.3.0-6.lnd.vec.24)
内核版本是5.4.18。

我不确定是不是因为本机loongarch不支持硬件浮点，而基于loongarch的glibc仅支持硬件浮点？
还是说需要修改检测脚本？

v20220108 duo le yi ge 3.15

3.15 Jinja

tar xvf ${DOWNLOADDIR}/Jinja2-3.0.3.tar.gz -C ${BUILDDIR}
pushd ${BUILDDIR}/Jinja2-3.0.3
python3 setup.py install --optimize=1
popd

	```sh
	cat > config.cache << "EOF"
	ac_cv_func_mmap_fixed_mapped=yes
	......
	EOF
	```

sunhaiyong1978 / clfs-for-loongarch Goto Github PK

clfs-for-loongarch's People

Contributors

Stargazers

Watchers

Forkers

clfs-for-loongarch's Issues

简述

具体信息

Recommend Projects

Recommend Topics

Recommend Org