Ben Tullis created BIGTOP-3720:
----------------------------------
Summary: Build failure for Hadoop to 2.10.2 in branch-1.5
Key: BIGTOP-3720
URL: https://issues.apache.org/jira/browse/BIGTOP-3720
Project: Bigtop
Issue Type: Bug
Components: hadoop
Affects Versions: 1.5.0
Reporter: Ben Tullis
Hello,
We're attempting to build bigtop packages for Hadoop version 2.10.2 on Debian
11 and we're currently facing a linker error.
I've initially created a `1.5.0-debian-11` build slave by updating
`bigtop_toolchain/bin/puppetize.sh` in the bigtop-1.5 branch, as per the master
branch.
```
diff --git a/bigtop_toolchain/bin/puppetize.sh
b/bigtop_toolchain/bin/puppetize.sh
index e13fde07..11334ad7 100755
— a/bigtop_toolchain/bin/puppetize.sh
+++ b/bigtop_toolchain/bin/puppetize.sh
@@ {-}42,7 +42,7 @@ case ${ID}{-}${VERSION_ID} in
apt-get update
apt-get -y install wget curl sudo unzip puppet
puppet-module-puppetlabs-apt puppet-module-puppetlabs-stdlib systemd-sysv
;;
- debian-10*)
+ debian-10*|debian-11*)
apt-get update
apt-get -y install wget curl sudo unzip puppet
puppet-module-puppetlabs-apt puppet-module-puppetlabs-stdlib systemd-sysv gnupg
procps
;;
```
I've also updated bigtop-packages/src/deb/hadoop/rules#L59 and replaced
`${PWD}` with `$(CURDIR)` as per
[https://github.com/apache/bigtop/pull/906#issuecomment-1172977748]
I've then created my build slave with:
```
cd docker/bigtop-puppet
./build.sh 1.5.0-debian-11
cd ../bigtop-toolchain
sudo ./build.sh 1.5.0-debian-11
cd ../
```
I then build my packages with:
```
docker run --rm -v `pwd`:/ws --workdir /ws bigtop/slaves:1.5.0-debian-11 bash
-c '. /etc/profile.d/bigtop.sh; ./gradlew allclean hadoop-deb'
```
The error I get seems to be from linking fuse-dfs.
```
[WARNING] collect2: error: ld returned 1 exit status
[WARNING] make[4]: ***
[main/native/fuse-dfs/CMakeFiles/fuse_dfs.dir/build.make:496:
main/native/fuse-dfs/fuse_dfs] Error 1
[WARNING] make[3]: *** [CMakeFiles/Makefile2:501:
main/native/fuse-dfs/CMakeFiles/fuse_dfs.dir/all] Error 2
[WARNING] make[2]: *** [Makefile:114: all] Error 2
```
Any help to resolve this would be much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
