patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net, stable@dpdk.org,
	Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH] ci: fix build for Arm cross compilation in GHA
Date: Tue, 6 Jun 2023 14:02:29 +0100	[thread overview]
Message-ID: <a04ae25c-43f4-1c90-2ab8-f6a703f6745f@amd.com> (raw)
In-Reply-To: <ZH8R2qmPoxfisXRc@bricha3-MOBL.ger.corp.intel.com>

On 6/6/2023 12:00 PM, Bruce Richardson wrote:
> On Tue, Jun 06, 2023 at 12:52:47PM +0200, David Marchand wrote:
>> We are hitting a storage limit when linking binaries statically.
>> On the other hand, native builds are tested in other part of the CI and
>> the chance of breaking static linking only is relatively low, so let's
>> simply test linking against shared libraries.
>>
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>> ---
>>  .github/workflows/build.yml | 1 +
>>  1 file changed, 1 insertion(+)
> 
> Yep, with the number of "test" apps now in each build, our build
> directories get rather massive!
> 
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>

Confirmed that this solves the "running out of disk space" issue seen on
'ubuntu-20.04-gcc-aarch64',

Tested-by: Ferruh Yigit <ferruh.yigit@amd.com>


  reply	other threads:[~2023-06-06 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 10:52 David Marchand
2023-06-06 11:00 ` Bruce Richardson
2023-06-06 13:02   ` Ferruh Yigit [this message]
2023-06-06 13:09     ` Thomas Monjalon

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=a04ae25c-43f4-1c90-2ab8-f6a703f6745f@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).