Re: Nubus machines wanted
Aurélien GÉRÔME wrote: > > This is also the time for users to post here if you still use Nubus > and want it to be brought back to life. I have a Nubus machine and definitely would love if it is resurrected. The machine has some hardware problems (Muck OS doesn't boot) which happened after I bought it and the transportation from another city. If I fix them, I'll happily donate it to you or the EMILE author. The only problem I see is how to ship it to France (I live in Varna, Bulgaria)... -- I had a very low opinion of TCL, basically because it wasn't Lisp. --RMS
[OT] Re: Regression in sleep code for PowerBook5,2
=?UTF-8?Q?Eddy_Petri=C5=9For?= wrote: > > (bah, git, again; it was not such a pleasent experience last time I > tried it). This is precisely the reason why it is popular as "shit" ;-} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GWorkspace doesn't work in Sarge
Jeffrey Rolland wrote: > > I have a Power Macintosh 7500/100 running Debian Sarge. > > I have recently switched from KDE to GNUStep/WindowMaker, and I am > having a problem with GWorkspace. [...] > Can anyone help sort out why GWorkspace doesn't work? I would really > appreciate any assistance you can provide. Most of the warnings are harmless, but I'm very surprised that it doesn't work. I don't have a Sarge machine with GNUstep installed to check this. Please ensure that GWorkspace is not running in the background, i.e. that it is not started when you start your X session. Also, try to start gdnc (GNUstep Distribution Notification Center) first -- see the manpage how to do that. (gdnc is shipped in the gnustep-base-common package which you should have installed because of the dependency chain). Finally, I'd suggest filing a bug in the BTS as it seems that the other GNUstep maintainers are not subscribed to -powerpc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GWorkspace doesn't work in Sarge
brian wrote: > > > Please be aware that there have been big/major developments in > > GnuStep over the past year. more so in the underneath layers than > > in the applications suite. This is true, but is irrelevant to the OP's problem. > > so that makes it difficult for the developers to do much for you, > > as before that it was stalled for quite a while. This is not true. I'm not a co-maintainer for gwrokspace.app, that's why I suggested filing a bug. Most probably there will be people who can help or at least try to locate the issue. > > the thing is you CAN upgrade to Xorg while still running the sarge > > 2.6.8 kernel, that is from testing; if you are willing to do so > > then you can update GnuStep to a recent version. Basically there is a reason why people run stable so advising them to upgrade to testing does not seem to be a good idea. Last time I tried (that was about a year ago, I think) GNUstep in Sarge was in a pretty good shape. > > but i would say that windowmaker and gworkspace both have some > > problems We would like to know about these problems, please. Window Maker is the preferred window manager for GNUstep both by upstream and the Debian maintainers. > > while when i had time i was trying to build the new gnustep > > desktop package -- that is called etoile. it is not in debian but > > it looks like it could be better. i had tried fsviewer also and > > found both to not work really well. The source package etoile is in Debian, but it currently builds only camaelon.app and dictionaryreader.app. Etoile is very unstable and a bit of vapourware so we have decided to postpone the whole work after the release of Etch. It's a pity that there are three efforts for a GNUstep desktop (Backbone, Etoile and GAP) and none of them is complete or at least working properly. Unfortunately, Etoile diverts very much from the original look & feel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GWorkspace doesn't work in Sarge
This is getting wildely offtopic for -powerpc, so please reply privately in order not to annoy the list subscribers. brian wrote: > > > This is true, but is irrelevant to the OP's problem. > > You seem to have a much different perspective on this than i > have. mine was that GnuStep needed and got a major overhaul this > year, which is will allow a real desktop now to develop that is > presently in a prototype stage with etoile' being the leading > contender (the others simply not not showing much more than the old > gworkspace/windowmaker results, or/and not getting adequate > developer interest) Well, with every release of the main GNUstep libraries there are major changes, especially in the past two years. It is true that the Etoile project is closer to a desktop than the other efforts. > > This is not true. I'm not a co-maintainer for gwrokspace.app, > > that's why I suggested filing a bug. Most probably there will be > > people who can help or at least try to locate the issue. > > yes, i am sorry but it is. there is besides the issue of gnustep big > change is that sarge will soon be old stable which with big change > in etch again makes asking superhuman demands from a limited group > of people. unless suddenly debian were to take a much more friendly > stance on developing new developers and/or officially supporting > backports -- i don't think though it has the resources to do either. But this suggests that stable is not supported -- I don't agree with you. The right place to obtain support is via the BTS or at least the pkg-gnustep mailing list. powerpc is just one of the arches where GNUstep runs. > > Basically there is a reason why people run stable so advising them > > to upgrade to testing does not seem to be a good idea. Last time > > I tried (that was about a year ago, I think) GNUstep in Sarge was > > in a pretty good shape. > > of course that is so. and i said before i kept a copy, at least a > mixed sarge/testing. actually i do keep a copy of sarge and use it > often enough to update it and test it. i sometimes think if you came > from a windows background you may find a much lower level of quality > adequate. however, mine was bsd, nextstep, and mac, and i just find > MS/W standards to be completely unacceptable. I find the standards of any proprietary system unacceptable. We were using stable at work (including GNUstep) but migrated all workstations to testing 1 year before the release of Sarge. I will keep an Etch machine to support my packages and I believe that the other maintainers have at least one Sarge installation to support theirs. > > We would like to know about these problems, please. Window Maker > > is the preferred window manager for GNUstep both by upstream and > > the Debian maintainers. > > this is like saying that MS/windows is preffered for C++. it is not > consistent, as windowmaker has nothing to do with gnustep, it is > just a look (and not much more). According to GNUstep's homepage and the vast majority of upstream developers wmaker is the preferred window manager. Certainly it has nothing to do with GNUstep. > IMHO WM/GW are not really fixable, in fact they are simply > absolete. if there is some political force once again that is > seeking to maintain the status quo, it is just going to create > further problems. Well, if you use GWorkspace's desktop feature (and/or the tabbed shelf) I agree that it is not very consistent. There is no political force, but bear in mind that Etoile is not part of GNUstep and not the official desktop, at least according to the core (GNUstep) developers. > i did say i have not been able to work with it lately, didn't I ?? > you seem to have taken out my context. but i would not call it > vaporware like the others, if you would look at a version from the > last 3 months, it too has grown in a very major way and that is half > the reason i have not been keeping up with it besides waiting for > debian/etch gnustep to stabilize. For a pretty long time Etoile has been "a bunch of screenshots" -- these are not my words. Of course, we will introduce Etoile in Debian and will support it as soon as it is feasible. > no, it is skinnable. you are confusing it with chameleon as it seems > most people confuse windowmaker with gnustep. No, I am not confusing anything. For someone that has been using GNUstep for years, Etoile looks weird. Others might like it, of course. > half of linux is either incomplete or doesn't work "properly", Linux is just a kernel, I guess you mean GNU/Linux here. > unless you go to one of the more commercial distros, and/or put > yourself in the middle mainstream, where it seems to me you are > missing the point (may as well use mac os X way before that, where > you can get most of debian anyway and gnustep besides via fink) I've never used Muck OS and will never use it. I have a few OldWorld Macs and the only mission of their Muck OS is to boot GNU/Linux. If you consider
Re: Problems with GNOME on Beige G3
Rick Thomas wrote: > > The computer in question is an OldWorld PowerMac Apple Macintosh, > "Beige G3" tower. This problem only happens on this machine. It > does not occur on my G4 test box. I have a Beige G3 "Gossamer", not a tower, but it's practically the same. > I'd very much appreciate it if somebody else with a beige G3 would > try it and let me know if they see the same problem. I noticed the same behaviour a few months ago. As I generally run Window Maker/GNUstep on that machine, I just ignored that as I thought there is something broken in my configuration. I'll try to find out what's wrong, but that won't happen in the forthcoming weeks. Apparently this has nothing to do with the installation CDs, as my machine has been running Debian for ages. One thing you could do, as a startup, is to attach gdb to that applet and see what's crashing it. That might give you a clue where to investigate further. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with GNOME on Beige G3
Oh, that's a nasty #404876; I'll try to provide a useful backtrace. I really should read all messges before replying. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cynthiune.app spurious FTBFS
[ Apologies for cross-posting. ] I am bewildered why cynthiune.app FTBFS on hurd-i386 and powerpc: | g++ -shared -rdynamic | -L../../Frameworks/Cynthiune/Cynthiune.framework/Versions/Current | -lCynthiune -lmcheck -Wl,-z,defs -Wl,--as-needed | -Wl,-rpath,/usr/lib/cynthiune.app -shared-libgcc -fexceptions -o | ./WindowsMedia.format/./WindowsMedia ./obj/WindowsMedia.m.o | ./obj/CWMFile.cpp.o -L/usr/local/lib -L/usr/lib -laviplay | -lgnustep-gui -lgnustep-base -lpthread -lobjc -lm | /usr/bin/ld: cannot find -lobjc | collect2: ld returned 1 exit status Here gnustep-make correctly invokes g++ in the link rule, because there is a C++ file involved. Naturally, libobjc is available, so my only possible conclusion is that there is something special on these archs that I'm entirely missing. Could someone please look and give me some clue where the problem lies, and eventually how it could be fixed? Thanks very much. (The WoedowsMedia bundle was never built on powerpc before, because avifile was not available there until recently.) -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Boot failure with kernel 2.6.16 on G3 (Gossamer)
[I hope this is the right list.] I have a G3 (Gossamer) running sid, which hasn't been updated for fairly long time. I installed linux-image-2.6.16-1-powerpc, but it fails to boot. I tried the last few versions (9-12). I see the initial message Welcome to Linux, kernel 2.6.16-1-powerpc Linked at : 0xc00. Frame buffer at : 0x (phys), 0xx (log) klimit: 0. boot_info at : 0. MSR : 0. PUR : 0. HID0 : 0. ICTC : 0. Total space used by parameters & ramdisk: 00503000 Preparing boot params... Preparing BAT... pmac_init():exit id mach():done MMU:enter MMU:hw init hash:enter hash:find piece hash:batch hash:done MMU:mapin MMU:setio MMU:exit and it stays forever. I use BootX 1.2.2, if it matters, ramdisk size 8192. I copy vmlinux-2.6.16-1-powerpc and initrd.img-2.6.16-powerpc to the MuckOS partition and point to them, as usual. My current kernel is 2.6.8 and it boots fine. What am I doing wrong? Thanks in advance. -- "Every non-free program has a lord, a master -- and if you use the program, he is your master." --RMS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot failure with kernel 2.6.16 on G3 (Gossamer)
At Mon, 8 May 2006 15:14:36 +0200, Hans Ekbrand wrote: > > My performa 5400 doesn't boot 2.6.16 in sid either. 2.6.15 works well > though. Try 2.6.15. If it works then we might have the same problem > with 2.6.16. Thanks for the pointer. 2.6.15 starts to boot, but I get the following error: i8042.c: No controller found. FATAL: Error inserting i8042 (/lib/modules/2.6.15-1-powerpc/kernel/drivers/input/serio/i8042.ko): No such device It then drops me to a shell. Same behaviour with 2.6.14 :/ -- "Every non-free program has a lord, a master -- and if you use the program, he is your master." --RMS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Video problems installing etch on oldworld PowerPC Mac (beige G3)
At Thu, 01 Jun 2006 23:02:13 -0700, Daniel Gimpelevich wrote: > > Make sure you don't use a version prior to 1.2.2, and copy the kernel args > for installation from the yaboot.conf on the CD, but increase the initrd > size to at least 20480. I think I have the same problem as the original OP with my Gossamer. I asked for help about a month ago, to no avail. I tried to follow your advice here, but still no luck. Currently I'm using kernel 2.6.8 under sid. -- "Every non-free program has a lord, a master -- and if you use the program, he is your master." --RMS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Flash < v7 compatible?
[EMAIL PROTECTED] wrote: > > So on the PPC, when you need to read a flash page, what are the > alternatives? Gnash, as has been pointed out. But basically, if a website has something in flash, its content is not important. Or at least, for the creators of the page, users and their rights are not important. Which is a good enough reason not to visit such pages. -- In the GNU Project, discrimination against proprietary software is not just a policy -- it's the principle and the purpose. Proprietary software is fundamentally unjust and wrong, so when we have the opportunity to place it at a disadvantage, that is a good thing. --RMS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gnustep-base mysterious FTBFS on powerpcspe
(I hope this is the right list.) gnustep-base/1.25.1-2 failed to build on powerpcspe [*] but unfortunately I cannot understand the reason. It appears like a successful build but the buildlog looks truncated at the end, like the buildd was shut down or the process got killed. What could be done in this case (other than giving it back, I guess)? [*] https://buildd.debian.org/status/fetch.php?pkg=gnustep-base&arch=powerpcspe&ver=1.25.1-2&stamp=1518991848&raw=0
Re: gnustep-base mysterious FTBFS on powerpcspe
On Mon, 19 Feb 2018 15:08:58 +0200, John Paul Adrian Glaubitz wrote: > On 02/19/2018 01:49 PM, Yavor Doganov wrote: > > gnustep-base/1.25.1-2 failed to build on powerpcspe [*] but > > unfortunately I cannot understand the reason. > > This sometimes happens on the machines pathfinder and atlantis but > not cb30. For some reason the kernel used on these two machines has > out-of-memory issues despite the fact those machines are equipped > with 8 GiB RAM each. Thanks for the info, sounds like a bug that is hard to identify and fix. > Will give the package back. It usually works the next time. Unfortunately it failed again (on atlantis): | dpkg-deb: building package 'gnustep-base-runtime-dbgsym' in '../gnustep-base-runtime-dbgsym_1.25.1-2_powerpcspe.deb'. | dpkg-deb: error: from tar -cf subprocess was killed by signal (Killed) | dh_builddeb: dpkg-deb --build debian/.debhelper/libgnustep-base1.25/dbgsym-root .. returned exit code 2 | dpkg-deb: building package 'libgnustep-base1.25' in '../libgnustep-base1.25_1.25.1-2_powerpcspe.deb'. | dh_builddeb: Aborting due to earlier error I'm quite surprised that gnustep-base is hit by this OOM issue, it's a dwarf package compared to many other beasts like libreoffice, webkit, gcc, etc. Could it be a powerpcspe-specific problem introduced in recent binutils?
Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function
Source: lynkeos.app Version: 2.10+dfsg1-2 Severity: serious Tags: patch User: debian-powerpc@lists.debian.org Usertags: ppc64el I would appreciate if someone knowledgeable from -powerpc confirms that the attached patch is correct. The build failure is: gcc /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m -c \ -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. -I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime -Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ -o obj/Lynkeos.obj/MyDeconvolution.m.o /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m: In function 'vector_Process_One_line': /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44: warning: excess elements in vector initializer 0x04050607, 0x04050607 }; ^~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44: note: (near initialization for 'Vperma') /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56: warning: excess elements in vector initializer 0x04050607, 0x04050607 }; ^~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56: note: (near initialization for 'Vperma') /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44: warning: excess elements in vector initializer 0x0C0D0E0F, 0x0C0D0E0F }; ^~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44: note: (near initialization for 'Vpermb') /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56: warning: excess elements in vector initializer 0x0C0D0E0F, 0x0C0D0E0F }; ^~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56: note: (near initialization for 'Vpermb') /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:13: warning: implicit declaration of function 'vec_madd' [-Wimplicit-function-declaration] Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); ^~~~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:23: warning: implicit declaration of function 'vec_ld'; did you mean 'vector'? [-Wimplicit-function-declaration] Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); ^~ vector /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:7: error: AltiVec argument passed to unprototyped function Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); ^~~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:41: warning: implicit declaration of function 'vec_cmplt' [-Wimplicit-function-declaration] const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr); ^ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:7: error: AltiVec argument passed to unprototyped function const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr); ^ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:27: warning: implicit declaration of function 'vec_and'; did you mean 'vscanf'? [-Wimplicit-function-declaration] __vector REAL Vge = vec_and(Vdx,Vmask); ^~~ vscanf /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:7: error: AltiVec argument passed to unprototyped function __vector REAL Vge = vec_and(Vdx,Vmask); ^~~~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:27: warning: implicit declaration of function 'vec_andc'; did you mean 'vscanf'? [-Wimplicit-function-declaration] __vector REAL Vlt = vec_andc(Vthr,Vmask); ^~~~ vscanf /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:7: error: AltiVec argument passed to unprototyped function __vector REAL Vlt = vec_andc(Vthr,Vmask); ^~~~ /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:92:13
Bug#918781: src:gnustep-base: odd FTBFS on powerpc, powerpcspe and ppc64
Source: gnustep-base Version: 1.26.0-1 Severity: important Tags: sid buster ftbfs User: debian-powerpc@lists.debian.org Usertags: powerpc powerpcspe ppc64 Hi PowerPC folks, As the subject says, gnustep-base failed to build in experimental on these architectures so I'd appreciate some help. The powerpcspe failure [1] is extremely awkward; the build appears successful but the log seems truncated, interrupted during dh_install. On powerpc [2] and ppc64 [3] there is testsuite failure, but all these tests pass for me on gcc110 from the GCC Compile Farm. However, that's different toolchain and it's not even running Debian so any conclusion is unreliable. I don't have access to the porter machines to test. Could these failures be related to the fact that kapitsa/kapitsa2 have some network-related issues as uploading build logs appears to be suspended for a certain (long) period? I guess give-backs on these three architectures wouldn't harm? [1] https://buildd.debian.org/status/fetch.php?pkg=gnustep-base&arch=powerpcspe&ver=1.26.0-1&stamp=1546973971&raw=0 [2] https://buildd.debian.org/status/fetch.php?pkg=gnustep-base&arch=powerpc&ver=1.26.0-1&stamp=1547024045&raw=0 [3] https://buildd.debian.org/status/fetch.php?pkg=gnustep-base&arch=ppc64&ver=1.26.0-1&stamp=1547024045&raw=0
