Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Ignored patches - WHY?
Date: Fri, 19 Oct 2007 01:47:46 +0200	[thread overview]
Message-ID: <1192751266.5848.7.camel@c-f97ee255> (raw)
In-Reply-To: <4717EE0C.2090900@promwad.com>

fre 2007-10-19 klockan 02:36 +0300 skrev Ivan Kuten:
> Rex Luscus wrote:
> > Ok. This patch only change the dir of the bin of daemon.
> > 
> > Can you change this or you want that I make a new patch?
> > 
> > 
> > PD: ok, ok, my english is HORRIBLE, but I don't use this too often for write, 
> > only for read :-)
> > 
> > 
> > Ivan Kuten escribi?:
> >> Sushi Sensei wrote:
> >>   
> >>> I have send some patches ( 0001534, 0001533, 0001532) this week with
> >>> the Patch Tracking page, the week before I have send the same patches
> >>> without notices of this inclusion or error, some patch was send 2 or 3
> >>> week before and was ignored... There are some problem with this
> >>> patches??
> >>>     
> >>
> >> Hi Sushi,
> >>
> >> I'm sorry I can not apply this patch : br2-olsr.patch:
> >>
> >> Index: package/olsr/S50olsr
> >> ===================================================================
> >> --- package/olsr/S50olsr        (revisi?n: 20228)
> >> +++ package/olsr/S50olsr        (copia de trabajo)
> >> @@ -6,7 +6,7 @@
> >>  case "$1" in
> >>    start)
> >>         echo "Starting OLSRd daemon: "
> >> -       /usr/sbin/olsrd -d 0 -nofork &
> >> +       /usr/bin/olsrd -d 0 -nofork &
> >>         ;;
> >>    stop)
> >>         echo "Stopping OLSRd daemon: "
> >>
> >>   
> > 
> 
> >>Because an daemon should reside in /usr/sbin directory ,
> >>please check other buildroot packages such as dropbear, mdnsresponder, and so on - they are all in sbin dir.
> >>You should change OLSR_TARGET_BINARY:=usr/bin/olsrd instead.
> 
> Unfortunately I could not manage to build OLSR correctly:
> 
> /opt/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-strip olsrd_dot_draw.so.0.3
> install -D -m 755 olsrd_dot_draw.so.0.3 /usr/lib/olsrd_dot_draw.so.0.3; /sbin/ldconfig -n /usr/lib
> install: cannot create regular file `/usr/lib/olsrd_dot_draw.so.0.3': Permission denied
> ...
> make[2]: Entering directory `/opt/buildroot/build_arm/olsrd-0.5.3/lib/dyn_gw'
> /opt/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-strip olsrd_dyn_gw.so.0.4
> install -D -m 755 olsrd_dyn_gw.so.0.4 /usr/lib/olsrd_dyn_gw.so.0.4; /sbin/ldconfig -n /usr/lib
> install: cannot create regular file `/usr/lib/olsrd_dyn_gw.so.0.4': Permission denied
> make[2]: Leaving directory `/opt/buildroot/build_arm/olsrd-0.5.3/lib/dyn_gw'
> ...
>  make[2]: Entering directory `/opt/buildroot/build_arm/olsrd-0.5.3/lib/secure'
> /opt/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-strip olsrd_secure.so.0.5
> install -D -m 755 olsrd_secure.so.0.5 /usr/lib/olsrd_secure.so.0.5; /sbin/ldconfig -n /usr/lib
> install: cannot create regular file `/usr/lib/olsrd_secure.so.0.5': Permission denied
> make[2]: Leaving directory `/opt/buildroot/build_arm/olsrd-0.5.3/lib/secure'
> 
> Could you provide a patch?
> 

OLSR will do an install in $(DESTDIR)/usr/lib
You need to add DESTDIR=$(STAGING_DIR) to the make.

I.E:

$(OLSR_DIR)/$(OLSR_BINARY): $(OLSR_DIR)/.unpacked
	$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR=$(STAGING_DIR) -C$(OLSR_DIR)
olsrd $(OLSR_PLUGINS)



-- 
Best Regards,
Ulf Samuelsson

  reply	other threads:[~2007-10-18 23:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 13:12 [Buildroot] Ignored patches - WHY? Sushi Sensei
2007-10-18 13:25 ` Ulf Samuelsson
2007-10-18 15:25 ` Kuten Ivan
2007-10-18 13:31   ` Ulf Samuelsson
2007-10-18 13:47     ` Sushi Sensei
2007-10-18 18:04       ` Erik Andersen
2007-10-18 19:12         ` Ivan Kuten
2007-10-18 18:12           ` Sushi Sensei
2007-10-18 22:21 ` Ivan Kuten
     [not found]   ` <4717DAC8.5050209@gmail.com>
2007-10-18 23:36     ` Ivan Kuten
2007-10-18 23:47       ` Ulf Samuelsson [this message]
2007-10-18 22:44 ` Ivan Kuten
2007-10-18 23:02   ` Ivan Kuten
2007-10-18 22:10     ` Rex Luscus

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=1192751266.5848.7.camel@c-f97ee255 \
    --to=ulf@atmel.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