Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001415]: SVN buildroot does not build configuration package
Date: Mon, 9 Jul 2007 21:16:45 +0200	[thread overview]
Message-ID: <20070709191645.GA25250@aon.at> (raw)
In-Reply-To: <37c712e0707091150q216848bqfb06055300b50398@mail.gmail.com>

On Mon, Jul 09, 2007 at 02:50:19PM -0400, Allan Clark wrote:
>On 7/9/07, Bernhard Fischer <rep.dot.nop@gmail.com> wrote:

>>There's no need to touch foo.h
>
>Actually, there is, and I discussed it in the list

You said something about it, have to revisit the details.
>
>>>patching file toolchain/gcc/4.2.0/500-bsd-no-map_anonymous.patch
>>>patching file toolchain/dependencies/dependencies.sh
>>>patching file toolchain/dependencies/dependencies.mk
>>>patching file package/make/make.mk
>>
>>Is there a newer version of make out there?
>
>I think it was updated in r19056; this change is used with following:
>
>>>patching file toolchain/dependencies/check-host-make.sh
>
>See also bug #1422

ah, i thought that was already in. My bad, it was automake for the host.

>>>:~/src/buildroot Allan$ chmod +x
>>>toolchain/dependencies/check-host-make.sh
>>
>>I don't think that you really need this to be executable
>
>Fails if it isn't executable.

It is called via
$(shell $(CONFIG_SHELL) $(check-lxdialog)
I fail to see how this would require it to be executable unless you
don't have a shell (which is unlikely since then you couldn't run it
either way ;)

>I assume if my bug#1422, resolved by file#1072 and 1073 is
>incorporated, then I won't need to make this file executable, it'll
>checkout executable just as check-host-sed.sh does.

That late-binding of MAKE1 would be really, really ugly. hm.

head -1
this is deprecated (didn't look if sed does the same; if so both need
fixing).

Re your change to dependencies.mk. Please explain why you do not use the
very same scheme for host-make as for sed-make?

  reply	other threads:[~2007-07-09 19:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 18:23 [Buildroot] [buildroot 0001415]: SVN buildroot does not build configuration package bugs at busybox.net
2007-07-09 18:27 ` Bernhard Fischer
2007-07-09 18:50   ` Allan Clark
2007-07-09 19:16     ` Bernhard Fischer [this message]
2007-07-09 21:41       ` Allan Clark
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 13:29 bugs at busybox.net
2007-07-10 15:43 bugs at busybox.net
2007-07-09 18:19 bugs at busybox.net
2007-07-09 17:29 bugs at busybox.net
2007-07-09 17:28 bugs at busybox.net
2007-07-09 16:55 bugs at busybox.net
2007-07-09 16:18 bugs at busybox.net
2007-07-08  0:29 bugs at busybox.net
2007-07-05 14:02 bugs at busybox.net
2007-07-03 19:11 bugs at busybox.net
2007-07-03  1:07 bugs at busybox.net
2007-07-03  1:05 bugs at busybox.net
2007-07-02 11:58 bugs at busybox.net
2007-07-02 11:56 bugs at busybox.net

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=20070709191645.GA25250@aon.at \
    --to=rep.dot.nop@gmail.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