Em Sat 12 Mar 2005 17:43, Michael escreveu:
> the third time I booted expert video=ofonly and that went fine. I went
> to execute shell script and everything worked fine.
>
> So my question is what is video=ofonly doing? And should I just do a
> net install of sarge using this, and is that even p
The gcc build currently uses the output of "gcc print-multi-os-directory" to
detect if the output from gcc is 64 or 32 bits. This fails when the 32 bits
libraries are not installed in /lib or the 64 bits ones in /lib64.
The attached "detect-output-format.dpatch" replaces that test with one that
I have successfully build a multiarch gcc in a ppc64. To do so I made some
changes to Andreas patch:
1) move powerpc64*-*-* before powerpc*-*-* in src/config-ml.in to make sure
the correct option is executed.
2) use /lib32/ld.so.1 as the 32 bits linker
3) fix the "bispecs" target in t-linux64 (
Hi, I have done some work on porting debian to the powerpc64. The original
post:
http://lists.debian.org/debian-powerpc/2004/10/msg00193.html
I also made some bug reports to add support for the powerpc architecture. One
missing is the one against dpkg
(http://bugs.debian.org/cgi-bin/bugreport.c
Em Qui 04 Nov 2004 06:58, Helge Kreutzmann escreveu:
> Hello,
> my current 64bit machine is reaching EOL and I am looking for a
> replacement. One option I seriously consider is using the current
> 64bit machines from Apple.
>
> Debian is only 32bit on all PPC machines, correct? And according to
>
I have compiled a self-hosting 64 bit debian in a ibm pseries. It can be
download from:
ftp.las.ic.unicamp.br:/pub/debian-ppc64/debian-ppc64.tar.bz2
The biggest problem by now is in linking libpng. The linker is failing with
"unresolvable R_PPC64_REL24 relocation against symbol
`.png_malloc_def
I have used a gentoo install to compile many debian packages in a ibm pseries
machine. All the binaries are 64 bit. In the process I have submitted some
bug-reports asking for powerpc64-support: 263743, 268076, 268078
The bootstrap procedure is:
compile libc in /trans
compile "debian" in / but l
On Friday 17 September 2004 09:28, Jens Schmalzing wrote:
> If you got as far as installing the base system, you can "Execute a
> shell" from the main menu and chroot into your newly installed system.
> Then you can get the bootloader running manually. If you think this
> should be fixed, make sur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Qua 25 Ago 2004 10:12, Frederik Dannemare escreveu:
> Hi,
...
>
> I will not be able to test again on a B50 for some time, unfortunately,
> but let me know if you want me to try a different way of booting it (or
> other suggestions) the next time, I
On Wednesday 18 August 2004 09:34, Michael Flaig wrote:
> Hi,
>
> does anyone else have problem with latest unstable apache2?
Sory, it is:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266372
> Thanks,
>
> mfl
Rafael
On Wednesday 18 August 2004 09:34, Michael Flaig wrote:
> Hi,
>
> does anyone else have problem with latest unstable apache2?
Yes:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=260927
> Thanks,
>
> mfl
Good luck,
Rafael
I am building some cross-compilers using the crosstool scripts
(http://kegel.com/crosstool/) and I think that they are generally useful to
Debian.
I have a new version that is based on crosstool 0.28-rc32 and also has a SPARC
cross-compiler. I don't have access to any other architecture to test
Em Monday 09 August 2004 19:56, Shaul Karl escreveu:
> I only tried cross compilation tools for a short time. I droped it
> due to the amount of work that was required to get the deb that I was
> interesting in cross compiled. Still, have you looked at dpkg-cross and
> the toolchain-source debs?
I am building some cross-compilers using the crosstool scripts
(http://kegel.com/crosstool/) and I think that they are generally useful to
Debian.
The source package is name crosstool and it produces the gcc-powerpc and
gcc-powerpc64 packages. Should add more as soon as possible.
The crosstoll
To boot a IBM pseries (at least the b50) from the cdrom it is necessary to:
1) create a directory /etc in the cdrom and put a yaboot.conf in it
2) use cdrom instead of cd in the device line in yaboot.conf
3) create a /ppc/bootinfo.txt with
Debian GNU/Linux
Debian GNU/Linux
boot &device;:\boot\ya
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Sunday 08 August 2004 15:20, Rogério Brito escreveu:
>
> Thank you very much. I was fearing that it could be a sign of data
> corruption, but I am much happier knowing that it is only a problem with
> case sensitiveness.
>
> Anyway, it seems that ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Who is responsible for building the iso images? debian-installer or debian-cd?
I notice the the rc1 image for the powerpc does not have a chrp partition. It
is necessary to boot some p-series machines. For more detains see
http://lists.debian.org/deb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Saturday 07 August 2004 18:37, Rogério Brito escreveu:
> But the compilation still failed near the linking phase (it complained
> about symbols related to jiffies not being found). I don't know what
> could be the cause of the problem, but I suspect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Friday 30 July 2004 05:13, Cajus Pollmeier escreveu:
> Btw - I tried the debian installer for ppc, but that machine seems to
> accept 64bit code on bootup, only.
Indeed. The following thread might be usefull:
http://lists.debian.org/debian-boot/200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Thursday 29 July 2004 20:39, you wrote:
> Rafael Ávila de Espíndola wrote:
> Thanks. Are the extra patches inside your attached patch good
> enough to contribute back to gcc mainline?
> e.g. would it be sensible to do
>mv debia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Wednesday 28 July 2004 01:09, Dan Kegel escreveu:
>
> OK. (For what it's worth, I'm also interested in supporting .deb's,
> and Debian has a similar wide range of platforms.)
I have done some work on generating debian cross-compilers. Currently I
I have successfully created a minimal package with a ppc64 cross-compiler. It
uses the crosstool script (http://kegel.com/crosstool/) to do the real work.
To build it:
1)create a directory named crosstool-0.28-rc29 and place the following files
in it:
binutils-2.15.tar.bz2
crosstool-0.28-rc29.ta
I was able to compile a 64 kernel debian package. The steps:
1)apply the attached patches to dpkg and kernel-package, compile and install
2)install a cross-compiler (use http://kegel.com/crosstool/)
3)apt-get install kernel-patch-powerpc-2.6.7 (don't know if it is necessary)
4)
export INITRD_OK=1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Saturday 10 July 2004 11:55, Sean Schertell escreveu:
> I tried this:
> linux root=/dev/hda11
>
> But still no joy...
Boot with the cdrom, mount /dev/hda11 and chroot into it. Now you may
"apt-get install" a kernel.
Good luck.
Rafael
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
(BHash: SHA1
(B
(BEm Saturday 10 July 2004 11:09, Sean Schertell escreveu:
(B> Oh man.. This just keeps getting dumber :-(
(B>
(B> You were right Sebyte, I needed to use your ISO, not the one I had. So I
(B> was able to mount my fs, but then in an effort t
25 matches
Mail list logo
