Stephen Liu wrote:
> After running configure changed to root ("su -" not "su" in my case)
> and ran "make install". That is all.
>
> The problem originated from "ldconfig" being on /sbin/ and in my case
> "su" did not have this path but "su -" had
>
This is due to recent changes in shadow. Ma
Hi Declan,
--- Declan Moriarty <[EMAIL PROTECTED]> wrote:
> I'm sure a real root is available on your system. There's 6 consoles
> and he can surely log into one of them.
>
> That said, the problem was not running ldconfig, right?
There was nothting wrong on ldconfig nor on the installing st
Simon Geard wrote:
On Fri, 2005-09-16 at 05:32 -0400, Chris Staub wrote:
That's a pretty weird system you have if "su" doesn't have /sbin or
/usr/sbin in the path.
Not really... remember, 'su' simply changes the current user, it doesn't
change the environment. Look at the output of 'env', and
Simon Geard wrote:
On Fri, 2005-09-16 at 05:32 -0400, Chris Staub wrote:
That's a pretty weird system you have if "su" doesn't have /sbin or
/usr/sbin in the path.
Not really... remember, 'su' simply changes the current user, it doesn't
change the environment. Look at the output of 'env', an
On Fri, 2005-09-16 at 05:32 -0400, Chris Staub wrote:
> That's a pretty weird system you have if "su" doesn't have /sbin or
> /usr/sbin in the path.
Not really... remember, 'su' simply changes the current user, it doesn't
change the environment. Look at the output of 'env', and you'll see that
th
Stephen Liu wrote:
hI Declan,
PROBLEM SOLVED.
Solution:
After running configure changed to root ("su -" not "su" in my case)
and ran "make install". That is all.
The problem originated from "ldconfig" being on /sbin/ and in my case
"su" did not have this path but "su -" had
bash-
hI Declan,
PROBLEM SOLVED.
> First of all rerun ldconfig. (hint from 30 secs with google).
>
> Have you tried running it? ld should work, and should return an error
> if called with no arguments.
>
> BTW, it doesn't say ld isn't there. It says collect2 can't find it.
>
> It's always worth read
