linuxdc-dev — Developer discussion list

[linuxdc-dev] Viruses - off topic, but interesting?

[Adrian M. <ad...@mc...>]

As part of my efforts to redesign the Lindc site I have attempted to download 
the GIMP for Windows (all my HTML tools are on Windows boxes and it's a pain 
to switch from one machine - in the living room - to another - in the bedroom 
just to twiddle the graphics).

But I've been unsuccesful because every version I've looked at appears to 
contain the backdoor/IRC-Flood/D virus (I think that's what it was called).

Is this a known problem? Or has my virus checking software just got it wrong?

Re: [linuxdc-dev] Kernel-boot.elf available for download

[Adrian M. <ad...@mc...>]

I've updated the kernel and busybox on my site - in theory it should now 
support NFS.

http://www.mcmen.demon.co.uk/linuxdc

About 40 people appear to have downloaded it - anyone got any feedback?


On Monday 24 September 2001  8:10 pm, ePAc wrote:
> mirrored :o)
>
> http://www.korigan.net/linux-dc/
>

Re: [linuxdc-dev] Kernel-boot.elf available for download

[ePAc <ep...@ko...>]

mirrored :o)

http://www.korigan.net/linux-dc/

---
Nothing is foolproof to a sufficiantly talented fool...
  oo
,(..)\
  ~~

On Mon, 24 Sep 2001, Adrian McMenamin wrote:

> Please note a gzipped version is now on the site. Please use it, as the
> uncompressed version will shortly be withdrawn.
>
> http://www.mcmen.demon.co.uk/linuxdc/
>
>
> On Sunday 23 September 2001  9:34 pm, Adrian McMenamin wrote:
> > If anybody out there wants to try to try a working LinuxDC kernel there is
> > now one available at:
> >
> > http://www.mcmen.demon.co.uk/linuxdc/kernel-boot.elf
> >
> > The kernel is configure to support a keyboard and the BBA.
> >
> > It also includes Busybox and has a telnet client, but not too much else.
> >
> > It is a 912017 byte download.
> >
> > To use it you will need to use dc-load or similar (using the default upload
> > address on dc-load works fine IME).
> >
> > Warnings: my ISP impose severe download restrictions, so I may have to put
> > it offline if demand is heavy!
> >
> > GPL stuff: This is licencesed under the GPL. I built this using Bill
> > Gatliff's excellent article and sources are available from there.
> >
> > http://www.billgatliff.com/articles/emblindc/emblindc/
> >
> >
> > Best of luck
> >
> > _______________________________________________
> > Linuxdc-dev mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] Kernel-boot.elf available for download

[Adrian M. <ad...@mc...>]

Please note a gzipped version is now on the site. Please use it, as the 
uncompressed version will shortly be withdrawn.

http://www.mcmen.demon.co.uk/linuxdc/


On Sunday 23 September 2001  9:34 pm, Adrian McMenamin wrote:
> If anybody out there wants to try to try a working LinuxDC kernel there is
> now one available at:
>
> http://www.mcmen.demon.co.uk/linuxdc/kernel-boot.elf
>
> The kernel is configure to support a keyboard and the BBA.
>
> It also includes Busybox and has a telnet client, but not too much else.
>
> It is a 912017 byte download.
>
> To use it you will need to use dc-load or similar (using the default upload
> address on dc-load works fine IME).
>
> Warnings: my ISP impose severe download restrictions, so I may have to put
> it offline if demand is heavy!
>
> GPL stuff: This is licencesed under the GPL. I built this using Bill
> Gatliff's excellent article and sources are available from there.
>
> http://www.billgatliff.com/articles/emblindc/emblindc/
>
>
> Best of luck
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

Re: [linuxdc-dev] Kernel-boot.elf available for download

[ePAc <ep...@ko...>]

I have a mirror for this one:
http://www.korigan.net/linux-dc/

I hope this helps :o)

---
Nothing is foolproof to a sufficiantly talented fool...
  oo
,(..)\
  ~~

On Sun, 23 Sep 2001, Adrian McMenamin wrote:

> If anybody out there wants to try to try a working LinuxDC kernel there is
> now one available at:
>
> http://www.mcmen.demon.co.uk/linuxdc/kernel-boot.elf
>
> The kernel is configure to support a keyboard and the BBA.
>
> It also includes Busybox and has a telnet client, but not too much else.
>
> It is a 912017 byte download.
>
> To use it you will need to use dc-load or similar (using the default upload
> address on dc-load works fine IME).
>
> Warnings: my ISP impose severe download restrictions, so I may have to put it
> offline if demand is heavy!
>
> GPL stuff: This is licencesed under the GPL. I built this using Bill
> Gatliff's excellent article and sources are available from there.
>
> http://www.billgatliff.com/articles/emblindc/emblindc/
>
>
> Best of luck
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

[linuxdc-dev] Kernel-boot.elf available for download

[Adrian M. <ad...@mc...>]

If anybody out there wants to try to try a working LinuxDC kernel there is 
now one available at:

http://www.mcmen.demon.co.uk/linuxdc/kernel-boot.elf

The kernel is configure to support a keyboard and the BBA. 

It also includes Busybox and has a telnet client, but not too much else.

It is a 912017 byte download.

To use it you will need to use dc-load or similar (using the default upload 
address on dc-load works fine IME).

Warnings: my ISP impose severe download restrictions, so I may have to put it 
offline if demand is heavy!

GPL stuff: This is licencesed under the GPL. I built this using Bill 
Gatliff's excellent article and sources are available from there.

http://www.billgatliff.com/articles/emblindc/emblindc/


Best of luck

[linuxdc-dev] Success!

[Renegade M. <dra...@sp...>]

After many weeks of occasional work on getting a cross compiler for the
Dreamcast working, thanks to much help from this list, i think i have a
working compiler. Binutils, gcc, and glibc are all compiled and hopefully
will work.

I just have a couple more quick questions before i start playing with the
compiler: now that glibc is compiled, should gcc be recompiled? (I saw
something in a generic cross-compilation FAC about recompiling gcc once
glibc is available.)

Secondly, what kernel options do i need to get broadband adapter support in
the kernel? I have noticed that if i do a "make ARCH=sh menuconfig" on the
kernel and select "General setup:PCI support" that i can then go into
"Network device support:Ethernet (10 or 100Mbit):EISA, VLB, PCI and on
board controllers" and select the "Realtek RTL-8139 PCI Fast Ethernet
Adapter support" and the "Support for Dreamcast Broad Band Adapter." Is
that sufficient to get support for the adapter itself, or should i be doing
something different?

Re: [linuxdc-dev] Linux DC

[M. R. B. <mr...@0x...>]

* Juliano Franz <jf...@gl...> on Mon, Sep 17, 2001:

> Where I can get the Linux DC booted
> 

Read this article:
http://www.billgatliff.com/articles/emblindc/emblindc/t1.html

Faint of heart need not apply :P.

Just kidding.

M. R.

Re: [linuxdc-dev] Linux DC

[Adrian M. <ad...@mc...>]

On Monday 17 September 2001  7:27 pm, Juliano Franz wrote:
> Where I can get the Linux DC booted
>
> Juliano Morato Franz
>

What have you got?

Basic steps:

download the sources off the cvs as described
Don't use the .config supplied on the site - I can email you one if you want
Do use the dcloader (have you got a BBA or a cable?)
But don't use the settings in the config file!

Or else you'll have to burn a CD-R!

[linuxdc-dev] Linux DC

[Juliano F. <jf...@gl...>]

Where I can get the Linux DC booted

Juliano Morato Franz


________________________________________
Psiu.com - A gente se encontra aqui. No chat da Globo.com. Entre agora: http://www.psiu.com

[linuxdc-dev] BSOD

[Adrian M. <ad...@mc...>]

Got to the point where I can load the zImage file - but then: blue screen of 
death.

What should I look for here to find out what's wrong - it looks like a load 
of register contents at the moment.

How can I debug remotely on this sort of setup (BBA)?

Re: [linuxdc-dev] Making some progress, but..

[Adrian M. <ad...@mc...>]

Anybody got the options file? I cannot find it on the site. The link is wrong 
- but I can't find it by digging about either.

Thanks

Adrian McMenamin

Re: [linuxdc-dev] Making some progress, but..

[M. R. B. <mr...@0x...>]

* Renegade Muskrat <dra...@sp...> on Wed, Sep 12, 2001:

> >And kernel driver work is very much active, current work includes
> >redesigning the framebuffer, improving the GD-ROM driver, and other
> >internal cleanups.
> 
> Just curious, how well is the broadband adapter supported?
> 

It works fine.

M. R.

Re: [linuxdc-dev] Making some progress, but..

[Renegade M. <dra...@sp...>]

>And kernel driver work is very much active, current work includes
>redesigning the framebuffer, improving the GD-ROM driver, and other
>internal cleanups.

Just curious, how well is the broadband adapter supported?

Re: [linuxdc-dev] Making some progress, but..

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Thu, Sep 13, 2001:

> Scartch the last message - I fiddled with the path and got it to compile.
> 
> Does this problem mean that the cvs has gotten ahead of the supplied .config? 
> Or have I simply kludged the whole thing for the sake of a compile?
> 

The linuxdc.org site desperately needs updating/redoing.  Yeah that .config
is about 4-5mos old, sorry you had to figure this out the hard way :).

If anyone out there has suggestions for improvement, or would like to
contribute in some way to redesigning the site, we're open for ideas - just
let us know.

> My special thanks to MR Brown for help in getting me this far :->
> 

No problem, that's what I'm here for :P.

And kernel driver work is very much active, current work includes
redesigning the framebuffer, improving the GD-ROM driver, and other
internal cleanups.

M. R.

Re: [linuxdc-dev] Making some progress, but..

[Adrian M. <ad...@mc...>]

Scartch the last message - I fiddled with the path and got it to compile.

Does this problem mean that the cvs has gotten ahead of the supplied .config? 
Or have I simply kludged the whole thing for the sake of a compile?

My special thanks to MR Brown for help in getting me this far :->

Fwd: Re: [linuxdc-dev] Making some progress, but..

[Adrian M. <ad...@mc...>]

----------  Forwarded Message  ----------
Subject: Re: [linuxdc-dev] Making some progress, but..
Date: Thu, 13 Sep 2001 00:04:08 +0100
From: Adrian McMenamin <ad...@mc...>
To: "M. R. Brown" 

On Wednesday 12 September 2001 11:46 pm, you wrote:
> * Adrian McMenamin <ad...@mc...> on Wed, Sep 12, 2001:
> > On Tuesday 11 September 2001 10:38 pm, Adrian McMenamin wrote:
> > > Thanks to the help I was give earlier I am not getting at least
> > > somethings to compile - but like others on this list I have no
> > > experience of cross compiling - or indeed of ever compiling a project
> > > of this size.
> >
> > Well, obviously this is a linking error, but I need some clues as to what
> > additional things to tell the linker? Any ideas - I'm scanned through the
> > whole list and got nwhere further forward on this one.
>
> You have some broken dependencies in the kernel.  Go through your config
> again (e.g. make ... menuconfig) and make sure you've picked the relevant
> networking options - those missing functions belong to the net driver.
>
> M. R.

Thanks, I did just that after I posted the other message. In effect I
switched networking on, but then I got these errors...

make[1]: Entering directory `/home/Adrian/linux/arch/sh/boot'
make -C compressed vmlinux
make[2]: Entering directory `/home/Adrian/linux/arch/sh/boot/compressed'
tmppiggy=_tmp_$$piggy; \
rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk; \
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/objcopy -O
binary -
R .note -R .comment -R .stab -R .stabstr -S -R .empty_zero_page
/home/Adrian/lin
ux/vmlinux $tmppiggy; \
gzip -f -9 < $tmppiggy > $tmppiggy.gz; \
echo "SECTIONS { .data : { input_len = .; LONG(input_data_end - input_data)
inpu
t_data = .; *(.data) input_data_end = .; }}" > $tmppiggy.lnk; \
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/ld -EL -r -o
piggy.
o -b binary $tmppiggy.gz -b elf32-sh-linux -T $tmppiggy.lnk; \
rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk
/bin/sh:
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/objcopy: N
o such file or directory
/bin/sh: _tmp_4561piggy: No such file or directory
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/ld: cannot open
_tm
p_4561piggy.gz: No such file or directory
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc
-D__ASSEMBLY__
-D__KERNEL__ -I/home/Adrian/linux/include -ml -m4-nofpu -traditional -c
 head.S /opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc
 -D__KERNEL__ -I
/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
-f
no-strict-aliasing -ml -m4-nofpu -pipe -D__KERNEL__
-I/home/Adrian/linux/include
  -c -o misc.o misc.c
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/ld -EL -Ttext
0x8c2
10000 -e startup -T /home/Adrian/linux/arch/sh/vmlinux.lds -o vmlinux head.o
mis
c.o piggy.o
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/ld: cannot open
pig
gy.o: No such file or directory
make[2]: *** [vmlinux] Error 1
make[2]: Leaving directory `/home/Adrian/linux/arch/sh/boot/compressed'
make[1]: *** [compressed/vmlinux] Error 2
make[1]: Leaving directory `/home/Adrian/linux/arch/sh/boot'
make: *** [zImage] Error 2

-------------------------------------------------------

Re: [linuxdc-dev] Making some progress, but..

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Wed, Sep 12, 2001:

> On Tuesday 11 September 2001 10:38 pm, Adrian McMenamin wrote:
> > Thanks to the help I was give earlier I am not getting at least somethings
> > to compile - but like others on this list I have no experience of cross
> > compiling - or indeed of ever compiling a project of this size.
> >
> Well, obviously this is a linking error, but I need some clues as to what 
> additional things to tell the linker? Any ideas - I'm scanned through the 
> whole list and got nwhere further forward on this one.

You have some broken dependencies in the kernel.  Go through your config
again (e.g. make ... menuconfig) and make sure you've picked the relevant
networking options - those missing functions belong to the net driver.

M. R.

Re: [linuxdc-dev] Making some progress, but..

[Adrian M. <ad...@mc...>]

On Tuesday 11 September 2001 10:38 pm, Adrian McMenamin wrote:
> Thanks to the help I was give earlier I am not getting at least somethings
> to compile - but like others on this list I have no experience of cross
> compiling - or indeed of ever compiling a project of this size.
>
Well, obviously this is a linking error, but I need some clues as to what 
additional things to tell the linker? Any ideas - I'm scanned through the 
whole list and got nwhere further forward on this one.

[linuxdc-dev] Making some progress, but..

[Adrian M. <ad...@mc...>]

Thanks to the help I was give earlier I am not getting at least somethings to 
compile - but like others on this list I have no experience of cross 
compiling - or indeed of ever compiling a project of this size.

The compile is now halting on this:

Any clues anyone?


sh4-linux-gcc -E -traditional -C -P -I/home/Adrian/linux/include -Ush 
arch/sh/vm
linux.lds.S >arch/sh/vmlinux.lds
sh4-linux-ld -EL -T arch/sh/vmlinux.lds -e _stext arch/sh/kernel/head.o 
arch/sh/
kernel/init_task.o init/main.o init/version.o \
        --start-group \
        arch/sh/kernel/kernel.o arch/sh/mm/mm.o kernel/kernel.o mm/mm.o 
fs/fs.o
ipc/ipc.o \
         drivers/char/char.o drivers/block/block.o drivers/misc/misc.o 
drivers/n
et/net.o drivers/media/media.o drivers/video/video.o \
        net/network.o \
        /home/Adrian/linux/arch/sh/lib/lib.a /home/Adrian/linux/lib/lib.a 
/home/
Adrian/linux/arch/sh/lib/lib.a 
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/li
b/gcc-lib/sh4-linux/3.0/libgcc.a \
        --end-group \
        -o vmlinux
net/network.o: In function `skb_copy_bits':
net/network.o(.text+0x4530): undefined reference to `BUG_TRAP'
net/network.o: In function `skb_checksum':
net/network.o(.text+0x46ac): undefined reference to `BUG_TRAP'
net/network.o(.text+0x46b0): undefined reference to `csum_block_add'
net/network.o: In function `skb_copy_and_csum_bits':
net/network.o(.text+0x4848): undefined reference to 
`csum_partial_copy_nocheck'
net/network.o(.text+0x484c): undefined reference to `BUG_TRAP'
net/network.o(.text+0x4850): undefined reference to `csum_block_add'
net/network.o: In function `skb_copy_datagram_iovec':
net/network.o(.text+0x5248): undefined reference to `BUG_TRAP'
net/network.o: In function `skb_copy_and_csum_datagram':
net/network.o(.text+0x5414): undefined reference to `csum_and_copy_to_user'
net/network.o(.text+0x5418): undefined reference to `BUG_TRAP'
net/network.o(.text+0x541c): undefined reference to `csum_block_add'
net/network.o: In function `skb_copy_and_csum_datagram_iovec':
net/network.o(.text+0x5504): undefined reference to `csum_fold'
make: *** [vmlinux] Error 1

Re: [linuxdc-dev] Confused (long)

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001:

> 
> Not wishing to sound ungrateful for what is, after all, help offered 
> voluntarily. But if I am meant to add an extra command why isn't it mentioned 
> in the HOWTOs?
> 

What extra command?  What are you complaining about?  Just add `ARCH=sh'
and be done with it.

I have updated the documentation per your "request" :P.

M. R.

Re: [linuxdc-dev] Confused (long)

[Adrian M. <ad...@mc...>]

On Tuesday 11 September 2001  3:54 am, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001:
> > The ftp site appears to be down and so I loaded the rpm for the tools
> > package ... but it doesn't appear to work for me.
> >
> > I am sure this is because of my settings, but I am not clever enough to
> > know how to set this right!
> >
> > When I run...
> >
> >  make
> > CROSS_COMPILE=/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bi
> >n/ dep zImage
>
> You forgot ARCH=sh in your make command.
>
> > I get this sort of thing...
> >
> > /opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc
> > -D__KERNEL__ -I/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2
> > -fomit-frame-pointer -fno-strict-aliasing -pipe  -march=i686   -c -o
> > init/main.o init/main.c
> > cc1: Invalid option `arch=i686'
> > In file included from /home/Adrian/linux/include/linux/wait.h:19,
> >                  from /home/Adrian/linux/include/linux/fs.h:12,
> >                  from /home/Adrian/linux/include/linux/capability.h:17,
> >                  from /home/Adrian/linux/include/linux/binfmts.h:5,
> >                  from /home/Adrian/linux/include/linux/sched.h:9,
> >                  from /home/Adrian/linux/include/linux/mm.h:4,
> >                  from /home/Adrian/linux/include/linux/slab.h:14,
> >                  from /home/Adrian/linux/include/linux/proc_fs.h:5,
> >                  from init/main.c:15:
>
> [snip]
>
> > {standard input}:1776: Error: unknown opcode
> > {standard input}:1777: Error: unknown opcode
> > {standard input}:1778: Error: invalid operands for opcode
> > make: *** [init/main.o] Error 1
> >
> >
> > Eeeek! What's wrong???
>
> Because you didn't specify ARCH=sh, you attempted to compile an i386
> kernel with a sh4 compiler.  Use that for *all* kernel targets, including
> menuconfig.
>
> And I hope you're using the latest kernel from LinuxSH CVS (should be at
> least 2.4.10-pre6).
>

I am using the latest stuff from the CVS, yes. Late last night I was able to 
access the ftp site - so should I use the downloaded tools or the ones that 
popped out of the RPM?

Not wishing to sound ungrateful for what is, after all, help offered 
voluntarily. But if I am meant to add an extra command why isn't it mentioned 
in the HOWTOs?


> M. R.

Re: [linuxdc-dev] More fun with glibc

[M. R. B. <mr...@0x...>]

* Renegade Muskrat <dra...@sp...> on Mon, Sep 10, 2001:

> I still have not been able to get glibc to compile. It compiles for about
> 20 minutes or so on my PII-450, and then gives these errors:
> 
> /usr/local/sh-linux/lib/gcc-lib/sh-linux/3.0/../../../../sh-linux/bin/ld:
> cannot find -lgcc_s_
> collect2: ld returned 1 exit status
> make[2]: *** [/home/build/build-glibc/iconvdata/ISO8859-1.so] Error 1
> make[2]: Leaving directory `/home/build/glibc-2.2.2/iconvdata'
> make[1]: *** [iconvdata/others] Error 2
> make[1]: Leaving directory `/home/build/glibc-2.2.2'
> make: *** [all] Error 2
> make: Leaving directory `/home/build/build-glibc'
> 

Grab the most recent gcc (3.0.1), binutils (2.11.2), and glibc (2.2.4) from
ftp.m17n.org:/pub/super-h/testing/.

M. R.

Re: [linuxdc-dev] Confused (long)

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001:

> The ftp site appears to be down and so I loaded the rpm for the tools package 
> ... but it doesn't appear to work for me.
> 
> I am sure this is because of my settings, but I am not clever enough to know 
> how to set this right!
> 
> When I run...
> 
>  make 
> CROSS_COMPILE=/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/ 
> dep zImage
> 

You forgot ARCH=sh in your make command.

> I get this sort of thing...
> 
> /opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc -D__KERNEL__ 
> -I/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer -fno-strict-aliasing -pipe  -march=i686   -c -o 
> init/main.o init/main.c
> cc1: Invalid option `arch=i686'
> In file included from /home/Adrian/linux/include/linux/wait.h:19,
>                  from /home/Adrian/linux/include/linux/fs.h:12,
>                  from /home/Adrian/linux/include/linux/capability.h:17,
>                  from /home/Adrian/linux/include/linux/binfmts.h:5,
>                  from /home/Adrian/linux/include/linux/sched.h:9,
>                  from /home/Adrian/linux/include/linux/mm.h:4,
>                  from /home/Adrian/linux/include/linux/slab.h:14,
>                  from /home/Adrian/linux/include/linux/proc_fs.h:5,
>                  from init/main.c:15:
[snip]
> {standard input}:1776: Error: unknown opcode
> {standard input}:1777: Error: unknown opcode
> {standard input}:1778: Error: invalid operands for opcode
> make: *** [init/main.o] Error 1
> 
> 
> Eeeek! What's wrong???
> 

Because you didn't specify ARCH=sh, you attempted to compile an i386
kernel with a sh4 compiler.  Use that for *all* kernel targets, including
menuconfig.

And I hope you're using the latest kernel from LinuxSH CVS (should be at
least 2.4.10-pre6).

M. R.

[linuxdc-dev] More fun with glibc

[Renegade M. <dra...@sp...>]

I still have not been able to get glibc to compile. It compiles for about
20 minutes or so on my PII-450, and then gives these errors:

/usr/local/sh-linux/lib/gcc-lib/sh-linux/3.0/../../../../sh-linux/bin/ld:
cannot find -lgcc_s_
collect2: ld returned 1 exit status
make[2]: *** [/home/build/build-glibc/iconvdata/ISO8859-1.so] Error 1
make[2]: Leaving directory `/home/build/glibc-2.2.2/iconvdata'
make[1]: *** [iconvdata/others] Error 2
make[1]: Leaving directory `/home/build/glibc-2.2.2'
make: *** [all] Error 2
make: Leaving directory `/home/build/build-glibc'

I tried building glibc with the following commands. I have also tried the
configure with various combinations of removing the "--target=${TARGET}"
and adding "--disable-debug" and "--disable-profile"

echo "CFLAGS := -ml -m4 -O \$(CFLAGS)
ASFLAGS-.o := -ml
LDFLAGS-relocatable := -ml
crts-predefined=yes
build-programs=no
CC=${TARGET}-gcc -ml -m4
RANLIB=${TARGET}-ranlib
AS=${TARGET}-gcc -ml
LD=${TARGET}-ld -ml
AR=${TARGET}-ar
BUILD_CC=gcc" > configparms
CC="${TARGET}-gcc -ml -m4" ../glibc-2.2.2/configure \
     --host=${TARGET} --build=${HOST} --target=${TARGET} \
     --prefix=${PREFIX} --enable-add-ons \
     --with-headers=${PREFIX}/linux/include \
     2>&1 | tee -a configure.out
make -w all \
     2>&1 | tee -a make.out

Any assistance would once again be most appreciated.

In case it helps, the command that make was trying to execute when it hit
the error was as follows:

sh-linux-gcc -ml -m4   -shared -o
/home/build/build-glibc/iconvdata/ISO8859-1.so
-Wl,-dynamic-linker=/usr/local/sh-linux/lib/ld-linux.so.2
-B/home/build/build-glibc/csu/    -L/home/build/build-glibc
-L/home/build/build-glibc/math -L/home/build/build-glibc/elf
-L/home/build/build-glibc/dlfcn -L/home/build/build-glibc/nss
-L/home/build/build-glibc/nis -L/home/build/build-glibc/rt
-L/home/build/build-glibc/resolv -L/home/build/build-glibc/crypt
-L/home/build/build-glibc/linuxthreads
-Wl,-rpath-link=/home/build/build-glibc:/home/build/build-glibc/math:/home/b
uild/build-glibc/elf:/home/build/build-glibc/dlfcn:/home/build/build-glibc/n
ss:/home/build/build-glibc/nis:/home/build/build-glibc/rt:/home/build/build-
glibc/resolv:/home/build/build-glibc/crypt:/home/build/build-glibc/linuxthre
ads -Wl,--whole-archive /home/build/build-glibc/iconvdata/iso8859-1.os
/home/build/build-glibc/libc.so -Wl,--no-whole-archive