Trying to build coreutils-8.14 fails because libstdbuf.so is installed in
/usr/lib/coreutils instead of /usr/lib64/coreutils, i.e. $libdir seems to be
ignored, which didn't happen in at least 8.12. Is this wad or a glitch and
if the former, why the change in behavior?
Philipp
On Thursday 13 October 2011 11:32:23 Philipp Thomas wrote:
> Trying to build coreutils-8.14 fails because libstdbuf.so is installed in
> /usr/lib/coreutils instead of /usr/lib64/coreutils, i.e. $libdir seems to
> be ignored, which didn't happen in at least 8.12. Is this wad or a glitch
> and if the
On 10/13/2011 04:32 PM, Philipp Thomas wrote:
>
> Trying to build coreutils-8.14 fails because libstdbuf.so is installed in
> /usr/lib/coreutils instead of /usr/lib64/coreutils, i.e. $libdir seems to be
> ignored, which didn't happen in at least 8.12. Is this wad or a glitch and
> if the former, w
Pádraig Brady writes:
> The dir was changed to appease newer automake
>
> http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e23f1795
The change is backwards. A library has no place in a PROGRAMS primary.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58C
* Pádraig Brady (p...@draigbrady.com) [20111013 18:03]:
> On 10/13/2011 04:32 PM, Philipp Thomas wrote:
> Note we don't link against this lib, so is it a package that's
> failing to build, rather than coreutils itself?
Yes sorry, I should have been more precise. I'm working on packaging
coreutils
On Friday 14 October 2011 06:09:09 Philipp Thomas wrote:
> * Pádraig Brady (p...@draigbrady.com) [20111013 18:03]:
> > The dir was changed to appease newer automake
> >
> > http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e23f1795
>
> So it should be as easy as passing "pkglibexecdir=
* Mike Frysinger (vap...@gentoo.org) [20111014 17:29]:
> or --libexecdir when running ./configure
That would work too, but as Andreas already wrote, libstdbuf.so shouldn't be
part of a PROGRAMS primary.
Philipp
On Friday 14 October 2011 11:36:27 Philipp Thomas wrote:
> * Mike Frysinger (vap...@gentoo.org) [20111014 17:29]:
> > or --libexecdir when running ./configure
>
> That would work too, but as Andreas already wrote, libstdbuf.so shouldn't
> be part of a PROGRAMS primary.
i'm not sure how that's rel
Mike Frysinger writes:
> i'm not sure how that's relevant. whether you set the path in configure or
> at
> make install time, you're still forcing all the libexec files to go to the
> same
> path.
libexecdir is not for libraries, so the library shouldn't be placed
there in the first place
On Friday 14 October 2011 13:57:43 Andreas Schwab wrote:
> Mike Frysinger writes:
> > i'm not sure how that's relevant. whether you set the path in configure
> > or at make install time, you're still forcing all the libexec files to
> > go to the same path.
>
> libexecdir is not for libraries, s
* Mike Frysinger (vap...@gentoo.org) [20111014 17:47]:
> i'm not sure how that's relevant.
As libdir *is* set correctly, libstdbuf.so would be installed correctly
without any additional action from my side if it was handled like a library
and not an executable. So we wouldn't have this discussion
11 matches
Mail list logo
