Mail archive

Re: [alpine-devel] Can't build apk-tools

From: Timo Teras <>
Date: Thu, 27 Jun 2013 09:39:17 +0300

On Wed, 26 Jun 2013 17:28:43 -0400
Dubiousjim <> wrote:

> On Tue, Jun 18, 2013 at 08:53:59AM +0300, Timo Teras wrote:
> >
> > How about uclibc-dev? Is that upstream or left broken from older
> > install?
> >
> > The thing is that __stack_chk_fail_local is a special kind of symbol
> > that gcc inserts, and is expected to be linked in with the
> > executable (most _not_ be in a .so). Thus you will not find it
> > in /lib/ (or glibc .so either for that matter).
> >
> > Instead, if you look at "/usr/lib/", it's a linker script
> > telling to link with the real .so and a set of nonshared static
> > objects, with uclibc, namely uclibc_nonshared.a. You should find
> > __stack_chk_fail_local in /usr/lib/uclibc_nonshared.a.
> >
> > You might want to check that /usr/lib/uclibc_nonshared.a
> > and /usr/lib/ come from uclibc-dev matching the libc0.9.32
> > installed. You could try "apk audit --system /usr/lib/*libc*" and/or
> > "apk fix uclibc-dev".
> Thanks for the suggestions with this. I did end up fixing it. It was a
> very idiosyncratic issue that I don't expect others to encounter, but
> just in case: I had manually created a /lib/ ->
> symlink, when I was trying to install/debug cross-compilers on my
> system. I had lost track of that and neglected to remove it. apk audit
> --system didn't report it because it's not a file that apk considers
> owned. I didn't experience total build failures because I guess /lib
> isn't one of the standard locations that gcc looks for libraries, so
> it was just a few buildsystems that included -L/lib which would break,
> because this symlink would shadow the script at /usr/lib/

Ah, that explains it. :)

> While debugging this I noticed a larger issue with apk-tools though:
> for some reason a bunch of files and links get (correctly) reported
> as owned by `apk info -W /path/to/file`, but get (incorrectly)
> reported as unowned (that is, no output and exit code 1) by `apk info
> -e /path/to/file`.
> Just run this to find some:
> find /sbin /bin /lib /usr \! -type d -exec sh -c 'apk info -q -e $1
> \ || { apk info -W $1 2>/dev/null | fgrep -q " is owned by " && \
> echo $1; }' sh {} \;

Not all symlinks are owned. They get owned by a package only if
the .apk file contained the symlink. One notable misuser is busybox,
that uses busybox -s --install via triggers to install it's symlinks.
When you install the utility providing the real command it overwrites
those - and when you remove it, the bb install recreates the symlink
back to bb.

One option would be to read the symlink target and print the owner of
it. Or come up with some kind of 'alternatives' system such as Debian.

> In fact I have a bunch of patches to propose against apk-tools, all of
> them UI-based. I've been using them locally for a while, and now that
> Timo is actively pushing new stuff to the apk-tools tree, I figure I'd
> better rebase them and clean them up and write up a rationale, so that
> you guys can consider them for inclusion in the main tree. I'll send
> those along in the next few days. I'll try to remember to ask again
> about the `apk info -e` then.

Sure. Will be glad to apply those. Most of apk-tools work for now is
done. Planning to tag new release soon.

> I've got a bunch of other little local patches against aports and some
> of the other Alpine repos, that I'll send to the list first, because
> they're easier.
> I realize that dumping a whole bunch of patches to the list at once
> means you guys not be able to look at them all right away. No worries
> on my side.



Received on Thu Jun 27 2013 - 09:39:17 UTC