From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Bizarre things on the allyespackageconfig build
Date: Fri, 10 May 2013 18:53:56 +0200 [thread overview]
Message-ID: <20130510165356.GA19822@free.fr> (raw)
In-Reply-To: <20130510175133.13d3fc6f@skate>
Thomas, All,
On 2013-05-10 17:51 +0200, Thomas Petazzoni spake thusly:
> Following the allyespackageconfig, I did explore the generated
> output/target filesystem, and noticed a number of bizarre things that
> probably should be fixed:
[--SNIP--]
> * There is a usr/arm-buildroot-linux-gnueabi directory, which contains
> just a 'bin' subdirectory, which contains ar, as, ld, nm, etc.
>
> $ ls usr/arm-buildroot-linux-gnueabi/bin/
> ar as ld ld.bfd nm objcopy objdump ranlib strip
>
> That's a strange installation location for binutils.
These should be hard-links to their fully-qualified counterparts in
/usr/bin:
arm-buildroot-linux-gnueabi-{ar,as,ld,ld,bfd,nm,objcopy,ranlib,strip}
That's typical of a binutils installation.
[--SNIP--]
> * There a bunch of libraries that don't have the executable bit set in
> usr/lib. I don't think it's a big problem, but it makes them
> different from the others.
Shared libraries do not need to be executable, except the dynamic linker
ld.so which is both a progrm and a library.
Also, libc.so from {,e}glibc is also executable, but not he libc.so from
uClibc.
I think it is not a problem per-se, and I think shared libraries should
not be executable at all.
> * Some packages seem to confuse /var with /usr/var: cups, netatalk,
> squid, polkit-1, vtund, stunnel. Here's what I have in usr/var/ :
[--SNIP--]
Two options here:
- ./configure --localstatedir=/var
Some packages do set it in their .mk, eg. (=/var unless specified):
avahi, sed, directfb, NM, lighttpd, dhcp (=/var/lib/dhcp),
php, oprofile, xserver_xorg-server, samba, dbus, collectd,
proftpd (=/var/run), sqlite, bind, dbus-glib, ndisc6, sql_net,
sqlcipher, connman, pulseaudio
Probably usefull to set it in the pkg-infra?
[--SNIP--]
> * usr/share represents 428 MB, which includes 121 MB of locales (I
> didn't select the removal of locales in my configuration)
Not a problem if locales where not /disabled/ in your config.
> If people are interested in fixing some of those issues, reply to this
> e-mail saying which issue you're going to have a look at.
I'll look at the /var issue.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-05-10 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 15:51 [Buildroot] Bizarre things on the allyespackageconfig build Thomas Petazzoni
2013-05-10 16:53 ` Yann E. MORIN [this message]
2013-05-10 20:58 ` Thomas Petazzoni
2013-05-10 22:27 ` Yann E. MORIN
2013-05-11 10:31 ` Thomas Petazzoni
2013-05-12 17:29 ` Yann E. MORIN
2013-05-12 19:38 ` Peter Korsgaard
2013-05-10 21:52 ` Arnout Vandecappelle
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=20130510165356.GA19822@free.fr \
--to=yann.morin.1998@free.fr \
--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