From: Alan S. <ala...@po...> - 2003-04-12 11:25:22
|
Hi, Trying to get e17 to work, I decided to get the latest version of all libs and rebuild them. My first question is about build order: the website says that imlib2 must be built before edb, but imlib2's README says that edb must already be installed ... So which one is first ? The second is about building imlib2. It fails because it cannot do make in libltdl. Here are some hints as what is happening: end of ./autogen.sh: configure: configuring in libltdl configure: WARNING: no configuration information is in libltdl it fails when doing make: make[1]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2' Making all in libltdl make[2]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2/libltdl' make[2]: *** No rule to make target `all'. Stop. which is not surprising: schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> ls libltdl/ acconfig.h CVS which seems to be due to: schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> cat libltdl/.cvsignore libtool config* Makefile* .libs .deps *.lo *.la *.in stamp* ltdl.c ltdl.h acinclude.m4 aclocal.m4 COPYING.LIB README So there is definitely something missing in that dir, I think ... Alan Schmitt -- The hacker: someone who figured things out and made something cool happen. |
From: Michael J. <e-...@ka...> - 2003-04-12 12:17:25
|
On Saturday, 12 April 2003, at 07:24:36 (-0400), Alan Schmitt wrote: > The second is about building imlib2. It fails because it cannot do make > in libltdl. Here are some hints as what is happening: > > end of ./autogen.sh: > > configure: configuring in libltdl > configure: WARNING: no configuration information is in libltdl > > it fails when doing make: > > make[1]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2' > Making all in libltdl > make[2]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2/libltdl' > make[2]: *** No rule to make target `all'. Stop. > > which is not surprising: > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> ls libltdl/ > acconfig.h CVS That is correct. acconfig.h and .cvsignore are the only files in that directory that should be in the repository. > which seems to be due to: > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> cat libltdl/.cvsignore > libtool > config* > Makefile* > .libs > .deps > *.lo > *.la > *.in > stamp* > ltdl.c > ltdl.h > acinclude.m4 > aclocal.m4 > COPYING.LIB > README That is also correct. > So there is definitely something missing in that dir, I think ... No, nothing is missing. Everything you need is there. Note this portion of autogen.sh: libtoolize --ltdl --force --copy || abort "libtoolize" libtoolize is responsible, thanks to the --ltdl flag, for populating the entire libltdl directory with configure, Makefile.in, etc. After autogen.sh runs, your libltdl directory should look something like this: total 700 drwxr-xr-x 3 mej mej 4096 Apr 12 08:15 ./ drwx------ 11 mej mej 4096 Apr 12 08:15 ../ -rw-r--r-- 1 mej mej 117 Apr 3 14:08 .cvsignore -rw-r--r-- 1 mej mej 26532 Apr 12 08:15 COPYING.LIB drwxr-xr-x 2 mej mej 4096 Apr 12 08:13 CVS/ -rw-r--r-- 1 mej mej 1357 Apr 12 08:15 Makefile.am -rw-r--r-- 1 mej mej 13334 Apr 12 08:15 Makefile.in -rw-r--r-- 1 mej mej 322 Apr 12 08:15 README -rw-r--r-- 1 mej mej 412 Oct 6 2002 acconfig.h -rw-r--r-- 1 mej mej 128069 Apr 12 08:15 acinclude.m4 -rw-r--r-- 1 mej mej 144512 Apr 12 08:15 aclocal.m4 -rw-r--r-- 1 mej mej 3954 Apr 12 08:15 config-h.in -rwxr-xr-x 1 mej mej 238868 Apr 12 08:15 configure* -rw-r--r-- 1 mej mej 1140 Apr 12 08:15 configure.in -rw-r--r-- 1 mej mej 83661 Apr 12 08:15 ltdl.c -rw-r--r-- 1 mej mej 11722 Apr 12 08:15 ltdl.h If it doesn't, your version of libtoolize sucks. Try another one. 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) ----------------------------------------------------------------------- "Narrow is the road and too high a price to pay when loneliness is such a sanctuary. Empty are the musings and wasted are the days when you say you were only waiting." -- Jars of Clay, "Famous Last Words" |
From: Alan S. <ala...@po...> - 2003-04-12 15:27:29
|
* Michael Jennings (e-...@ka...) wrote: > Note this portion of autogen.sh: > > libtoolize --ltdl --force --copy || abort "libtoolize" OK, I'm using schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> libtoolize --version libtoolize (GNU libtool) 1.4.3 and I get: schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> libtoolize --ltdl --force --copy ls: libltdl/*: No such file or directory The trick was to install libltdl3-devel (I'm on a cooker system). Maybe this could be said in the README. Thanks for your help, Alan Schmitt -- The hacker: someone who figured things out and made something cool happen. |
From: Michael J. <e-...@ka...> - 2003-04-13 04:45:57
|
On Saturday, 12 April 2003, at 11:26:43 (-0400), Alan Schmitt wrote: > The trick was to install libltdl3-devel (I'm on a cooker > system). ^^^^^^^^^^^^^^^ Mandrake Cooker is in the same category as Rawhide and Debian unstable. If you're using it, it's because you don't mind the occasional screw-up, and you are willing and capable to solve the problems yourself. In other words, you deserve what you get, and you don't get to bitch to us when shit breaks. :-) > Maybe this could be said in the README. Uh, no. :) 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) ----------------------------------------------------------------------- "A woman broke up with me and sent me pictures of her and her new boyfriend in bed together. Solution? I sent them to her dad." -- Christopher Case |
From: Alan S. <ala...@po...> - 2003-04-13 07:31:10
|
* Michael Jennings (e-...@ka...) wrote: > On Saturday, 12 April 2003, at 11:26:43 (-0400), > Alan Schmitt wrote: > > > The trick was to install libltdl3-devel (I'm on a cooker > > system). ^^^^^^^^^^^^^^^ > > Mandrake Cooker is in the same category as Rawhide and Debian > unstable. If you're using it, it's because you don't mind the > occasional screw-up, and you are willing and capable to solve the > problems yourself. > > In other words, you deserve what you get, and you don't get to bitch > to us when shit breaks. :-) I agree, that's why I did not bitch and tried to be nice asking the question ;-) > > > Maybe this could be said in the README. > > Uh, no. :) I'm sorry, but I don't understand why. Libltdl is supposed to be installed by default on every system ? I was just proposing to add it as a requirement in the README (as another mail attest, I'm not the only one who got bitten by this). In any case, thanks for the help. I'm now happily back to using e17 as my default wm, and it's just great (I find it much more responsive than e16). Alan -- The hacker: someone who figured things out and made something cool happen. |
From: Michael J. <e-...@ka...> - 2003-04-13 13:41:14
|
On Sunday, 13 April 2003, at 03:30:21 (-0400), Alan Schmitt wrote: > I agree, that's why I did not bitch and tried to be nice asking the > question ;-) :-) > I'm sorry, but I don't understand why. Libltdl is supposed to be > installed by default on every system ? I was just proposing to add > it as a requirement in the README (as another mail attest, I'm not > the only one who got bitten by this). I find it surprising (and a little confusing, to be honest) that Mandrake would split out libltdl from libtool. To the best of my knowledge, no other distro does that. I can't think of any good reason to do so; I mean, it's not like the libltdl stuff takes up a couple hundred meg of disk space or something! :) The reason I said "no" was because I don't want to get into the habit of adding blurbs to the README's whenever some interim incarnation of a distro happens to have an issue. I think that sort of thing is better left to the mailing list archive and the e1x forums. That said, if Mandrake releases with that still being an issue, we will probably need to take some sort of corrective action. Although I'd prefer to add additional smarts to autogen.sh for detecting the problem, rather than depending on users to read the README. I think you can guess why.... :-) > In any case, thanks for the help. I'm now happily back to using e17 > as my default wm, and it's just great (I find it much more > responsive than e16). Glad to hear it. :) 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) ----------------------------------------------------------------------- "It's been awhile since I've seen the way the candles light your face. And it's been awhile, but I can still remember just the way you taste." -- Staind, "It's Been Awhile" |
From: Alan S. <ala...@po...> - 2003-04-14 08:23:21
|
* Michael Jennings (e-...@ka...) wrote: > That said, if Mandrake releases with that still being an issue, we > will probably need to take some sort of corrective action. Although > I'd prefer to add additional smarts to autogen.sh for detecting the > problem, rather than depending on users to read the README. I think > you can guess why.... :-) I did a quick check using rpmfind.net, and it seems that Mandrake is the only one seperating these files. They started doing so in Mandrake 9.0. I could not find any justification for doing so. Alan -- The hacker: someone who figured things out and made something cool happen. |
From: Ibukun O. <ib...@co...> - 2003-04-14 15:22:13
|
On Mon 14 Apr 2003, Alan Schmitt wrote: > * Michael Jennings (e-...@ka...) wrote: > > That said, if Mandrake releases with that still being an issue, we > > will probably need to take some sort of corrective action. Although > > I'd prefer to add additional smarts to autogen.sh for detecting the > > problem, rather than depending on users to read the README. I think > > you can guess why.... :-) > > I did a quick check using rpmfind.net, and it seems that Mandrake is the > only one seperating these files. They started doing so in Mandrake 9.0. > I could not find any justification for doing so. No, I believe libltdl has been separated from libtool for at least a good while before 9.0, likely in the 8.1 or 8.2 releases. I know because as far back as I remember I've always had to install libltdl and libtool as separate packages. > > Alan -- | /*\ Ibukun Olumuyiwa | \ / Join the ASCII Ribbon Campaign http://xcomputerman.com | X against HTML mail today! | / \ |
From: Ryan L. <rli...@co...> - 2003-04-15 01:24:02
|
On Mon, 2003-04-14 at 04:22, Alan Schmitt wrote: > I did a quick check using rpmfind.net, and it seems that Mandrake is the > only one seperating these files. They started doing so in Mandrake 9.0. > I could not find any justification for doing so. The reason Mandrake does this is to split the development headers and tools out from packages/libs that would otherwise be needed for a "Desktop" System. For example you can install libncurses and run progs that require it (like lynx), but to build a kernel you still need ncurses-devel (The ncurses headers) if you want to build menuconfig :) This (IMHO) is a good idea, considering their primary target is the desktop environment. No need to have all these tools and headers on a box if your only users don't need them. I would have thought someone running cooker would know this...it's been this way on Mandrake systems as long as I can remember (although maybe not for libltdl). KainX: Perhaps a note that simply says "Please ensure you have all of the necessary development packages from your distribution installed before attempting to build this library" Ryan AKA Quan |
From: Michael J. <e-...@ka...> - 2003-04-15 01:50:39
|
On Monday, 14 April 2003, at 21:24:26 (-0400), Ryan Little wrote: > The reason Mandrake does this is to split the development headers > and tools out from packages/libs that would otherwise be needed for > a "Desktop" System. For example you can install libncurses and run > progs that require it (like lynx), but to build a kernel you still > need ncurses-devel (The ncurses headers) if you want to build > menuconfig :) No, that's why Mandrake (following RedHat's lead) separates library headers from the actual libraries. Like gtk+ and gtk+-devel. libtool is solely a developer's tool. It is completely, totally, and 100% useless to someone who doesn't build software (i.e., the "desktop environment," as you put it). So it doesn't make any sense to have a "-devel" package for libtool. > This (IMHO) is a good idea, considering their primary target is the > desktop environment. No need to have all these tools and headers on > a box if your only users don't need them. I would have thought > someone running cooker would know this...it's been this way on > Mandrake systems as long as I can remember (although maybe not for > libltdl). If libtool is there, there is absolutely no reason whatsoever not to have libltdl. 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) ----------------------------------------------------------------------- "He is everything you want; he is everything you need. He is everything inside of you that you wish you could be. He says all the right things at exactly the right time, but he means nothing to you and you don't know why." -- Vertical Horizon, "Everything" |
From: Kevin B. <co...@co...> - 2003-04-12 12:38:33
|
Alan Schmitt wrote: > > > Hi, > > Trying to get e17 to work, I decided to get the latest version of all > libs and rebuild them. > > My first question is about build order: the website says that imlib2 > must be built before edb, but imlib2's README says that edb must already > be installed ... So which one is first ? > We've covered this before... imlib2_loaders needs edb, imlib2 technically does not. I've changed the README. Thanks. > The second is about building imlib2. It fails because it cannot do make > in libltdl. Here are some hints as what is happening: > > end of ./autogen.sh: > > configure: configuring in libltdl > configure: WARNING: no configuration information is in libltdl > > it fails when doing make: > > make[1]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2' > Making all in libltdl > make[2]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2/libltdl' > make[2]: *** No rule to make target `all'. Stop. > > which is not surprising: > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> ls libltdl/ > acconfig.h CVS > > which seems to be due to: > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> cat libltdl/.cvsignore > libtool > config* > Makefile* > .libs > .deps > *.lo > *.la > *.in > stamp* > ltdl.c > ltdl.h > acinclude.m4 > aclocal.m4 > COPYING.LIB > README > > So there is definitely something missing in that dir, I think ... autofoo versions again. Some will work, some will not. You'll need to work through this one on your own. Or backdate autotools. -- Kevin |
From: Bryan C. <god...@cr...> - 2003-04-12 14:01:26
|
I got this error recently too whilst building E17. It turned out I simply hadn't installed libtdl. Grabbed an RPM and error went away - so it might not be an autofoo error - might just be stuff missing. Bry > -----Original Message----- > From: enl...@li... > [mailto:enl...@li...] On > Behalf Of Kevin Brosius > Sent: Saturday, April 12, 2003 1:37 PM > To: Alan Schmitt > Cc: e-develop > Subject: Re: [E-devel] making imlib2 > > > Alan Schmitt wrote: > > > > > > Hi, > > > > Trying to get e17 to work, I decided to get the latest > version of all > > libs and rebuild them. > > > > My first question is about build order: the website says > that imlib2 > > must be built before edb, but imlib2's README says that edb must > > already be installed ... So which one is first ? > > > > We've covered this before... imlib2_loaders needs edb, > imlib2 technically does not. I've changed the README. Thanks. > > > > The second is about building imlib2. It fails because it cannot do > > make in libltdl. Here are some hints as what is happening: > > > > end of ./autogen.sh: > > > > configure: configuring in libltdl > > configure: WARNING: no configuration information is in libltdl > > > > it fails when doing make: > > > > make[1]: Entering directory `/usr/src/enlightenment/e17/libs/imlib2' > > Making all in libltdl > > make[2]: Entering directory > > `/usr/src/enlightenment/e17/libs/imlib2/libltdl' > > make[2]: *** No rule to make target `all'. Stop. > > > > which is not surprising: > > > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> ls > > libltdl/ acconfig.h CVS > > > > which seems to be due to: > > > > schmitta@alan-schm1p:/usr/src/enlightenment/e17/libs/imlib2> cat > > libltdl/.cvsignore libtool > > config* > > Makefile* > > .libs > > .deps > > *.lo > > *.la > > *.in > > stamp* > > ltdl.c > > ltdl.h > > acinclude.m4 > > aclocal.m4 > > COPYING.LIB > > README > > > > So there is definitely something missing in that dir, I think ... > > > autofoo versions again. Some will work, some will not. > You'll need to work through this one on your own. Or > backdate autotools. > > -- > Kevin > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of > TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you > feeling lost and > disoriented. TotalView can help you find your way. Available > on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > |