4 ms·
So you build glibc and GCC with the CentOS supplied gcc in something like ~/opt then used that to build Chrome? I'll bet there was some fiddling and well done.
by 2b3a51 4y ago
So you build glibc and GCC with the CentOS supplied gcc in something like ~/opt then used that to build Chrome?
I'll bet there was some fiddling and well done.
Just wondering what version of CentOS, i.e. how old the Xorg and GTK stuff was.
- boomboomsubban 4y agoScientific Linux shipped with some ancient stuff, like they moved to GTK 3 in 2020. https://distrowatch.com/table.php?distribution=scientific https://distrowatch.com/table.php?distribution=scientific
- captainmuon 4y agoThat must have been around 2011, 2012. I don't know which CentOS version it was. It was the current supported version, so not ancient, but not exactly bleeding edge. The problem was that closed source stuff like Chrome didn't work because they only considered Ubuntu and maybe Fedora? You had to build glibc and GCC in unison, and building them is always difficult, especially the first time. But once I figured out the steps (configure, make, ...) it was easy. The only fiddling was to get all the executables to use "rpath=$ORIGIN" so I could just pop it in my home directory and it would reference the correct variables. I didn't build Chrome (I'm not that crazy), in fact the above was done so I could avoid building Chrome and just run a Chrom(ium) binary. I think the main reason for this ordeal was to be able to run Flash :-D but I also learned a bit about GCC and so on.