From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/3] libatomic-ops: switch to own directroy and use cvs version
Date: Tue, 22 Mar 2011 09:19:38 +0100 [thread overview]
Message-ID: <im9m2q$pse$1@dough.gmane.org> (raw)
In-Reply-To: <1300780910-28866-2-git-send-email-heinold@inf.fu-berlin.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-03-11 09:01, heinold@inf.fu-berlin.de wrote:
> From: Henning Heinold <heinold@inf.fu-berlin.de>
> +++ b/recipes/libatomic-ops/libatomic-ops_cvs.bb
> @@ -0,0 +1,15 @@
> +DESCRIPTION = "A library for atomic integer operations"
> +LICENSE = "MIT"
> +
> +PV = "4.0+cvs${SRCDATE}"
> +
> +SRC_URI = "cvs://anonymous@bdwgc.cvs.sourceforge.net/cvsroot/bdwgc;module=bdwgc"
> +
> +S = "${WORKDIR}/bdwgc/libatomic_ops/"
> +
> +inherit autotools pkgconfig
> +
> +# Allow empty package to fix SDK depchains
> +ALLOW_EMPTY_${PN} = "1"
> +
> +FILES_${PN}-doc += "${datadir}/libatomic_ops/COPYING ${datadir}/libatomic_ops/*.txt"
Where are you setting SRCDATE for this recipe?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNiFuaMkyGM64RGpERAkn6AKC5bgVE7shDA6lUCMmPVjP4NdqaagCfQ4L4
aenatxfKDnffrucGwrGnD7I=
=N/3n
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-22 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 8:01 Attempt to fix libatomic-ops heinold
2011-03-22 8:01 ` [PATCH 1/3] libatomic-ops: switch to own directroy and use cvs version heinold
2011-03-22 8:19 ` Koen Kooi [this message]
2011-03-22 9:00 ` Henning Heinold
2011-03-22 9:05 ` Martin Jansa
2011-03-22 9:05 ` Koen Kooi
2011-03-22 8:01 ` [PATCH 2/3] cairo.inc: let arm, mips and ppc depend on libatomic-ops heinold
2011-03-22 8:31 ` Paul Menzel
2011-03-22 9:07 ` Koen Kooi
2011-03-22 17:19 ` Khem Raj
2011-03-22 17:30 ` Henning Heinold
2011-03-22 18:14 ` Khem Raj
2011-03-23 10:21 ` Phil Blundell
2011-03-22 8:01 ` [PATCH 3/3] pulseaudio.inc: " heinold
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='im9m2q$pse$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.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