Rebuilding the Software Package

Procedure

1. Log in to the Kunpeng DevKit. In the navigation tree on the left, choose Porting Advisor > Software Package Rebuild. On the page displayed, click Upload to upload the x86 RPM package to Package Path and upload the required dependencies listed in Table 1 to Dependency File Path. After the upload is complete, click Rebuild to rebuild the software package.
   Figure 1 Uploading the RPM package to be rebuilt
   
   During the rebuild process, the Kunpeng Porting Advisor automatically downloads target JAR packages and uses them to replace existing ones. After all files are replaced, an .aarch64 RPM package is generated. You do not need to manually compile JAR and RPM packages.

   

   In an offline environment, deselect Allow Access to Internet in Figure 1, and then compile and upload the dependency JAR package.

   For snappy-java-1.0.5.jar, see snappy-java-1.0.4.1,1.0.5 Porting Guide.

   For netty-all-4.1.48.Final.jar, see netty-all-4.0.52.Final.jar Porting Guide.

   Big Data documentation: https://www.hikunpeng.com/document/detail/en/kunpengbds/overview/kunpengbds.html

   If the dependency files to be replaced are incomplete, the RPM package fails to be rebuilt and the missing dependency files are displayed in the report. Upload the missing dependency files and rebuild the RPM package again.

2. After the rebuild is complete, the hadoop-hdfs-3.2.2-1.el7.aarch64.rpm package is generated. Click Download Package Rebuilt in the rebuild report to obtain the rebuilt package. Click Download Report to obtain the rebuild task report.
   Figure 2 Downloading the rebuilt package