Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Andreas Ziegler <br015@umbiko.net>
Cc: "Romain Naour" <romain.naour@gmail.com>,
	"Jörg Krause" <joerg.krause@embedded.rocks>,
	"Fabrice Fontaine" <fontaine.fabrice@gmail.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/zziplib: create symlinks only if target is missing
Date: Tue, 13 Sep 2022 16:18:15 +0200	[thread overview]
Message-ID: <87mtb3tl20.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220729163718.58963-1-br015@umbiko.net> (Andreas Ziegler's message of "Fri, 29 Jul 2022 18:37:18 +0200")

>>>>> "Andreas" == Andreas Ziegler <br015@umbiko.net> writes:

 > Symlink creation to base file names is only needed for versioned libraries. 
 > Modify CMake rules to prevent overwriting existing libraties with recursive
 > links.

 > Fixes the following autobuild failures:
 > http://autobuild.buildroot.net/results/dd1/dd1974dbc1a22a96a3cedb117417e66119821514/
 > http://autobuild.buildroot.net/results/df8/df8406402ccff7cec34ae5858b8da57d1a4ae9c1/
 > http://autobuild.buildroot.net/results/743/7433a2ad111e2f014c81f196d3d1e2f63dffa858/
 > http://autobuild.buildroot.net/results/79f/79f88e9ec14cda7d07cf689eee864791ba949892/
 > ...
 > http://autobuild.buildroot.net/results/892/8922efbbbfe79e8286a411acce4086b5c77c57c0/
 > http://autobuild.buildroot.net/results/dfa/dfa8ade3a4c1750e6dd58e652f60af2a44f80dd8/
 > http://autobuild.buildroot.net/results/9cd/9cd4147486f32d642513ba14efca3a02d5745ab9/

 > Regression test cases:
 > http://autobuild.buildroot.net/results/ba7/ba711034c0abe980f677e26de41739223e2f66e9/
 > http://autobuild.buildroot.net/results/032/032aaff121fb114f388c67dbca3ad2b02f670e38/
 > http://autobuild.buildroot.net/results/6c5/6c56b645a2b723920f07b98474452824fba5e2c1/

 > Signed-off-by: Andreas Ziegler <br015@umbiko.net>
 > ---
 > Changes v1 -> v2:
 >  - correct file name in generator expressions

Committed to 2022.05.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-09-13 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 16:21 [Buildroot] [PATCH 1/1] package/zziplib: fix static build failure with mpd Andreas Ziegler
2021-12-24 17:22 ` Thomas Petazzoni
2021-12-27  7:40   ` [Buildroot] [PATCH v2 " Andreas Ziegler
2022-03-20 11:41     ` [Buildroot] [PATCH v3 " Andreas Ziegler
2022-03-27 15:57       ` Arnout Vandecappelle
2022-03-30 19:43       ` Peter Korsgaard
2022-07-25 20:49       ` Arnout Vandecappelle
2022-07-26  6:24         ` Andreas Ziegler
2022-07-28 14:36         ` Andreas Ziegler
2022-07-29  9:13         ` [Buildroot] [PATCH 1/1] package/zziplib: create symlinks only if target is missing Andreas Ziegler
2022-07-29  9:34           ` Andreas Ziegler
2022-07-29 16:37           ` [Buildroot] [PATCH v2 " Andreas Ziegler
2022-07-29 20:15             ` Arnout Vandecappelle
2022-09-13 14:18             ` Peter Korsgaard [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-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=87mtb3tl20.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=br015@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=joerg.krause@embedded.rocks \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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