All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/5] hdparm: 9.48 -> 9.50
Date: Thu, 22 Dec 2016 14:34:35 +0100	[thread overview]
Message-ID: <d99876dc-4982-496b-2b9d-34540ce09b01@opendreambox.org> (raw)
In-Reply-To: <ea7ce818-05fa-a41d-c70e-b94260328d09@windriver.com>

On 22.12.2016 04:14, Robert Yang wrote:
> On 12/22/2016 11:09 AM, Andreas Oberritter wrote:
>> On 22.12.2016 03:47, Robert Yang wrote:
>>> On 12/21/2016 09:27 PM, Andre McCurdy wrote:
>>>> Passing LDFLAGS on the make command line might be a cleaner solution
>>>> than patching the Makefile.
>>>
>>> We can't do that since there is a "-e MAKEFLAGS=" in EXTRA_OEMAKE,
>>> and its
>>> Makefile is:
>>>
>>> all:
>>>     make -j2 hdparm
>>>
>>> hdparm: hdparm.h sgio.h $(OBJS)
>>>     $(CC) $(LDFLAGS) -o hdparm $(OBJS)
>>>     $(STRIP) hdparm
>>>
>>> The "make -j2 hdparm" doesn't pass any env vars to sub make since
>>> MAKEFLAGS=,
>>> so that need use weak assignment "?=" here.
>>
>> You don't need to use target 'all'. Try this:
>>
>> do_compile() {
>>     oe_runmake hdparm
>> }
> 
> I know this will work, but "make hdparm" rather than "all" may cause other
> issues in the future when hdparm gets ugpraded, for example, "all" doesn't
> only contain "hdmarm". And do we have really have to add a do_compile()
> here ?

It's certainly easier to delete do_compile in a future version's recipe
than regenerating patches. hdparm is looking for a new maintainer, btw.

'hdparm' has been the only target built by 'all' since at least version
3.1, which dates back to 1996.

Regards,
Andreas


  reply	other threads:[~2016-12-22 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  6:17 [PATCH 0/5] Packages Upgrade Robert Yang
2016-12-21  6:17 ` [PATCH 1/5] debianutils: 4.8 -> 4.8.1 Robert Yang
2016-12-21  6:17 ` [PATCH 2/5] mklibs-native: 0.1.41 -> 0.1.43 Robert Yang
2016-12-21  6:17 ` [PATCH 3/5] quilt: 0.64 -> 0.65 Robert Yang
2016-12-21  6:17 ` [PATCH 4/5] guile: 2.0.12 -> 2.0.13 Robert Yang
2016-12-21  6:17 ` [PATCH 5/5] hdparm: 9.48 -> 9.50 Robert Yang
2016-12-21 13:27   ` Andre McCurdy
2016-12-22  2:47     ` Robert Yang
2016-12-22  2:49       ` Robert Yang
2016-12-22 12:55         ` Andre McCurdy
2016-12-22  3:09       ` Andreas Oberritter
2016-12-22  3:14         ` Robert Yang
2016-12-22 13:34           ` Andreas Oberritter [this message]
2017-01-04  2:12             ` Robert Yang

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=d99876dc-4982-496b-2b9d-34540ce09b01@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=armccurdy@gmail.com \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@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 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.