Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Viallard Anthony <viallard@syscom-instruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Force rebuild of local site packages and theirs local dependencies
Date: Mon, 22 Jun 2015 12:01:56 +0200	[thread overview]
Message-ID: <5587DD14.2020001@syscom-instruments.com> (raw)
In-Reply-To: <20150616163054.GA4861@dkarchlinux64.currentcomm.com>

On 06/16/2015 06:30 PM, rdkehn at yahoo.com wrote:
> make[3]: Nothing to be done for 'all'.
>>>> test 1.0.0 Installing to target
>
> I was expecting libtest.c in libtest to be rebuilt and all of test
> to be rebuilt.  A second execution of 'make test-rebuild' does
> perform the expected steps.  ...interesting.
>
> I apologize if I've mucked this whole thing up.  These were just my
> observations for an interesting patch that followed a similar work
> flow.
>
> Regards,
> ...doug
>

Hi doug,

Indeed. There is a big problem with my patch. I believed the job was 
done and rebuild the package and these dependencies if change was found 
but it doesn't. I'm disappointed. I pushed the patch too quickly.

I'm trying to find a new way to implement my needs.

Regards,
Anthony.

  reply	other threads:[~2015-06-22 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:21 [Buildroot] [PATCH 1/1] Force rebuild of local site packages and theirs local dependencies Anthony Viallard
2015-06-16 16:30 ` rdkehn at yahoo.com
2015-06-22 10:01   ` Viallard Anthony [this message]
2015-06-16 19:50 ` Thomas Petazzoni
2015-06-22 10:15   ` Viallard Anthony
2015-06-22 12:07     ` Viallard Anthony
2015-06-22 16:13     ` rdkehn at yahoo.com
2015-07-02  8:56       ` Viallard Anthony
2015-06-23  7:56     ` Jérôme Pouiller
2015-07-02  9:01       ` Viallard Anthony
2015-07-02 15:32         ` Jérôme Pouiller

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=5587DD14.2020001@syscom-instruments.com \
    --to=viallard@syscom-instruments.com \
    --cc=buildroot@busybox.net \
    /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