Re: Silo breakage creating woody r2 CDs for sparc

2003-12-01 Thread Steve McIntyre
On Tue, Dec 02, 2003 at 01:31:26AM +, Steve McIntyre wrote:
>
>
>We're late getting the r2 images created, and changes to the packages
>that we need to use don't help. The script to make sparc CDs bootable
>contains the following:
>
>silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
># put the relevant parts of SILO boot loader
>(ar p $silo_deb data.tar.gz | \
>tar zxf - -C $inst/ ./boot/{cd,second}.b)
>
>This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
>a cd.b file at all, so the sparc build fails. Generally after an hour
>of frantic disk-thrashing. I don't know if the change to silo is
>deliberate or not, but for now I'm patching the script to use the bits
>out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
>need. If this is wrong, please shout!

Christ. This gets even better. Two more runs, and things are failing
further down the line. mkisofs now complains:

/usr/bin/mkisofs: No such file or directory. Invalid node - boot/second.b

I go looking for the reason, and I can't find one - the directory
boot1 is included in the command line, and that's where boot/second.b
lives. Why is it failing. Oh, I see - the options passed in

-silo-boot boot/second.b -s /boot/silo.conf -S boot/cd.b boot1

aren't being parsed properly. It seems that recent versions of mkisofs
don't support the -silo-boot option. And nobody has flagged this as a
problem AT ALL. I'm now trying again, hacking around this by using an
old woody version of mkisofs. FFS, this should not be necessary.

If this next attempted build fails, I'm going to abandon the sparc
images altogether, and recommend that woody r2 does not include sparc
CDs. Does anybody actually care in the SLIGHTEST about supporting
sparc CDs? It certainly doesn't look that way. It's now 2.30am here,
and I'm going to bed. I'll check in the morning if the CDs built, but
as it stands right now I'd be quite surprised...

-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Is there anybody out there?


signature.asc
Description: Digital signature


Silo breakage creating woody r2 CDs for sparc

2003-12-01 Thread Steve McIntyre


We're late getting the r2 images created, and changes to the packages
that we need to use don't help. The script to make sparc CDs bootable
contains the following:

silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
# put the relevant parts of SILO boot loader
(ar p $silo_deb data.tar.gz | \
tar zxf - -C $inst/ ./boot/{cd,second}.b)

This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
a cd.b file at all, so the sparc build fails. Generally after an hour
of frantic disk-thrashing. I don't know if the change to silo is
deliberate or not, but for now I'm patching the script to use the bits
out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
need. If this is wrong, please shout!

-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
We don't need no education.
We don't need no thought control.


signature.asc
Description: Digital signature


Re: /lib64/libc.so.6: unexpected reloc type 0x08

2003-12-01 Thread Ben Collins
On Mon, Dec 01, 2003 at 12:03:02PM -0500, Andy Dougherty wrote:
> I am currently running the "testing" distribution on an Ultra 10.
> A trivial compilation produces the following error message:
> 
> echo 'int main(void) { return 0; }' > x.c && gcc -o x x.c && ./x
> ./x: error while loading shared libraries: /lib64/libc.so.6: unexpected 
> reloc type 0x08
> 
> The relevant packages are:

See another post about fixing 64-bit with some temporary packages I
built.

You probably want 32-bit anyway, so try this instead:

echo 'int main(void) { return 0; }' > x.c && sparc32 gcc -o x x.c && ./x

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/



Re: default gcc on UltraSparc

2003-12-01 Thread Ben Collins
On Mon, Dec 01, 2003 at 01:55:09PM -0800, David S. Miller wrote:
> On Mon, 1 Dec 2003 15:08:20 -0500
> Ben Collins <[EMAIL PROTECTED]> wrote:
> 
> > > ./a.out: error while loading shared libraries: /lib64/libc.so.6: 
> > > unexpected reloc type 0x08
> > 
> > This was a bug in libc6-sparc64. It's fixed now (just update to the
> > latest).
> 
> Either it isn't really fixed or the archive I'm using does not
> have the new packages:
> 
> ? echo "main(){exit(0);}" >foo.c; gcc -o foo foo.c; ./foo
> ./foo: error while loading shared libraries: /lib64/libc.so.6: unexpected 
> reloc type 0x08
> ?
> 
> What archive did you get the fixed package from Ben?

My mistake. It's fixed in our CVS repo of the glibc packages, and I have
that build installed. Here's the two packages:

http://www.phunnypharm.org/pub/for/sparc-folks/

These will get fixed next time glibc gets built.

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/



Re: default gcc on UltraSparc

2003-12-01 Thread David S. Miller
On Mon, 1 Dec 2003 15:08:20 -0500
Ben Collins <[EMAIL PROTECTED]> wrote:

> > ./a.out: error while loading shared libraries: /lib64/libc.so.6: unexpected 
> > reloc type 0x08
> 
> This was a bug in libc6-sparc64. It's fixed now (just update to the
> latest).

Either it isn't really fixed or the archive I'm using does not
have the new packages:

? echo "main(){exit(0);}" >foo.c; gcc -o foo foo.c; ./foo
./foo: error while loading shared libraries: /lib64/libc.so.6: unexpected reloc 
type 0x08
?

What archive did you get the fixed package from Ben?



Re: default gcc on UltraSparc

2003-12-01 Thread Ben Collins
> ./a.out: error while loading shared libraries: /lib64/libc.so.6: unexpected 
> reloc type 0x08

This was a bug in libc6-sparc64. It's fixed now (just update to the
latest).

> > Anyhow, you can override this easily by prepeding your build commands
> > with the sparc32 command. E.g.
> > 
> > # sparc32 ./configure
> > # sparc32 make
> > 
> > I've also added a "permanent" override that will be coming in the next,
> > for those that wish to do a system-wide override. You can just touch
> > /etc/disable_64_gcc, and all the defaults will be -m32.
> This is good to know. Thanks for your fast reply. This is what I need to 
> build debian-compliant packes, right?
> 
> Best regards,

Yes.

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/



/lib64/libc.so.6: unexpected reloc type 0x08

2003-12-01 Thread Andy Dougherty
I am currently running the "testing" distribution on an Ultra 10.
A trivial compilation produces the following error message:

echo 'int main(void) { return 0; }' > x.c && gcc -o x x.c && ./x
./x: error while loading shared libraries: /lib64/libc.so.6: unexpected 
reloc type 0x08

The relevant packages are:

Package: gcc
Version: 4:3.3.1-2
(though gcc itself reports "gcc version 3.3.2 (Debian)")

Package: libc6-sparc64
Version: 2.3.2.ds1-10

I know how to work around the problem with the sparc32 command or
with the -m32 option to gcc, and those are fine as temporary
workarounds, but is there something wrong with my setup?

If others are seeing this, does anyone know what the error message
means and how to go about fixing it?

Thanks,

Andy Dougherty  [EMAIL PROTECTED]



Re: default gcc on UltraSparc

2003-12-01 Thread Wolfram Quester
On Mon, Dec 01, 2003 at 10:03:01AM -0500, Ben Collins wrote:
> On Mon, Dec 01, 2003 at 11:47:48AM +0100, Wolfram Quester wrote:
> > Hi alltogether!
> > 
> > gcc produces 64Bit executables by default on UltraSparc.
> > I consider this a broken behaviour since many debian-packages don't
> > build any longer:
> > [EMAIL PROTECTED]:~/src/sodipodi/sodipodi-0.32.uus.20031012$ fakeroot 
> > dpkg-buildpackage -us -uc
> > 
> > checking build system type... sparc64-unknown-linux-gnu
> > checking host system type... sparc64-unknown-linux-gnu
> > checking for style of include used by make... GNU
> > checking for gcc... gcc
> > checking for C compiler default output file name... a.out
> > checking whether the C compiler works... configure: error: cannot run C 
> > compiled programs.
> > If you meant to cross compile, use `--host'.
> > See `config.log' for more details.
> > 
> > IMHO, gcc should default to -m32. If it really should default to -m64
> > then this should only be done if all libs are 64Bit-compliant.
> 
> I'd be interested in the error in config.log

Here it is:
configure:2514: $? = 0
configure:2516: gcc -v &5
Reading specs from /usr/lib/gcc-lib/sparc-linux/3.3.2/specs
Configured with: ../src/configure -v 
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
--mandir=/usr/share/man --infodir=/usr/share/info 
--with-gxx-include-dir=/usr/inc
lude/c++/3.3 --enable-shared --with-system-zlib --enable-nls 
--without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu 
--enable-debug --enable-java-gc=boehm --enable-java-awt=xlib
 --with-cpu=v7 --enable-objc-gc sparc-linux
Thread model: posix
gcc version 3.3.2 (Debian)
configure:2519: $? = 0
configure:2521: gcc -V &5
gcc: couldn't run `sparc-linux-gcc--m64': No such file or directory
configure:2524: $? = 1
configure:2547: checking for C compiler default output file name
configure:2550: gcc -O2   conftest.c  >&5
configure:2553: $? = 0
configure:2599: result: a.out
configure:2604: checking whether the C compiler works
configure:2610: ./a.out
./a.out: error while loading shared libraries: /lib64/libc.so.6: unexpected 
reloc type 0x08
configure:2613: $? = 127
configure:2622: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

> 
> Anyhow, you can override this easily by prepeding your build commands
> with the sparc32 command. E.g.
> 
> # sparc32 ./configure
> # sparc32 make
> 
> I've also added a "permanent" override that will be coming in the next,
> for those that wish to do a system-wide override. You can just touch
> /etc/disable_64_gcc, and all the defaults will be -m32.
This is good to know. Thanks for your fast reply. This is what I need to 
build debian-compliant packes, right?

Best regards,

Wolfi

> 
> 
> -- 
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> WatchGuard - http://www.watchguard.com/
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

-- 


pgp5CBx9poFda.pgp
Description: PGP signature


Re: default gcc on UltraSparc

2003-12-01 Thread Ben Collins
On Mon, Dec 01, 2003 at 11:47:48AM +0100, Wolfram Quester wrote:
> Hi alltogether!
> 
> gcc produces 64Bit executables by default on UltraSparc.
> I consider this a broken behaviour since many debian-packages don't
> build any longer:
> [EMAIL PROTECTED]:~/src/sodipodi/sodipodi-0.32.uus.20031012$ fakeroot 
> dpkg-buildpackage -us -uc
> 
> checking build system type... sparc64-unknown-linux-gnu
> checking host system type... sparc64-unknown-linux-gnu
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... configure: error: cannot run C 
> compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
> 
> IMHO, gcc should default to -m32. If it really should default to -m64
> then this should only be done if all libs are 64Bit-compliant.

I'd be interested in the error in config.log

Anyhow, you can override this easily by prepeding your build commands
with the sparc32 command. E.g.

# sparc32 ./configure
# sparc32 make

I've also added a "permanent" override that will be coming in the next,
for those that wish to do a system-wide override. You can just touch
/etc/disable_64_gcc, and all the defaults will be -m32.


-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/



Trouble with Installation over NFS

2003-12-01 Thread Carsten Friede

Hi!

I've recently bought a SPARCstation 20. So I wished to get a Linux 
running on it. Debian seemed to me the best choice.
I went all the way through the installation procedure using Root-NFS 
from another Debian box(that SPARC thingy has to run diskless, because 
of lacking a SCA-SCSI hard drive). All works fine. The images boots, the 
installation comes up, but when it reaches the point from where the 
package drivers.tgz is meant to be installed, is reports that there was 
an error with it. I found out, that something with bad headers may be 
the root cause for this.
First I thought some part of the file had been broken during copying, 
but when I changed the installation source (cdrom, mounted fs, nfs, ftp) 
the same error occurred. Next I tried was repacking the archive but it 
didn't help either. I'm nearly desperated now, wasting my time with 
those stupid things. Does anybody know, how I can get this fixed?

Thanks in advance for any kind of help.

Cya!

Carsten Friede

--
==
Dresden University of Technology
Department of Computer Science
Dresden, Germany
==



Console problem at Enterprise 3000

2003-12-01 Thread Carlos Emir M. Macedo
Hi,

I've recently installed Debian Woody at an Sparc Enterprise 3000. 
Everything went ok, except the console. It works fine at default 
installation, but after kernel recompilation, I can´t useit (tty1 to tty6) 
anymore. I can logon through ssh. No reported errors at system logs.
I've been working with Debian for a long time, but never with 
Sparc platform. Could someone help me?
Thanks in advance.

=
Carlos Emir Mantovani Macedo
Technical Support
Tecnologia Bancária S.A.
+55 11 3244-1900 R. 8817
[EMAIL PROTECTED]
http://www.tecban.com.br
=

As informações existentes nessa mensagem são para uso restrito, sendo seu 
sigilo protegido por lei. Caso não seja destinatário, saiba que leitura, 
divulgação ou cópia são proibidas.
Favor apagar as informações e notificar o remetente. O uso impróprio será 
tratado conforme as normas da empresa e a legislação em vigor.

The informations contained in this message are restricted, and its 
confidentiality protected by law. In case you are not theaddressee, be 
aware that the reading, spreading and copy of this message is 
unauthorized.
Please, delete this message and notify the sender. The improper use of 
this information will be treated according the company's internal rules 
and legal laws.



default gcc on UltraSparc

2003-12-01 Thread Wolfram Quester
Hi alltogether!

gcc produces 64Bit executables by default on UltraSparc.
I consider this a broken behaviour since many debian-packages don't
build any longer:
[EMAIL PROTECTED]:~/src/sodipodi/sodipodi-0.32.uus.20031012$ fakeroot 
dpkg-buildpackage -us -uc

checking build system type... sparc64-unknown-linux-gnu
checking host system type... sparc64-unknown-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C 
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

IMHO, gcc should default to -m32. If it really should default to -m64
then this should only be done if all libs are 64Bit-compliant.

Best regards,

Wolfi

-- 


pgpgRl0L57A51.pgp
Description: PGP signature