Ld: fatal: relocation error: R_SPARC_DISP64 error when linking on Solaris 8

Hi,
I get the following error when trying to link on Solaris 8 using Forte CC. This code links without any problems on Solaris 6 using g++. I've tried searching the web for info, but to no avail.
Also, in this ckErrorCode class there are 4 methods(note there are also 4 of these unknown symbols) and when I comment out all the code it links, but I get unresolved symbols later, as you'd expect.
Anyone come across this before?
Thanks in advance,
Chris
CC -c -xarch=v9 -instances=static -g -D_DEBUG -KPIC -mt -DPOSIX_THREADS -D__EXTENSIONS__ -D_POSIX_PTHREAD_SEMANTICS -D_POSIX_C_SOURCE -I../inc -I.. -I../Dev/Source -I../Unsupported ../src/ckErrorCode.cpp -o ../src/ckErrorCode_g.o
CC -xarch=v9 -mt -i -KPIC -G -h ckTester_51g.so -I../inc -I.. -I../Dev/Source -I../Unsupported -o ckTester_51g.so ../src/ckErrorCode_g.o
ld: fatal: relocation error: R_SPARC_DISP64: file ../src/ckErrorCode_g.o: symbol <unknown>: offset 0xffffffff7e500ce4 is non-aligned
ld: fatal: relocation error: R_SPARC_DISP64: file ../src/ckErrorCode_g.o: symbol <unknown>: offset 0xffffffff7e500cf4 is non-aligned
ld: fatal: relocation error: R_SPARC_DISP64: file ../src/ckErrorCode_g.o: symbol <unknown>: offset 0xffffffff7e500d21 is non-aligned
ld: fatal: relocation error: R_SPARC_DISP64: file ../src/ckErrorCode_g.o: symbol <unknown>: offset 0xffffffff7e500d31 is non-aligned
make: *** [ckTester_51g.so] Error 1

Try setting the configure runtime linking environment:
#crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/usr/local/etc/mysql/lib
Shane Kinsch
NetraCorp LLC / SecurNET Consulting

Similar Messages

Ld error under x86 when linking boost serialization

Hi all,
I am trying to compile and link boost serialization project. I am doing this work under two architectures:
- sparc using sunstudio12 libraries and CC version 5.8
- x86 using sunstudio12 libraries and CC version 5.10
Under sparc I can compile the code and generate libserialization.so, release and debug.
However, I can't generate libserialization.so under x86 environment in debug mode (release mode works)
Here are my variables:
CPPFLAGS := -w -g -DDEBUG -KPIC -features=extensions -I.
LDFLAGS := -G -Bsymbolic -Llib/x86/DEBUG -ldl -lm -lrt -lnsl -lsocket -lCstd -lCrun -I.
The link takes about 2 minutes (few sconds under sparc) and ld crash displaying this message and generating a core:
CC: Fatal error in ld: Segmentation Fault (core dumped)
make: *** [home/.../boost/lib/x86/DEBUG/libserialization.so] Error 1
I think ld crashes because I don't have enough space under the swap partition, but why is it works under sparc? and faster?
Thanks for your help,

One difference is debug data is due to the compiler version, not differences between sparc and x86.
C++ 5.8 (in Sun Studio 11) generates debug data in stabs format. C++ 5.10 (in Sun Studio 12u1) generates debug data in dwarf format.
By default, stabs data remains in the .o files and is not copied into the executable program.
But dwarf data is copied into the executable. The program will need more memory when it is being linked, and take up more space on disk. (You can get the same effect with stabs if you link using the -xs option.) The dwarf data in the executable does not affect the amount of memory the running program needs, since it is not loaded into the program address space.
The advantage of putting the debug data in the executable is that you do not need access to the original .o files when debugging the program. With stabs, if you delete or move the .o files, or run the program from a location where the .o files are not visible via the original path, the debugger can't find any debug data.
Dwarf format does not allow omitting the debug data from the program; debugging via debug data in .o files is not an option.

Error message appears when linking one project to another.

I keep having problems linking a captivate project to another project. The projects are saved as .cp files stored in the same folder as all of my other Captivate files. I did publish them to .htm files and it worked.
Why would they not link properly when they are in .cp format? It also gives me a message that states the directory the file is in does not exist. However, I have checked the pathfile name twice and it is correct.
Any ideas what may be happening?

The last Captivate version to use .cp format was Captivate 4. So you must be speaking about version 4 or earlier here?
The .cp format is the source project file, not an output format like HTML/SWF or PDF. You may be accustomed to other software apps like MS Office where the output is the same as the source (DOC, PPT, XLS, etc) but Captivate is a different beast.
There's no point trying to link one Captivate project file to another. What you are probably hoping to do is link the OUTPUT from one Captivate project to the OUTPUT from another project. Is that correct?

Ld.so.1 problem - fatal: relocation error - "referenced symbol not found"

Hi, I've been trying to compile and run my application non Solaris using CC (detils below) but haven't got luck with running the application because of a linker error :
ld.so.1: java: fatal: relocation error: file ./libtest.so: symbol __1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___J__nullref_: referenced symbol not found
Here's what I'm trying to do :
I'm compieing one library to include another shared library whcih uses the "string" class (STL). The compilation of both the libraries proceeds perfectly fine. However, when i preload this library with LD_PRELOAD and run a JAVA application (which will have calls to some function in the preloaded library), the get the above linker error.
Here's what all I have tries to get thsi wroking : ( I understand that this error is due to a missing library that CC has not linked to and i've no idea what the library is!!!)
1.> # LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH
# export LD_LIBRARY_PATH - NO LUCK :-(
2.> linked to /opt/SUNWspro/lib/libCrun.so (found this from another forum on the net), but NO LUCK :-(
3.> export LD_DEBUG=bindings
export LD_DEBUG_OUTPUT=/home/log.txt (so that all sysmbols refered are logged!!!)
i did a grep on the log for the symbol but NO LUCK!!! :-(
Please can you help me with this? What is the library that is to be linked too, or is there something else?
Details About my system, compiler and compilation options :
1.> uname -a output : SunOS sh1sol9 5.9 Generic_117171-12 sun4u sparc SUNW,Sun-Fire-280R Solaris
2.> CC version : Sun WorkShop 6 update 2 C++ 5.3
3.> Compilation flags i've used to build the library :
FIRST LIBRARY : CC -G -xcode=pic32 -I../common/ -ldl ../common/logger.cpp helper_functions.cpp BCPEntries.cpp BCP_class.cpp -o libBCP.so
SECOND LIBRARY : CC -G -xcode=pic32 -I../common/ test_BCP_construct.cpp -lBCP -L. -o libtest.so
Please help me out of this,
Any and every help (or even a hint to it) will be appreciated!!!
Thanks in advance,
Madhur Kumar Tanwani

Refer to the C++ Users Guide that comes with the compiler, the chapter on Building Libraries, which explains these points in more detail.
When you build a C++ shared library, you must explicitly list all the libraries that it depends on. Unlike building an executable, the CC -G command does not by default create dependencies on system libraries. Although not explained well in the Guide, you should be sure you get the shared (.so) versions of all libraries, not the static (.a) versions.
All C++ programs require at least libCrun and libc. Programs that use the C++ Standard library (using anything in the std namespace, like std::string) also need to link to the appropriate version of the library.
The default library is libCstd. If you compile using the optional STLport library, you need the libstlport instead. You cannot use both libCstd and libstlport in the same program.
In your case, the build command would look something like this, assuming you are using the default libCstd:
CC -G -o mylib.so ..... -library=Cstd,Crun -lc
Be sure that any preceeding -Bstaic option is followed by -Bdynamic before listing these system libraries.
To verify you have picked up the dynamic libraries, run the command
ldd mylib.so
to see a list of dependencies. If you don't see the following in the list
/usr/lib/libCstd
/usr/lib/libCrun
/usr/lib/libc (or /lib/libc)
something is wrong.
A note about LD_LIBRARY_PATH: don't use it.
Ideally, the environment variable should never be set. If you must set it to reach vendor-supplied libraries, never put the system directories /lib or /usr/lib on the path, and never put the compiler installation directory, like /opt/SUNWspro/... on the path. You can wind up forcing the runtime loader to seach directories in the wrong order and pick up inappropriate versions of libraries.
For more on LD_LIBRARY_PATH, read this note in Rod Evans' blog. He's the Sun linker expert. The material here is available in the manuals, but his blog has a nice summary.
http://blogs.sun.com/roller/page/rie/?anchor=tt_ld_library_path_tt

Ldopen() failed:ld.s0.1: fatal: relocation error: ..symbol not found

Hi All,
I got the following fatal error when running my application:
dlopen() failed:ld.so.1: delosd: fatal: relocation error: file libwellbuilder.so.1: symbol __1cDstdM__node_alloc4BiA_N_M_deallocate6FpvI_v_: referenced symbol not found
I compile and link with option -library=stlport4,Crun
I check the libwellbuilder.so.1 but don't see stlport lib at all. Not sure in what lib the undefined symbol is defined.
ldd libwellbuilder.so.1
libconfig.so.1 => /mnt/calnas02/home/zik31726/libs/server/libconfig.so.1
liblogging.so.1 => /mnt/calnas02/home/zik31726/libs/server/liblogging.so.1
libtiff.so.1 => (file not found)
libcdm.so.1 => (file not found)
libdelos.so.1 => /mnt/calnas02/home/zik31726/libs/server/libdelos.so.1
libdbaccess.so.1 => (file not found)
libxtiff.so.1 => (file not found)
libsrvutil.so.1 => /mnt/calnas02/home/zik31726/libs/server/libsrvutil.so.1
libdbprovider.so.1 => (file not found)
libsrvnet.so.1 => /mnt/calnas02/home/zik31726/libs/server/libsrvnet.so.1
libloader.so.1 => /mnt/calnas02/home/zik31726/libs/server/libloader.so.1
libiss_conf.so.1 => /mnt/calnas02/home/zik31726/libs/server/libiss_conf.so.1
libCrun.so.1 => /*usr/lib/libCrun.so.1*
libmd5.so.1 => /usr/lib/libmd5.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libc.so.1 => /usr/lib/libc.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Ultra-250/lib/libmd5_psr.so.1
/usr/platform/SUNW,Ultra-250/lib/libc_psr.so.1
My solaris system is as following:
CC -V: CC: Sun C++ 5.8 2005/10/13
uname -a: SunOS dlp001 5.9 Generic_122300-32 sun4u sparc SUNW,Ultra-250System = SunOS
If you know how to resolve this issue, please let me know.
Thanks,
Iceman

Thanks for your quick response.
Here is the compiling line, I cut off some due it exceed 5000 line:
/sw/opt/SUNWspro/bin/CC -KPIC -zdefs -library=stlport4 -library=stlport4,Crun -lm -lc -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.config/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.logging/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.vendor.lib.libtiff/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/nsl/1.1 -I/usr/include/test -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.loader/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.issconf/1.0 -DSunOS=900000 -g -DUNIX -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.config/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.util/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.dbprovider/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.net/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.loader/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.issconf/1.0 -c CurveDigits.cpp -o CurveDigits.cpp_So.o
/usr/ccs/bin/ld -o CurveDigits.So -r CurveDigits.cpp_So.o
/bin/rm CurveDigits.cpp_So.o
And linking line:
/sw/opt/SUNWspro/bin/CC -Bdynamic -G -zdefs -library=stlport4 -library=stlport4,Crun -lm -lc -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.config/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.logging/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.vendor.lib.libtiff/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.loader/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.issconf/1.0 -DSunOS=900000 -g -DUNIX -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.config/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.logging/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.loader/1.0 -I/mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.issconf/1.0 -o libwellbuilder.so.1 -h libwellbuilder.so.1 *.So -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.config/1.0 -lconfig -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.logging/1.0 -llogging -lxtiff -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.util/1.0 -lsrvutil -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.dbprovider/1.0 -ldbprovider -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.net/1.0 -lsrvnet -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.loader/1.0 -lloader -L /mnt/calnas02/home/zik31726/devcm/workspaces/merge_server/inst/SunOS-5.9-sun4u/NativeLibrary/src.server.lib.issconf/1.0 -liss_conf

Ld.so.1: vi: fatal: relocation error: file e: symbol cur_term: referenced

I got this message when i tried to install remedy on Solaris 7. T
ld.so.1: ex: fatal: relocation error: file ex: symbol cur_term: referenced
symbol not found
Killed
Then i took advices from others and set the LD_LIBRARY_PATH to "/usr/openwin/lib:/usr/dt/lib:/usr/ucblib", seemed it worked for others, but i still get the same error messages.
Any1 has any idea how to fix it?
thanks

Then i took advices from others and set the
LD_LIBRARY_PATH to
"/usr/openwin/lib:/usr/dt/lib:/usr/ucblib", seemed it
worked for others, but i still get the same error
messages.A bad advice.
You have a good installation of the OS and other
custom programs when you can run all programs without
LD_LIBRARY_PATH! (Hint: Use the -R linker option when
compiling your own programs)
Remove the LD_LIBRARY_PATH environment variable and vi
starts working again.
(At least remove /usr/ucblib, this directory on the
general ld library path is really bad)

Firefox-bin fatal relocation error libthebes.so symbol round referenced symbol not found

I compiled Firefox 3.6.23 on Solaris 9. When I try to start firefox it exits with the following error.
ld.so.1 firefox-bin: fatal: relocation error: file /usr/local/lib/firefox-3.6.23/components/../libthebes.so: symbol round: referenced symbol not found killed

It is not in the java documentation because it is not a java problem.
When you write JNI code (or any other code for that matter) you probably should look at the documentation for the compilers and other tools that you are using for recommendations for how to use these third party tools.
What would have been surprizing to me, is if your C++ compiler manual did not recommend linking with the standard C++ library when you use code contained in the library. Which was the problem here.

Ld.so.1: java: fatal: relocation error: file :referenced symbol not found

Hello,
I am trying to run my application (using Java) on windows which in turn calls the Remote Manager on Solaris(Solaris 9 on SPARC Processor).
It gives the following linker error:
ApiInitLocal():ApiInitLocal: START
ApiInitLocal():* * * A P I I N I T * * *
ld.so.1: java: fatal: relocation error: file /opt/rm902/remotemanager/soFile/libACEUser.so: symbol Sd_ApiInit: referenced symbol not found
Killed
I tried setting "LD_LIBRARY_PATH" , but that also didnt work.
Any help would be highly appreciated.
Thanks in advance

Hello all
I am new to JNI and while trying to run my
to run my first program I am receiving an error in
compilation of the 'C' file. For ur clarity my taken
steps are given as follows:
a. First I created 'HelloNative.java'
Then I compiled it and after running created the
the HelloNative.h
b. Then I wrote the HelloNative.c file and when I
compile it using MS VC++ then it gives the
following error:
--------------------Configuration: helloNative -
- Win32 Debug--------------------
Compiling...
helloNative.c
f:\bin\hellonative.c(3) : fatal error C1083: Cannot
open include file: 'jni.h': No such file or directory
Error executing cl.exe.
helloNative.obj - 1 error(s), 0 warning(s)
PLZ HELP ME ON THIS.
So for a quick patch, copy the jni.h file from the include
directory of your java installation files to the include
files that your c complirer has and uses.

I was referred to this site when I looked for answers to why I got Fatal Error message with error code c0000005 when trying to upload photos to my computer. I see that someone else asked the same question, 90 people viewed but no answer given?

I was referred to this site when I got Fatal Error message Error code c0000005 while trying to upload photos to computer. Someone else asked the same question in this forum, 90 people viewed the question but it was never answered?

It looks to me like it is a problem on your Windows computer not being able to start an application. See the following link to Microsoft Community support (although the specifics of the problem in that case may not be applicable) and also note all of the "Related Content" at the upper right side of that link (and there may be others if you search that forum). http://answers.microsoft.com/en-us/windows/forum/windows_7-system/the-applicatio n-is-unable-to-start-correctly/bbb9c037-77b3-4fae-93b9-ded70f7f9a17
It may help if you know or can determine which program Windows is trying to open when you upload photos -- there can be many different ones and it can be set by the user. If you are using Windows 7, you may need to check your Autoplay settings. There are some instructions in the following link that may help and that discuss how you can use Windows Explorer to manually transfer the photos: http://support.apple.com/kb/HT4083

Kernel Error: ld.so.1: disp+work: fatal: relocation error

Dear gurus,
We got problem in our Production Server since 28 September 2009.
SAP suggested to update kernel as mentioned in note 561459
But when applying patch kernel on:
SAP R/3 4.6B - SunOS 5.6 - Oracle 8.0.4 by latest kernel patch, we got this error when executing disp+work via console:
#disp+work
ld.so.1: disp+work: fatal: relocation error: file disp+work: symbol __1cG__CrunSregister_exit_code6FpG_v_v_:
referenced symbol not found
can someone help us please?
Thanks for your help.
Best Regards,
Edited by: Bobby Gunawan on Oct 2, 2009 3:17 PM
Edited by: Bobby Gunawan on Oct 2, 2009 3:19 PM

> SAP suggested to update kernel as mentioned in note 561459
So which kernel and patchlevel did you install?
> But when applying patch kernel on:
> SAP R/3 4.6B - SunOS 5.6 - Oracle 8.0.4 by latest kernel patch, we got this error when executing disp+work via console:
>
> #disp+work
>
ld.so.1: disp+work: fatal: relocation error: file disp+work: symbol __1cG__CrunSregister_exit_code6FpG_v_v_:
> referenced symbol not found
wow - your system is really ancient
You have the problem that the C-/C++-Runtime for your patch is not high enough (an operating system patch).
Markus

Ld.so.1: tar: fatal: relocation error: file /usr/sbin/tar: symbol fstatat64

Hi Gurus.
Please help in this one.
When I try to use tar the following output is displayed:
tar cvf 123.tar 123.txt
ld.so.1: tar: fatal: relocation error: file /usr/sbin/tar: symbol fstatat64
tar xvf 123.tar
ld.so.1: tar: fatal: relocation error: file /usr/sbin/tar: symbol fchownat: referenced symbol not found
Killed
Check output ldd:
ldd -r /usr/bin/tar
libcmd.so.1 => /usr/lib/libcmd.so.1
libsec.so.1 => /usr/lib/libsec.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-xxx/lib/libc_psr.so.1
symbol not found: attropen64 (/usr/sbin/tar)
symbol not found: fstatat64 (/usr/sbin/tar)
symbol not found: openat64 (/usr/sbin/tar)
symbol not found: fchownat (/usr/sbin/tar)
symbol not found: unlinkat (/usr/sbin/tar)
symbol not found: futimesat (/usr/sbin/tar)
symbol not found: fdopendir (/usr/sbin/tar)
Output of: LD_LIBRARY_PATH
echo $LD_LIBRARY_PATH
/usr/lib:/usr/dt/lib:/opt/app/lib
already try unset LD_LIBRARY_PATH
Any ideas.
I can tell You that tar was working fine 2 months ago.
I suspect data corruption
Many thanks
Allrounder

Hi,
Is Vi functional on your system? If you havent already tried this you may want to try removing /usr/ucb/lib from LD_LIBRARY_PATH environment variable, or put /usr/lib in LD_LIBRARY_PATH before /usr/ucblib. This might clear up some of the problems you are having.
Regards,
Andrew
Sun Developer Technical Support
I got this message when i tried to install remedy on
Solaris 7. T
ld.so.1: vi: fatal: relocation error: file vi: symbol
cur_term: referenced
symbol not found
Killed
Then i took advices from others and set the
LD_LIBRARY_PATH to
"/usr/openwin/lib:/usr/dt/lib:/usr/ucblib", seemed it
worked for others, but i still get the same error
messages.
Any1 has any idea how to fix it?
thanks

Getting a fatal relocation error while using a sudo command.

I am getting the following error while trying to execute a sudo command:
ld.so.1: sudo: fatal: relocation error: file /usr/local/bin/sudo: symbol closefrom: referenced symbol not found
the sudo version I use is: 1.6.8p9
the SUNWcsu package that contains the ld.so.1 library is version: 11.8.0,REV=2000.01.08.18.12
any ideas?

Just had the same error
ld.so.1: sudo: fatal: libintl.so.8: open failed: No such file or directory
Killed
was solved by adding the Dependances
libintl-3.4.0-sol10-sparc-local.gz Libintl is used with gettext and is needed by a few programs when libintl in not in /usr/lib - installs in /usr/local/lib. The 3.4.0 package number indicates that this provides /usr/local/lib/libintl.so.3.4.0 (and also the new /usr/local/lib/libintl.so.8.0.2). Dependencies: libiconv and to have /usr/local/lib/libgcc_s.so.1 and /usr/local/lib/libstdc++.so.6, either the libgcc-3.4.6 or gcc-3.4.6 packages.
http://www.sunfreeware.com/indexsparc10.html

Fatal:relocation error: While running JDK1.4 on Sun Sparc Generic_106541-08

Hi,
I installed the new jdk1.4 on my Solaris-7 machine. Initially I installed 32-bit jdk1.4 and then installed 64-bit jdk1.4 as indicated on your (sun's) installation page. I used executable binary version of installation for installing the software.
The installation was successfully completed. But while I run java command then it gave following error
Error: failed /export/home/j2sdk1.4.0/jre/lib/sparc/client/libjvm.so, because ld.so.1: ./java: fatal: relocation error: file /export/home/j2sdk1.4.0/jre/lib/sparc/client/libjvm.so: symbol __1cG__CrunSregister_exit_code6FpG_v_v_: referenced symbol not found
Why I am not able to execute any java command with this version? On the same machine I am able to run jdk1.2 and jdk1.3
Please advise on it. It will be of great help If I get some suggestion.
Thanks in Advance,
Ashish

In particular, patch 106327-14 seems to solve the problem.

My external hard drive will not open and only shows up in Disk Utilities. When I try yo repair it, it give me and error of invalid sibling link. How do I fix my external hard drive?

My external hard drive will not open and only shows up in Disk Utilities. When I try yo repair it, it give me and error of invalid sibling link. How do I fix my external hard drive?

Invalid sibling link may not be fixable by Disk Utility. (Disk Utility is very conservative, and will not attempt repairs that might cause you to lose data.)
It is an indication of serious Directory damage.
that leaves
a) third-party Utilities that will take those risks, or
b) re-initializing the drive (which deletes all your data) and restoring from another backup source.
c) "Copying off whatever files you can salvage" has gone by, and you cannot copy anything off a drive that will not mount. You may be able to use "rescue" programs such as prosoft engineering Data Rescue to copy files to another drive, but that sounds a lot better than its reality. You may get many files, but not get ANY filenames.

Error code: 3194 when restoring.. "Secure link to iTunes store failed" when diagnostics is ran..

as mentioned in the title, I have encountered 2 errors, one is when I am trying to restore my iphone and the other when iTunes diagnotics feature is ran..
I have read the information about the diagnostics result and saw something like "connection attempt to firmware update server unsuccessful". Because of this information I have concluded that the "error code 3194" happens because iTunes itself is unable to connect to the "firmware update server".
I am using Windows 7 64-bit and iTunes is now on the latest version.
below are the things I have done so far, but to no avail:
- removed/disabled my antivirus program
- put iTunes to exception list of WIndows Firewall
- disabled windows firewall and windows defender
- re-installed iTunes and made sure that it is of the latest version (version 10.6.1)
- performed recommendation from: https://discussions.apple.com/message/17409780#17409780
- perform flush dns command using command prompt
In addition to the steps I mentioned, I also tried running the diagnostics on two other computers running on different versions on iTunes, 10.5 and 10.6.0. I also did the same steps as above on these two computers, but I am getting the "secure connection to iTunes store failed" when the diagnostics were ran.
thanks for any help that you can give.

I think its weird that I experienced both the 3194 error code and "secure link to the itunes store failed" diagnostics error on three computers running on different OS (XP, vista and 7), itunes version and connectivity types (wireless and cabled). Could it be possible that there is a problem on Apple's server?
Are you still there, shintenhouji?
Perhaps try the following document:
Apple software on Windows: May see performance issues and blank iTunes Store
(I've seen a few cases in recent times of this sort of thing being associated with LSP issues.)

Ld: fatal: relocation error: R_SPARC_DISP64 error when linking on Solaris 8

Similar Messages

Maybe you are looking for