From: Tom G. <to...@li...> - 2001-10-08 10:35:40
|
* Michael Jennings (e-...@ka...) wrote: > On Monday, 08 October 2001, at 07:52:57 (+0100), > > that you don't tell him "bugger off, it's debian's fault", as raster > > does - every time. Okay? :) > > No, it's his/her own fault for using Debian unstable. If someone were > bitching about problems with RedHat Rawhide, I'd make the same > argument. It just so happens that more Debian users choose unstable > than RedHat users choose Rawhide, primarily due to historical lack of > options. So if the user has gone to gnu.org and got the current version of the software, it's their fault too? That logic escapes me :) Tom. -- .^. .-------------------------------------------------------. /V\ | Tom Gilbert, London, England | http://linuxbrit.co.uk | /( )\ | Open Source/UNIX consultant | to...@li... | ^^-^^ `-------------------------------------------------------' |
From: Hall S. <hal...@mi...> - 2001-10-08 13:00:27
|
> ... but then again, RedHat releases multiple times a > year, whereas Debian releases happen less than even > once a year. Those are *marketing* department decisions as to when a new 'release' should be put out. Look at how different software jumps in release numbers in order to catch up with others. Didn't Slackware jump from a relatively low number up to v7.x about a year ago ?? Suse, Mandrake, and others were up around that version, so Slackware doesn't want to be perceived as "'x' versions behind...". Pick some versions of packages that are included in Redhat's latest release and see what version is currently in Debian 'testing'. Plenty of people will argue that Redhat's releases often can't be considered real stable... Hall |
From: Michael J. <e-...@ka...> - 2001-10-08 17:19:14
|
On Monday, 08 October 2001, at 09:00:23 (-0400), Hall Stevenson wrote: > Those are *marketing* department decisions as to when a new > 'release' should be put out. Not entirely. If the marketing department were calling all the shots, RH 7.2 would've been released for LinuxWorld back in August. > Look at how different software jumps in release numbers in order to > catch up with others. RedHat did no such thing. > Didn't Slackware jump from a relatively low number up to v7.x about > a year ago ?? Suse, Mandrake, and others were up around that > version, so Slackware doesn't want to be perceived as "'x' versions > behind...". So what's your point? > Pick some versions of packages that are included in Redhat's latest > release and see what version is currently in Debian 'testing'. Again, if you're trying to make a point here, please make it. > Plenty of people will argue that Redhat's releases often can't be > considered real stable... I'm not sure who these "plenty of people" are, but having worked with RedHat over several release cycles, I can say that RedHat 7.0 was certainly an awful release, but 6.2 and 7.1 were both quite solid. I run RH-VALE 7.1.1 on all my systems, and it was proven quite reliable. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <me...@ka...> n+1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Who are you people?" "We're writers." "What are you striking for?" "More money." "How much do you earn?" "$350,000." -- conversation with striking Writer's Guild member as reported by Bernard Weintraub in the New York Times |
From: <ra...@ra...> - 2001-10-08 06:50:13
|
On Mon, 8 Oct 2001 07:14:08 +0100 Tom Gilbert <to...@li...> babbled profusely: > It's not a cvs release (in debian these always have a foobar-cvs package > name) or an unauthorised beta release (for example redhat's last > compiler). It's the current stable version of the software. Stop > misunderstanding the reasoning for debian's "unstable" monicker. > > "There is no reasonable justification to expect software developers to > use software which is obviously neither commonplace nor ready for > widespread use". but mej is right. it is not commonplace. it's new. as of a few motnhs ago not one "stable" (ie on a cd or downloadable/installable) dsitribution used it. mej is right. if there were a godo reaosn to use it (ie the previous version had problems we've encountered and had to just live with and the new one magically solves it) then there'd be a good reaosn to move. but right now its a new version just for the sake of it - as far as development here is concerned. and new versions for the sake fo it from a developers poitn of view is not good - ESPECIALLy if they break what u already have. :) > Is just horseshit because this is a stable release of the software :) a new stable release. windows xp is a new stabel release. does this mean u'll use it the moment it coems out? or every version of anything? no - i generally liek tpo let it mature. i only use brand spanking new thing sif i NEED their funtionality - or fixes... or it'm my own stuff and i can kick my own bum for any problems i might have :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... Unemployed Bum ra...@de... Mobile Phone: +61 (0)408 363 984 Home Phone: 02 9386 9362 |
From: Tom G. <to...@li...> - 2001-10-08 07:08:19
|
* ra...@ra... (ra...@ra...) wrote: > On Mon, 8 Oct 2001 07:14:08 +0100 Tom Gilbert <to...@li...> babbled > profusely: > > > It's not a cvs release (in debian these always have a foobar-cvs package > > name) or an unauthorised beta release (for example redhat's last > > compiler). It's the current stable version of the software. Stop > > misunderstanding the reasoning for debian's "unstable" monicker. > > > > "There is no reasonable justification to expect software developers to > > use software which is obviously neither commonplace nor ready for > > widespread use". > > but mej is right. it is not commonplace. it's new. as of a few motnhs ago not > one "stable" (ie on a cd or downloadable/installable) dsitribution used it. mej > is right. if there were a godo reaosn to use it (ie the previous version had > problems we've encountered and had to just live with and the new one magically > solves it) then there'd be a good reaosn to move. but right now its a new > version just for the sake of it - as far as development here is concerned. and > new versions for the sake fo it from a developers poitn of view is not good - > ESPECIALLy if they break what u already have. :) No but what I am saying is that if it's the current release, you have to expect users to go and download it. Whether you decide to fix your setup for the changes in the new version, or tell people to downgrade, I don't much care. As ever, I object to you trolling about distributions, not you sticking with old versions of development tools. "Nuff said" :) Tom. -- .^. .-------------------------------------------------------. /V\ | Tom Gilbert, London, England | http://linuxbrit.co.uk | /( )\ | Open Source/UNIX consultant | to...@li... | ^^-^^ `-------------------------------------------------------' |
From: <ra...@ra...> - 2001-10-08 07:30:59
|
On Mon, 8 Oct 2001 08:08:13 +0100 Tom Gilbert <to...@li...> babbled profusely: > No but what I am saying is that if it's the current release, you have to > expect users to go and download it. Whether you decide to fix your setup aaaah! here is where we differ. these are not users. if u get code form cvs and use automake, autoconf etc. to build configure scritp and makefile.in's.. you are no longer a user. you are now a developer. those tools are not required and should nto be needed on any end-user system at all- thats the idea of them. they are developer tools only. when we finally are ready we build the configure critp and makefile.in's here and then throw out a tarball. at this point the .in's and .am's arent actually needed anymore (i actually shoudl strip them out of the final tar.gz as they are packager/relase moaintainer files only - as well as autogen.sh). anyway.. thats where we differ :) yes - as far as end users.. yes - i shoudl definitely (aroudn nearing time of release) make sure to the greatest extent the package will build form the TARBALL on as many systems as possible (given they meet the requirments) and make sure the tarball tells u what requirements you fail to meet. > for the changes in the new version, or tell people to downgrade, I don't > much care. As ever, I object to you trolling about distributions, not > you sticking with old versions of development tools. "Nuff said" :) my facts were still correct. i didnt troll - i stated facts - and they still stand. :) > Tom. > -- > .^. .-------------------------------------------------------. > /V\ | Tom Gilbert, London, England | http://linuxbrit.co.uk | > /( )\ | Open Source/UNIX consultant | to...@li... | > ^^-^^ `-------------------------------------------------------' > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... Unemployed Bum ra...@de... Mobile Phone: +61 (0)408 363 984 Home Phone: 02 9386 9362 |
From: Igor K. <ko...@ui...> - 2001-10-08 08:22:02
|
You guys argue way too much, makes me wonder how e16 ever got written.. :) But the screenshots Brian posted keep me hopefull... Adding: ASFLAGS="$ASFLAGS -I../" AM_PROG_AS to configure.in will fix the problem with automake1.5 . Hope it doesn't brake anything elsewhere... there you go making me start to learn auto*. Argh. ik -- ------------------------------------------------------------------------------- ko...@ui... GPG Public Key: www.tambuka.net/key.html www.tambuka.net Key Signature: ED872B110DBF4EC8FE280350FF9E0C810792EA1D ------------------------------------------------------------------------------- |
From: Tom G. <to...@li...> - 2001-10-08 10:33:34
|
* ra...@ra... (ra...@ra...) wrote: > On Mon, 8 Oct 2001 08:08:13 +0100 Tom Gilbert <to...@li...> babbled > profusely: > > > No but what I am saying is that if it's the current release, you have to > > expect users to go and download it. Whether you decide to fix your setup > > aaaah! here is where we differ. these are not users. if u get code > form cvs and use automake, autoconf etc. to build configure scritp and > makefile.in's.. you are no longer a user. you are now a developer. > those tools are not required and should nto be needed on any end-user > system at all- thats the idea of them. they are developer tools only. > when we finally are ready we build the configure critp and > makefile.in's here and then throw out a tarball. at this point the > .in's and .am's arent actually needed anymore (i actually shoudl strip > them out of the final tar.gz as they are packager/relase moaintainer > files only - as well as autogen.sh). Then stop doing interviews telling _users_ how cool the stuff in CVS is, stop pointing to it on the website and stop raving about it in IRC :)p > > for the changes in the new version, or tell people to downgrade, I don't > > much care. As ever, I object to you trolling about distributions, not > > you sticking with old versions of development tools. "Nuff said" :) > > my facts were still correct. i didnt troll - i stated facts - and they still > stand. :) No I'm sorry you did troll. "It's debian's fault", "they shipped an unstable version of automake", these things aren't facts :) Tom. -- .^. .-------------------------------------------------------. /V\ | Tom Gilbert, London, England | http://linuxbrit.co.uk | /( )\ | Open Source/UNIX consultant | to...@li... | ^^-^^ `-------------------------------------------------------' |
From: <ra...@ra...> - 2001-10-08 11:45:22
|
On Mon, 8 Oct 2001 11:33:28 +0100 Tom Gilbert <to...@li...> babbled profusely: > * ra...@ra... (ra...@ra...) wrote: > > On Mon, 8 Oct 2001 08:08:13 +0100 Tom Gilbert <to...@li...> babbled > > profusely: > > > > > No but what I am saying is that if it's the current release, you have to > > > expect users to go and download it. Whether you decide to fix your setup > > > > aaaah! here is where we differ. these are not users. if u get code > > form cvs and use automake, autoconf etc. to build configure scritp and > > makefile.in's.. you are no longer a user. you are now a developer. > > those tools are not required and should nto be needed on any end-user > > system at all- thats the idea of them. they are developer tools only. > > when we finally are ready we build the configure critp and > > makefile.in's here and then throw out a tarball. at this point the > > .in's and .am's arent actually needed anymore (i actually shoudl strip > > them out of the final tar.gz as they are packager/relase moaintainer > > files only - as well as autogen.sh). > > Then stop doing interviews telling _users_ how cool the stuff in CVS is, > stop pointing to it on the website and stop raving about it in IRC :)p peoelp as q's - i answer them. so do i say "i wont talk abotu anything i'm doing" to peoel asking for interviews? i think not. > > > for the changes in the new version, or tell people to downgrade, I don't > > > much care. As ever, I object to you trolling about distributions, not > > > you sticking with old versions of development tools. "Nuff said" :) > > > > my facts were still correct. i didnt troll - i stated facts - and they still > > stand. :) > > No I'm sorry you did troll. "It's debian's fault", "they shipped an > unstable version of automake", these things aren't facts :) i didnt say that.. here is my mail: ... that's not the problem. debian's libtool and/or automake package is putting these in expecting them to get substituted and they aren't. it shouldnt' be doing this as i shouldn not HAVE to AC_SUBST the ASFLAGS and AS variables - just like CFLAGS and CC. basically things suddenly broke due to an upgrade on your system - due to debian's upgrading t a new version of software that may not have ben fully tested or may hav eincompatible changes made. simple: downgrade your system. ... that is the exact quote. i stick by what i said. > Tom. > -- > .^. .-------------------------------------------------------. > /V\ | Tom Gilbert, London, England | http://linuxbrit.co.uk | > /( )\ | Open Source/UNIX consultant | to...@li... | > ^^-^^ `-------------------------------------------------------' > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... Unemployed Bum ra...@de... Mobile Phone: +61 (0)408 363 984 Home Phone: 02 9386 9362 |
From: Jerome De G. <jde...@br...> - 2001-10-08 12:39:33
|
* ra...@ra... (ra...@ra...) wrote: > On Mon, 8 Oct 2001 11:33:28 +0100 Tom Gilbert <to...@li...> babbled > profusely: > > > * ra...@ra... (ra...@ra...) wrote: > > > On Mon, 8 Oct 2001 08:08:13 +0100 Tom Gilbert <to...@li...> babbled > > > profusely: > > > > > > > No but what I am saying is that if it's the current release, you have to > > > > expect users to go and download it. Whether you decide to fix your setup > > > > > > aaaah! here is where we differ. these are not users. if u get code > > > form cvs and use automake, autoconf etc. to build configure scritp and > > > makefile.in's.. you are no longer a user. you are now a developer. > > > those tools are not required and should nto be needed on any end-user > > > system at all- thats the idea of them. they are developer tools only. > > > when we finally are ready we build the configure critp and > > > makefile.in's here and then throw out a tarball. at this point the > > > .in's and .am's arent actually needed anymore (i actually shoudl strip > > > them out of the final tar.gz as they are packager/relase moaintainer > > > files only - as well as autogen.sh). > > > > Then stop doing interviews telling _users_ how cool the stuff in CVS is, > > stop pointing to it on the website and stop raving about it in IRC :)p > > peoelp as q's - i answer them. so do i say "i wont talk abotu anything i'm > doing" to peoel asking for interviews? i think not. > > > > > for the changes in the new version, or tell people to downgrade, I don't > > > > much care. As ever, I object to you trolling about distributions, not > > > > you sticking with old versions of development tools. "Nuff said" :) > > > > > > my facts were still correct. i didnt troll - i stated facts - and they still > > > stand. :) > > > > No I'm sorry you did troll. "It's debian's fault", "they shipped an > > unstable version of automake", these things aren't facts :) > > i didnt say that.. here is my mail: > ... > that's not the problem. debian's libtool and/or automake package is putting > these in expecting them to get substituted and they aren't. it shouldnt' be > doing this as i shouldn not HAVE to AC_SUBST the ASFLAGS and AS variables - just > like CFLAGS and CC. basically things suddenly broke due to an upgrade on your > system - due to debian's upgrading t a new version of software that may not have > ben fully tested or may hav eincompatible changes made. simple: downgrade your > system. > ... > that is the exact quote. i stick by what i said. And here's the exact quote from automake 1.5-1 info file: `AM_PROG_AS' Use this macro when you have assembly code in your project. This will choose the assembler for you (by default the C compiler), and will set `ASFLAGS' if required. So what? Either it's time to correct configure.in and/or configure.ac (both in Eterm and Imlib2), either you should put somewhere that automake < 1.5 is a requirement to compile Imlib2 and Eterm. I solved my compile problems by downgrading to automake 1.4-p4-1 (Debian/Sid) but I think this new macro in automake 1.5 is much more a feature than a bug. Regards, Jerome -- +-------------------------------------------------------------------+ | 'the panorama of the city is wrong | | in fact the city seems to be gone!' | | the clash, stop the world, 1980 | +-------------------------------------------------------------------+ |
From: Christian K. <kre...@in...> - 2001-10-08 12:56:43
|
Jerome De Greef wrote: > > And here's the exact quote from automake 1.5-1 info file: > > `AM_PROG_AS' > Use this macro when you have assembly code in your project. This > will choose the assembler for you (by default the C compiler), > and will set `ASFLAGS' if required. > > So what? Either it's time to correct configure.in and/or configure.ac > (both in Eterm and Imlib2), either you should put somewhere that > automake < 1.5 is a requirement to compile Imlib2 and Eterm. > > I solved my compile problems by downgrading to automake 1.4-p4-1 > (Debian/Sid) but I think this new macro in automake 1.5 is much more a > feature than a bug. Right. Raster, to save us from threads like this one and "You said Debian sucks" -- "No I didn't" -- "You said that I said that you said it sucks" in the future, please invest those 2.5 minutes to upgrade and then this issue is over for good, okay? I'm tired of this. Thanks :D Regards, -- Christian. ________________________________________________________________________ http://www.whoop.org |
From: Jerome De G. <jde...@br...> - 2001-10-08 13:26:11
|
* Christian Kreibich (kre...@in...) wrote: > Jerome De Greef wrote: > > > > And here's the exact quote from automake 1.5-1 info file: > > > > `AM_PROG_AS' > > Use this macro when you have assembly code in your project. This > > will choose the assembler for you (by default the C compiler), > > and will set `ASFLAGS' if required. > > > > So what? Either it's time to correct configure.in and/or configure.ac > > (both in Eterm and Imlib2), either you should put somewhere that > > automake < 1.5 is a requirement to compile Imlib2 and Eterm. > > > > I solved my compile problems by downgrading to automake 1.4-p4-1 > > (Debian/Sid) but I think this new macro in automake 1.5 is much more a > > feature than a bug. > > Right. Raster, to save us from threads like this one and "You said > Debian sucks" -- "No I didn't" -- "You said that I said that you said it > sucks" in the future, please invest those 2.5 minutes to upgrade and > then this issue is over for good, okay? I'm tired of this. Thanks :D What? You said that I said that Giblet said that Raster said that Debian sucks ;) I suck too because I posted a mail about this yesterday without even noticing that there was already a thread on the topic... Sorry. Jerome -- +-------------------------------------------------------------------+ | 'the panorama of the city is wrong | | in fact the city seems to be gone!' | | the clash, stop the world, 1980 | +-------------------------------------------------------------------+ |
From: Lyle K. <te...@ke...> - 2001-10-08 16:16:34
|
* Christian Kreibich (kre...@in...) wrote: > Right. Raster, to save us from threads like this one and "You said > Debian sucks" -- "No I didn't" -- "You said that I said that you said it > sucks" in the future, please invest those 2.5 minutes to upgrade and > then this issue is over for good, okay? I'm tired of this. Thanks :D I can't agree more. I also can't believe we're still arguing about this like it has anything to do with a distribution. And no one reply saying it does, please -- I don't agree with you, 300 pages of email isn't going to make me agree with your indefensible desire to attack a distribution about an API change in a piece of ubiquitous software that they have no direct control over, and I really have no interest in reading it. Instead, someone just make me read a commits email fixing it, or tell me where I make the changes that will produce one. term |
From: <Val...@vt...> - 2001-10-08 17:21:48
|
On Mon, 08 Oct 2001 16:40:30 +1000, ra...@ra... said: > a new stable release. windows xp is a new stabel release. does this mean u'll > use it the moment it coems out? or every version of anything? no - i generally > liek tpo let it mature. i only use brand spanking new thing sif i NEED their > funtionality - or fixes... or it'm my own stuff and i can kick my own bum for > any problems i might have :) Amen. The 4 machines in my office are usually riding close to the bleeding edge - that's what they are FOR. I had AIX 5.0 in my office, which was a 'developer only' early release. On the other hand, the IBM machines across the hall will probably *start* seeing AIX 5.1 in May or so.... Of course, I end up doing my share of bitching about compatability issues as well. Sometimes it's fairly easy to support the bleeding edge and still work under the old stuff. Sometimes it's a bitch. And I'll leave it at that. /Valdis |
From: Igor K. <ko...@ui...> - 2001-10-10 09:49:00
|
So when I boot e17 I get as far as the background coming up and then things die: e17: relocation error: e17: undefined symbol efsd_cleanup_event efsd crashes and gdb comes up but it complains that it can't get a stack trace because connection was reset by peer and it suddenly can't find the child proceess. Did I miss something, fam's up, efsd's up and I just start with .xinitrc having only e17. Let me know why I'm being stupid :), ik -- ------------------------------------------------------------------------------- ko...@ui... GPG Public Key: www.tambuka.net/key.html www.tambuka.net Key Signature: ED872B110DBF4EC8FE280350FF9E0C810792EA1D ------------------------------------------------------------------------------- |
From: Christian K. <kre...@in...> - 2001-10-10 09:55:40
|
Igor Kofman schrieb: > > So when I boot e17 I get as far as the background coming up and then things die: > e17: relocation error: e17: undefined symbol efsd_cleanup_event You have a broken build I'd say :) make install for efsd again, and rebuild e17. > efsd crashes and gdb comes up but it complains that it can't get a stack trace because Eh? It shouldn't. Did you successfully make install for efsd? > Did I miss something, fam's up, efsd's up and I just start with .xinitrc having only > e17. Again, I do not recommend starting e17 from startup scripts. Run it from a terminal to see the output, and launch efsd separetely so that you can start it as efsd -f -d. -- Christian. ________________________________________________________________________ http://www.whoop.org |
From: Igor K. <ko...@ui...> - 2001-10-10 10:05:00
|
make install on efd works without any complaints. i did as you suggested but still have the same problem here's the efsd output when i run e17: efsd [1024]: New connection -- client 0. efsd [1024]: Read timed out... 4 efsd [2051]: Handling STARTMON_FILE efsd [2051]: Looking up /home/kofman, as dir: 0 efsd [2051]: Looking up /home/kofman in stat cache efsd [2051]: Looking up /home/kofman, as dir: 0 efsd [2051]: Comparing /home/kofman 0 -- /home/kofman 0 efsd [2051]: Returning 0 efsd [2051]: /home/kofman is monitored, dir requested: 0, monitored as dir: 0 efsd [2051]: Incrementing internal use count for monitoring file /home/kofman, now (1/1). efsd [2051]: Starting monitoring file /home/kofman. efsd [1026]: Handling FAM event 8 for file /home/kofman efsd [1026]: Handling FAM event 9 for file /home/kofman Efsd [12154] received signal 11, attempting stack trace. Launching /usr/bin/gdb -x /usr/local/share/efsd/gdb.scr /home/kofman/code/e17/apps/efsd/efsd 12154 Error: Connection reset by peer efsd [1024]: Closing connection 0 efsd [1024]: Client 0 found monitoring /home/kofman, use count now (1/0) efsd [1024]: Removing client 0 from monitor for /home/kofman GNU gdb 5.0.90-cvs (MI_OUT) Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"..."/home/kofman/code/e17/apps/efsd/efsd": not in executable format: Is a directory //12154: No such file or directory. Attaching to process 12154 Child process unexpectedly missing: No child processes. here's what e says: kofman@tambuka:~$ e17 e_view_file_added(1, "/home/kofman"); e17: relocation error: e17: undefined symbol: efsd_cleanup_event kofman@tambuka:~$ ideas? ik -- Around Wed, 10 Oct 2001 11:55:54 +0200 Christian Kreibich <kre...@in...> did say: > > > Igor Kofman schrieb: > > > > So when I boot e17 I get as far as the background coming up and then things die: > > e17: relocation error: e17: undefined symbol efsd_cleanup_event > > You have a broken build I'd say :) make install for efsd again, and > rebuild e17. > > > efsd crashes and gdb comes up but it complains that it can't get a stack trace because > > Eh? It shouldn't. Did you successfully make install for efsd? > > > Did I miss something, fam's up, efsd's up and I just start with .xinitrc having only > > e17. > > Again, I do not recommend starting e17 from startup scripts. Run it from > a terminal to see the output, and launch efsd separetely so that you can > start it as efsd -f -d. > > -- Christian. > ________________________________________________________________________ > http://www.whoop.org > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------------------------------------------------------------------------- ko...@ui... GPG Public Key: www.tambuka.net/key.html www.tambuka.net Key Signature: ED872B110DBF4EC8FE280350FF9E0C810792EA1D ------------------------------------------------------------------------------- |
From: Christian K. <kre...@in...> - 2001-10-10 10:19:53
|
Igor Kofman wrote: > > make install on efd works without any complaints. i did as you suggested but still > have the same problem here's the efsd output when i run e17: > > efsd [1024]: New connection -- client 0. > efsd [1024]: Read timed out... 4 > efsd [2051]: Handling STARTMON_FILE > efsd [2051]: Looking up /home/kofman, as dir: 0 > efsd [2051]: Looking up /home/kofman in stat cache > efsd [2051]: Looking up /home/kofman, as dir: 0 > efsd [2051]: Comparing /home/kofman 0 -- /home/kofman 0 > efsd [2051]: Returning 0 > efsd [2051]: /home/kofman is monitored, dir requested: 0, monitored as dir: 0 > efsd [2051]: Incrementing internal use count for monitoring file /home/kofman, now (1/1). > efsd [2051]: Starting monitoring file /home/kofman. > efsd [1026]: Handling FAM event 8 for file /home/kofman > efsd [1026]: Handling FAM event 9 for file /home/kofman > Efsd [12154] received signal 11, attempting stack trace. > Launching /usr/bin/gdb -x /usr/local/share/efsd/gdb.scr /home/kofman/code/e17/apps/efsd/efsd 12154 > Error: Connection reset by peer > efsd [1024]: Closing connection 0 > efsd [1024]: Client 0 found monitoring /home/kofman, use count now (1/0) > efsd [1024]: Removing client 0 from monitor for /home/kofman > GNU gdb 5.0.90-cvs (MI_OUT) > Copyright 2001 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-linux"..."/home/kofman/code/e17/apps/efsd/efsd": not in executable format: Is a directory > > //12154: No such file or directory. > Attaching to process 12154 > Child process unexpectedly missing: No child processes. > > here's what e says: > kofman@tambuka:~$ e17 > e_view_file_added(1, "/home/kofman"); > e17: relocation error: e17: undefined symbol: efsd_cleanup_event > kofman@tambuka:~$ > > ideas? Okay. I still think that the relocation error is evil, make sure your e17 build is okay. The efsd crash looks like a real segfault. Since it appears to be reproducible, just run efsd from gdb and send me the backtrace, please. -- Christian. ________________________________________________________________________ http://www.whoop.org |
From: Carsten H. (T. R. <ra...@ra...> - 2001-10-10 13:21:04
|
On Wed, 10 Oct 2001 04:48:54 -0500 Igor Kofman <ko...@ui...> babbled profusely: > > So when I boot e17 I get as far as the background coming up and then things > die: > e17: relocation error: e17: undefined symbol efsd_cleanup_event > efsd crashes and gdb comes up but it complains that it can't get a stack trace > because > connection was reset by peer and it suddenly can't find the child proceess. > Did I miss something, fam's up, efsd's up and I just start with .xinitrc > having only > e17. > Let me know why I'm being stupid :), sounds liek you maye have multiepl libefsd's installed and the prog has linked to one link tim and to another runtime... ? > ik > -- > ------------------------------------------------------------------------------- > ko...@ui... GPG Public Key: www.tambuka.net/key.html > www.tambuka.net Key Signature: ED872B110DBF4EC8FE280350FF9E0C810792EA1D > ------------------------------------------------------------------------------- > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... Unemployed Bum ra...@de... Mobile Phone: +61 (0)408 363 984 Home Phone: 02 9386 9362 |
From: Van B. <bui...@ho...> - 2001-11-09 00:27:08
|
Hi, been running cvs e for about a week now, the first time i installed it everything runs okay.. until i updated 2days ago.. eveything still installs fine, but now im gettin this prob libefsd: connect() error. launch efsd... 12443 libefsd: connect() error. e still load up, but most of the times i can't close any window or load up programs running RedHat 7.2 , any help would be appreciated! thanks _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
From: Marmot <mar...@sh...> - 2001-11-09 00:36:50
|
On Thu, Nov 08, 2001 at 07:26:54PM -0500, Van Bui wrote: > > Hi, been running cvs e for about a week now, the first time i installed it > everything runs okay.. until i updated 2days ago.. eveything still installs > fine, but now im gettin this prob > > libefsd: connect() error. > launch efsd... 12443 > libefsd: connect() error. > > e still load up, but most of the times i can't close any window or load up > programs > > running RedHat 7.2 , any help would be appreciated! thanks > Sounds like fam is not running. 7.2 has fam rpms. I have the following installed fam-devel-2.6.4-11 fam-2.6.4-11 Also make sure that fam is running. rpcinfo -p | grep fam will tell you if it is. the redhat fam package should be starting fam from /etc/xinetd.d/sgi_fam. Make sure the service is not disabled and is running correctly. Phil, > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel |
From: kim s. <yan...@ya...> - 2001-12-28 02:33:02
|
subscribe |
From: Elias P. <xw...@ot...> - 2002-01-14 22:51:07
|
ermm.... just downloaded the CVS eterm running autogen resulted to this : creating cache ./config.cache ./configure: line 575: syntax error near unexpected token `AM_INIT_AUTOMAKE(Eterm,' ./configure: line 575: `AM_INIT_AUTOMAKE(Eterm, 0.9.2)' saywhat???? |
From: Chimou <ch...@no...> - 2002-02-14 07:15:42
|
From: Donald M. <juj...@ya...> - 2002-02-28 08:28:27
Attachments:
patch
|
This is just a little one-line patch to adjust the length of a text field. On my system, the text field was so big that it didn't allow the executable browse button to even be displayed. I also added a line in the README listing gdbm as a dependency. __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com |