Welcome to the Linux Foundation Forum!

HTTP/2 on cPanel/WHM with EA4

Posts: 4
edited January 2017 in Software

Trying to install, or enable http/2 on WHM but getting stuck. Using below tutorial.


  1. #Prep work
  2. mkdir /root/rpmbuild
  3. cd /root/rpmbuild
  4. yum -y install rpm-build
  5. mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
  6. echo ‘%_topdir %(echo $HOME)/rpmbuild > ~/.rpmmacros
  7. #openssl depend
  8. yum -y install perl-WWW-Curl
  9. #apr depend
  10. yum -y install lksctp-tools-devel
  11. #apache depend
  12. yum -y install xmlto lua-devel ea-apr-devel ea-apr-util-devel
  13. yum -y install createrepo
  14. mkdir /root/repo
  15. nano /etc/yum.repos.d/local.repo
  16. [local]
  17. name=CentOS-$releasever local packages
  18. baseurl=file:///root/repo
  19. enabled=1
  20. gpgcheck=0
  21. protect=1
  22. cost=20
  23. priority=1
  24. #Grab crap
  25. cd /root/rpmbuild
  26. mkdir poop
  27. git clone https://github.com/Cacasapo/ea-apache2-http2.git poop
  28. mv -n poop/SOURCES/find.pl /usr/lib64/perl5
  29. \cp -R poop/SPECS/* SPECS/
  30. \cp -R poop/SOURCES/* SOURCES/
  31. rm -fr poop
  32. #OpenSSL
  33. rpmbuild -ba SPECS/openssl.spec
  34. \cp RPMS/x86_64/openssl-parallel* ../repo
  35. createrepo /root/repo
  36. yum clean expire-cache
  37. yum -y install openssl-parallel
  38. #Do nghttp2
  39. rpmbuild -ba SPECS/nghttp2.spec
  40. \cp RPMS/x86_64/libng* ../repo
  41. \cp RPMS/x86_64/nghttp* ../repo
  42. createrepo /root/repo
  43. yum clean expire-cache
  44. yum -y install libnghttp2-devel
  45. #Do apache
  46. rpmbuild -ba SPECS/ea-apache24.spec
  47. \cp RPMS/x86_64/ea-apache24* ../repo
  48. createrepo /root/repo
  49. yum clean expire-cache
  50. yum -y install ea-apache24

Stuck on this line:

rpmbuild -ba SPECS/nghttp2.spec


  1. /usr/lib64/libssl.so.10: error adding symbols: DSO missing from command line
  2. collect2: error: ld returned 1 exit status
  3. make[2]: *** [libevent-client] Error 1
  4. make[2]: *** Waiting for unfinished jobs....
  5. libtool: link: gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -Wl,-z -Wl,relro -o .libs/client client.o -pthread ../lib/.libs/libnghttp2.so ../third-party/.libs/libhttp-parser.a -levent_openssl -levent -L/opt/ssl/lib -ldl -pthread
  6. /usr/bin/ld: client.o: undefined reference to symbol 'SSL_get_error@@libssl.so.10'
  7. /usr/lib64/libssl.so.10: error adding symbols: DSO missing from command line
  8. collect2: error: ld returned 1 exit status
  9. make[2]: *** [client] Error 1
  10. libtool: link: gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -Wl,-z -Wl,relro -o .libs/libevent-server libevent-server.o -pthread ../lib/.libs/libnghttp2.so ../third-party/.libs/libhttp-parser.a -levent_openssl -levent -L/opt/ssl/lib -ldl -pthread
  11. /usr/bin/ld: libevent-server.o: undefined reference to symbol 'SSL_CTX_free@@libssl.so.10'
  12. /usr/lib64/libssl.so.10: error adding symbols: DSO missing from command line
  13. collect2: error: ld returned 1 exit status
  14. make[2]: *** [libevent-server] Error 1
  15. libtool: link: gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -Wl,-z -Wl,relro -o .libs/tiny-nghttpd tiny-nghttpd.o -pthread ../lib/.libs/libnghttp2.so ../third-party/.libs/libhttp-parser.a -levent_openssl -levent -L/opt/ssl/lib -ldl -pthread
  16. make[2]: Leaving directory `/root/rpmbuild/BUILD/nghttp2-1.17.0/examples'
  17. make[1]: *** [all-recursive] Error 1
  18. make[1]: Leaving directory `/root/rpmbuild/BUILD/nghttp2-1.17.0'
  19. make: *** [all] Error 2
  20. error: Bad exit status from /var/tmp/rpm-tmp.TZCKCT (%build)
  21. RPM build errors:
  22. Bad exit status from /var/tmp/rpm-tmp.TZCKCT (%build)

 

Comments

  • Posts: 777
    edited January 2017

    All we see is a bunch of commands. First, help us understand what is it you are trying to do and why. 

    1. What is the goal you are trying to get to
    2. How did you plan on getting there
    3. What tools were you planning on using
    4. What documentations did you read

    If you can give of these details, we can better understand your intentions and the problem.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training