I have a shared object built on 32 bit SuSE Linux. It loads and runs fine on 40
bit Red Hat Enterprise Linux. If I pass it to g++ to link with, though, I get:
/path/name.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
Running g++ under strace didn't make this more clear. nm reads symbols fine.
objdump --syms --dynamic-syms is happy, and so is nm.
So what does "invalid operation" mean, besides the very act of running g++ under
RHEL?
P.S. "gcc is not the operating system" is as valuable an observation in this
context as "the barrel is not the gun".
P.P.S. why does RHEL (or RHEL's tcsh, or some other sub-sucker of a larger
sucker) lists terminated jobs after the command following a kill command, and
not when they are actually terminated?
P.P.P.S. why is tcsh located in different places in SuSE and RHEL? I'm not
saying that one of the locations is right, just that, um, I don't /understand/
the person that saw the stupid program located in some stupid place and said
"hmmm, I know a MUCH BETTER place!". What makes a human move a shell?
