| Summary: | libtool fails to recognize the echo command | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bruno Mahe <bruno.mahe> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bruno.mahe, cjw, fundawang, mageia, marja11 |
| Version: | 1 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | libtool-2.4-3 | CVE: | |
| Status comment: | |||
|
Description
Bruno Mahe
2011-10-20 20:44:56 CEST
Bruno Mahe
2011-10-20 20:45:12 CEST
CC:
(none) =>
bruno.mahe Thanks for your bug report. We don't have a maintainer for libtools, atm, but we have a newer version of libtools in cauldron and expect that to go into Mga 2 stable. CC'ing some committers of libtools CC:
(none) =>
cjw, fundawang, mageia, marja11 (In reply to comment #1) > Thanks for your bug report. > > We don't have a maintainer for libtools, atm, but we have a newer version of > libtools in cauldron and expect that to go into Mga 2 stable. > > CC'ing some committers of libtools s /libtools /libtool Looks like you have some old libtool files using $echo in the tarball: $ LC_ALL=C ls -lh $(grep -rl \$echo ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/) -rwxr-xr-x 1 blino blino 217K Dec 13 22:51 ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/build/native/Linux-amd64-64/libtool* -rw-r--r-- 1 blino blino 426K Dec 13 22:50 ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/src/c++/libhdfs/autom4te.cache/output.0 -rw-r--r-- 1 blino blino 256K Oct 7 08:19 ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/src/native/aclocal.m4 -rw-r--r-- 1 blino blino 196K Oct 7 08:19 ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/src/native/config/ltmain.sh -rw-r--r-- 1 blino blino 728K Oct 7 08:19 ./build/hadoop/rpm/BUILD/hadoop-0.20.205.0/src/native/configure You should run autoreconf. @ Bruno Did you see blino's reply and if so, is this solved now? Keywords:
(none) =>
NEEDINFO Olivier> Marja> Thanks a lot! This is exactly how I worked around it on https://issues.apache.org/jira/browse/BIGTOP-128 So I guess the ticket can be closed. Status:
NEW =>
RESOLVED |