All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco d'Itri <md@linux.it>
To: Jakub Wilk <jwilk@debian.org>, 766811@bugs.debian.org
Cc: Nathan Scott <nathans@debian.org>
Subject: Bug#766811: spurious library links
Date: Wed, 10 Feb 2016 04:17:03 +0100	[thread overview]
Message-ID: <20160210031703.GA28092@bongo.bofh.it> (raw)
In-Reply-To: <20160206132241.GA2869@jwilk.net>


[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]

On Feb 06, Jakub Wilk <jwilk@debian.org> wrote:

> AFAICS this is the code responsible for creating /lib/libfoo <->
> /usr/lib/libfoo symlinks (see include/buildmacros:79):
> 
> if [ "x$(shell readlink -f $(PKG_LIB_DIR))" != \
>     "x$(shell readlink -f $(PKG_ROOT_LIB_DIR))" ]; then \
>        ../$(INSTALL) -S $(PKG_LIB_DIR)/$(LIBNAME).a $(PKG_ROOT_LIB_DIR)/$(LIBNAME).a; \
>        ../$(INSTALL) -S $(PKG_LIB_DIR)/$(LIBNAME).la $(PKG_ROOT_LIB_DIR)/$(LIBNAME).la; \
>        ../$(INSTALL) -S $(PKG_ROOT_LIB_DIR)/$(LIBNAME).so $(PKG_LIB_DIR)/$(LIBNAME).so; \
> fi

Right. Nathan, this code path is not used on Red Hat and SuSE, which 
already implemented a merged /usr, and it has always been wrong on 
Debian: I think it should just be removed from the upstream package.
Should I NMU?

-- 
ciao,
Marco

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 648 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-02-10  3:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1coxuK-000ALN-Uw@fasolo.debian.org>
2014-10-26  0:48 ` Bug#766811: spurious library links Marco d'Itri
2016-01-04  4:41   ` Marco d'Itri
2016-01-24 15:13   ` Jakub Wilk
2016-02-06  0:58     ` Marco d'Itri
2016-02-06 13:22       ` Jakub Wilk
2016-02-10  3:17         ` Marco d'Itri [this message]
2016-02-10  3:20           ` Nathan Scott
2017-03-16 16:28             ` Michael Biebl
     [not found]               ` <CAFMei7NSLSmONCC6AT1hbyLi18e4MWkYwt9pjqBrWACBEa+AfA@mail.gmail.com>
2017-03-17 14:32                 ` Michael Biebl
     [not found]                   ` <CAFMei7Obi6WV2+RW4kccQn7zyqMZZcm7WtSAKt6D2a-VKH0cDA@mail.gmail.com>
2017-03-17 20:42                     ` Michael Biebl
2017-03-17 19:54   ` Bug#766811: marked as done (spurious library links) Debian Bug Tracking System
     [not found] ` <148691383691.1180.7344036562989980417.reportbug@9c82cf89c040>
2017-03-17 19:54   ` Bug#854961: marked as done (xfslibs-dev won't install in Docker image (where /lib -> /usr/lib)) Debian Bug Tracking System
     [not found] ` <8737edpeu4.fsf@linaro.org>
2017-03-17 19:54   ` Bug#857932: marked as done (xfslibs-dev:ppc64el Fails to install on multi-arch setup with merged /usr) Debian Bug Tracking System

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=20160210031703.GA28092@bongo.bofh.it \
    --to=md@linux.it \
    --cc=766811@bugs.debian.org \
    --cc=jwilk@debian.org \
    --cc=nathans@debian.org \
    /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.