From: Soren A <sor...@fa...> - 2002-09-27 18:47:02
|
Hello, It seems to me that if I want to get in on the MinGW/MSYS 'libtool' -fixing game, for instance, I need to download the MSYS-DTK (alpha) package which Earnie prepared earlier this year, is this right? I am wondering where the sources for things themselves are. I haven't ever seriously tried to build 'automake' for example, on any platform (yes, I do realize that 'automake' is a Perl script, thus it is not compiled per se, but I guess that there are various arcane and mysterious things done when it is "built"?). Looking at the 'browse cvs' at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mingw I cannot really find the sources themselves. Is it the implication, then, that no patching is done and the user is expected to go to the canonical download locations (or cvs locations) for each of these pieces of MSYS-DTK? I cannot even come close to expressing adequately how much I am not loving the need to mess around with 'automake' in such a way that I am going to have to grapple with its installation issues, but I don't see any alternative if I am to learn and get up to speed with what Earnie, Max and others are doing here. I have been using my Cygwin autotools (from in a separate Cygwin bash session, obviously) in order to rebuild generated autotool'ed files ('configure's and 'Makefile.in's) in the MinGW packages I have been working on, but that just lets me enjoy the bugs in Cygwin autotools, which are falling behind in version anyway. one lonely C file. Rather than start from "scratch", isn't what I want to do to get the MSYS-DTK and then one-by-one go grab the latest of everything from their respective cvs repositories: Automake, Autoconf, libtool itself of course. And try to update each piece at a time? I am sure the answer, when it comes, is going to be something very obvious, but I think I ought to ask anyway. Under / mingw / msys / dvlpr / pm we find: msysDTK.pm Package Version Architectures Directories -------- ------- -------------- ----------- autoconf 2.53 i386 i586 i686 /bin automake 1.6.4 i386 i586 i686 /bin libtool cvssrc i386 i586 i686 /bin perl 5.6.1 i386 openssh openssl 0.9.6b i386 /bin cvs inetutils vim 5.8 /usr/share/vim zlib gdbm ---------------------------------------------------- While the main sf page describing msysDTK snapshot 1.0.0 says: Includes the msys-1.0.dll dependent binary releases of: autoconf-2.53 automake-1.6.1 libtool-1.4.2 perl-5.6.1 openssl-0.9.6b openssh-2.9p2 (client tools only) zlib-1.1.3 gdbm-1.8.0 cvs-1.11 (client tools only) inetutils-1.3.2 (client tools only) and the usr/share/vim/ files. ------------------------------------------------------- BTW, "zlib-1.1.3" is out of date and should be replaced with 1.1.4 because of a security issue. TIA, Soren A P.S. Regarding my frequent derogatory allusions concerning 'automake', its not like there don't exist any alternatives: there's GNU 'mfg' for instance. |
From: Soren A <sor...@fa...> - 2002-09-27 18:53:21
|
Soren A <soren_andersen=97j...@pu...> wrote around 27 Sep 2002 news:Xns9296965E99B96soren1Gmane@80.91.224.249: > one lonely C file. Sorry,my text was victimized. It was gremlins, I swear it. My IP packets were abducted on their way to you and tampered with ;-). That referred to the fact that under src/ buried in the "view cvs" stuff on sf there's only one file (a .c source file). Soren A |
From: Soren A <sor...@fa...> - 2002-09-27 19:13:10
|
Soren A <soren_andersen=97j...@pu...> wrote around 27 Sep 2002 news:Xns9296965E99B96soren1Gmane@80.91.224.249: > And try to update each piece at a time? I didn't need the ssl stuff, or cvs, or vim. In order to prune out the unneeded stuff from the package I used this: ------------8<----------------------------------------------------- ## Used this to prune out some stuff from the distro: $ tar -xvz -f msysDTK-1.0.0-alpha-1.tar.gz \ --exclude='ssl/*' --exclude='share/vim/*' --exclude='lib/cvs/*' \ --exclude='include/*' --exclude='bin/s*' ## ------------8<----------------------------------------------------- Untested as of this writing. Apply this "tip" at your own risk. This left the Autotools, and msys-perl (which ought to act pretty much exactly like cygwin-Perl, right Earnie? Isn't your perl build very much similar?) and so on. Thanks again, Earnie, for the DTK. Soren A |
From: Earnie B. <ear...@ya...> - 2002-09-27 20:00:06
|
Soren A wrote: > > Soren A <soren_andersen=97j...@pu...> wrote around 27 Sep 2002 news:Xns9296965E99B96soren1Gmane@80.91.224.249: > > > And try to update each piece at a time? > > I didn't need the ssl stuff, or cvs, or vim. In order to prune out the > unneeded stuff from the package I used this: > > ------------8<----------------------------------------------------- > ## Used this to prune out some stuff from the distro: > $ tar -xvz -f msysDTK-1.0.0-alpha-1.tar.gz \ > --exclude='ssl/*' --exclude='share/vim/*' --exclude='lib/cvs/*' \ > --exclude='include/*' --exclude='bin/s*' > ## > ------------8<----------------------------------------------------- > > Untested as of this writing. Apply this "tip" at your own risk. > > This left the Autotools, and msys-perl (which ought to act pretty much > exactly like cygwin-Perl, right Earnie? Isn't your perl build very much > similar?) and so on. > Mostly, I did a basic build with the MSYS host/build system found in msysDVLPR package. > Thanks again, Earnie, for the DTK. > You're welcome. Earnie. |
From: Earnie B. <ear...@ya...> - 2002-09-27 19:55:46
|
Soren A wrote: > > Hello, > > It seems to me that if I want to get in on the MinGW/MSYS 'libtool' > -fixing game, for instance, I need to download the MSYS-DTK (alpha) > package which Earnie prepared earlier this year, is this right? > > I am wondering where the sources for things themselves are. I haven't > ever seriously tried to build 'automake' for example, on any platform > (yes, I do realize that 'automake' is a Perl script, thus it is not > compiled per se, but I guess that there are various arcane and > mysterious things done when it is "built"?). > Since it was an alpha build I just haven't gotten too it. :( You would need msysDVLPR package as well to build the source. MSYS has a way to go before some packages will interoperate between Win32 and POSIX style paths and interprocess communication. :( That's why I needed the msysDTK package anyway. I'll upgrade it with source within 2 to 3 weeks. Earnie. |
From: Soren A <sor...@fa...> - 2002-09-27 20:11:51
|
Earnie Boyd <ear...@ya...> wrote around 27 Sep 2002 news:3D9...@ya...: [Soren A] >> I haven't ever seriously tried to build 'automake' for example, on >> any platform (yes, I do realize that 'automake' is a Perl script, >> thus it is not compiled per se, but I guess that there are various >> arcane and mysterious things done when it is "built"?). > Since it was an alpha build I just haven't gotten too it. :( You would > need msysDVLPR package as well to build the source. MSYS has a way to > go before some packages will interoperate between Win32 and POSIX style > paths and interprocess communication. :( That's why I needed the > msysDTK package anyway. I'll upgrade it with source within 2 to 3 > weeks. OK! I am wondering, in the interim. It may not be such an easy question to answer, but if it isn't too complex a head-scratcher... could you offer me advice based on your knowledge of the 'libtool' part of autotools: how could I best go about updating *just* libtool? I know very little, but I know that 'libtool' is one shell script 'ltmain.sh' + a bunch of stuff (somewhere under "share/"[??]). And what is the canonical download location and / or cvs url for libtool? I am looking at the libtool developers Lists but cannot figure this out. Thanks, Soren A |
From: Earnie B. <ear...@ya...> - 2002-09-27 21:37:07
|
Soren A wrote: > > Earnie Boyd <ear...@ya...> wrote around 27 Sep 2002 > news:3D9...@ya...: > > [Soren A] > >> I haven't ever seriously tried to build 'automake' for example, on > >> any platform (yes, I do realize that 'automake' is a Perl script, > >> thus it is not compiled per se, but I guess that there are various > >> arcane and mysterious things done when it is "built"?). > > > Since it was an alpha build I just haven't gotten too it. :( You would > > need msysDVLPR package as well to build the source. MSYS has a way to > > go before some packages will interoperate between Win32 and POSIX style > > paths and interprocess communication. :( That's why I needed the > > msysDTK package anyway. I'll upgrade it with source within 2 to 3 > > weeks. > > OK! > > I am wondering, in the interim. It may not be such an easy question to > answer, but if it isn't too complex a head-scratcher... could you offer > me advice based on your knowledge of the 'libtool' part of autotools: > how could I best go about updating *just* libtool? I know very little, > but I know that 'libtool' is one shell script 'ltmain.sh' + a bunch of > stuff (somewhere under "share/"[??]). And what is the canonical download > location and / or cvs url for libtool? I am looking at the libtool > developers Lists but cannot figure this out. > $ cat CVS/Root :pserver:an...@su...:/cvsroot/libtool http://subversions.gnu.org/ As for the replacement, I'll see what I can do for you this weekend. HTH, Earnie. |
From: Soren A <sor...@fa...> - 2002-10-01 00:47:32
|
Earnie Boyd <ear...@ya...> wrote around 27 Sep 2002 news:3D9...@ya...: >> OK! >> >> I am wondering, in the interim. It may not be such an easy question to >> answer, but if it isn't too complex a head-scratcher... could you offer >> me advice based on your knowledge of the 'libtool' part of autotools: >> how could I best go about updating *just* libtool? I know very little, >> but I know that 'libtool' is one shell script 'ltmain.sh' + a bunch of >> stuff (somewhere under "share/"[??]). And what is the canonical download >> location and / or cvs url for libtool? I am looking at the libtool >> developers Lists but cannot figure this out. >> > > $ cat CVS/Root >:pserver:an...@su...:/cvsroot/libtool > > http://subversions.gnu.org/ > > As for the replacement, I'll see what I can do for you this weekend. I don't know how that's going (but _thanks_); but I got the src for libtool from cvs and built it myself. I have a bit of lingering doubt that i would like to have resolved, tho, before I begin to invest time and expectation in the newly-updated libtool I now have installed (I have one in /bin). When i run "$ libtool --version" I get: ./libtool: s%^.*/%%: No such file or directory ltmain.sh (GNU libtool) 1.4e (1.1133 2002/09/25 04:26:19) [and then the rest of the GNU copyleft information] What's up with that first line? Just noise or something real? Phoooey. Now I get why people are badmouthing libtool. The command named 'ltconfig' went away, didn't it, and now there's no way to run a configuration to set up libtool aside from a GNU Autoconf-based 'configure.ac' script? That has the odorous stench of a really unfortunate midstream change of direction by libtool's developers. Bleah. Best, Soren A |
From: Earnie B. <ear...@ya...> - 2002-10-01 01:05:30
|
Soren A wrote: > > > > > As for the replacement, I'll see what I can do for you this weekend. > Obviously, I didn't get a round tuit this weekend. > I don't know how that's going (but _thanks_); but I got the src for libtool > from cvs and built it myself. I have a bit of lingering doubt that i would > like to have resolved, tho, before I begin to invest time and expectation > in the newly-updated libtool I now have installed (I have one in /bin). > > When i run "$ libtool --version" I get: > ./libtool: s%^.*/%%: No such file or directory > ltmain.sh (GNU libtool) 1.4e (1.1133 2002/09/25 04:26:19) > The libtool script is for some reason missing a `SED=sed', add it near the top of the script and all should be happy. > [and then the rest of the GNU copyleft information] > > What's up with that first line? Just noise or something real? > > Phoooey. Now I get why people are badmouthing libtool. The command named > 'ltconfig' went away, didn't it, and now there's no way to run a > configuration to set up libtool aside from a GNU Autoconf-based > 'configure.ac' script? That has the odorous stench of a really > unfortunate midstream change of direction by libtool's developers. > Bleah. > You should try building CVS version of autoconf and/or automake. What a circular dependency mess. One must `touch configure' in the package before proceeding to `make'. Earnie. |
From: Soren A <sor...@fa...> - 2002-10-01 04:34:16
|
Earnie Boyd <ear...@ya...> wrote around 30 Sep 2002 news:3D9...@ya...: > Soren A wrote: >> >> > >> > As for the replacement, I'll see what I can do for you this >> > weekend. >> > > Obviously, I didn't get a round tuit this weekend. I've been finding more and more that square or rectangular tuits work nearly as well and are far more readily available to me ... ;-) >> I don't know how that's going (but _thanks_); but I got the src for >> libtool from cvs and built it myself. I have a bit of lingering doubt >> that i would like to have resolved, tho, before I begin to invest >> time and expectation in the newly-updated libtool I now have >> installed (I have one in /bin). >> >> When i run "$ libtool --version" I get: >> ./libtool: s%^.*/%%: No such file or directory >> ltmain.sh (GNU libtool) 1.4e (1.1133 2002/09/25 04:26:19) >> > > The libtool script is for some reason missing a `SED=sed', add it near > the top of the script and all should be happy. :-) yep, makes me happy! >> [and then the rest of the GNU copyleft information] >> >> What's up with that first line? Just noise or something real? >> >> Phoooey. Now I get why people are badmouthing libtool. The command >> named 'ltconfig' went away, didn't it, and now there's no way to run >> a configuration to set up libtool aside from a GNU Autoconf-based >> 'configure.ac' script? That has the odorous stench of a really >> unfortunate midstream change of direction by libtool's developers. >> Bleah. >> > > You should try building CVS version of autoconf and/or automake. What > a circular dependency mess. One must `touch configure' in the package > before proceeding to `make'. Sheesh, yeah, that's very symptomatic of 'make' dependencies tables out of control. Thanks very much, Earnie, Soren |