From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] slang.mk (was: something (slang?) creates buildroot/build_i486/staging_dir/include)
Date: Mon, 30 Jul 2007 12:02:02 +0200 [thread overview]
Message-ID: <20070730100202.GH23273@aon.at> (raw)
In-Reply-To: <0707291107480.8510@somehost>
On Sun, Jul 29, 2007 at 11:38:54AM +0200, Cristian Ionescu-Idbohrn wrote:
>On Sun, 29 Jul 2007, Cristian Ionescu-Idbohrn wrote:
>
>> On Sun, 29 Jul 2007, Cristian Ionescu-Idbohrn wrote:
>>
>> > See attachment, and that may be screwing up things.
>> > See also my previous posts.
>>
>> Moving buildroot/build_i486/staging_dir/include away will allow libpcap,
>> tcpdump, wget and which to build. Though I still have troubles building
>> gawk and util-linux :(
>
>Replying to myself :)
>Yes, package/slang/slang.mk screws up things :(
Applied as r19335. Thanks!
>I do not know much about the buildroot backyard, but I read some
>discussions about the include-dir being $(STAGING_DIR)/usr/include/
>and not $(STAGING_DIR)/include/. Wouldn't it be a good idea to make that a
>variable somewhere in the top makefiles, something like:
>
> STAGING_INCLUDE_DIR = $(STAGING_DIR)/usr/include/
>
>and change all .mk files to use that instead? That should give one point
No, we do not need a STAGING_INCLUDE_DIR.
Every package that installs headers into $(STAGING_DIR)/include is wrong
(i.e. was not yet corrected to properly install into ../usr/include).
The libraries should be installed to the same dir (/lib vs. /usr/lib) as
on an LFS compliant host (usually into /usr/lib except some rare libs
such as libc).
>of control on where the header files are installed and avoid errors and
>confusion.
>
>I noticed the .mk files use `cp' rather than `install', to install various
>files. Is there a good reason for that?
There is no good reason, no. I'd favour to use $(INSTALL) myself,
patches welcome.
>
>On my box (debian sid), these two make variables:
>
> INSTALL = /usr/bin/install
> RM = rm -f
>
>are predefined. Why not use them in the make files. Top makefiles would
>again be the place to control the behaviour, should there be any
>compatibility concerns with various distributions.
>
>Shouldn't the clean-targets even clean stuff that was installed under the
>STAGING_DIR?
yes, it should. Not all packages are yet adjusted to do this. Again,
patches to fix these are welcome.
TIA,
Bernhard
prev parent reply other threads:[~2007-07-30 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 23:08 [Buildroot] something (slang?) creates buildroot/build_i486/staging_dir/include Cristian Ionescu-Idbohrn
2007-07-28 23:25 ` Cristian Ionescu-Idbohrn
2007-07-29 9:38 ` [Buildroot] [patch] slang.mk (was: something (slang?) creates buildroot/build_i486/staging_dir/include) Cristian Ionescu-Idbohrn
2007-07-29 17:09 ` Ulf Samuelsson
2007-07-30 10:02 ` Bernhard Fischer [this message]
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=20070730100202.GH23273@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 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.