From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 5/5] sgpio : add new recipe
Date: Wed, 19 Nov 2014 15:33:30 +0100 [thread overview]
Message-ID: <20141119143330.GF3315@jama> (raw)
In-Reply-To: <1416222008-9218-6-git-send-email-lixin.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 3900 bytes --]
On Mon, Nov 17, 2014 at 07:00:08PM +0800, Li xin wrote:
> Intel SGPIO enclosure management utility
>
> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> ---
> .../0001-Makefile-modify-some-parameters.patch | 51 ++++++++++++++++++++++
> meta-oe/recipes-extended/sgpio/sgpio_1.2.0.10.bb | 28 ++++++++++++
> 2 files changed, 79 insertions(+)
> create mode 100644 meta-oe/recipes-extended/sgpio/sgpio-1.2.0.10/0001-Makefile-modify-some-parameters.patch
> create mode 100644 meta-oe/recipes-extended/sgpio/sgpio_1.2.0.10.bb
>
> diff --git a/meta-oe/recipes-extended/sgpio/sgpio-1.2.0.10/0001-Makefile-modify-some-parameters.patch b/meta-oe/recipes-extended/sgpio/sgpio-1.2.0.10/0001-Makefile-modify-some-parameters.patch
> new file mode 100644
> index 0000000..8b23a19
> --- /dev/null
> +++ b/meta-oe/recipes-extended/sgpio/sgpio-1.2.0.10/0001-Makefile-modify-some-parameters.patch
> @@ -0,0 +1,51 @@
> +From ecb100a252c691075720ff0604e2ebdb83deb994 Mon Sep 17 00:00:00 2001
> +From: Li xin <lixin.fnst@cn.fujitsu.com>
> +Date: Mon, 17 Nov 2014 12:26:21 +0900
> +Subject: [PATCH] Makefile : modify some parameters
> +
> +Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> +---
> + Makefile | 13 ++++++++-----
> + 1 file changed, 8 insertions(+), 5 deletions(-)
> +
> +diff --git a/Makefile b/Makefile
> +index 278d966..431d993 100755
> +--- a/Makefile
> ++++ b/Makefile
> +@@ -23,25 +23,28 @@
> +
> +
> + MANDIR ?= /usr/local/man
> ++SBIN_DIR = /sbin
> ++INSTALL =/usr/bin/install -c
> + ALL = sgpio
> ++CFLAGS = -g -Wall
> +
> + all: $(ALL)
> +
> + sgpio.o: sgpio.c
> +- gcc -g -Wall -c sgpio.c
> ++ ${CC} $(CFLAGS) -c sgpio.c
> +
> + sgpio: sgpio.o
> +- gcc -g sgpio.o -o sgpio
> ++ ${CC} -g sgpio.o -o sgpio
> +
> + clean:
> + rm -f sgpio.o sgpio
> +
> + install: $(ALL)
> + for i in $(ALL); do \
> +- install $$i /sbin/$$i; \
> ++ $(INSTALL) -D $$i $(SBIN_DIR)/$$i; \
> + done
> +- install -d $(MANDIR)/man1
> +- install -m 0644 *.1 $(MANDIR)/man1
> ++ $(INSTALL) -d $(MANDIR)/man1
> ++ $(INSTALL) -m 0644 *.1 $(MANDIR)/man1
> +
> + uninstall:
> + for i in $(ALL); do \
> +--
> +1.8.4.2
> +
> diff --git a/meta-oe/recipes-extended/sgpio/sgpio_1.2.0.10.bb b/meta-oe/recipes-extended/sgpio/sgpio_1.2.0.10.bb
> new file mode 100644
> index 0000000..7867d9d
> --- /dev/null
> +++ b/meta-oe/recipes-extended/sgpio/sgpio_1.2.0.10.bb
> @@ -0,0 +1,28 @@
> +SUMMARY = "SGPIO captive backplane tool"
> +DESCRIPTION = "Intel SGPIO enclosure management utility"
> +HOMEPAGE = "http://sources.redhat.com/lvm2/wiki/DMRAID_Eventing"
> +SECTION = "System Environment/Base"
> +
> +SRC_URI = "http://pkgs.fedoraproject.org/repo/pkgs/${PN}/${PN}-1.2-0.10-src.tar.gz/a417bf68da4e9bd79a4664c11d7debd1/${PN}-1.2-0.10-src.tar.gz"
> +
> +SRC_URI += "file://0001-Makefile-modify-some-parameters.patch"
> +
> +SRC_URI[md5sum] = "a417bf68da4e9bd79a4664c11d7debd1"
> +SRC_URI[sha256sum] = "9bf8c42acaa247efd9321bdb1fc2390022f0c554d77fbbd4a7363d990fc0270b"
> +
> +S = "${WORKDIR}/${PN}"
> +
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://LICENSE_GPL;md5=393a5ca445f6965873eca0259a17f833"
> +
> +do_compile_prepend() {
> + oe_runmake clean
> +}
> +
> +do_install() {
> + oe_runmake install \
> + INSTALL="/usr/bin/install -p" \
> + DESTDIR=${D} \
> + SBIN_DIR=${D}/${sbindir} \
> + MANDIR=${D}/${mandir}
use 4 spaces for indentation, no tabs and definitely no mix of tabs and
spaces
I've fixed this one when cherry-picking to master-next
> +}
> --
> 1.8.4.2
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-11-19 14:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:00 [PATCH 0/5] Adding some recipes Li xin
2014-11-17 11:00 ` [PATCH 1/5] rarpd : add recipe Li xin
2014-11-18 2:07 ` Rongqing Li
2014-11-18 9:55 ` [meta-oe][PATCH v2] rarpd : add new recipe Li xin
2014-11-18 20:14 ` Christopher Larson
2014-11-19 14:40 ` Martin Jansa
2014-11-17 11:00 ` [PATCH 2/5] nicstat : add recipe Li xin
2014-11-18 2:11 ` Rongqing Li
2014-11-18 5:13 ` Li, Xin
2014-11-18 5:52 ` [PATCH v2] nicstat : add new recipe Li xin
2014-11-19 14:35 ` Martin Jansa
2014-11-17 11:00 ` [PATCH 3/5] sblim-sfcb " Li xin
2014-11-17 12:22 ` Wolfgang Denk
2014-11-21 14:06 ` Martin Jansa
2014-11-17 11:00 ` [PATCH 4/5] sblim-sfcc : add recipe Li xin
2014-11-17 11:00 ` [PATCH 5/5] sgpio : add new recipe Li xin
2014-11-19 14:33 ` Martin Jansa [this message]
2014-11-21 14:03 ` Martin Jansa
2014-11-25 2:17 ` Li, Xin
2014-11-26 6:42 ` [meta-oe][PATCH v2] " Li xin
2015-01-21 3:21 ` [meta-oe][PATCH v2] sgpio: " Li xin
2015-01-22 15:16 ` Martin Jansa
2015-01-23 2:49 ` [meta-oe][PATCH v3] " Li xin
2015-01-28 10:53 ` Martin Jansa
2015-01-29 9:47 ` Li, Xin
2015-06-29 9:32 ` Li, Xin
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=20141119143330.GF3315@jama \
--to=martin.jansa@gmail.com \
--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