All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Köry Maincent" <kory.maincent@bootlin.com>
Cc: scooby22@web.de, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gcnano-binaries: bump version to 4.3.7
Date: Wed, 8 Jun 2022 16:34:12 +0200	[thread overview]
Message-ID: <20220608163412.4213947c@windsurf> (raw)
In-Reply-To: <20220608154609.3fb671f0@kmaincent-XPS-13-7390>

On Wed, 8 Jun 2022 15:46:09 +0200
Köry Maincent <kory.maincent@bootlin.com> wrote:

> > > +	cp -a $(@D)/$(GCNANO_BINARIES_USERLAND_SUBDIR)/release/include/*
> > > $(1)/usr/include/
> > > +	ln -s gbm/gbm.h $(1)/usr/include/gbm.h
> > > +	cd $(@D)/$(GCNANO_BINARIES_USERLAND_SUBDIR)/pkgconfig/ ; \
> > > +	for file in * ; do \
> > > +		sed -e "s|#PREFIX#|/usr|" $$file > $$file.temp ; \
> > > +		$(INSTALL) -D -m 0644 $$file.temp
> > > $(1)/usr/lib/pkgconfig/$$file ; \
> > > +		rm $$file.temp ; \    
> > 
> > I'd say you can leave the $$file.tmp around in the build directory, it
> > will not cause any problem.  
> 
> It does, in the case we call the reinstall task, these temp files will be added
> to the for loop.

Change the for loop to:

	for file in *.pc; do

and problem solved.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-06-08 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 13:29 [Buildroot] [PATCH] package/gcnano-binaries: bump version to 4.3.7 Kory Maincent via buildroot
2022-06-08 13:35 ` Thomas Petazzoni via buildroot
2022-06-08 13:46   ` Köry Maincent via buildroot
2022-06-08 14:34     ` Thomas Petazzoni via buildroot [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=20220608163412.4213947c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=kory.maincent@bootlin.com \
    --cc=scooby22@web.de \
    --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 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.