Thread replies: 7
Thread images: 1
Thread images: 1
File: knowing-1.jpg (51KB, 550x362px) Image search:
[Google]
51KB, 550x362px
Hey /g/,
Cross compiling can be a tricky business. Just because you know the target architecture, it seems unlikely you can cross compile any program without error. What all do you need to know about a machine (architecture)? What are some common pitfalls (memory configuration)? What compiles do you suggest (gcc)?
Background: I am learning about server-side scripting so I can make dynamic webzones. I discover my host doesn't allow me to run a gcc from their /usr/bin/gcc directory for "security reasons". So I have to cross compile. Surprisingly I was able to compile on my machine, and upload the result, but that surprised me. What do I need to know to make about the target machine to properly cross compile?
If this doesn't fit /g/, this can be a general compilers/assemblers thread.
>>
Oh yeah, operating system seems important to know too.
>>
Operating system and architecture should be enough
>>
>>55262432
Do you know if their are any issues with linked libraries? It seems prudent to make stand-alone executables.
>>
Also, last question, how compatible are different version of linux in terms of executable units?
>>
>>55262707
Very. Linux does not break userspace.
Your executable will run on any version of linux released since the most recently added syscall that you use was added.
>>
>>55263101
As long as you don't use something in libstdc++ or glibc that has ABI changes between versions ,':^)
Thread posts: 7
Thread images: 1
Thread images: 1