Installing CentOS7 NodeJS source compilation / v12.16.1 LTS

0. Installation environment (g ++ 6.3.x)

CentOS 7 has gcc version 4.8 installed by default. However, nodejs build environment requires version 6.3 or higher.
Please refer to the following link to install version 6.3.

 
Installing CentOS7 GCC 6.x devtoolset-6
Installing CentOS7 GCC 6.x Installing GCC on CentOS 7 will install version 4.8.5. In some cases, you may need to install a higher version. The following is how to install GCC, G ++ 6.x version. $ sudo yum install ..
lucidmaj7.tistory.com

 

1. Download NodeJS source

Connect to the NodeJS homepage and download the source of the LTS version using the wget command.

 
Download | Node.js
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
nodejs.org

[root@localhost ~]# wget https://nodejs.org/dist/v12.16.1/node-v12.16.1.tar.gz

2. Decompression

Unzip the source compressed file received as tar.gz.
[root@localhost ~]# tar xfz node-v12.16.1.tar.gz
You can see that the node-v12.16.1 folder is created. The contents of the file in the extracted folder are as follows.

3. configure


Run configure in the unzipped folder of nodejs.
[root@localhost node-v12.16.1]# ./configure

4. make

After running configure, run the make command to compile.
# make
Depending on the performance of your computer, it may take a very long time, so wait until it is over.
Compiling.
Build complete

5. make install

When the build is complete, install it in the installation path using the make install command.
# make install

6. Command confirmation

When install is complete, you can run npm and node commands as follows to view version information.

Comments

Post a Comment

Popular posts from this blog

Enabling Com Port on Hyper-V 2nd Generation VM / Windbg

Image
To test the UEFI boot environment, I created a second generation virtual machine in Hyper-V. And I had to configure the Com port to attach the kernel debugger.  However, the Com Port device was not visible in the 2nd generation Hyper-V VM.  Invisible Com port device Hyper-V 2nd generation VM must be assigned a pipe to the Com port to be visible in the device list. 1. VM termination First, shut down the VM before working. 2. Run as Powrshell administrator Detailed configuration of Hyper-V VM can be done through Powershell command.  Run Powershell with administrator privileges.  3. set-vmcomport  Run the following command to activate the com port. set -vmcomport -vmname [VM이름] -number [COM포트번호] [파이프이름] To check the COM port to which the pipe is assigned, execute the following command. get -vmcomport -vmname [VM이름] The following is an example of command execution.  https://docs.microsoft.com/en-us/powershell/module/hyper-v/set-vmcomport?view=win10-ps
Read more

DLL Injection using CreateRemoteThread in Windows 10

Image
DLL Injection using CreateRemoteThread One of the methods of DLL injection is to create a RemoteThread and load the desired DLL into the target process.  This is one of the simplest and most widely used methods.  CreateRemoteThread You can create a thread in another process using the API. CreateRemoteThread If you browse on MSDN, you'll see the following in Remarks: https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createremotethread   CreateRemoteThread function (processthreadsapi.h)-Win32 apps Creates a thread that runs in the virtual address space of another process. docs.microsoft.com Terminal Services isolates each terminal session by design.  Therefore,  CreateRemoteThread  fails if the target process is in a different session than the calling process. In translation, Terminal Services Pros say that if the target process is running in a different session, it will fail because the session is specified and executed
Read more

Using Overlapped I / O in DeviceIoControl

Image
Using Overlapped I / O in DeviceIoControl Various methods can be used, such as  synchronizing with events and continuously receiving events through polling, to monitor the frequent events in the kernel driver one by one in user mode  . Scenario in question Imagine that you continue to receive events with relatively simple polling.  The kernel driver queues the event that occurred, and the user mode application issues the IOCTL to retrieve the contents of the queue.  In this type of logic, the user-mode application will  While execute the same loop as  DeviceIoControl and will continue to communicate with the driver by calling. while ( true ) { BOOL ret = DeviceIoControl(hDevice, IOCTL_RECV, &data, sizeof (DATA), 0 , 0 ,&dwReturn, NULL ); if (ret) { // 처리.. } } DeviceIoControl Blocking 발생 In the previously used logic,  DeviceIoControl blocking occurs  until an event occurs in the kernel driver  .  DeviceIoControl Blocking occurs in the user m
Read more