From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: trouble with cp command in autotools.bbclass
Date: Tue, 01 Apr 2008 08:47:57 +0200 [thread overview]
Message-ID: <fsslqt$uhe$2@ger.gmane.org> (raw)
In-Reply-To: <47F185E1.9070307@gmx.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Schuster schreef:
| Hi,
| lately the following copy operation has been added to autotools.bbclass:
|
| # Otherwise libtool wasn't used, and lib/ can be copied
| # directly.
| echo "cp -fpPR ${STAGE_TEMP}/${libdir}/* ${STAGING_LIBDIR}"
| cp -fpPR ${STAGE_TEMP}/${libdir}/* ${STAGING_LIBDIR}
|
| I have trouble with this and a package that creates an empty ${libdir}.
| Shell globbing (*) wont find a file and instead tries to copy a file
| named "*" ... and fails and so does my built.
|
| I would like to replace this with the following lines which uses find
| and is more robust:
|
| # (The find command handles an empty ${STAGE_TEMP/${libdir} correctly)
| echo "find ${STAGE_TEMP}/${libdir} -mindepth 1 -maxdepth 1 -exec cp
| -fpPR {} ${STAGING_LIBDIR}" \;
|
| find ${STAGE_TEMP}/${libdir} -mindepth 1 -maxdepth 1 -exec cp -fpPR {}
| ${STAGING_LIBDIR} \;
|
| Ok for commit?
or use:
autotools_stage_dir ${STAGE_TEMP}/${libdir} ${STAGING_LIBDIR}
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH8dqdMkyGM64RGpERAuRsAKCZscg8u3San7ui3qkZfjJPwOWvPACgp7oF
Qzjxe69KN+cq/BayJRi1/Ic=
=iHP3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-04-01 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 0:46 trouble with cp command in autotools.bbclass Robert Schuster
2008-04-01 6:47 ` Koen Kooi [this message]
2008-04-02 23:08 ` Robert Schuster
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='fsslqt$uhe$2@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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