All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chu, Zhuliang (NSB - CN/Shanghai) <zhuliang.chu@nokia-sbell.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv1 0/4] Per-package SDK and target directories
Date: Thu, 9 Nov 2017 08:19:10 +0000	[thread overview]
Message-ID: <5DBA847110A28B46BBA17BE675F0C9B2181AA4B9@cnshjmbx01> (raw)
In-Reply-To: <20171108172914.GA4602@scaer>

Hello Yann E,

>
>So, I wonder what openssl you are using... :-/
I am sorry to cause your confusion. This is an imaginary example I give.
I've already explained this issue in the email that responded to Thomas Petazzoni.

>> Q2: Space Expension
>> in qemu_x86_defconfig, the size of output increased from 3.4G to 3.6G between mainstream with 'ppsh'.
>> in my private, the rate of space occupancy growth is higher. it`s crazy from 3.6G to 9G .This obviously can not accept. (A large
>> part of reason is that I use a very large toolchain-external which about 1.5G)
>> Before a package only consumes one space, but now a package maybe reoccupied space below per-package.
>
>As others already stated, in may depend on the tools you use to report
>the disk usage, but can also depend on the type of filesystem.
>
>What filesystem are you using: ext3/4, btrfs, xfs, other?
>
>What command did you run to come up with those numbers?

my filesystem is xfs of centos7.
Sorry.This problem is likely to be one of my mistake rather than 'per-package'.
That day I encountered a compilation error 'toolchain HOST_DIR' which had been reported to Thomas Petazzoni.
The details:
when run the command 'output/per-package/toolchain/host//usr/bin/mips64-octeon-linux-gnu-gcc  --version'.
there will raise a error 'output/per-package/toolchain-external-custom/host/opt/ext-toolchain/bin/mips64-octeon-linux-gnu-gcc: No such file or directory'
When I encountered this error. I made a patch to solve it.
But after I saw thomas reply, I carefully checked my patch and I found out that my patch duplicates the toolchain-tar in the per-package/ package which dependent toolchain.

I am currently testing per-package. I have not finished all the compilation.
I have encountered many problems, of which some are my own environment issues and others are per-package issues.
I am trying to solve these problems to promote its progress.
Hopefully per-package SDK can be pushed into the mainstream as soon as possible.

Chu,Zhuliang
Best Regards,

  parent reply	other threads:[~2017-11-09  8:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5DBA847110A28B46BBA17BE675F0C9B2181A8D38@cnshjmbx01>
2017-11-07 17:13 ` [Buildroot] [RFCv1 0/4] Per-package SDK and target directories Thomas Petazzoni
2017-11-07 17:55   ` Arnout Vandecappelle
2017-11-07 19:55     ` Thomas Petazzoni
2017-11-07 20:54       ` Arnout Vandecappelle
2017-11-09  5:02     ` Chu, Zhuliang
2017-11-11 10:20       ` Arnout Vandecappelle
2017-11-09  4:32   ` Chu, Zhuliang
2017-11-11 10:37     ` Arnout Vandecappelle
2017-11-15  8:59       ` Chu, Zhuliang
2017-11-08 16:55 ` Thomas Petazzoni
2017-11-09  4:44   ` Chu, Zhuliang
2017-11-08 17:29 ` Yann E. MORIN
2017-11-08 18:35   ` Thomas De Schampheleire
2017-11-09  8:19   ` Chu, Zhuliang [this message]
2017-11-03 16:06 Thomas Petazzoni
2017-11-07 23:21 ` Arnout Vandecappelle

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-all 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=5DBA847110A28B46BBA17BE675F0C9B2181AA4B9@cnshjmbx01 \
    --to=zhuliang.chu@nokia-sbell.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.