[gobolinux-users] Re: Rootless problems

[Rohan Nicholls]

I haven't used it lately (work computer), but I had much of rootless
working on a FC3 system, with a few notable exceptions:
1. It always asked in install glibc when I used Compile (Bad idea!!)

2. InstallPackage worked flawlessly.

The only thing that needed adjusting was fixing where Compile and
InstallPackage searched for recipes|packages.

Now I have not used it in a couple of months although I am debating
installing it on this machine despite compilation being tricky on this
machine.

Other than that I would run into problems from time to time with
compilations but it is hard to tell whether that is because of rootless
or hardware failures on this old beast.

Probably doesn't help, but that is my story.

Rohan


 On Thu, 9 Feb 2006 07:33:49 -0500
"Sean E. Russell" <gobo at ser1.net> wrote:

> On Wednesday 08 February 2006 22:27, Hisham Muhammad wrote:
> > I'm not the ideal person to answer this, since I don't use or maintain
> > Rootless for a few years now. But hopefully I can clarify some issues
> > until someone comes up with a better answer. :)
> 
> Thanks :-)
> 
> > I may be wrong, but it looks like zshrc is not being run by a copy of
> > zsh, weird.
> 
> Interesting.  I might be able to track that one down.
> 
> > Well, the thing is, many packages have hardcoded paths in them.
> > InstallPackage is not a "supported operation" in the rootless world.
> > Some packages like Compile and OpenOffice happen to have no hardcoded
> > paths, but in the general case, you should Compile your own packages
> > when using rootless.
> 
> Oh, OK.  Then the CreateRootlessEnvironment script probably shouldn't tell 
> users to install packages with hardcoded paths:
> 
> "You can now restart your session in order to enjoy GoboLinux Rootless
> 
> Commands recommended to be executed afterwards:
>   InstallPackage Atool
>   InstallPackage Compile
>   InstallPackage Mtail
> "
> 
> So, my problem is this: Rootless doesn't come with Compile, and CompileProgram 
> depends on Atool, which has that hard-coded path.  So the user bootstraps 
> Compile with InstallPackage and try to compile perl, which tries to install a 
> whole bunch of stuff, but fails because it can't unpack archives:
> 
> Compile: Unpacking file /home/ser/Files/Compile/Archives/glibc-2.3.2.tar.gz...
> /home/ser/System/Links/Executables/Compile: /home/ser/System/Links/Executables/aunpack: /System/Links/Executables/perl: 
> bad interpreter: No such file or directory
> Compile: Could not unpack ''.
> Compile: Locating a recipe for Glibc ...
> 
> So, InstallPackage is the only installation tool that works in rootless, but 
> we're not supposed to use it because it isn't supported?
> 
> I think the problem here is the use of aunpack, or the fact that aunpack has 
> hardcoded links to perl.  InstallPackage doesn't appear to use aunpack, and 
> so it works.
> 
> > This is related to the Perl you installed not being compatible with
> > the host system. For core dependencies such as this, I suggest
> > installing the perl package from your distribution. You can also try
> > to run Compile perl.
> 
> Perl is installed, but none of the Gobo scripts are finding it, because of the 
> hardcoded path.
> 
> > I think you need a basic development environment working "natively" in
> > the base system to get things started (gcc, perl, etc.) If you have
> > that, it should be possible to get Rootless to work.
> 
> That isn't the problem; I certainly have a working gcc and perl in my Gentoo 
> root OS.  The problem is that paths to the perl interpreter are hardcoded, so 
> the root OS's perl will never be found.  The fix requires the user to go in 
> and hack scripts to get a working Rootless Gobo.
> 
> Actually, the problems are much deeper.   I went in and fixed aunpack and 
> pointed it at my root OS's perl, so that I could run Compile.  The first 
> thing I try to compile is perl, which has a bunch of dependencies.  This gets 
> me into some sort of compile loop, where the compilations invariably fail in 
> the configure step with:
> 
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the environment variable
> *** and run configure again.
> PrepareProgram: configure failed.
> Compile: Preparation step failed.
> 
> make: Makefile: No such file or directory
> make: *** No rule to make target `Makefile'.  Stop.
> Compile: Build process failed.
> 
> 
> Does anybody have a working Rootless Gobo running on a non-Gobo system?
> 
> -- 
> --- SER
> 
> "As democracy is perfected, the office of president represents, 
> more and more closely, the inner soul of the people.  On some 
> great and glorious day the plain folks of the land will reach 
> their heart's desire at last and the White House will be adorned 
> by a downright moron."        -  H.L. Mencken (1880 - 1956)
> _______________________________________________
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users