Icecat on Pine H64
#7
[/quote]

gotcha. I didn't catch you had a pre-built package. preamble - I only slightly understand all this but the ldconfig is the related program in linux. run "man ldconfig" if you want to know more.

When you build software you can statically or dynamically link the libraries it uses.  At run-time dynamically linked builds have to go searching the system for libraries and if it doesn't know where to get the libraries it obviously won't find them.

to get around this you can set the LD_LIBRARY_PATH system variable and run the program in the same line.  Something like:
Code:
LD_LIBRARY_PATH=/path/to/you/libs ./icecat
 
But Linus will tell you that is a bad practice.  You should learn and understand how ldconfig does the magic bits.... I'll let you know when I fully grok that too. lol.
[/quote]

Eminently comprehensible - thank you! Just to check my understanding: so the “guix install icecat” build method I had initially been trying was a dynamically linked build but could be made statically linked with the “LD_LIBRARY_PATH” approach you suggested? In any case, that would only be useful on a box with sufficient memory resources for me to (cross)compile Firefox*. I had no idea you could run such a static link argument in the same line as a run command for a prebuilt package, I might just give it a try if no other suggestions arise - as you say, Linus would say it’s bad practice, and I’d like to be able to approach this from as good a practice as possible lol.

*In a duplicate of my first post, @wibble suggests cross-compiling on a box with more RAM.

Other than probably being less lazy, what is the benefit of learning how ldconfig works behind the scenes over using ldconfig itself in the manner you describe? Would it risk breaking backwards compatibility/something else, whereas deploying select commands that it performs behind the scenes wouldn’t?

Next question: does ensuring that one has libstdc++.so.6 and libc.so.6 installed somewhere on the system automatically mean that the relevant GLIBCXX and GLIBC versions are also installed? Is there a way to check this, or install them if they’re missing? Despite my searches, I haven’t yet understood which of those versions apply to which point releases of the libstdc++6 and libc6 libraries :S
  Reply


Messages In This Thread
Icecat on Pine H64 - by armuser97 - 08-04-2021, 02:24 PM
RE: Icecat on Pine H64 - by rgreen - 08-13-2021, 01:35 PM
RE: Icecat on Pine H64 - by 3460p - 03-17-2022, 11:28 AM
RE: Icecat on Pine H64 - by rgreen - 03-18-2022, 10:25 AM
RE: Icecat on Pine H64 - by 3460p - 03-18-2022, 12:03 PM
RE: Icecat on Pine H64 - by rgreen - 03-18-2022, 01:22 PM
RE: Icecat on Pine H64 - by 3460p - 03-19-2022, 11:50 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
  DietPi OS for PINE H64 MichaIng 0 3,803 12-16-2020, 07:22 AM
Last Post: MichaIng
  LibreELEC testing image for Pine H64 Luke 7 8,301 06-12-2020, 02:38 AM
Last Post: p1x3l3d
  Some test PINE H64 “Model B”-3GB, please! stslit 1 2,549 08-25-2019, 12:41 PM
Last Post: stslit

Forum Jump:


Users browsing this thread: 1 Guest(s)