I tried to reconfigure my local to en_CA using dpkg-reconfigure
locales and it's going better but still failing.
I have to install libzip-dev which was not listed in the README.
With libzip-dev and the local changed, it's making way more but it's
failing at this:
[exec]
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libtool:
3212:
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libtool:
install_prog+=cp: not found
and
[exec]
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libtool:
3232:
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libtool:
files+=
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libhadoop.la:
not found
I have libtool in this folder, so I'm not sure what is missing now.
libhadoop.la also is thereé
jmspaggi@buldo:~/bigtop-0.3.0-incubating$ ll
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libhadoop.la
-rw-r--r-- 1 jmspaggi jmspaggi 1018 Feb 13 11:58
/home/jmspaggi/bigtop-0.3.0-incubating/output/hadoop/hadoop-1.0.1/build/native/Linux-amd64-64/libhadoop.la
Regarding 1.0.1 vs 1.0.3, I understand why it's trying to use 1.0.1.
Should BigTop try to get 1.0.1 from another location? Or should it try
to get 1.0.2, then 1.0.3 and so on, if the previous one is not
available?
JM
2013/2/12, Roman Shaposhnik <[email protected]>:
> On Tue, Feb 12, 2013 at 7:10 AM, Jean-Marc Spaggiari
> <[email protected]> wrote:
>> @Bruno: I think also that it's the issue. If I have time I will give
>> it a try and change the local...
>
> Please do let us know what happens. Better yet, could you please
> create a JIRA and record your experience over there? That way
> we can benefit from it some time down the road.
>
>> @Doug: I don't see version 1.1.0 anywhere :( It's all 1.0.x... x
>> beeing 1 for BigTop, but 4 for the last hadoop release.
>> @Mark: Exact. It's trying to take a version which doesn't exist. Maybe
>> the script should try to retreive the most recent 1.0.x version
>> instead of a fixed one?
>
> Bigtop releases guarantee a certain bill of materials -- in that we can't
> retroactively change the source of the bits. We can, however, provide
> those fixes in the branch-0.3. -- send us a patch!
>
> Thanks,
> Roman.
>
