From: Boris Itkis (Linux) <borisitk@fortunet.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with building sudo
Date: Wed, 20 Dec 2006 14:04:10 -0800 [thread overview]
Message-ID: <4589B35A.90204@fortunet.com> (raw)
In-Reply-To: <20061220182814.GA26024@aon.at>
Bernhard Fischer wrote:
> On Fri, Dec 15, 2006 at 10:14:27AM -0800, Boris Itkis (Linux) wrote:
>
>> Bernhard Fischer wrote:
>>
>>> On Fri, Dec 15, 2006 at 04:10:39PM +0100, Bernhard Fischer wrote:
>>>
>>>
>>>> On Fri, Dec 08, 2006 at 01:32:35PM -0800, Boris Itkis (Linux) wrote:
>>>>
>>>>
>>>>> sudu.mk has a problem for building:
>>>>>
>>>>> $(TARGET_DIR)/usr/bin/sudo
>>>>>
>>>>> it echo's the command to install sudu instead of running it.
>>>>>
>>>>>
>>>> I'll look into this.
>>>>
>>>>
>>> Can you update and retry? The installation is done via fakeroot, sudo
>>> didn't depend on fakeroot so may not be built for you, depending on your
>>> config.
>>>
>>>
>>>
>> The Part I am Refering to is:
>>
>> $(TARGET_DIR)/usr/bin/sudo: $(SUDO_DIR)/sudo
>> # Use fakeroot to pretend to do 'make install' as root
>> echo "$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR="$(TARGET_DIR)" -C
>> $(SUDO_DIR) install" \
>> > $(STAGING_DIR)/.fakeroot.sudo
>> touch -c $(TARGET_DIR)/usr/bin/sudo
>>
>> If you execute ${STAGING_DIR)/.fakeroot.sudo it does the installation
>> correctly.
>>
>> May I suggest that you change:
>>
>> echo "$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR="$(TARGET_DIR)" -C
>> $(SUDO_DIR) install" \
>> > $(STAGING_DIR)/.fakeroot.sudo
>>
>> to:
>>
>> $(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR="$(TARGET_DIR)" -C
>> $(SUDO_DIR) install \
>> > $(STAGING_DIR)/.fakeroot.sudo
>>
>> I believe that should fix the problem of not automatically installing sudo:
>>
>
> what does cat .fakeroot.sudo say if you output stdout of that make
> install into it?
>
>
the consents of .fakeroot.sudo is:
make -j1
PATH=/opt/armtools/bin:/home/root/dist/arm-tool/buildroot/toolchain_build_arm/bin:/home/root/dist/arm-tool/buildroot/fakebin:/home/root/dist/bin:/usr/bin:/bin:/usr/sbin:/sbin
AR=/opt/armtools/bin/arm-linux-uclibc-ar
AS=/opt/armtools/bin/arm-linux-uclibc-as
LD=/opt/armtools/bin/arm-linux-uclibc-ld
NM=/opt/armtools/bin/arm-linux-uclibc-nm
CC=/opt/armtools/bin/arm-linux-uclibc-gcc
GCC=/opt/armtools/bin/arm-linux-uclibc-gcc
CXX=/opt/armtools/bin/arm-linux-uclibc-g++
CPP=/opt/armtools/bin/arm-linux-uclibc-cpp
RANLIB=/opt/armtools/bin/arm-linux-uclibc-ranlib
STRIP=/opt/armtools/bin/arm-linux-uclibc-strip
OBJCOPY=/opt/armtools/bin/arm-linux-uclibc-objcopy
DESTDIR=/home/root/dist/arm-tool/buildroot/build_arm/root -C
/home/root/dist/arm-tool/buildroot/build_arm/sudo-1.6.8p9 install
> Could it be that what you really need is quoting the echoed '"'?
>
> echo "$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR=\"$(TARGET_DIR)\" -C
> $(SUDO_DIR) install" > $(STAGING_DIR)/.fakeroot.sudo
>
>
>
The other option is to change the " to a ` to tiger command execution so
the command would look like:
echo `$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR="$(TARGET_DIR)" -C
$(SUDO_DIR) install` \
> $(STAGING_DIR)/.fakeroot.sudo
prev parent reply other threads:[~2006-12-20 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 21:32 [Buildroot] Problem with building sudo Boris Itkis
2006-12-15 15:10 ` Bernhard Fischer
2006-12-15 15:29 ` Bernhard Fischer
2006-12-15 18:14 ` Boris Itkis
2006-12-20 18:28 ` Bernhard Fischer
2006-12-20 22:04 ` Boris Itkis [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=4589B35A.90204@fortunet.com \
--to=borisitk@fortunet.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.