René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"how the official linux binary is built?","articleBody":"Version: 6.11.5\r\nPlatform: Linux fcdev 4.13.13-300.fc27.x86_64 #1 SMP Wed Nov 15 15:47:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux\r\n\r\nI am trying to build nodejs binary on a Fedora 27 host, using --fully-static, because my target host is Fedora Core 6. This is how I build:\r\n\r\n./configure --fully-static\r\nmake -j\r\n\r\nThe compile/link would go thru and generate a node binary, with some warnings similar to the one below:\r\n\r\ndso_dlfcn.c:(.text+0x12): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking\r\n/home/syen/src/node-v6.11.5/out/Release/obj.target/node/src/node.o: In function `node::InitGroups(v8::FunctionCallbackInfov8::Value const&)':\r\n\r\nBut I could run this node binary just fine on the Fedora 27 build host. But when I copy node binary to my target Fedora 6 host and run it, it would segment fault immediately without even get to the \">\" prompt.\r\n\r\nThe weird thing is, the official linux binary from nodejs.org site would have no problem running on my target Fedora 6 host. I can get a \">\" prompt, and I can execute my javascript with this binary.\r\n\r\nSo, my questions:\r\n\r\n1. how is the official node binary for linux built?\r\n2. why my \"--fully-static\" binary build would still generate some binary that will reference a shared glibc library?\r\n\r\nI've looked up and down on nodejs website and I couldn't find any documentation on how the official binary was built...\r\n","author":{"url":"https://github.com/shyhpei","@type":"Person","name":"shyhpei"},"datePublished":"2017-12-25T06:22:44Z","url":"https://github.com/nodejs/help/issues/1039"}