From: Didier C. <did...@sp...> - 2004-05-08 09:32:21
|
Some help needed! I got some compilation errors with etox in cvs Please check it out. ------------------------------------------------------------ (didier@anaconda:etox-0.9.0)$ make [..] checking dynamic linker characteristics... GNU/Linux ld.so checking for edb-config... yes checking for evas-config... yes configure: creating ./config.status config.status: creating Makefile config.status: creating etox-config config.status: creating src/Makefile config.status: creating src/style/Makefile config.status: creating test/Makefile config.status: creating config.h config.status: error: cannot find input file: config.h.in + set +x Now type: make make install have fun. (didier@anaconda:etox-0.9.0)$ make install Making install in src make[1]: Entering directory `/home/didier/build_home/d/e17/libs/etox-0.9.0/src' Makefile:250: .deps/etox.Plo: No such file or directory Makefile:251: .deps/etox_context.Plo: No such file or directory Makefile:252: .deps/etox_line.Plo: No such file or directory Makefile:253: .deps/etox_obstacle.Plo: No such file or directory Makefile:254: .deps/etox_selection.Plo: No such file or directory make[1]: *** No rule to make target `.deps/etox_selection.Plo'. Stop. make[1]: Leaving directory `/home/didier/build_home/d/e17/libs/etox-0.9.0/src' make: *** [install-recursive] Error 1 ------------------------------------------------------------------- With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Didier C. <did...@sp...> - 2004-05-10 06:25:36
|
Etox still failed to compile with the new cvs snapshot today... Did anybody have the same problem? And does anybody know why it's looking for config.h.in?? Cheers, Didier. On 08/05/04, at 17:23 +0800, Didier Casse <did...@sp...> wrote: > Some help needed! > I got some compilation errors with etox in cvs Please check it out. > > ------------------------------------------------------------ > (didier@anaconda:etox-0.9.0)$ make > > [..] > checking dynamic linker characteristics... GNU/Linux ld.so > checking for edb-config... yes > checking for evas-config... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating etox-config > config.status: creating src/Makefile > config.status: creating src/style/Makefile > config.status: creating test/Makefile > config.status: creating config.h > config.status: error: cannot find input file: config.h.in > + set +x > Now type: > > make > make install > > have fun. > > (didier@anaconda:etox-0.9.0)$ make install > > Making install in src > make[1]: Entering directory > `/home/didier/build_home/d/e17/libs/etox-0.9.0/src' > Makefile:250: .deps/etox.Plo: No such file or directory > Makefile:251: .deps/etox_context.Plo: No such file or directory > Makefile:252: .deps/etox_line.Plo: No such file or directory > Makefile:253: .deps/etox_obstacle.Plo: No such file or directory > Makefile:254: .deps/etox_selection.Plo: No such file or directory > make[1]: *** No rule to make target `.deps/etox_selection.Plo'. Stop. > make[1]: Leaving directory > `/home/didier/build_home/d/e17/libs/etox-0.9.0/src' > make: *** [install-recursive] Error 1 > ------------------------------------------------------------------- > |
From: Didier C. <did...@sp...> - 2004-05-10 11:11:34
|
On 10/05/04, at 14:16 +0800, Didier Casse <did...@sp...> wrote: > > Etox still failed to compile with the new cvs snapshot today... Did > anybody have the same problem? > > And does anybody know why it's looking for config.h.in?? > config.h.in has disappeared from cvs! I digged some old cvs snapshot to find in and when I placed the file back ni the tree everything worked. But dudes put it back in cvs! :-p With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Michael J. <e-...@ka...> - 2004-05-10 13:39:38
|
On Monday, 10 May 2004, at 19:02:25 (+0800), Didier Casse wrote: > config.h.in has disappeared from cvs! I digged some old cvs snapshot > to find in and when I placed the file back ni the tree everything > worked. > > But dudes put it back in cvs! :-p No. config.h.in is autogenerated and should not be in CVS. If you lack the tools to recreate it, you shouldn't be building out of CVS. 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) ----------------------------------------------------------------------- "I will be there for you, with these five words I swear to you. When you breathe, I want to be the air for you. I'll be there for you. I'd live and I'd die for you, steal the sun from the sky for you. Words can't say what a love can do. I'll be there for you." -- Bon Jovi |
From: Didier C. <did...@sp...> - 2004-05-11 02:55:15
|
On 10/05/04, at 09:39 -0400, Michael Jennings <e-...@ka...> wrote: > On Monday, 10 May 2004, at 19:02:25 (+0800), > Didier Casse wrote: > > > config.h.in has disappeared from cvs! I digged some old cvs snapshot > > to find in and when I placed the file back ni the tree everything > > worked. > > > > But dudes put it back in cvs! :-p > > No. config.h.in is autogenerated and should not be in CVS. If you > lack the tools to recreate it, you shouldn't be building out of CVS. Dear Michael, Well it is because I DO have the tools that I'm puzzled about it. If I did lack the tools, then the logical thing to do is to try to get them. Right? And also to know which ones to get. The reason why I'm posting here is to get some information and help on these stuff. Because I'm also planning to build rpms out of these to make life easier for others. And you're not really helping out, by telling me "you shouldn't be building out of CVS"! I would have preferred an answer like Ibukun's one that tells to check my autoconf/automake packages, which I just did and upgraded. With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Michael J. <e-...@ka...> - 2004-05-11 12:17:04
|
On Tuesday, 11 May 2004, at 10:46:11 (+0800), Didier Casse wrote: > > > But dudes put it back in cvs! :-p ... > Well it is because I DO have the tools that I'm puzzled about it. If > I did lack the tools, then the logical thing to do is to try to get > them. Right? And also to know which ones to get. > > The reason why I'm posting here is to get some information and help > on these stuff. Because I'm also planning to build rpms out of these > to make life easier for others. Kindly point me to the part of "But dudes put it back in cvs!" which was requesting help, seeking information, or asking a question of any kind. Thanks in advance. 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) ----------------------------------------------------------------------- "If everything is coming your way, you're in the wrong lane." -- fortune |
From: Didier C. <did...@sp...> - 2004-05-11 16:01:34
|
On 11/05/04, at 08:16 -0400, Michael Jennings <e-...@ka...> wrote: > On Tuesday, 11 May 2004, at 10:46:11 (+0800), > Didier Casse wrote: > > > > > But dudes put it back in cvs! :-p > > ... > > > Well it is because I DO have the tools that I'm puzzled about it. If > > I did lack the tools, then the logical thing to do is to try to get > > them. Right? And also to know which ones to get. > > > > The reason why I'm posting here is to get some information and help > > on these stuff. Because I'm also planning to build rpms out of these > > to make life easier for others. > > Kindly point me to the part of "But dudes put it back in cvs!" which > was requesting help, seeking information, or asking a question of any > kind. Thanks in advance. Sorry but I thought it was missing. My mistake. But you could simply have told me "it's not missing, it's your autoconf/automake which is messing with you! Check it out". Besides my sentence had a smile at the end. You take things too seriously in the mailing list. I do not want to argue with you because I love your work and respect you. :-) But hey I have the right to compile from cvs too. I got some success with some PERL scripts of mine that automatically downloaded the libs from cvs and built rpms. Generated today! etox seems to be weird w/ my autoconf/automake. I still have to check it out ------------------------------------------------- ecore-1.0.0_pre7-0.fc1.20040511.i386.rpm ewl-0.0.3-0.fc1.20040511.i386.rpm edb-1.0.5-0.fc1.20040511.i386.rpm imlib2-1.1.1-0.fc1.20040511.i386.rpm edb-ed-1.0.5-0.fc1.20040511.i386.rpm imlib2-devel-1.1.1-0.fc1.20040511.i386.rpm edb-gtk_ed-1.0.5-0.fc1.20040511.i386.rpm imlib2-filters-1.1.1-0.fc1.20040511.i386.rpm edb-vt_ed-1.0.5-0.fc1.20040511.i386.rpm imlib2-loader_argb-1.1.1-0.fc1.20040511.i386.rpm edje-0.5.0-0.fc1.20040511.i386.rpm imlib2-loader_bmp-1.1.1-0.fc1.20040511.i386.rpm eet-0.9.9-0.fc1.20040511.i386.rpm imlib2-loader_gif-1.1.1-0.fc1.20040511.i386.rpm embryo-0.0.1-0.fc1.20040511.i386.rpm imlib2-loader_jpeg-1.1.1-0.fc1.20040511.i386.rpm epeg-0.9.0-0.fc1.20040511.i386.rpm imlib2-loader_png-1.1.1-0.fc1.20040511.i386.rpm epsilon-0.0.2-0.fc1.20040511.i386.rpm imlib2-loader_pnm-1.1.1-0.fc1.20040511.i386.rpm esmart-0.9.0-0.fc1.20040511.i386.rpm imlib2-loader_tga-1.1.1-0.fc1.20040511.i386.rpm estyle-0.0.2-0.fc1.20040511.i386.rpm imlib2-loader_tiff-1.1.1-0.fc1.20040511.i386.rpm evas-1.0.0_pre13-0.fc1.20040511.i386.rpm imlib2-loader_xpm-1.1.1-0.fc1.20040511.i386.rpm ------------------------------------------------- I'm left with examine, engage, and entice to teach my script to build. :-) With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Michael J. <e-...@ka...> - 2004-05-11 16:09:07
|
On Tuesday, 11 May 2004, at 23:52:25 (+0800), Didier Casse wrote: > Sorry but I thought it was missing. My mistake. But you could simply > have told me "it's not missing, it's your autoconf/automake which is > messing with you! Check it out". Yes, but you didn't *ask*, you told. Had you asked, I probably would've worded it differently. :-) > But hey I have the right to compile from cvs too. I would say "privilege" rather than "right." CVS is, first and foremost, a developer tool. Always has been. What's in CVS at any particular moment may or may not compile, and those who lack insight into the how's and why's of each module's status are generally encouraged to refrain from complaints (although patches are always welcome) because it takes developer time away from more worthy tasks. > I got some success with some PERL scripts of mine that automatically > downloaded the libs from cvs and built rpms. You really should check out mezzanine (www.kainx.org/mezzanine/). After running "make dist" a simple "mzbuild" will create RPM's and SRPM's for you. You can also build inside a chroot jail (-r /path/to/jail) or as another user (-u userid) with minimal difficulty. This also makes building for multiple targets as easy as using multiple buildroots, which in turn is as easy as invoking mzbuild multiple times with each chroot path (e.g., "mzbuild -r /path/to/fc1/root ; mzbuild -r /path/to/fc2/root"). > ecore-1.0.0_pre7-0.fc1.20040511.i386.rpm ^^^^^^^^^^^^^^ I'd recommend 0.YYYYMMDD.fcN myself. Otherwise you're giving preference to a dist upgrade over a package upgrade. 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) ----------------------------------------------------------------------- "When I get the courage up to love somebody new, it always falls apart 'cause they just can't compare to you." -- Boyz II Men, "Four Seasons of Loneliness" |
From: Didier C. <did...@sp...> - 2004-05-12 05:11:12
|
On 11/05/04, at 12:09 -0400, Michael Jennings <e-...@ka...> wrote: > > Yes, but you didn't *ask*, you told. Had you asked, I probably > would've worded it differently. :-) I now know what was wrong. In line 5 of the etox configure.in, it's written AM_CONFIG_HEADER(config.h) but if I change it to AC_CONFIG_HEADERS(config.h), it compiles nicely. Apparently the new automake versions do not like AM_..._HEADER but prefers AC_..._HEADERS. I got this info from these automake mailing lists. Now let me rephrase correctly :-p, are you guys going to change this line or must I instruct my scripts to change the line on my machine and compile? > I would say "privilege" rather than "right." CVS is, first and > foremost, a developer tool. Always has been. What's in CVS at any > particular moment may or may not compile, and those who lack insight > into the how's and why's of each module's status are generally > encouraged to refrain from complaints (although patches are always > welcome) because it takes developer time away from more worthy tasks. Ok "privilege" is the right word. I know it's a developer tool. But many people including me want to try out the libraries and install the cool E17 apps. I do not know the "how's and why's of each module's status" but I still wanna help out and understand: in order to make rpms and make life easier for other people with the same type of distro. Because what you guys are doing is terrific and I want more people to share the same pleasure I have in using E. That is why (despite the fact that it's pleasurable and I'm contributing something) I decided to embark on an E17 apt repository project. So far it's advancing. I had to revise all the specs file which seem to be outdated in syntax and style, plus write some cool scripts which extracts info on the modules and buile the rpms. If we wait for really stable EFLs and apps, then we'll be waiting forever and that is not fun! :-p Lay persons wanna have the fun too. Please bear some complaints for E! > You really should check out mezzanine (www.kainx.org/mezzanine/). > After running "make dist" a simple "mzbuild" will create RPM's and > SRPM's for you. You can also build inside a chroot jail > (-r /path/to/jail) or as another user (-u userid) with minimal > difficulty. This also makes building for multiple targets as easy as > using multiple buildroots, which in turn is as easy as invoking > mzbuild multiple times with each chroot path (e.g., "mzbuild -r > /path/to/fc1/root ; mzbuild -r /path/to/fc2/root"). Very cool set of scripts. My building script ressembles yours. Not as elegant of course but which still works and do the job correctly. There are some neat ideas inside yor scripts worth having a look. Thanks a lot. > > ecore-1.0.0_pre7-0.fc1.20040511.i386.rpm > ^^^^^^^^^^^^^^ > I'd recommend 0.YYYYMMDD.fcN myself. Otherwise you're giving > preference to a dist upgrade over a package upgrade. > Yeps. noted. Thanks. With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Corey D. <cdo...@me...> - 2004-05-13 17:57:28
|
* Didier Casse (did...@sp...) wrote: > On 11/05/04, at 12:09 -0400, Michael Jennings <e-...@ka...> wrote: > > > > > Yes, but you didn't *ask*, you told. Had you asked, I probably > > would've worded it differently. :-) > > I now know what was wrong. In line 5 of the etox configure.in, it's > written > > AM_CONFIG_HEADER(config.h) > > but if I change it to AC_CONFIG_HEADERS(config.h), it compiles > nicely. Apparently the new automake versions do not like AM_..._HEADER > but prefers AC_..._HEADERS. I got this info from these automake mailing > lists. > > Now let me rephrase correctly :-p, are you guys going to change this line > or must I instruct my scripts to change the line on my machine and > compile? > This fixed someone else's compile errors on #edevelop. Thanks Didier. Does someone want to commit this ? __ Corey Donohoe http://www.atmos.org/ |
From: Michael K. <lavnrose@e.sarang.net> - 2004-05-13 21:12:23
Attachments:
EDR16-KOREAN.tar.bz2
|
We want the theme and menu to be included in a distribution. Project were not changed though I sent the mail. The item to be included is as follows. Korean menu and theme. ---------------------------------------------------------------------------- ---------------- config.ko ----------------------------------------------> menu item for Korean enlightenment-0.16.5-ko_no_bin.patch ------> patch for Makefile BlueSteel.etheme.ko ------------------------------> theme BrushedMetal-Tigert.etheme.ko ----------------> theme ShinyMetal.etheme.ko -----------------------------> theme Ganymede.etheme.ko -----------------------------> theme ---------------------------------------------------------------------------- ---------------- Site URL ------------- FTP : ftp://e.sarang.net/pub/enlightenment/sources/patch WWW : http://e.sarangnet/ |
From: Kim W. <ki...@wo...> - 2004-05-13 22:07:54
|
Hello Michael, I would be happy to include this, however... The changes seem to apply to E16.5. The directory layout and other stuff has changed quite a lot since that. Could you please update this to be a patch on the current CVS? /Kim Michael Kim wrote: > We want the theme and menu to be included in a distribution. > Project were not changed though I sent the mail. > > The item to be included is as follows. > Korean menu and theme. > ---------------------------------------------------------------------------- > ---------------- > config.ko ----------------------------------------------> menu item for > Korean > enlightenment-0.16.5-ko_no_bin.patch ------> patch for Makefile > BlueSteel.etheme.ko ------------------------------> theme > BrushedMetal-Tigert.etheme.ko ----------------> theme > ShinyMetal.etheme.ko -----------------------------> theme > Ganymede.etheme.ko -----------------------------> theme > ---------------------------------------------------------------------------- > ---------------- > > Site URL > ------------- > FTP : ftp://e.sarang.net/pub/enlightenment/sources/patch > WWW : http://e.sarangnet/ |
From: Michael K. <lavnrose@e.sarang.net> - 2004-05-18 13:38:18
Attachments:
enlightenment-0.16.7-ko.patch.bz2
|
I am sorry for doing so that you have long wait. Yes, here modified patch for korean. - Updated config for Korean. (config.ko) - Added winter theme for korean. (winter.etheme.ko) - Fixed Makefile for multingua. (theme/Makefile.am) - Removed old theme in DR16.6 (No longer BlueSteel, BurshedMetal,...) But, If you need theme for korean, visit a follow address ftp://e.sarang.net/pub/enlightenment/theme/DR16/ ---------------- Site URL ------------- WWW : http://e.sarangnet/ ----- Original Message ----- From: "Kim Woelders" > Hello Michael, > > I would be happy to include this, however... > The changes seem to apply to E16.5. > The directory layout and other stuff has changed quite a lot since that. > Could you please update this to be a patch on the current CVS? > > /Kim > > Michael Kim wrote: > > We want the theme and menu to be included in a distribution. > > Project were not changed though I sent the mail. > > > > The item to be included is as follows. > > Korean menu and theme. > > -------------------------------------------------------------------------- -- > > ---------------- > > config.ko ----------------------------------------------> menu item for > > Korean > > enlightenment-0.16.5-ko_no_bin.patch ------> patch for Makefile > > BlueSteel.etheme.ko ------------------------------> theme > > BrushedMetal-Tigert.etheme.ko ----------------> theme > > ShinyMetal.etheme.ko -----------------------------> theme > > Ganymede.etheme.ko -----------------------------> theme > > -------------------------------------------------------------------------- -- > > ---------------- > > > > Site URL > > ------------- > > FTP : ftp://e.sarang.net/pub/enlightenment/sources/patch > > WWW : http://e.sarangnet/ > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > |
From: Kim W. <ki...@wo...> - 2004-05-20 22:35:00
|
Michael Kim wrote: > Yes, here modified patch for korean. > > - Updated config for Korean. (config.ko) > - Added winter theme for korean. (winter.etheme.ko) > - Fixed Makefile for multingua. (theme/Makefile.am) > - Removed old theme in DR16.6 (No longer BlueSteel, BurshedMetal,...) > OK, committed (with minor changes in the auto* stuff). The old themes are still in CVS, now under e16/ethemes/..., and are released in separate packages. I think you had Korean addittions for those, if you want them added too, please send a patch for that. /Kim |
From: Ibukun O. <ib...@co...> - 2004-05-10 13:42:39
|
Didier Casse wrote: > On 10/05/04, at 14:16 +0800, Didier Casse <did...@sp...> wrote: > > >>Etox still failed to compile with the new cvs snapshot today... Did >>anybody have the same problem? >> >>And does anybody know why it's looking for config.h.in?? >> > > > > config.h.in has disappeared from cvs! I digged some old cvs snapshot to > find in and when I placed the file back ni the tree everything worked. > > But dudes put it back in cvs! :-p > config.h.in is automatically generated by autoheader from configure.in. If it isn't getting generated during autogen then something must be wrong with your autoconf/automake installation. There is no config.h.in anywhere in the e17/ repository in CVS. Ibukun |
From: Didier C. <did...@sp...> - 2004-05-11 02:46:27
|
On 10/05/04, at 08:42 -0500, Ibukun Olumuyiwa <ib...@co...> wrote: > Didier Casse wrote: > > On 10/05/04, at 14:16 +0800, Didier Casse <did...@sp...> wrote: > > > > > >>Etox still failed to compile with the new cvs snapshot today... Did > >>anybody have the same problem? > >> > >>And does anybody know why it's looking for config.h.in?? > >> > > > > > > > > config.h.in has disappeared from cvs! I digged some old cvs snapshot to > > find in and when I placed the file back ni the tree everything worked. > > > > But dudes put it back in cvs! :-p > > > > config.h.in is automatically generated by autoheader from configure.in. > If it isn't getting generated during autogen then something must be > wrong with your autoconf/automake installation. There is no config.h.in > anywhere in the e17/ repository in CVS. > Thanks Ibukun. I never have any problems with autoconf/automake until 2 days ago. I could build etox very straighforward from ./autogen.sh I use autoconf-2.59 automake-1.7.9 It can't be that bad. ----------------------------------------------------------------- + autoheader autoheader: error: AC_CONFIG_HEADERS not found in configure.in + libtoolize --ltdl --force --copy You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. + aclocal + automake --foreign --add-missing configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' configure.in:5: required file `./config.h.in' not found src/Makefile.am: installing `./depcomp' + autoconf + test -z '' ---------------------------------------------------------------- somehow it tells me this which I never had before: "AC_CONFIG_HEADERS not found in configure.in" But when I sort of put it in debug mode by bash -x autogen.sh, it compiles perfectly. Weird! With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg / didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg |
From: Andreas V. <li...@br...> - 2004-05-13 23:05:06
|
Am Mon, 10 May 2004 14:16:32 +0800 (SGT) schrieb Didier Casse: > > Etox still failed to compile with the new cvs snapshot today... Did > anybody have the same problem? > Yes, the problem is still im Gentoo. I reported it to bugs.gentoo.org but get no answer yet. Andreas |