[sudo-users] Fwd: SUDO package for Sparc version 1.6.8p12
p.stepowski at qut.edu.au
Thu Jun 28 02:38:38 EDT 2007
If the problem is a non (Solaris) standard vi linked to GCC:
Would fail too with the same error, no? Easy enough to confirm.
NOTE: If you compile sudo against GCC and the libgcc_s.so.1, is not present,
sudo will still run fine, unless you try to run a command using the NOEXEC
feature. Then you'll see the linking error.
Chris Jepeway wrote:
> (Hey, Paul didn't preserve the cc:, so the original questioner)
> (questioner didn't get his reply. I'll bottom quote it. )
> On Jun 27, 2007, at 12:47 AM, Paul Stepowski wrote:
>> The way the noexec feature works is to substitute the exec*() system
>> calls with
>> stub system calls.
>>>> ld.so.1: /usr/bin/vi: fatal: libgcc_s.so.1: open failed: No such
>>>> file or directory
> But, the error is given by ld.so as trouble exec'ing /usr/bin/vi.
> Not in starting sudo.
> Perhaps Tim has substituted Solaris' /usr/bin/vi with vim?
> And vim might need ligcc_s?
> This would tell us, yes?
> csh% env - /usr/bin/vi /tmp/z
> If that *doesn't* work, then the problem might be that sudo
> isn't passing "scary" envariables like LD_LIBRARY_PATH.
> If it *does* work, well, then try (as root) a
> csh# ldd /usr/sfw/bin/sudo
> (or wherever sudo is installed) & check that all the
> libraries resolve.
> Chris <jepeway at blasted-heath.com>.
>> The dynamic linker can't find the library to link to.
>> Looks like this version of sudo was compiled using gcc and this
>> library doesn't
>> exist on your system.
>> For Solaris, I always use the native compiler so I don't have this
>> Otherwise you need to supply the gcc libraries as part of the package.
> sudo-users mailing list <sudo-users at sudo.ws>
> For list information, options, or to unsubscribe, visit:
More information about the sudo-users