Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Properly setting up hotplug
Date: Wed, 22 Apr 2009 10:52:56 +0200	[thread overview]
Message-ID: <87hc0hoys7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <E8FBAEC0D1A8452EA1A58E35916B04E6@apexjs> (Sagaert Johan's message of "Sat\, 18 Apr 2009 12\:10\:53 +0200")

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

Hi,

 Sagaert> 1) libssp issue

 Sagaert> I started of with a clean build again to do the check:

 Sagaert> I enabled the packages openssh ,openssl

 Sagaert> After building the libssp.so.0,libssp.so.0.0.0 and libssp.so are under
 Sagaert> build_arm/stagingdir/usr/arm-linux-uclibc/lib
 Sagaert> But they are NOT insite the project_build_arm/.../root

 Sagaert> Generating RSA Key...
 Sagaert> /usr/bin/ssh-keygen: can't load library 'libssp.so.0'
 Sagaert> Generating DSA Key...
 Sagaert> THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!

 Sagaert> /usr/bin/ssh-keygen: can't load library 'libssp.so.0'

That's not really an issue with openssh as such, but the fact that we
used to compile gcc with --enable-libssp and NOT install the libs in
the target. It should be fixed in r26182 - r26183.

 Sagaert> 2) dbus

 Sagaert> After distclean the build_arm directoory gets cleaned,but
 Sagaert> the autotools-stamps not, As a result dbus get build again
 Sagaert> but never installed again.(this may apply to others too)

Hmm.. distclean removes toolchain_build_arch, build_arch,
project_build_arch and binaries, so this I don't get. Are you talking
about the dbus-clean / dbus-dirclean make targets instead?

 Sagaert> 3) .. /root/var

 Sagaert> I always remove the var directory and replace it with a
 Sagaert> symlink to /tmp/ I then create the required directory
 Sagaert> structure (var lock, etc) in init.d/ S00mktmp Doing so
 Sagaert> results in var been actually on tmpfs, this avoids that my
 Sagaert> flash gets written.

Yes, that's pretty similar to what the generic target does (/var is on
rootfs, but the subdirs cache, lock, log, pcmcia, run, spool, tmp are
all symlinks to /tmp.

 Sagaert> Maybe this is something to consider making this configurable.

 Sagaert> (for the same reason i have put a symplink /etc/resolv.conf
 Sagaert> pointing to /tmp/ resolv.conf )

Same for the generic target.

-- 
Bye, Peter Korsgaard

       reply	other threads:[~2009-04-22  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E8FBAEC0D1A8452EA1A58E35916B04E6@apexjs>
2009-04-22  8:52 ` Peter Korsgaard [this message]
2009-04-17  8:33 [Buildroot] Properly setting up hotplug Sagaert Johan
2009-04-17  8:52 ` Thiago A. Corrêa
2009-04-17 13:56   ` Peter Korsgaard
2009-04-17 14:19     ` Lloyd Sargent
2009-04-17 13:36 ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-04-14 17:33 Dan Lyke
2009-04-15 18:01 ` Peter Korsgaard
2009-04-16  7:10   ` Thomas Petazzoni
2009-04-16 17:59     ` Peter Korsgaard
2009-04-17  0:42       ` Hamish Moffatt
2009-04-17  5:20         ` Peter Korsgaard
2009-04-17 14:19         ` Dan Lyke

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=87hc0hoys7.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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