Re: [gobolinux-devel] No BuildLiveCD recipe

2007-02-11 Thread Koen Weddepohl
Jonatan Liljedahl wrote: >>> My thought was that one could have a list of /Programs apps and how to >>> make AppDirs of them, they could be automatically symlinked to /ROX-Apps >>> too... Perhaps one could use that inotify shellscript tool some dev on >>> this list created (lucas? don't remember...

Re: [gobolinux-devel] libc update

2007-02-11 Thread Jonatan Liljedahl
Ricardo Nabinger Sanchez wrote: > On Sun, 11 Feb 2007 19:40:41 +0100 > Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > >> I sometimes get strange "double free or corruption" program aborts, and >> am thinking that my libc (2.3.5 with NPTL, compiled myself...) may be >> broken? >> >> Now, it was a l

Re: [gobolinux-devel] libc update

2007-02-11 Thread Ricardo Nabinger Sanchez
On Sun, 11 Feb 2007 19:40:41 +0100 Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > I sometimes get strange "double free or corruption" program aborts, and > am thinking that my libc (2.3.5 with NPTL, compiled myself...) may be > broken? > > Now, it was a long time I upgraded libc. What do I need t

[gobolinux-devel] libc update

2007-02-11 Thread Jonatan Liljedahl
I sometimes get strange "double free or corruption" program aborts, and am thinking that my libc (2.3.5 with NPTL, compiled myself...) may be broken? Now, it was a long time I upgraded libc. What do I need to do? And what do I need to recompile after compiling/installing the new libc? -- /Jonata

Re: [gobolinux-devel] No BuildLiveCD recipe

2007-02-11 Thread Jonatan Liljedahl
Koen Weddepohl wrote: > Jonatan Liljedahl wrote: >> Koen Weddepohl wrote: >>> I'd like to experiment with building a ROX-based Live CD ("RoboLinux", >>> perhaps). >> Nice! I've been thinking about that too... Please report on the progress. > I managed to Compile BuildLiveCD (thanks Lucas), right n

Re: [gobolinux-devel] [gobolinux-commits] tools/ChrootCompile/bin ChrootCompile

2007-02-11 Thread Lucas C. Villa Real
On 2/10/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > How about making "setup-environment" taking an argument and default to > $PDW if no argument is given? Just took a time to see that again, and we already have this functionality by combining --setup-environment and --use-directory. If one do