Hello,
On Sun, 2024-12-01 at 15:28 +0100, Jan Montag wrote:
> Am 30.11.24 um 23:03 schrieb Ken Cunningham:
>
> > I realize I could sort it out, but doing these kinds of things always
> > takes a lot of time to get organized, so if anyone cares to share the
> > step-by-step process, it would be gr
On Sat, 2024-11-30 at 14:03 -0800, Ken Cunningham wrote:
> If anyone goes through all the steps to get to the point where they could
> try building Firefox on one of these builders through to completion, and
> perhaps downloading it to their local machine for testing, I would very
> much appreciate
Hi Ken
Am 30.11.24 um 23:03 schrieb Ken Cunningham:
I realize I could sort it out, but doing these kinds of things always takes a
lot of time to get organized, so if anyone cares to share the step-by-step
process, it would be great.
I am really interested, too.
--
Herzlichst Jan Montag
via
st, I give them a try because it
sounds clever ^^
Thank you,
Jan
Hi Jan,
I don't recommend using an old PowerMac for building anything as big as
Firefox. Rather, I'd recommend either requesting an instance running
Debian ppc64 (big-endian) on the OpenPOWER platform [1] or getting an
a
0 +0100, John Paul Adrian Glaubitz wrote:
>> I don't recommend using an old PowerMac for building anything as big as
>> Firefox. Rather, I'd recommend either requesting an instance running
>> Debian ppc64 (big-endian) on the OpenPOWER platform [1] or getting an
>> ac
Hi,
On Sat, 2024-11-30 at 17:20 +0100, John Paul Adrian Glaubitz wrote:
> I don't recommend using an old PowerMac for building anything as big as
> Firefox. Rather, I'd recommend either requesting an instance running
> Debian ppc64 (big-endian) on the OpenPOWER platfor
he problem of not
> having the time or not having the hardware or to be frustrated because
> nothing works.
I don't recommend using an old PowerMac for building anything as big as
Firefox. Rather, I'd recommend either requesting an instance running
Debian ppc64 (big-endian)
Hi Adrian,
I am with you,
I tried to apply the patches provided by solaris, I tried to compile but
on the Powermac itself it lasts three days to compile with the end of
did'nt successfully compiled. I do understand now the problem of not
having the time or not having the hardware or to be frus
On Mon, Nov 18, 2024 at 03:43:28PM +0100, Jan Montag wrote:
> I also keep trying to compile or install a current
> browser. Unfortunately this doesn't work for reasons I don't
> understand. How has this progressed? The current version of Firefox
> is 132.0.0.2 and still produces the memory access
Hi,
John Paul Adrian Glaubitz wrote:
[1]https://github.com/oracle/solaris-userland/tree/master/components/desktop/firefox/patches
interesting set... I recognize one:
https://github.com/oracle/solaris-userland/blob/master/components/desktop/firefox/patches/firefox-53-sparc-gfx-atomicops.patch
Hi,
Jan Montag wrote:
since I just bought a Powermac G5 (powermac11.2) Dual 2 GHz, I'm
running Debian 12 SID on it. I also keep trying to compile or install a
current browser. Unfortunately this doesn't work for reasons I don't
understand. How has this progressed? The current version of Firefox
Hello John,
thank you very much for your quick feedback. My question
was not intended as criticism, you shouldn't misunderstand that. But
since the topic was already a year old, I was interested to see if
there were any new findings. SeaLion is an exciting thing and it works.
Otherwise, the Power
Hi Jan,
On Mon, 2024-11-18 at 15:43 +0100, Jan Montag wrote:
> since I just bought a Powermac G5 (powermac11.2) Dual 2 GHz, I'm
> running Debian 12 SID on it. I also keep trying to compile or install a
> current browser. Unfortunately this doesn't work for reasons I don't
> understand. How has thi
Hello,
since I just bought a Powermac G5 (powermac11.2) Dual 2 GHz, I'm
running Debian 12 SID on it. I also keep trying to compile or install a
current browser. Unfortunately this doesn't work for reasons I don't
understand. How has this progressed? The current version of Firefox is
132.0.0.2 and
Hi Adrian,
I’m getting stuck building firefox, and as you’re building it already, how do
we get past this?
thanks,
Ken
I did this:
$ apt-get build-dep firefox
$ apt source firefox
$ apt install python-is-python3
$ cd firefox-120.0
$ dpkg-buildpackage -us -uc
but I keep getting this:
——
Hi!
On Thu, 2023-11-23 at 23:45 +0100, kristoffer...@tuta.io wrote:
>
> Deeper debugging is beyond my skills. I don't know if this helps but the "bt"
> command gave me this:
>
> (gdb) bt
> #0 i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
> #1 w2c_rlbox_streqci (var_p0=var_p0@entry=2
Deeper debugging is beyond my skills. I don't know if this helps but the "bt"
command gave me this:
(gdb) bt
#0 i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
#1 w2c_rlbox_streqci (var_p0=var_p0@entry=262000, var_p1=2016478208,
instance=) at rlbox.wasm.c:1499
#2 0x7fffe91969a8 in
Am Donnerstag, dem 23.11.2023 um 09:01 +0100 schrieb Johannes
Brakensiek:
> Crashdump was attached.
Backtrace, to be more precise.
Johannes
Hi,
Am Mittwoch, dem 22.11.2023 um 10:18 +0100 schrieb
kristoffer...@tuta.io:
> I caught this today thru gdb and Firefox 120.0-1 on my dual G5:
>
> Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
> i32_load8_u (addr=2016478208, mem=) at
> rlbox.wasm.c:146
> 146 rlbox.wasm.c: No su
Hi,
I caught this today thru gdb and Firefox 120.0-1 on my dual G5:
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146
146 rlbox.wasm.c: No such file or directory.
Regards,
Kris
--
Wysyłano z Tuta, ciesz się bezpiecznymi i
Hi!
On Tue, 2023-11-21 at 22:05 +0100, Johannes Brakensiek wrote:
> Am Dienstag, dem 21.11.2023 um 21:20 +0100 schrieb John Paul Adrian
> Glaubitz:
> >
> > Please test this build which include the image decoder big-endian fix
> > from VoidPPC:
> >
> > > https://people.debian.org/~glaubitz/firefo
Hi Adrian,
Am Dienstag, dem 21.11.2023 um 21:20 +0100 schrieb John Paul Adrian
Glaubitz:
>
> Please test this build which include the image decoder big-endian fix
> from VoidPPC:
>
> > https://people.debian.org/~glaubitz/firefox-ppc64/test002/
>
> Adrian
>
thanks for providing the binary. It
On Tue, 2023-11-21 at 20:38 +0100, John Paul Adrian Glaubitz wrote:
> I have just been reminded by a comment in the upstream bug report [1] that
> the VoidPPC
> project actually has a number of patches which fix issues in Firefox on
> PowerPC [2] and
> I'm rebuilding Firefox with this patch [3] n
Hi!
On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
> There is currently no up-to-date version of Firefox for 32-bit PowerPC since
> Firefox
> currently requires NodeJS to build which is not available on 32-bit PowerPC
> at the
> moment.
>
> It is actually possible, however,
On Tue, 2023-11-21 at 08:32 -0800, Ken Cunningham wrote:
> I added an 8GB swapfile, and (slowly) got this backtrace:
>
> # cat error.txt
> Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
> i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146
> 146 rlbox.wasm.c: No such file or
I added an 8GB swapfile, and (slowly) got this backtrace:
# cat error.txt
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146
146 rlbox.wasm.c: No such file or directory.
(gdb) bt
#0 i32_load8_u (addr=2014643200, mem=) at rlb
Trying to run firefox under gdb with the debug symbols installed appears to
result in an out-of-memory situation on my DualG5 with 3.5GB ram, I’m afraid.
Perhaps someone else has a system with more memory, or set up better than mine,
that could help.
Ken
-
$ gdb firefox
GNU gdb (Debian 13.2-1
To be honest, I did run it under gdb, and ran the backtrace, but the backtrace
was mostly uninterpretable without the debug symbols of course.
So somewhere in libxul was all I could offer.
I’ll see if adding the debug symbols narrows it down a bit.
Ken
> On Nov 21, 2023, at 02:13, John Paul Ad
Hello!
On Mon, 2023-11-20 at 15:39 -0800, Ken Cunningham wrote:
> on my system I had another segfault, in libxul.
A more detailed backtrace would be useful. libxul is basically all of
Firefox, so referring to a crash in libxul is not saying much.
Try installing the debug package from here:
> ht
> On Nov 20, 2023, at 12:37 PM, Jeffrey Walton wrote:
>
> On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
> wrote:
>>
>> On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
>>
On Nov 20, 2023, at 10:56 AM, Jeroen Diederen
wrote:
Firefox does not work.
>>>
>>>
On 2023-11-20, at 3:21 PM, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
>> Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder
>> whether
>> it might be fixed by this particular patch [3].
>
> I have rebuild the
On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote:
> Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder
> whether
> it might be fixed by this particular patch [3].
I have rebuild the Firefox package for ppc64 with this patch included:
> https://people.d
Hi Jeffrey!
On Mon, 2023-11-20 at 15:37 -0500, Jeffrey Walton wrote:
> On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
> wrote:
> >
> >
> > The one I have installed is:
> >
> > firefox/unstable,now 119.0.1-1 ppc64
> >
> > and it has a segmentation fault when you launch it.
>
> Out of curiosit
On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham
wrote:
>
> On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
>
> >> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen
> >> wrote:
> >>
> >> Firefox does not work.
> >
> > Did you try the latest version 119?
> >
> > If there is a patch which fi
On 2023-11-20, at 2:06 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
>> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote:
>>
>> Firefox does not work.
>
> Did you try the latest version 119?
>
> If there is a patch which fixes the crash on big-endian targets, we could
> include it in
Hello!
> On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote:
>
> Firefox does not work.
Did you try the latest version 119?
If there is a patch which fixes the crash on big-endian targets, we could
include it in the Debian package or I could try to get it merged upstream.
Adrian
Hi Adrian,
Firefox does not work.
Regards,
Jeroen
John Paul Adrian Glaubitz schreef op 2023-11-20 13:01:
On Sun, 2023-11-19 at 16:46 -0800, Ken Cunningham wrote:
Does anyone have or know about a browser they use on debian
ppc64 they would feel comfortable to recommend?
Firefox is available
on. :)
> Does anyone have or know about a browser they use on debian ppc64 they would
> feel comfortable to recommend?
Of course I use ArcticFox on PPC. Since version 43.0 it works again on PPC.
It is "only" AF though, don't expect Firefox 118 compatibility. No
github or fac
On Sun, 2023-11-19 at 16:46 -0800, Ken Cunningham wrote:
> Does anyone have or know about a browser they use on debian
> ppc64 they would feel comfortable to recommend?
Firefox is available and up to date for ppc64.
> https://buildd.debian.org/status/package.php?p=firefox&suite=sid
a few different browsers inside debian (Firefox,
> Epiphany).
>
> Does anyone have or know about a browser they use on debian ppc64 they would
> feel comfortable to recommend?
>
> Does it involve any installation trickery? If so, some short notes on how to
> get it installed would be appreciated.
>
> Thanks,
>
> Ken
>
>
es available, and I think there are
> some official channels for a few different browsers inside debian (Firefox,
> Epiphany).
>
> Does anyone have or know about a browser they use on debian ppc64 they
> would feel comfortable to recommend?
>
> Does it involve any installation
debian ppc64 they would
feel comfortable to recommend?
Does it involve any installation trickery? If so, some short notes on how to
get it installed would be appreciated.
Thanks,
Ken
On 10/26/20 5:30 PM, Lennart Sorensen wrote:
> On Mon, Oct 26, 2020 at 05:04:48PM +0100, John Paul Adrian Glaubitz wrote:
>> I had to re-read this several times and just to be clear: You can still
>> run big-endian code perfectly fine on POWER8 machines and newer (unless
>> IBM removed support with
On Mon, Oct 26, 2020 at 05:04:48PM +0100, John Paul Adrian Glaubitz wrote:
> I had to re-read this several times and just to be clear: You can still
> run big-endian code perfectly fine on POWER8 machines and newer (unless
> IBM removed support with POWER10).
You can, but it seems very few people
On 10/26/20 4:55 PM, Lennart Sorensen wrote:
> And it seems power8+ machines really just run ppc64el because that is
> what IBM wants people to run (apparently because converting the data from
> big endian to little endian before passing it to an nvidia GPU that only
> does little endian made a sig
On Sun, Oct 25, 2020 at 03:30:05PM -0300, Alexandre Bencz wrote:
> well...
>
> this is quite interesting, even for use on Power7 servers ... I have several
> clients that use Debian on P7 and P6 so, having a compilation that uses
> the latest CPU instructions, would be interesting
Right, so
On 25th of October 2020 Carlos Rodrigues wrote:
Newer servers, such as Power8 and Power9 support BE operating systems,
including Debian ... the problem is that Debian PPC64 is compiled to be
compatible with older servers (power4 standard), it is possible to
generate a release of Debian PPC64 BE
Glaubitz wrote:
Hello Carlos!
On 10/25/20 6:49 PM, Carlos Rodrigues wrote:
Newer servers, such as Power8 and Power9 support BE operating systems,
including Debian ...
the problem is that Debian PPC64 is compiled to be compatible with older
servers (power4
standard), it is possible to generate a
Hello Carlos!
On 10/25/20 6:49 PM, Carlos Rodrigues wrote:
> Newer servers, such as Power8 and Power9 support BE operating systems,
> including Debian ...
> the problem is that Debian PPC64 is compiled to be compatible with older
> servers (power4
> standard), it is possibl
Newer servers, such as Power8 and Power9 support BE operating systems,
including Debian ... the problem is that Debian PPC64 is compiled to be
compatible with older servers (power4 standard), it is possible to
generate a release of Debian PPC64 BE, using Power8 standards (I mean
newer
Hi Adrian,
that issue
https://bugzilla.mozilla.org/show_bug.cgi?id=1269654
was never fixed, i reported many months ago (or year) and just made firefox
slower but is not making the crash.
Im using right now for writing here firefox 47 (with that issue present) from
ubuntu but no problems just
On 10/22/2017 10:45 AM, luigi burdo wrote:
> probably this small report can made understand one of the reason why firefox
> crash on debian PPC64.
> (...)
> look like the issue come on debian because a pipe error.
No, it isn't. The log messages you provide don't reveal any
I Adrian,
probably this small report can made understand one of the reason why firefox
crash on debian PPC64.
Plus i made an experiment yesterday
On this last sid i installed one of my archived firefox esr 45.x ( from old
debian sid archive) that is working on others ppc64 distros (fedora
Hello,
Yesterday, at MiniDebConf Curitiba 2017, we announced that our free
"POWER Minicloud" has support and images available for ppc64 port,
besides the traditional ppc64el.
The naming scheme is a little bit weird, but Debian 8 BE means ppc64,
and LE means ppc64el.
http://openpower.ic.unicamp.b
* szukw...@arcor.de [2015-06-19 17:32 +]:
> On Fri, 19 Jun 2015 16:17:14 +0200, Elimar Riesebieter wrote:
>
> >What tells (as root)
> >
> ># fdisk -l /dev/sdb
>
> root@g5:~# fdisk -l /dev/sdb
>
> Disk /dev/sdb: 58,9 GiB, 63216549888 bytes, 123469824 sectors
> Units: sectors of 1 * 512 = 51
On Fri, 19 Jun 2015 16:17:14 +0200, Elimar Riesebieter wrote:
>What tells (as root)
>
># fdisk -l /dev/sdb
root@g5:~# fdisk -l /dev/sdb
Disk /dev/sdb: 58,9 GiB, 63216549888 bytes, 123469824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O si
* szukw...@arcor.de [2015-06-19 16:01 +]:
> I had installed ppc64 7.6.0. Now I have installed 8.1.0.
>
> Some images were stored on a USB stick. This USB stick
> I had inserted when I installed 8.1.0.
>
> Unfortunately this stick now seems to be reformatted: the
> type is no longer FAT32. I
I had installed ppc64 7.6.0. Now I have installed 8.1.0.
Some images were stored on a USB stick. This USB stick
I had inserted when I installed 8.1.0.
Unfortunately this stick now seems to be reformatted: the
type is no longer FAT32. I do not know which type it is:
trying to mount with different
>
> Hmmm,
> I didn't consider for qemu.
> It may be inconvenience that it cannot use as an image of qemu.
>
> About not supporting for POWER4/5 machines, it is intentional on this time
> powerpc port already existing.
>
>
> >>According Debian ppc64 w
werpc ML, and for making sure,
please add pp...@debian-ports.org (ppc64 buildd maintainers of Debian Ports) to
CC.
Lennart Sorensen wrote:
On Sat, Feb 16, 2013 at 12:07:09AM +0800, Liang Guo wrote:
I'm working to run Debian ppc64 ports on my xbox360 box, but
failed to setup a chrooted e
On Sat, Feb 16, 2013 at 12:07:09AM +0800, Liang Guo wrote:
> I'm working to run Debian ppc64 ports on my xbox360 box, but
> failed to setup a chrooted environment with "Illegal instruction"
> error. After some dig on this problem, I found this is caused
> by PowerP
Hi, List,
I'm working to run Debian ppc64 ports on my xbox360 box, but
failed to setup a chrooted environment with "Illegal instruction"
error. After some dig on this problem, I found this is caused
by PowerPC vector instrunctions, and according to the build
log[1], the package
On 10/5/10, Thibaut VARÈNE wrote:
>
> Are you a Gentoo user? ;^P
>
No because I do not have the steady internet needed and besides I
would wish to do custom build as a group. But I know what you mean
Gentoo lets you auto build everything yourself from scratch.
Its a pain besides that's why I pref
Le 5 oct. 10 à 05:32, Brian Morris a écrit :
On 10/4/10, Wartan Hachaturow wrote:
The same reasoning as before applies -- why would you want to do
this?
What are the benefits compared to multiarch ppc32/ppc64?
If you are using double precision floating point, the speed of a
program comp
Le Tue, Oct 28, 2008 at 06:36:16PM +0100, Christophe Lecerf a écrit :
>
> I experienced the same problem with a PPC G5 using LVM for /, /usr and other
> partitions.
Hi all,
just for the record, I made a minimal test install on a iMac G5 with the daily
build installer for Lenny, using a ext3 /boo
Christophe Lecerf wrote:
Hello,
On Thu, 6 Mar 2008, FJP wrote:
So the installation went OK, but the reboot failed.
This looks like a kernel issue to me, although it could also be something
related to the bootloader or the initrd. Unfortunately there is very little
powerpc knowledge inside the
Hello,
On Thu, 6 Mar 2008, FJP wrote:
> So the installation went OK, but the reboot failed.
>
> This looks like a kernel issue to me, although it could also be something
> related to the bootloader or the initrd. Unfortunately there is very little
> powerpc knowledge inside the debian-installer t
On Friday 07 March 2008, Ulrich Enslin wrote:
> Since you are going to update the code, can you also check that you are
> catering for a
> IBM RS6000 (7026-H70) and
> IBM pseries 630 (7028-6C4).
The second already was supported, but I've updated the patch to also catch
the first. As Olof suggeste
On Fri, Mar 07, 2008 at 03:49:21PM +0200, Ulrich Enslin wrote:
> Hi Frans
>
> Since you are going to update the code, can you also check that you are
> catering for a
> IBM RS6000 (7026-H70) and
> IBM pseries 630 (7028-6C4).
>
> IBM RS6000 (7026-H70):
It would be a better catch-all to check for R
Hi Frans
Since you are going to update the code, can you also check that you are
catering for a
IBM RS6000 (7026-H70) and
IBM pseries 630 (7028-6C4).
IBM RS6000 (7026-H70):
~ # cat /proc/cpuinfo
processor : 0
cpu : RS64-II (northstar)
clock : 339.999568MHz
revision
tags 469030 + pending
thanks
On Friday 07 March 2008, Ulrich Enslin wrote:
> Frans Pop wrote:
> > On Friday 07 March 2008, Ulrich Enslin wrote:
> >> Using the rescue I booted into a chroot of the
> >> installed system. Installed the correct 64 bit kernel with 'aptitude
> >> install linux-image-2.6
Please find attached the '/var/log/installer/hardware-summary'.
Frans Pop wrote:
On Friday 07 March 2008, Ulrich Enslin wrote:
Using the rescue I booted into a chroot of the
installed system. Installed the correct 64 bit kernel with 'aptitude
install linux-image-2.6-powerpc64' and that solve
On Friday 07 March 2008, Ulrich Enslin wrote:
> Using the rescue I booted into a chroot of the
> installed system. Installed the correct 64 bit kernel with 'aptitude
> install linux-image-2.6-powerpc64' and that solved the problem.
>
> This does point to a bug in the installer though.
Yes, it does
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will re
Thanks all for your contributions.
As suggested, installing the correct kernel with 'aptitude install
linux-image-2.6-powerpc64' fixed the problem.
So just a quick summery, since I have not included all the correct recipients in
all the correspondence:
I installed debian 40r3 on a IBM Power
On Thursday 06 March 2008, Gaudenz Steinlin wrote:
> > Should the kernel not have a 64 somewhere in the name.
>
> Yes I think you have the wrong kernel installed. Try to install
> linux-image-2.6-powerpc64. Try "aptitude install
> linux-image-2.6-powerpc64" after booting into rescue mode and mounti
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will re
Hi
On Thu, Mar 06, 2008 at 04:19:29PM +0200, Ulrich Enslin wrote:
>
> I installed debian 40r3 on a IBM Power 620 (7025-f0) from CD
> (debian-40r3-powerpc-netinst.iso). The install was successful, but the
> system did not boot from the scsi disc, with the output shown below.
>
> Boot messages:
I installed debian 40r3 on a IBM Power 620 (7025-f0) from CD
(debian-40r3-powerpc-netinst.iso). The install was successful, but the
system did not boot from the scsi disc, with the output shown below.
Boot messages:
Welcome to yaboot version 1.3.13
Enter "help" to get some basic usage infor
On Sunday 02 March 2008, Ulrich Enslin wrote:
> I installed debian 40r3 on a IBM Power 620 (7025-f0). The install was
> successful, but the system did not boot from the scsi disc, with the
> output shown below.
>
> Welcome to yaboot version 1.3.13
> Enter "help" to get some basic usage information
On Thu, Sep 20, 2007 at 03:26:30PM -0400, Cesar Bello wrote:
> Hi, I'm looking for information about the implementations and projects for
> Debian on the Powerpc 64 bits servers. I'm working in a presentation about
> this topic, but I have troubles to find information about it.
>
> If someone know
Hi, I'm looking for information about the implementations and projects for
Debian on the Powerpc 64 bits servers. I'm working in a presentation about
this topic, but I have troubles to find information about it.
If someone knows were can I find
Thanks for your help
On Tue, Jun 07, 2005 at 07:48:43PM -0700, Shyamal Prasad wrote:
> "Sven" == Sven Luther <[EMAIL PROTECTED]> writes:
>
> Sven> On Sat, Jun 04, 2005 at 12:33:10PM -0700, Shyamal Prasad
> Sven> wrote:
>
> >> It works. But it is missing the fan control patches from the
> >> sarge
"Sven" == Sven Luther <[EMAIL PROTECTED]> writes:
Sven> On Sat, Jun 04, 2005 at 12:33:10PM -0700, Shyamal Prasad
Sven> wrote:
>> It works. But it is missing the fan control patches from the
>> sarge debian kernel, so my fans are going full blast.
Sven> Cool. Sorry about t
On Sat, Jun 04, 2005 at 12:33:10PM -0700, Shyamal Prasad wrote:
> "Sven" == Sven Luther <[EMAIL PROTECTED]> writes:
>
> Sven> On Sat, May 28, 2005 at 04:15:39PM +0200, Sven Luther wrote:
> >> Hello all,
> >>
> >> Thanks to the great job of Jeff Bailey and Matthias Klose, who
>
On Sat, Jun 04, 2005 at 08:07:35AM +0200, Sven Luther wrote:
> On Sat, May 28, 2005 at 04:15:39PM +0200, Sven Luther wrote:
> > Hello all,
> >
> > Thanks to the great job of Jeff Bailey and Matthias Klose, who provided a
> > set
> > of gcc-3.4/glibc-2.3.5 based biarch toolchain, i have managed to
On Sat, May 28, 2005 at 04:15:39PM +0200, Sven Luther wrote:
> Hello all,
>
> Thanks to the great job of Jeff Bailey and Matthias Klose, who provided a set
> of gcc-3.4/glibc-2.3.5 based biarch toolchain, i have managed to build a first
> ppc64 kernel package, which is available at :
>
> http:/
On Tue, Dec 21, 2004 at 06:56:18PM -0800, David Schleef wrote:
> On Mon, Dec 20, 2004 at 11:10:53PM +0100, Sven Luther wrote:
> > Actually, as i recall, the 64bit code should be slower, since all pointers
> > are
> > now 64bit, and thus you have to transfer double amount of code from the ram
> > a
On Tue, 2004-12-21 at 18:56 -0800, David Schleef wrote:
> I can really only think of two cases where 64-bit code could be
> faster (not that it _would_ be in practise) -- 1) arithmetic on
> 64-bit types, and 2) optimized versions of strlen().
>
> All in all, I'd consider it a wash, and would not
On Mon, Dec 20, 2004 at 11:10:53PM +0100, Sven Luther wrote:
> Actually, as i recall, the 64bit code should be slower, since all pointers are
> now 64bit, and thus you have to transfer double amount of code from the ram
> and so on.
AIUI, 64-bit powerpc code is generally only slightly larger than
Sven Luther wrote:
On Mon, Dec 20, 2004 at 01:59:44PM -0800, Joaquin Menchaca wrote:
Benjamin Herrenschmidt wrote:
On Sun, 2004-12-19 at 13:50 +0100, Andreas Jochens wrote:
It is of course true that some other distributions put 32 bit libraries
in /usr/lib and 64 bit librar
On Mon, Dec 20, 2004 at 01:59:44PM -0800, Joaquin Menchaca wrote:
> Benjamin Herrenschmidt wrote:
>
> >On Sun, 2004-12-19 at 13:50 +0100, Andreas Jochens wrote:
> >
> >
> >
> >>It is of course true that some other distributions put 32 bit libraries
> >>in /usr/lib and 64 bit libraries in /usr/lib
Benjamin Herrenschmidt wrote:
On Sun, 2004-12-19 at 13:50 +0100, Andreas Jochens wrote:
It is of course true that some other distributions put 32 bit libraries
in /usr/lib and 64 bit libraries in /usr/lib64. I will not follow that
path because for a native 64 bit distribution this will lea
> > I'm still rather unsure of the interest of having the ppc64 distribution
> > be native... Unlike amd64, as I wrote several times, there is no benefit
> > as in more registers etc... All you'll get is bigger/slower code...
>
> What about power3/power4 optimized code, in opposition to generic p
On Sun, Dec 19, 2004 at 03:40:08PM +0100, Benjamin Herrenschmidt wrote:
> On Sun, 2004-12-19 at 13:50 +0100, Andreas Jochens wrote:
>
> > It is of course true that some other distributions put 32 bit libraries
> > in /usr/lib and 64 bit libraries in /usr/lib64. I will not follow that
> > path bec
On Sun, 2004-12-19 at 13:50 +0100, Andreas Jochens wrote:
> It is of course true that some other distributions put 32 bit libraries
> in /usr/lib and 64 bit libraries in /usr/lib64. I will not follow that
> path because for a native 64 bit distribution this will lead to an
> almost empty /usr/li
On 04-Dec-19 10:27, Benjamin Herrenschmidt wrote:
> Which means you'll have a different directory layout that all other
> ppc64 distros ...
Gentoo uses basically the same directory layout as the experimental
ppc64 archive on alioth, with the exeception that 32 bit support is
not yet fully workin
On Sun, Dec 19, 2004 at 12:31:51PM +, Martin Michlmayr wrote:
> * Sven Luther <[EMAIL PROTECTED]> [2004-12-19 10:41]:
> > BTW, there is now a ppc64 list on alioth's ppc64 project at :
> > https://alioth.debian.org/mail/?group_id=30565
>
> Why cannot we just have the discussion on the debian-
* Sven Luther <[EMAIL PROTECTED]> [2004-12-19 10:41]:
> BTW, there is now a ppc64 list on alioth's ppc64 project at :
> https://alioth.debian.org/mail/?group_id=30565
Why cannot we just have the discussion on the debian-powerpc list?
--
Martin Michlmayr
http://www.cyrius.com/
On Sun, Dec 19, 2004 at 10:27:04AM +0100, Benjamin Herrenschmidt wrote:
>
> > However, it will also be possible to compile and run 32 bit powerpc-linux
> > binaries. This will be achieved by using the '-enable-multilib' gcc
> > switch and by placing the necessary 32 bit powerpc libraries in
> >
1 - 100 of 168 matches
Mail list logo
