Hi, I'm new to this community. I'm facing a very strange problem because of a symbolic link we are creating while packaing. The problem occurs on my build environment which is a x86 64-bit machine with Fedora core 6. While packaging (rpmbuild), i'm getting a segmentation fault because of the soft link i'm creating for the -devel package that points to my library (libmylib.so.x). (Please see the code snippet for which we are getting the segmentation fault) _______________________________________________________________________________________________ %install %ifarch ppc rm -rf $RPM_BUILD_ROOT mkdir -p $RPM_BUILD_ROOT/usr/lib cp lib/ppu/libmylib.so $RPM_BUILD_ROOT/usr/lib # Create Symbolic Link cd $RPM_BUILD_ROOT/usr/lib mv ./libmylib.so ./libmylib.so.1 ln -s ./libmylib.so.1 libmylib.so %else ..... ..... %endif _______________________________________________________________________________________________ The problem comes because both the softlink and the library are in the same directory and the rpmbuild somehow gives this segmentation fault when we use the relative path to create the soft-link. However, when I modify the soft-link creation by giving the absolute path, it works fine. i.e. the below code works fine # Create Symbolic Link cd $RPM_BUILD_ROOT/usr/lib mv ./libmylib.so ./libmylib.so.1 ln -s /usr/lib/libmylib.so.1 libmylib.so The requirement is /usr/lib directory will have : libmylib.so.x libmylib.so -> libmylib.so.x I'm not sure, what's wrong here, can't the file and the symlink to it be in the same directory for rpmbuild packaing? Please help... Regards, Jyoti The error for your reference ------ Processing files: mylib-3.0-5 Provides: libmylib.so Requires(interp): /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) -- This is an email sent via The Fedora Community Portal https://fcp.surfsite.org https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=195368&topic_id=42857&forum=31#forumpost195368 If you think, this is spam, please report this to webmaster@xxxxxxxxxxxxxxxx and/or blame jyotisankar@xxxxxxxxxx