From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jon Ander Hernandez <jonan.h-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Debian multiarch support
Date: Thu, 19 Apr 2012 12:15:23 +0200 [thread overview]
Message-ID: <4F8FE5BB.6060705@redhat.com> (raw)
In-Reply-To: <CAGEveXqScm9T-cto8jRYh2_dM6Md+grqppXs0nWTjB_Vo69zMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 16.04.2012 11:34, schrieb Jon Ander Hernandez:
> Hello,
>
> Before considering my patch I should note that it has a bug, it should be:
>
> # Detect lib paths
> [[ $libdir ]] || for libdir in /lib64 /lib; do
> - [[ -d $libdir ]] && break
> + [[ -d $libdir ]] && libdirs+=" $libdir" && break
> done || {
> dfatal 'No lib directory?!!!'
> exit 1
> }
>
> [[ $usrlibdir ]] || for usrlibdir in /usr/lib64 /usr/lib; do
> - [[ -d $usrlibdir ]] && break
> + [[ -d $usrlibdir ]] && libdirs+=" $usrlibdir" && break
> done || dwarn 'No usr/lib directory!'
>
> Now there is a space before $libdir and $usrlibdir, which avoids
> suffixing the libdirs value defined on a *.conf file with $libdir. I'm
> sorry.
>
> Regards,
>
> JonAn.
pushed
prev parent reply other threads:[~2012-04-19 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 10:45 Debian multiarch support Jon Ander Hernandez
[not found] ` <CAGEveXprJz33cnna8PDQE7eyNUw1S-RDYtyZY405STOH7FfswA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 13:14 ` Jon Ander Hernandez
[not found] ` <CAGEveXr7G+5_rcuHUWBrg-rAQ1y6wU2ozVy2yBbQuo3PYdx3Mw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-16 9:34 ` Jon Ander Hernandez
[not found] ` <CAGEveXqScm9T-cto8jRYh2_dM6Md+grqppXs0nWTjB_Vo69zMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-19 10:15 ` Harald Hoyer [this message]
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=4F8FE5BB.6060705@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jonan.h-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox