From: "Rebecca Cran" <rebecca@bsdio.com>
To: gaoliming <gaoliming@byosoft.com.cn>,
devel@edk2.groups.io, 'Chao Li' <lichao@loongson.cn>,
'Baoqi Zhang' <zhangbaoqi@loongson.cn>,
'Dongyan Qian' <qiandongyan@loongson.cn>
Cc: 'Michael D Kinney' <michael.d.kinney@intel.com>
Subject: Re: 回复: [edk2-devel] Reducing the size of the loongarch64 toolchain download
Date: Thu, 29 Dec 2022 20:24:56 -0700 [thread overview]
Message-ID: <d4fc3e66-508b-f58b-2b0b-07ebe923cc73@bsdio.com> (raw)
In-Reply-To: <01a501d91bf4$025d7630$07186290$@byosoft.com.cn>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
The directory exists, that's not the problem.
The issue is that it's far larger than it needs to be: we could save bandwidth and time.
(.venv) bcran@cube:~/src/uefi/tmp/edk2/BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep$ ldd bin/loongarch64-unknown-linux-gnu-*
...
bin/loongarch64-unknown-linux-gnu-gcc:
not a dynamic executable
...
(.venv) bcran@cube:~/src/uefi/tmp/edk2/BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep$ du -h --max-depth=3
4.0K ./include
66M ./bin
134M ./libexec/gcc/loongarch64-unknown-linux-gnu
134M ./libexec/gcc
134M ./libexec
...
40M ./share
23M ./lib/gcc/loongarch64-unknown-linux-gnu
23M ./lib/gcc
12K ./lib/bfd-plugins
23M ./lib
...
37M ./loongarch64-unknown-linux-gnu
396M ./target/usr/include
2.6G ./target/usr/lib64
4.0K ./target/usr/lib
3.0G ./target/usr
3.0G ./target
3.2G .
--
Rebecca Cran
On 12/29/22 19:11, gaoliming wrote:
> Rebecca:
> BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep directory should be created after Stuart build. Please confirm it.
>
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人:devel@edk2.groups.io <devel@edk2.groups.io> 代表 Rebecca Cran
>> 发送时间: 2022年12月28日 16:15
>> 收件人: Chao Li<lichao@loongson.cn>; Baoqi Zhang
>> <zhangbaoqi@loongson.cn>; Dongyan Qian<qiandongyan@loongson.cn>
>> 抄送:devel@edk2.groups.io; Michael D Kinney<michael.d.kinney@intel.com>
>> 主题: [edk2-devel] Reducing the size of the loongarch64 toolchain download
>>
>> I noticed the BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep
>> directory is 3.2GB. However, 2.6GB of that is from target/usr/lib64
>> (which includes X and Qt libraries).
>>
>> Since it appears the gcc binaries are statically linked, I was wondering
>> if the lib and lib64 directories could be excluded from future uploads?
>>
>>
>> --
>> Rebecca Cran
>>
>>
>>
>>
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2812 bytes --]
prev parent reply other threads:[~2022-12-30 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 8:15 Reducing the size of the loongarch64 toolchain download Rebecca Cran
2022-12-28 8:55 ` 回复：Reducing " Chao Li
2022-12-30 2:11 ` 回复: [edk2-devel] Reducing " gaoliming
2022-12-30 3:24 ` Rebecca Cran [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4fc3e66-508b-f58b-2b0b-07ebe923cc73@bsdio.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox