gc-linux-devel

[Gc-linux-devel] uClibc toolchain

[<a.o...@bl...>]

Hi,

As a step toward pushing anything useful in http://gc-linux.org/down/
into the sf.net project File Release system, the uClibc toolchain has
found it's rightfull home; grab it under 'Development Tools->Toolchain':

  [1] ppc-linux-uclibc-toolchain-20040609.tar.bz2
  [2] uclibc-toolchain-src-20040609.tar.bz2

[1] is pre-built for x86 hosts. I strongly suggest building from source,
however, hence [2]. See http://uclibc.org/toolchains.html and the README
in [2] for more. Have fun.

	Arthur

Re: [Gc-linux-devel] uClibc toolchain

[<a.o...@bl...>]

On Thu, Jun 10, 2004 at 03:03:04AM +0200, Arthur Othieno wrote:
>
> As a step toward pushing anything useful in http://gc-linux.org/down/
> into the sf.net project File Release system, the uClibc toolchain has
> found it's rightfull home; grab it under 'Development Tools->Toolchain':

After shuffling things around a bit, you'll find this under
'uClibc Toolchain', now.

	Arthur

[Gc-linux-devel] website/yagcd

[Groepaz <gr...@gm...>]

i've updated yagcd some minutes ago and noticed that the 
images i added dont show up in the online version (although
the links to the are correct) .... could anyone tell me
what might be wrong? (before i start trying all kinds of
things? :))

gpz

Re: [Gc-linux-devel] website/yagcd

[Michael S. <st...@in...>]

On Jun 16, 2004, at 4:20 PM, Groepaz wrote:
> i've updated yagcd some minutes ago and noticed that the
> images i added dont show up in the online version (although
> the links to the are correct) .... could anyone tell me
> what might be wrong? (before i start trying all kinds of
> things? :))

Place then images in /pic, change their mode to -rw-rw-r--, and link to 
them using src="/pic/blah.jpg"

   Michael

Re: [Gc-linux-devel] website/yagcd

[Groepaz <gr...@gm...>]

On Thursday 17 June 2004 10:17, Michael Steil wrote:
> On Jun 16, 2004, at 4:20 PM, Groepaz wrote:
> > i've updated yagcd some minutes ago and noticed that the
> > images i added dont show up in the online version (although
> > the links to the are correct) .... could anyone tell me
> > what might be wrong? (before i start trying all kinds of
> > things? :))
>
> Place then images in /pic, change their mode to -rw-rw-r--, and link to
> them using src="/pic/blah.jpg"

ok :) the fact that my images are .png shouldnt be a problem i guess? :o)
(just asking, you never know whatthehell those scripts are doing :=P)

gpz

Re: [Gc-linux-devel] website/yagcd

[Michael S. <st...@in...>]

On Jun 17, 2004, at 10:30 AM, Groepaz wrote:
> On Thursday 17 June 2004 10:17, Michael Steil wrote:
>> On Jun 16, 2004, at 4:20 PM, Groepaz wrote:
>>> i've updated yagcd some minutes ago and noticed that the
>>> images i added dont show up in the online version (although
>>> the links to the are correct) .... could anyone tell me
>>> what might be wrong? (before i start trying all kinds of
>>> things? :))
>>
>> Place then images in /pic, change their mode to -rw-rw-r--, and link 
>> to
>> them using src="/pic/blah.jpg"
>
> ok :) the fact that my images are .png shouldnt be a problem i guess? 
> :o)
> (just asking, you never know whatthehell those scripts are doing :=P)

The system doesn't touch /pic.

   Michael

Re: [Gc-linux-devel] website/yagcd

[<a.o...@bl...>]

On Wed, Jun 16, 2004 at 04:20:05PM +0200, Groepaz wrote:
> 
> i've updated yagcd some minutes ago and noticed that the 
> images i added dont show up in the online version (although
> the links to the are correct) .... could anyone tell me
> what might be wrong? (before i start trying all kinds of
> things? :))
> 
> gpz
 
Ok, I've just noticed the stuff in /.../htdocs/ has actually been edited
directly for some time now. Which really defeats the purpose of the
`htdocs' module in CVS -- to track changes made to the website. And yes,
the inconsistencies introduced are rather appalling.

I'd appreciate it if anything edited outside of CVS is actually sync'd
back, and future changes be made to the CVS module, instead. Also,
instead of having to manually run `update.sh' each time a commit is
made, I think I'll stick this one into a cron job that runs once a
day, or something more reasonable, depending on the rate at which
stuff is updated.

	Arthur