[gobolinux-devel] ChrootCompile
ChrootCompile is really good, but there's two things that I miss about it: * the ability to call it from any directory with a recipe name, i.e. 'ChrootCompile --root=/Files/Myroot KDE-Libs 3.5.5' * the ability to bind any directory inside the mount (how else would one have access to the kernel sources). Shouldn't we make ChrootCompile a Scripts citizen? Not include it it Scripts, but make it use all the useful functions from Scripts. -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
[gobolinux-devel] Rootless withing GoboLinux
An idea I got that I just wanted to share and get some opinions on: How about enabling rootless by default within a gobolinux system? If I, as normal user, don't have sudo privileges couldn't it be possible for Compile and InstallPackage to fall back to some sort of rootless within my home directory? Not completly rootless (not that I have used it) but more like a user /Programs and corresponding /System/Links, which will be inlcuded in that users paths. -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] ChrootCompile
On Mon, 04 Dec 2006 09:06:07 +0100, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > > Shouldn't we make ChrootCompile a Scripts citizen? Not include it it > Scripts, but make it use all the useful functions from Scripts. > Somehow I missed the fact that this was implemented two days ago... I must learn to update the cvs copy before start digging in the code. :) -- /Jonas PS. Can anyone tell me how threading works in other clients when I reply like this? Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
[gobolinux-devel] Glibc upgrade
I just _successfully_ upgraded glibc using InstallPackage. After trying and failed manually so many times this was really simple! Finally! :) Though... To compile apps after having upgraded glibc I also had to upgrade gcc and binutils. Is it possible to make some sort of test to ensure that (if those are installed) they are compiled against the "right" version of glibc? -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Glibc upgrade
On 12/4/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > I just _successfully_ upgraded glibc using InstallPackage. After trying > and failed manually so many times this was really simple! Finally! :) Hooray! > Though... > To compile apps after having upgraded glibc I also had to upgrade gcc and > binutils. Is it possible to make some sort of test to ensure that (if > those are installed) they are compiled against the "right" version of > glibc? What kind of errors did you get? I upgraded my box up to Glibc 2.5 and didn't have to upgrade GCC or Binutils (I was already using GCC 4 though). -- Hisham ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Glibc upgrade
On Tue, 05 Dec 2006 02:34:36 +0100, Hisham Muhammad <[EMAIL PROTECTED]> wrote: > On 12/4/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: >> I just _successfully_ upgraded glibc using InstallPackage. After trying >> and failed manually so many times this was really simple! Finally! :) > > Hooray! > >> Though... >> To compile apps after having upgraded glibc I also had to upgrade gcc >> and >> binutils. Is it possible to make some sort of test to ensure that (if >> those are installed) they are compiled against the "right" version of >> glibc? > > What kind of errors did you get? I upgraded my box up to Glibc 2.5 and > didn't have to upgrade GCC or Binutils (I was already using GCC 4 > though). > I updated from Glibc 2.3.2 to 2.4 and configure produced the following (after i have updated gcc): checking for a BSD-compatible install... /System/Links/Executables/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. PrepareProgram: configure failed. Compile: Preparation step failed. I was already using gcc 4.1.1, I just reinstalled it from repository to have the version linked against my new glibc, but that was before I got the message. I don't even think I tried to compile anything before I updated gcc. The mentioned error went away when I installed the binutils package. -- /Jonas PS. Right, it's glibc 2.5 that's the latest and greatest. I forgot that. Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] [gobolinux-commits] tools/ChrootCompile bin/ChrootCompile Resources...
On 12/4/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> --- bin/ChrootCompile 4 Dec 2006 18:47:14 - 1.15
> +++ bin/ChrootCompile 4 Dec 2006 21:02:11 - 1.16
> @@ -15,17 +15,18 @@
> Add_Option_Boolean "l" "local-repository" "Look at the local repository for
> recipes." ""
> Add_Option_Boolean "p" "local-programs" "Take entries from /Programs (use
> with care)." ""
> Add_Option_Entry "X" "cross-compile" "Use a cross-compiler according to the
> configuration in Cross-.conf." ""
> +Add_Option_Entry "d" "use-directory" "Use specified directory as root for
> ChrootCompile." ""
> Parse_Options "$@"
>
>
> #
> # Operation
> #
> -chrootcompileMode="gobo"
> -[ -e "./Compile.conf" ] && chrootcompileCompileConf="./Compile.conf"
> -
> +Parse_Conf Compile.conf
> # allows one to override any of the above variables
> -[ -e "./ChrootCompile.conf" ] && source "./ChrootCompile.conf"
> +Parse_Conf --mandatory ChrootCompile.conf
ChrootCompile.conf should be optional, there's no need to use --mandatory here.
> +Is_Entry "use-directory" && chrootCompileDir="$(Entry 'use-directory')"
>
> if [ "$UID" -ne 0 ]
> then sudo=sudo
> @@ -80,16 +81,32 @@
> unset verbose
> Boolean "verbose" && verbose="--verbose"
>
> -
> #
> # Verify our whereabouts
> #
> if [ ! -d BaseDependencies -a ! "$local_programs" ]
> then
> if [ ! -z "`ls`" ]
> - then Die "This doesn't look like a ChrootCompile environment directory.
> Rerun this script on an empty directory to build an environment."
> + then
> + if [ ! -z "${chrootCompileDir}" ]
> + then
> + cd "${chrootCompileDir}"
I would suggest to use 'Quiet pushd' (and to add the missing 'Quiet
popd' afterwards).
Cheers,
--
Lucas
powered by /dev/dsp
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] [gobolinux-commits] tools/ChrootCompile bin/ChrootCompile Resources...
On Tue, 05 Dec 2006 04:09:55 +0100, Lucas C. Villa Real
<[EMAIL PROTECTED]> wrote:
> On 12/4/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
>> -chrootcompileMode="gobo"
>> -[ -e "./Compile.conf" ] && chrootcompileCompileConf="./Compile.conf"
>> -
>> +Parse_Conf Compile.conf
>> # allows one to override any of the above variables
>> -[ -e "./ChrootCompile.conf" ] && source "./ChrootCompile.conf"
>> +Parse_Conf --mandatory ChrootCompile.conf
>
> ChrootCompile.conf should be optional, there's no need to use
> --mandatory here.
>
It slipped in. I used --mandatory as debug...
>> +Is_Entry "use-directory" && chrootCompileDir="$(Entry 'use-directory')"
>>
>> if [ "$UID" -ne 0 ]
>> then sudo=sudo
>> @@ -80,16 +81,32 @@
>> unset verbose
>> Boolean "verbose" && verbose="--verbose"
>>
>> -
>>
>> #
>> # Verify our whereabouts
>>
>> #
>> if [ ! -d BaseDependencies -a ! "$local_programs" ]
>> then
>> if [ ! -z "`ls`" ]
>> - then Die "This doesn't look like a ChrootCompile environment
>> directory. Rerun this script on an empty directory to build an
>> environment."
>> + then
>> + if [ ! -z "${chrootCompileDir}" ]
>> + then
>> + cd "${chrootCompileDir}"
>
> I would suggest to use 'Quiet pushd' (and to add the missing 'Quiet
> popd' afterwards).
>
I'll do that :)
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
