From: Jamie L. <jla...@gm...> - 2009-03-28 05:43:11
|
I am trying to build a C library called RSL. The author gave me a few files to speed up the process but I can into a problem trying to "make": $ make cd . && automake --foreign Makefile /bin/sh: automake: command not found make: *** [Makefile.in] Error 127 this seems like automake is not available. Is this true? Can it be installed successfully? -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jr...@hu... |
From: Sisyphus <sis...@op...> - 2009-03-28 08:09:26
|
----- Original Message ----- From: "Jamie Lahowetz" <jla...@gm...> To: "MinGW Users List" <min...@li...> Sent: Saturday, March 28, 2009 4:43 PM Subject: [Mingw-users] Building RSL >I am trying to build a C library called RSL. I recently tried to build that library (v1.40) in the msys shell using the official source. Configure ran fine, but struck trouble when it came to compiling some of the source files during 'make'. There were a couple of C source files (rapic_routines.c and dorade.c) that contained: #include netinet/in.h My MinGW has no netinet/in.h, but I was able to get those 2 files to compile by simply commenting out the offending "#include netinet/in.h" However, a third file (lassen.c) also wants to include the non-existent rpc/rpc.h. That's where I got snookered - seems that file really *is* needed by the source, so the include cannot simply be removed. Has the author fixed the rpc/rpc.h dependency for you ? If not it will rear its head at some stage for you, too. Cheers, Rob |
From: Jamie L. <jla...@gm...> - 2009-03-28 14:53:13
|
On Sat, Mar 28, 2009 at 3:07 AM, Sisyphus <sis...@op...> wrote: > > ----- Original Message ----- > From: "Jamie Lahowetz" <jla...@gm...> > To: "MinGW Users List" <min...@li...> > Sent: Saturday, March 28, 2009 4:43 PM > Subject: [Mingw-users] Building RSL > > > >I am trying to build a C library called RSL. > > I recently tried to build that library (v1.40) in the msys shell using the > official source. Configure ran fine, but struck trouble when it came to > compiling some of the source files during 'make'. > > There were a couple of C source files (rapic_routines.c and dorade.c) that > contained: > #include netinet/in.h > > My MinGW has no netinet/in.h, but I was able to get those 2 files to > compile > by simply commenting out the offending "#include netinet/in.h" The author did send me a set of files that gets rid of the netinet. I can send them to you. They need the automake stuff mentioned above. Maybe you can get them going and see if the rpc dependency is needed. > > > However, a third file (lassen.c) also wants to include the non-existent > rpc/rpc.h. That's where I got snookered - seems that file really *is* > needed > by the source, so the include cannot simply be removed. > > Has the author fixed the rpc/rpc.h dependency for you ? If not it will rear > its head at some stage for you, too. > > Cheers, > Rob > > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jr...@hu... |
From: Keith M. <kei...@us...> - 2009-03-28 15:26:10
|
On Saturday 28 March 2009 14:53:02 Jamie Lahowetz wrote: > They need the automake stuff mentioned above. Autoconf, automake and libtool are all in the MSYS Supplementary Tools collection, on the project download site at SF. > Maybe you can get them going and see if the rpc dependency is needed. Why can you not get them going for yourself? -- Regards, Keith. |
From: Jamie L. <jla...@gm...> - 2009-03-28 16:23:11
|
On Sat, Mar 28, 2009 at 10:25 AM, Keith Marshall < kei...@us...> wrote: > On Saturday 28 March 2009 14:53:02 Jamie Lahowetz wrote: > > They need the automake stuff mentioned above. > > Autoconf, automake and libtool are all in the MSYS Supplementary Tools > collection, on the project download site at SF. Con't seem to get it installed I am getting this: cp: cannot stat `/tmp/ac-wrapper-4.sh': No such file or directory tar (child): /usr/local/src/autoconf/wrapper/autoconf-4/../autoconf-4-1-bin.tar.bz2: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now local/ local/bin/ local/bin/autoconf local/bin/autoheader local/bin/autom4te local/bin/autoreconf local/bin/autoscan local/bin/autoupdate local/bin/ifnames local/share/ local/share/autotools/ ./mingwPORT.sh: line -677: 4652 Broken pipe tar cv${cmparg}f ${BINPKG} * tar: mingwPORT/mingwPORT/mingwPORT.*: Cannot stat: No such file or directory tar: mingwPORT/mingwPORT/mirrors.sf: Cannot stat: No such file or directory tar: Error exit delayed from previous errors cp: cannot stat `/tmp/ac-wrapper-4.sh': No such file or directory autoconf-4-1-mingwPORT.tar.bz2 tar (child): /usr/local/src/autoconf/wrapper/autoconf-4/../autoconf-4-1-src.tar.bz2: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors With the beginning Q's as such? Archive file? (ac-wrapper-4.sh) Download directory? (/tmp) Source path? (/usr/local/src/autoconf/wrapper/autoconf-4) /autoconf-4/mingwPORT Installation directory? (/usr/local) /local CFLAGS (-O3 -s -mms-bitfields -mcpu=pentium) CXXFLAGS (-O3 -s -mms-bitfields -mcpu=pentium) I put the acwrapper-4.sh in the /tmp folder but still get the error. > > > > Maybe you can get them going and see if the rpc dependency is needed. > > Why can you not get them going for yourself? I'm trying. > > > -- > > Regards, > Keith. > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jr...@hu... |
From: Keith M. <kei...@us...> - 2009-03-28 18:03:29
|
On Saturday 28 March 2009 16:23:01 Jamie Lahowetz wrote: > > Autoconf, automake and libtool are all in the MSYS Supplementary > > Tools collection, on the project download site at SF. > > Con't seem to get it installed I am getting this: > [...snip...] > > I put the acwrapper-4.sh in the /tmp folder but still get the error. Why there? What exactly are you trying to install? You need: * http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 * http://downloads.sourceforge.net/mingw/autoconf2.1-2.13-3-bin.tar.bz2 * http://downloads.sourceforge.net/mingw/autoconf2.5-2.61-1-bin.tar.bz2 * http://downloads.sourceforge.net/mingw/autoconf-4-1-bin.tar.bz2 * http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 cd to your MSYS *root* directory: $ cd / then untar all of those there, e.g. $ tar xjf /<your-downloads-dir>/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 etc. Then it should work. -- Regards, Keith. |
From: Jamie L. <jla...@gm...> - 2009-03-28 23:15:38
|
On Sat, Mar 28, 2009 at 1:03 PM, Keith Marshall < kei...@us...> wrote: > On Saturday 28 March 2009 16:23:01 Jamie Lahowetz wrote: > > > Autoconf, automake and libtool are all in the MSYS Supplementary > > > Tools collection, on the project download site at SF. > > > > Con't seem to get it installed I am getting this: > > [...snip...] > > > > I put the acwrapper-4.sh in the /tmp folder but still get the error. > > Why there? What exactly are you trying to install? You need: > > * http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > * http://downloads.sourceforge.net/mingw/autoconf2.1-2.13-3-bin.tar.bz2 > * http://downloads.sourceforge.net/mingw/autoconf2.5-2.61-1-bin.tar.bz2 > * http://downloads.sourceforge.net/mingw/autoconf-4-1-bin.tar.bz2 > * http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 > > cd to your MSYS *root* directory: > > $ cd / > > then untar all of those there, e.g. > > $ tar xjf /<your-downloads-dir>/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > > etc. Then it should work. I need to install automake so that I can get rsl built. I downloaded all those files and untared them in my / directory. I'm guessing that I need to get and untar: autoconf2.5-2.61-1-mingwPORT.tar.bz2 cd to the directory and ran ./mingwPORT.sh Yes to the download since I dont have autoconf-2.61.tar.gz After that I get the error: --18:08:04-- http://voxel.dl.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz => `autoconf-2.61.tar.gz' Resolving voxel.dl.sourceforge.net... done. Connecting to voxel.dl.sourceforge.net[72.26.194.82]:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?download&failedmirror=voxel.dl.sourceforge.net[following] --18:08:06-- http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?download&failedmirror=voxel.dl.sourceforge.net => `autoconf-2.61.tar.gz@download&failedmirror= voxel.dl.sourceforge.net' Resolving downloads.sourceforge.net... done. Connecting to downloads.sourceforge.net[216.34.181.60]:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://sourceforge.net/projects/autoconf2-5/files [following] --18:08:06-- http://sourceforge.net/projects/autoconf2-5/files => `files.2' Resolving sourceforge.net... done. Connecting to sourceforge.net[216.34.181.60]:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] 0K ......... 104.46 KB/s 18:08:06 (104.46 KB/s) - `files.2' saved [10162] tar (child): /download/autoconf-2.61.tar.gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors mingwPORT.afterquestion: tar: FATAL: command failed; mingwPORT cannot continue. I am confused on the reason I needed to download and install all the prior modules? The Perl module is fairly old and there are more than one autoconf version. Can anyone explain why I need all these files and what is the minimal amount of work that I need to do to install automake? > > > -- > > Regards, > Keith. > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jr...@hu... |
From: Keith M. <kei...@us...> - 2009-03-29 16:50:47
|
On Saturday 28 March 2009 23:15:33 Jamie Lahowetz wrote: > On Sat, Mar 28, 2009 at 1:03 PM, Keith Marshall < > > kei...@us...> wrote: > > On Saturday 28 March 2009 16:23:01 Jamie Lahowetz wrote: > > > > Autoconf, automake and libtool are all in the MSYS Supplementary > > > > Tools collection, on the project download site at SF. > > > > > > Con't seem to get it installed I am getting this: > > > [...snip...] > > > > > > I put the acwrapper-4.sh in the /tmp folder but still get the > > > error. > > > > Why there? What exactly are you trying to install? You need: > > > > * http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > > * http://downloads.sourceforge.net/mingw/autoconf2.1-2.13-3-bin.tar.bz2 > > * http://downloads.sourceforge.net/mingw/autoconf2.5-2.61-1-bin.tar.bz2 > > * http://downloads.sourceforge.net/mingw/autoconf-4-1-bin.tar.bz2 > > * http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 > > > > cd to your MSYS *root* directory: > > > > $ cd / > > > > then untar all of those there, e.g. > > > > $ tar xjf /<your-downloads-dir>/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > > > > etc. Then it should work. > > I need to install automake so that I can get rsl built. It's the last of the packages I listed. > I downloaded all those files and untared them in my / directory. > I'm guessing that I need to get and untar: > autoconf2.5-2.61-1-mingwPORT.tar.bz2 No, you don't. Sorry, I did miss one prerequisite: http://downloads.sourceforge.net/mingw/m4-1.4.7-MSYS.tar.bz2 If you install that, plus what I've listed previously, you will have a working autoconf, and automake too, I believe; (I use autoconf routinely, but I avoid automake like the plague). > cd to the directory and ran ./mingwPORT.sh > Yes to the download since I dont have autoconf-2.61.tar.gz > > After that I get the error: > --18:08:04-- > http://voxel.dl.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz > => `autoconf-2.61.tar.gz' > Resolving voxel.dl.sourceforge.net... done. > Connecting to voxel.dl.sourceforge.net[72.26.194.82]:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: > http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?downl >oad&failedmirror=voxel.dl.sourceforge.net[following] --18:08:06-- > http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?downl >oad&failedmirror=voxel.dl.sourceforge.net => > `autoconf-2.61.tar.gz@download&failedmirror= > voxel.dl.sourceforge.net' > Resolving downloads.sourceforge.net... done. > Connecting to downloads.sourceforge.net[216.34.181.60]:80... connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: http://sourceforge.net/projects/autoconf2-5/files [following] > --18:08:06-- http://sourceforge.net/projects/autoconf2-5/files > => `files.2' > Resolving sourceforge.net... done. > Connecting to sourceforge.net[216.34.181.60]:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: unspecified [text/html] > > 0K ......... 104.46 > KB/s > > 18:08:06 (104.46 KB/s) - `files.2' saved [10162] > > tar (child): /download/autoconf-2.61.tar.gz: Cannot open: No such file > or directory > tar (child): Error is not recoverable: exiting now > tar: Child returned status 2 > tar: Error exit delayed from previous errors > mingwPORT.afterquestion: tar: FATAL: command failed; mingwPORT cannot > continue. Don't know what's going on there; the mingwPORT should not be looking on SF for the sources -- it should use direct download from the FSF site. Anyway, you *don't* need the mingwPORT! > I am confused on the reason I needed to download and install all the > prior modules? The Perl module is fairly old and there are more than > one autoconf version. Can anyone explain why I need all these files and > what is the minimal amount of work that I need to do to install > automake? Install the files I've listed; that should suffice. You *must* have perl installed, and it *must* understand MSYS emulated POSIX paths; hence it must be that version I've specified, regardless of its age. There are multiple autoconf versions because there were some significant, and incompatible changes between the 2.1x series and the 2.5x/6x series, but some projects still demand the older variant; the autoconf-4 *isn't* autoconf proper; it is a wrapper to automagically select between the 2.1x or 2.5x/6x variant, based on the content of the input, so you just run autoconf, and it will DTRT. If you just want the newer autoconf, you can just as well get the current FSF autoconf-2.63 source, and build it; (it should build OOTB, *provided* you use a build directory *outside* the source tree, and you *must* also first have those MSYS versions of perl and m4 installed). -- Regards, Keith. |
From: Jamie L. <jla...@gm...> - 2009-03-29 20:19:27
|
On Sun, Mar 29, 2009 at 11:50 AM, Keith Marshall < kei...@us...> wrote: > On Saturday 28 March 2009 23:15:33 Jamie Lahowetz wrote: > > On Sat, Mar 28, 2009 at 1:03 PM, Keith Marshall < > > > > kei...@us...> wrote: > > > On Saturday 28 March 2009 16:23:01 Jamie Lahowetz wrote: > > > > > Autoconf, automake and libtool are all in the MSYS Supplementary > > > > > Tools collection, on the project download site at SF. > > > > > > > > Con't seem to get it installed I am getting this: > > > > [...snip...] > > > > > > > > I put the acwrapper-4.sh in the /tmp folder but still get the > > > > error. > > > > > > Why there? What exactly are you trying to install? You need: > > > > > > * > http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > > > * > http://downloads.sourceforge.net/mingw/autoconf2.1-2.13-3-bin.tar.bz2 > > > * > http://downloads.sourceforge.net/mingw/autoconf2.5-2.61-1-bin.tar.bz2 > > > * http://downloads.sourceforge.net/mingw/autoconf-4-1-bin.tar.bz2 > > > * > http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 > > > > > > cd to your MSYS *root* directory: > > > > > > $ cd / > > > > > > then untar all of those there, e.g. > > > > > > $ tar xjf /<your-downloads-dir>/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > > > > > > etc. Then it should work. > > > > I need to install automake so that I can get rsl built. > > It's the last of the packages I listed. > > > I downloaded all those files and untared them in my / directory. > > I'm guessing that I need to get and untar: > > autoconf2.5-2.61-1-mingwPORT.tar.bz2 > > No, you don't. Sorry, I did miss one prerequisite: > http://downloads.sourceforge.net/mingw/m4-1.4.7-MSYS.tar.bz2 > > If you install that, plus what I've listed previously, you will have a > working autoconf, and automake too, I believe; (I use autoconf routinely, > but I avoid automake like the plague). > > > cd to the directory and ran ./mingwPORT.sh > > Yes to the download since I dont have autoconf-2.61.tar.gz > > > > After that I get the error: > > --18:08:04-- > > http://voxel.dl.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz > > => `autoconf-2.61.tar.gz' > > Resolving voxel.dl.sourceforge.net... done. > > Connecting to voxel.dl.sourceforge.net[72.26.194.82]:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: > > http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?downl > >oad&failedmirror=voxel.dl.sourceforge.net[following] --18:08:06-- > > http://downloads.sourceforge.net/autoconf2.5/autoconf-2.61.tar.gz?downl > >oad&failedmirror=voxel.dl.sourceforge.net => > > `autoconf-2.61.tar.gz@download&failedmirror= > > voxel.dl.sourceforge.net' > > Resolving downloads.sourceforge.net... done. > > Connecting to downloads.sourceforge.net[216.34.181.60]:80... connected. > > HTTP request sent, awaiting response... 301 Moved Permanently > > Location: http://sourceforge.net/projects/autoconf2-5/files [following] > > --18:08:06-- http://sourceforge.net/projects/autoconf2-5/files > > => `files.2' > > Resolving sourceforge.net... done. > > Connecting to sourceforge.net[216.34.181.60]:80... connected. > > HTTP request sent, awaiting response... 200 OK > > Length: unspecified [text/html] > > > > 0K ......... 104.46 > > KB/s > > > > 18:08:06 (104.46 KB/s) - `files.2' saved [10162] > > > > tar (child): /download/autoconf-2.61.tar.gz: Cannot open: No such file > > or directory > > tar (child): Error is not recoverable: exiting now > > tar: Child returned status 2 > > tar: Error exit delayed from previous errors > > mingwPORT.afterquestion: tar: FATAL: command failed; mingwPORT cannot > > continue. > > Don't know what's going on there; the mingwPORT should not be looking on > SF for the sources -- it should use direct download from the FSF site. > Anyway, you *don't* need the mingwPORT! > > > I am confused on the reason I needed to download and install all the > > prior modules? The Perl module is fairly old and there are more than > > one autoconf version. Can anyone explain why I need all these files and > > what is the minimal amount of work that I need to do to install > > automake? > > Install the files I've listed; that should suffice. You *must* have perl > installed, and it *must* understand MSYS emulated POSIX paths; hence it > must be that version I've specified, regardless of its age. > > There are multiple autoconf versions because there were some significant, > and incompatible changes between the 2.1x series and the 2.5x/6x series, > but some projects still demand the older variant; the autoconf-4 *isn't* > autoconf proper; it is a wrapper to automagically select between the 2.1x > or 2.5x/6x variant, based on the content of the input, so you just run > autoconf, and it will DTRT. > > If you just want the newer autoconf, you can just as well get the current > FSF autoconf-2.63 source, and build it; (it should build OOTB, *provided* > you use a build directory *outside* the source tree, and you *must* also > first have those MSYS versions of perl and m4 installed). > Thanks very much. Now I know. I installed the pack listed above and ran make for RSL again. I got this error: $ make cd . && automake-1.9 --foreign Makefile /bin/sh: automake-1.9: command not found make: *** [Makefile.in] Error 127 I then changed the AUTOMAKE to automake-1.10 and ran make again. Got this popup: perl5.6.1.exe - Unable to Locate Component This application has failed to start because msys-crypt-0.dll was not found. Re-installing the application may fix this problem. And got this in the terminal: $ make cd . && automake-1.10 --foreign Makefile make: *** [Makefile.in] Error 53 Anyone got this before? > > -- > > Regards, > Keith. > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jr...@hu... |
From: Keith M. <kei...@us...> - 2009-03-30 18:34:12
|
On Sunday 29 March 2009 21:19:21 Jamie Lahowetz wrote: > I installed the pack listed above and ran make for RSL again. > I got this error: > $ make > cd . && automake-1.9 --foreign Makefile > /bin/sh: automake-1.9: command not found > make: *** [Makefile.in] Error 127 Ok, we are now getting into the realms of blind leading blind, because as I said, I do not use automake. However, it appears that automake uses much the same arrangement as autoconf, with multiple versions supported via a wrapper, so I guess that also installing: http://downloads.sourceforge.net/mingw/automake1.9-1.9.6-2-bin.tar.bz2 http://downloads.sourceforge.net/mingw/automake-3-1-bin.tar.bz2 in addition to: http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 would let you run it naturally, as just `automake' rather than explicitly as `automake-1.10'. > I then changed the AUTOMAKE to automake-1.10 and ran make again. Got > this popup: > perl5.6.1.exe - Unable to Locate Component > This application has failed to start because msys-crypt-0.dll was not > found. Re-installing the application may fix this problem. This is telling you that you have a missing dependency: http://downloads.sourceforge.net/mingw/crypt-1.1-1-MSYS-1.0.11-1.tar.bz2 (don't ask *me* why automake should depend on a cryptography library; it defies my sense of logic, that this should be a necessary prerequisite). > And got this in the terminal: > $ make > cd . && automake-1.10 --foreign Makefile > make: *** [Makefile.in] Error 53 > > Anyone got this before? I haven't, but then I don't use automake, (and I don't use MSYS as my main development platform, in any case; FTR, that is on GNU/Linux). You may find other dependencies. If so, then I'm sorry but we don't, as yet, have a package manager to resolve them automatically; you will have to get and install the necessary packages manually, from: https://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879 -- Regards, Keith. |
From: Ralf W. <Ral...@gm...> - 2009-03-30 19:13:28
|
Hello Keith, Jamie, * Keith Marshall wrote on Mon, Mar 30, 2009 at 03:27:38PM CEST: > On Sunday 29 March 2009 21:19:21 Jamie Lahowetz wrote: > > $ make > > cd . && automake-1.9 --foreign Makefile > > /bin/sh: automake-1.9: command not found > > make: *** [Makefile.in] Error 127 > > Ok, we are now getting into the realms of blind leading blind, because as > I said, I do not use automake. However, it appears that automake uses > much the same arrangement as autoconf, with multiple versions supported > via a wrapper, so I guess that also installing: > http://downloads.sourceforge.net/mingw/automake1.9-1.9.6-2-bin.tar.bz2 > http://downloads.sourceforge.net/mingw/automake-3-1-bin.tar.bz2 Yes, correct. The fact that an automake-1.9 rerun is triggered at all by "make" suggests that either the time stamps in the tarball is broken, or extracting has somehow messed them up. [...] > would let you run it naturally, as just `automake' rather than explicitly > as `automake-1.10'. > > I then changed the AUTOMAKE to automake-1.10 and ran make again. Got > > this popup: > > perl5.6.1.exe - Unable to Locate Component > > This application has failed to start because msys-crypt-0.dll was not > > found. Re-installing the application may fix this problem. > > This is telling you that you have a missing dependency: > http://downloads.sourceforge.net/mingw/crypt-1.1-1-MSYS-1.0.11-1.tar.bz2 > > (don't ask *me* why automake should depend on a cryptography library; it > defies my sense of logic, that this should be a necessary prerequisite). Automake should not depend on crypt, and I haven't seen this before. It would be nice if somebody could debug this, I would like to have it fixed if the issue still exists. Thanks. Please feel free to direct further issues about Automake to the bug-automake at gnu.org list (you don't need to subscribe, but there is first-post moderation). Cheers, Ralf |
From: Jamie L. <jla...@gm...> - 2009-03-30 19:21:23
|
On Mon, Mar 30, 2009 at 8:27 AM, Keith Marshall < kei...@us...> wrote: > On Sunday 29 March 2009 21:19:21 Jamie Lahowetz wrote: > > I installed the pack listed above and ran make for RSL again. > > I got this error: > > $ make > > cd . && automake-1.9 --foreign Makefile > > /bin/sh: automake-1.9: command not found > > make: *** [Makefile.in] Error 127 > > Ok, we are now getting into the realms of blind leading blind, because as > I said, I do not use automake. However, it appears that automake uses > much the same arrangement as autoconf, with multiple versions supported > via a wrapper, so I guess that also installing: > http://downloads.sourceforge.net/mingw/automake1.9-1.9.6-2-bin.tar.bz2 > http://downloads.sourceforge.net/mingw/automake-3-1-bin.tar.bz2 > > in addition to: > http://downloads.sourceforge.net/mingw/automake1.10-1.10-1-bin.tar.bz2 > > would let you run it naturally, as just `automake' rather than explicitly > as `automake-1.10'. > > > I then changed the AUTOMAKE to automake-1.10 and ran make again. Got > > this popup: > > perl5.6.1.exe - Unable to Locate Component > > This application has failed to start because msys-crypt-0.dll was not > > found. Re-installing the application may fix this problem. > > This is telling you that you have a missing dependency: > http://downloads.sourceforge.net/mingw/crypt-1.1-1-MSYS-1.0.11-1.tar.bz2 Definitely what was needed, thank you very much. I have yet ran into another problem. $ make cd . && automake-1.9 --foreign Makefile Can't locate strict.pm in @INC (@INC contains: /usr/local/share/automake-1.9 /usr/lib/perl5/5.6/msys /usr/lib/perl5/5.6 /usr/lib/perl5/site_perl/5.6/msys /usr/lib/perl5/site_perl/5.6 /usr/lib/perl5/site_perl/5.6 /usr/lib/perl5/vendor_perl/5.6/msys /usr/lib/perl5/vendor_perl/5.6 /usr/lib/perl5/vendor_perl/5.6 .) at /usr/local/share/automake-1.9/Automake/Struct.pm line 31. BEGIN failed--compilation aborted at /usr/local/share/automake-1.9/Automake/Struct.pm line 31. Compilation failed in require at /bin/automake-1.9 line 47. BEGIN failed--compilation aborted at /bin/automake-1.9 line 47. make: *** [Makefile.in] Error 2 I'm not sure how to add the directory leading to strict.pm to @INC. Any ideas? > > > (don't ask *me* why automake should depend on a cryptography library; it > defies my sense of logic, that this should be a necessary prerequisite). > > > And got this in the terminal: > > $ make > > cd . && automake-1.10 --foreign Makefile > > make: *** [Makefile.in] Error 53 > > > > Anyone got this before? > > I haven't, but then I don't use automake, (and I don't use MSYS as my main > development platform, in any case; FTR, that is on GNU/Linux). > > You may find other dependencies. If so, then I'm sorry but we don't, as > yet, have a package manager to resolve them automatically; you will have > to get and install the necessary packages manually, from: > > https://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879 > > -- > > Regards, > Keith. > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Sisyphus <sis...@op...> - 2009-03-30 22:56:33
|
----- Original Message ----- From: "Jamie Lahowetz" <jla...@gm...> > Can't locate strict.pm in @INC (@INC contains: > /usr/local/share/automake-1.9 > /usr/lib/perl5/5.6/msys /usr/lib/perl5/5.6 > /usr/lib/perl5/site_perl/5.6/msys > /usr/lib/perl5/site_perl/5.6 /usr/lib/perl5/site_perl/5.6 > /usr/lib/perl5/vendor_perl/5.6/msys /usr/lib/perl5/vendor_perl/5.6 > /usr/lib/perl5/vendor_perl/5.6 .) at > /usr/local/share/automake-1.9/Automake/Struct.pm line 31. > BEGIN failed--compilation aborted at > /usr/local/share/automake-1.9/Automake/Struct.pm line 31. > Compilation failed in require at /bin/automake-1.9 line 47. > BEGIN failed--compilation aborted at /bin/automake-1.9 line 47. > make: *** [Makefile.in] Error 2 > > I'm not sure how to add the directory leading to strict.pm to @INC. Any > ideas? Looks like there's something wrong with your perl installation. I have strict.pm in both /usr/lib/perl5/5.6 (C:\_32\msys\1.0\lib\perl5\5.6\strict.pm) and /usr/lib/perl5/5.6/msys (C:\_32\msys\1.0\lib\perl5\5.6\msys\strict.pm). Both of those locations are already in @INC, and it therefore gets found without any problem for me. ############################## Rob@DESKTOP2 ~ $ perl -Mstrict -le 'print $strict::VERSION' 1.01 Rob@DESKTOP2 ~ ############################## Where is strict.pm located in your installation ? I suspect it might be missing altogether, and if that's the case try re-installing perl. The perl package that Keith specified (http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2) definitely contains strict.pm in the 2 @INC locations I mentioned above. Cheers, Rob |
From: Jamie L. <jla...@gm...> - 2009-03-30 23:24:21
|
On Mon, Mar 30, 2009 at 5:55 PM, Sisyphus <sis...@op...> wrote: > > ----- Original Message ----- > From: "Jamie Lahowetz" <jla...@gm...> > > > Can't locate strict.pm in @INC (@INC contains: > > /usr/local/share/automake-1.9 > > /usr/lib/perl5/5.6/msys /usr/lib/perl5/5.6 > > /usr/lib/perl5/site_perl/5.6/msys > > /usr/lib/perl5/site_perl/5.6 /usr/lib/perl5/site_perl/5.6 > > /usr/lib/perl5/vendor_perl/5.6/msys /usr/lib/perl5/vendor_perl/5.6 > > /usr/lib/perl5/vendor_perl/5.6 .) at > > /usr/local/share/automake-1.9/Automake/Struct.pm line 31. > > BEGIN failed--compilation aborted at > > /usr/local/share/automake-1.9/Automake/Struct.pm line 31. > > Compilation failed in require at /bin/automake-1.9 line 47. > > BEGIN failed--compilation aborted at /bin/automake-1.9 line 47. > > make: *** [Makefile.in] Error 2 > > > > I'm not sure how to add the directory leading to strict.pm to @INC. Any > > ideas? > > Looks like there's something wrong with your perl installation. I have > strict.pm in both /usr/lib/perl5/5.6 > (C:\_32\msys\1.0\lib\perl5\5.6\strict.pm) and /usr/lib/perl5/5.6/msys > (C:\_32\msys\1.0\lib\perl5\5.6\msys\strict.pm). > > Both of those locations are already in @INC, and it therefore gets found > without any problem for me. > > ############################## > Rob@DESKTOP2 ~ > $ perl -Mstrict -le 'print $strict::VERSION' > 1.01 > > Rob@DESKTOP2 ~ > ############################## When I run the command I get: $ perl -Mstrict -le 'print $strict::VERSION' 1.04 > > > Where is strict.pm located in your installation ? I suspect it might be > missing altogether, and if that's the case try re-installing perl. The perl > package that Keith specified > (http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2) > definitely contains strict.pm in the 2 @INC locations I mentioned above. strict.pm can be found in: C:\msys\1.0\local\lib\perl5\5.6 == /local/lib/perl5/5.6 C:\msys\1.0\local\lib\perl5\5.6\msys == /local/lib/perl5/5.6/msys These dont seem to be in @INC, how do I add them? > > Cheers, > Rob > > > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Sisyphus <sis...@op...> - 2009-03-31 00:24:34
|
----- Original Message ----- From: "Jamie Lahowetz" <jla...@gm...> > > When I run the command I get: > $ perl -Mstrict -le 'print $strict::VERSION' > 1.04 Odd .... that should have thrown up the same @INC problem - unless you ran that command from within a directory that contains strict.pm. I've no idea how you get version 1.04. We're obviously looking at different perl tarballs here. > >> >> >> Where is strict.pm located in your installation ? I suspect it might be >> missing altogether, and if that's the case try re-installing perl. The >> perl >> package that Keith specified >> (http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2) >> definitely contains strict.pm in the 2 @INC locations I mentioned above. > > > strict.pm can be found in: > C:\msys\1.0\local\lib\perl5\5.6 == /local/lib/perl5/5.6 > C:\msys\1.0\local\lib\perl5\5.6\msys == /local/lib/perl5/5.6/msys > > These dont seem to be in @INC, how do I add them? Not easily - better to have everything installed in the right place. Were you in 'local' when you unpacked the package ? You need to 'cd /' before unpacking it. I'm no longer sure that http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 is the package that I used to install my perl - but I've checked, and that package definitely unpacks into 'lib', 'bin', etc. and not 'local/lib', 'local/bin', etc. I can only assume that you were in the wrong directory when you unpacked it, and that you ought to remedy that by cd'ing to the root directory and unpacking again. The duplication of perl in 'local' shouldn't matter, though you could go through and remove as much of it as you like. For example, you could remove the 'perl' folder from /local/lib. But the first thing I would be doing is re-installing perl, and ensuring that it goes into /usr, not /usr/local. Cheers, Rob |
From: Jamie L. <jla...@gm...> - 2009-03-31 03:27:02
|
On Mon, Mar 30, 2009 at 7:23 PM, Sisyphus <sis...@op...> wrote: > > ----- Original Message ----- > From: "Jamie Lahowetz" <jla...@gm...> > > > > > When I run the command I get: > > $ perl -Mstrict -le 'print $strict::VERSION' > > 1.04 > > Odd .... that should have thrown up the same @INC problem - unless you ran > that command from within a directory that contains strict.pm. > > I've no idea how you get version 1.04. We're obviously looking at different > perl tarballs here. > > > > >> > >> > >> Where is strict.pm located in your installation ? I suspect it might be > >> missing altogether, and if that's the case try re-installing perl. The > >> perl > >> package that Keith specified > >> ( > http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2) > >> definitely contains strict.pm in the 2 @INC locations I mentioned > above. > > > > > > strict.pm can be found in: > > C:\msys\1.0\local\lib\perl5\5.6 == /local/lib/perl5/5.6 > > C:\msys\1.0\local\lib\perl5\5.6\msys == > /local/lib/perl5/5.6/msys > > > > These dont seem to be in @INC, how do I add them? > > Not easily - better to have everything installed in the right place. Were > you in 'local' when you unpacked the package ? You need to 'cd /' before > unpacking it. > > I'm no longer sure that > http://downloads.sourceforge.net/mingw/perl-5.6.1-MSYS-1.0.11-1.tar.bz2 is > the package that I used to install my perl - but I've checked, and that > package definitely unpacks into 'lib', 'bin', etc. and not 'local/lib', > 'local/bin', etc. I can only assume that you were in the wrong directory > when you unpacked it, and that you ought to remedy that by cd'ing to the > root directory and unpacking again. The duplication of perl in 'local' > shouldn't matter, though you could go through and remove as much of it as > you like. For example, you could remove the 'perl' folder from /local/lib. > But the first thing I would be doing is re-installing perl, and ensuring > that it goes into /usr, not /usr/local. > > Cheers, > Rob > It seems that this is never ending. Went ahead and installed perl in /usr instead. went to make and got yet another error: $ make cd . && automake-1.9 --foreign Makefile sh: /bin/autoconf: No such file or directory automake-1.9: autoconf failed with exit status: 127 make: *** [Makefile.in] Error 127 its looking for /bin/autoconf which is where it is. Thought that it maybe PATH: export PATH=".:/bin:/usr/local/bin:/mingw/bin:$PATH" deadpickle@ITSONLYCHEESE / $ ls bin/ a2p.exe diff.exe lnkcnv rview aclocal diff3.exe ls.exe rvim aclocal-1.10 dirname.exe m4.exe rxvt.exe aclocal-1.9 dprofpp make.exe s2p autoconf echo makeinfo.exe sed.exe autoconf-2.13 egrep md5sum.exe sh.exe I know I'm going to feel stupid but, what am I missing? > > > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Keith M. <kei...@us...> - 2009-04-01 16:39:06
|
[Please stop posting HTML multipart/alternative; plain text only is what we prefer, thanks] On Tuesday 31 March 2009 04:26:56 Jamie Lahowetz wrote: > its looking for /bin/autoconf which is where it is. Thought that > it maybe PATH: > export PATH=".:/bin:/usr/local/bin:/mingw/bin:$PATH" The default, set in /etc/profile, is export PATH=".:/usr/local/bin:/mingw/bin:/bin:$PATH" You shouldn't need to change that. > deadpickle@ITSONLYCHEESE / > $ ls bin/ > a2p.exe diff.exe lnkcnv rview > aclocal diff3.exe ls.exe rvim > aclocal-1.10 dirname.exe m4.exe rxvt.exe > aclocal-1.9 dprofpp make.exe s2p > autoconf echo makeinfo.exe sed.exe > autoconf-2.13 egrep md5sum.exe sh.exe > > I know I'm going to feel stupid but, what am I missing? Quite a lot, if that's all you have in your MSYS /bin; in fact, by *definition*, this couldn't possibly be an MSYS /bin, because it is missing msys-1.0.dll. Here's what you should have, as a bare minimum, (after extraction of msysCORE-1.0.11-20080826.tar.gz, and subsequently applying the bug fixing msys-1.0.11-20090120-dll.tar.gz upgrade, which represents a minimal installation): $ ls bin awk false.exe lzma.exe sed.exe basename.exe fgrep m4.exe sh.exe bash.exe file.exe make.exe sleep.exe bunzip2 find.exe makeinfo.exe sort.exe bzip2.exe fold.exe md5sum.exe split.exe cat.exe ftp mkdir.exe start chmod.exe gawk.exe mount stty.exe cls grep.exe msys-1.0.dll tail.exe clsb gunzip msys-bz2-1.dll tar.exe cmd gzip.exe msysinfo tee.exe cmp.exe head.exe msysmnt.exe texi2dvi comm.exe id.exe mv.exe texindex.exe cp.exe info.exe od.exe touch.exe cut.exe infokey.exe patch.exe tr.exe date.exe install.exe patch.exe.manifest true.exe diff3.exe install.exe.manifest printf umount diff.exe install-info.exe ps.exe uname.exe dirname.exe less.exe pwd uniq.exe echo libW11.dll rmdir.exe wc.exe egrep ln.exe rm.exe which env.exe lnkcnv rvi xargs.exe expr.exe ls.exe rxvt.exe (and even that looks incomplete, to me; I would have also expected to find `install-info.exe.manifest', with identical content to each of the other two identical `*.manifest' files). If I were you, I'd be inclined to reinstall from scratch. If your existing MSYS installation is in `c:/msys/1.0', then from an existing MSYS shell, you can: $ mkdir /c/msys/1.0-new $ cd /c/msys/1.0-new $ tar xzf /path/to/msysCORE-1.0.11-20080826.tar.gz $ tar xzf /path/to/MSYS-1.0.11-20090120-dll.tar.gz $ ( cd /; tar cf - home ) | tar xf - then, exit *all* active MSYS sessions, and from the Windows Explorer, delete the *entire* c:\msys\1.0 tree, and rename `c:\msys\1.0-new' to become `c:\msys\1.0'. Now, you can restart MSYS: $ cd / use the `tar' command, to reinstall those packages you want, but may have been having trouble with, e.g.: $ tar xjf perl-5.6.1-MSYS-1.0.11-1.tar.bz2 $ tar xjf m4-1.4.7-MSYS.tar.bz2 [...] and remount your MinGW installation, e.g. for a standard installation in `c:/mingw', (or substitute your alternative path): $ mount c:/mingw /mingw -- Regards, Keith. |
From: Jamie L. <jla...@gm...> - 2009-04-01 21:23:09
|
On Wed, Apr 1, 2009 at 10:41 AM, Keith Marshall <kei...@us...> wrote: > > [Please stop posting HTML multipart/alternative; plain text only is > what we prefer, thanks] > > On Tuesday 31 March 2009 04:26:56 Jamie Lahowetz wrote: > > its looking for /bin/autoconf which is where it is. Thought that > > it maybe PATH: > > export PATH=".:/bin:/usr/local/bin:/mingw/bin:$PATH" > > The default, set in /etc/profile, is > > export PATH=".:/usr/local/bin:/mingw/bin:/bin:$PATH" > > You shouldn't need to change that. > > > deadpickle@ITSONLYCHEESE / > > $ ls bin/ > > a2p.exe diff.exe lnkcnv rview > > aclocal diff3.exe ls.exe rvim > > aclocal-1.10 dirname.exe m4.exe rxvt.exe > > aclocal-1.9 dprofpp make.exe s2p > > autoconf echo makeinfo.exe sed.exe > > autoconf-2.13 egrep md5sum.exe sh.exe > > > > I know I'm going to feel stupid but, what am I missing? > > Quite a lot, if that's all you have in your MSYS /bin; in fact, by > *definition*, this couldn't possibly be an MSYS /bin, because it is > missing msys-1.0.dll. > > Here's what you should have, as a bare minimum, (after extraction of > msysCORE-1.0.11-20080826.tar.gz, and subsequently applying the bug > fixing msys-1.0.11-20090120-dll.tar.gz upgrade, which represents a > minimal installation): > > $ ls bin > awk false.exe lzma.exe sed.exe > basename.exe fgrep m4.exe sh.exe > bash.exe file.exe make.exe sleep.exe > bunzip2 find.exe makeinfo.exe sort.exe > bzip2.exe fold.exe md5sum.exe split.exe > cat.exe ftp mkdir.exe start > chmod.exe gawk.exe mount stty.exe > cls grep.exe msys-1.0.dll tail.exe > clsb gunzip msys-bz2-1.dll tar.exe > cmd gzip.exe msysinfo tee.exe > cmp.exe head.exe msysmnt.exe texi2dvi > comm.exe id.exe mv.exe texindex.exe > cp.exe info.exe od.exe touch.exe > cut.exe infokey.exe patch.exe tr.exe > date.exe install.exe patch.exe.manifest true.exe > diff3.exe install.exe.manifest printf umount > diff.exe install-info.exe ps.exe uname.exe > dirname.exe less.exe pwd uniq.exe > echo libW11.dll rmdir.exe wc.exe > egrep ln.exe rm.exe which > env.exe lnkcnv rvi xargs.exe > expr.exe ls.exe rxvt.exe > > (and even that looks incomplete, to me; I would have also expected to > find `install-info.exe.manifest', with identical content to each of > the other two identical `*.manifest' files). > > If I were you, I'd be inclined to reinstall from scratch. If your > existing MSYS installation is in `c:/msys/1.0', then from an existing > MSYS shell, you can: > > $ mkdir /c/msys/1.0-new > $ cd /c/msys/1.0-new > $ tar xzf /path/to/msysCORE-1.0.11-20080826.tar.gz > $ tar xzf /path/to/MSYS-1.0.11-20090120-dll.tar.gz > $ ( cd /; tar cf - home ) | tar xf - > > then, exit *all* active MSYS sessions, and from the Windows Explorer, > delete the *entire* c:\msys\1.0 tree, and rename `c:\msys\1.0-new' to > become `c:\msys\1.0'. Now, you can restart MSYS: > > $ cd / > > use the `tar' command, to reinstall those packages you want, but may > have been having trouble with, e.g.: > > $ tar xjf perl-5.6.1-MSYS-1.0.11-1.tar.bz2 > $ tar xjf m4-1.4.7-MSYS.tar.bz2 > [...] > > and remount your MinGW installation, e.g. for a standard installation > in `c:/mingw', (or substitute your alternative path): > > $ mount c:/mingw /mingw Very good idea I went ahead and reinstalled EVERYTHING. I did find out something as well, when I mount c:camelbox /mingw and try to configure anything expr.exe fails with a window popup. If I dont mount everything appears to work ok. Back to RSL. ./configure worked fine. when I went to make I got this error: $ make cd . && automake --foreign Makefile configure.in:5: version mismatch. This is Automake 1.9.6, configure.in:5: but the definition used by this AM_INIT_AUTOMAKE configure.in:5: comes from Automake 1.9.2. You should recreate configure.in:5: aclocal.m4 with aclocal and run automake again. make: *** [Makefile.in] Error 63 I may need to mail the author and see if he can write the makefile in 1.10 or something, i'm not sure. Any ideas? > > -- > > Regards, > Keith. > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Earnie B. <ea...@us...> - 2009-04-02 12:18:31
|
Quoting Jamie Lahowetz <jla...@gm...>: > > Very good idea I went ahead and reinstalled EVERYTHING. I did find out > something as well, when I mount c:camelbox /mingw and try to configure > anything expr.exe fails with a window popup. If I dont mount > everything appears to work ok. > You may have mistyped your mount but JIC the mount should be: mount c:/camelbox /mingw > Back to RSL. ./configure worked fine. when I went to make I got this error: > $ make > cd . && automake --foreign Makefile > configure.in:5: version mismatch. This is Automake 1.9.6, > configure.in:5: but the definition used by this AM_INIT_AUTOMAKE > configure.in:5: comes from Automake 1.9.2. You should recreate > configure.in:5: aclocal.m4 with aclocal and run automake again. > make: *** [Makefile.in] Error 63 > > I may need to mail the author and see if he can write the makefile in > 1.10 or something, i'm not sure. Any ideas? > Just do what the error told you to do. In the source directory do: aclocal automake -- Earnie |
From: Jamie L. <jla...@gm...> - 2009-04-02 16:02:35
|
On Thu, Apr 2, 2009 at 7:18 AM, Earnie Boyd <ea...@us...> wrote: > > Quoting Jamie Lahowetz <jla...@gm...>: > > > > > Very good idea I went ahead and reinstalled EVERYTHING. I did find out > > something as well, when I mount c:camelbox /mingw and try to configure > > anything expr.exe fails with a window popup. If I dont mount > > everything appears to work ok. > > > > You may have mistyped your mount but JIC the mount should be: > > mount c:/camelbox /mingw deadpickle@ITSONLYCHEESE / $ mount c:/camelbox /mingw get the windows warnings about expr.exe still. Could these constant problem I am having be caused in part by not having mingw mounted and being smooth? > > > Back to RSL. ./configure worked fine. when I went to make I got this error: > > $ make > > cd . && automake --foreign Makefile > > configure.in:5: version mismatch. This is Automake 1.9.6, > > configure.in:5: but the definition used by this AM_INIT_AUTOMAKE > > configure.in:5: comes from Automake 1.9.2. You should recreate > > configure.in:5: aclocal.m4 with aclocal and run automake again. > > make: *** [Makefile.in] Error 63 > > > > I may need to mail the author and see if he can write the makefile in > > 1.10 or something, i'm not sure. Any ideas? > > > > Just do what the error told you to do. In the source directory do: > > aclocal > automake $ aclocal aclocal:configure.in:13: warning: macro `AM_PROG_LIBTOOL' not found in library $ automake Makefile.am:9: Libtool library used but `LIBTOOL' is undefined Makefile.am:9: Makefile.am:9: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' Makefile.am:9: to `configure.in' and run `aclocal' and `autoconf' again. Added `AC_PROG_LIBTOOL' to the top of `configure.in' and ran again: $ aclocal aclocal:configure.in:13: warning: macro `AM_PROG_LIBTOOL' not found in library $ autoconf configure.in:13: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:14: error: possibly undefined macro: AC_PROG_LIBTOOL looked at the documentation for m4_pattern_allow. Of coarse I have no clue what I am looking for exactly. Quick google search did not turn up much. > > -- > Earnie > > > ------------------------------------------------------------------------------ > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Ralf W. <Ral...@gm...> - 2009-04-06 18:14:04
|
Hello Jamie, * Jamie Lahowetz wrote on Thu, Apr 02, 2009 at 06:02:15PM CEST: > > $ aclocal > aclocal:configure.in:13: warning: macro `AM_PROG_LIBTOOL' not found in library > > $ automake > Makefile.am:9: Libtool library used but `LIBTOOL' is undefined > Makefile.am:9: > Makefile.am:9: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' > Makefile.am:9: to `configure.in' and run `aclocal' and `autoconf' again. Please install the Libtool package if you haven't already. There is a tarball for MinGW. Then run libtoolize, and then rerun aclocal, automake, and autoconf. Actually, just try "autoreconf -vif" instead of running all tools manually. Hope that helps. Cheers, Ralf |
From: Jamie L. <jla...@gm...> - 2009-04-09 00:55:08
|
On Mon, Apr 6, 2009 at 1:13 PM, Ralf Wildenhues <Ral...@gm...> wrote: > Hello Jamie, > > * Jamie Lahowetz wrote on Thu, Apr 02, 2009 at 06:02:15PM CEST: >> >> $ aclocal >> aclocal:configure.in:13: warning: macro `AM_PROG_LIBTOOL' not found in library >> >> $ automake >> Makefile.am:9: Libtool library used but `LIBTOOL' is undefined >> Makefile.am:9: >> Makefile.am:9: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' >> Makefile.am:9: to `configure.in' and run `aclocal' and `autoconf' again. > > Please install the Libtool package if you haven't already. There is a > tarball for MinGW. Then run libtoolize, and then rerun aclocal, > automake, and autoconf. Actually, just try "autoreconf -vif" instead > of running all tools manually. It worked wonders thank you. configure worked perfectly and I moved onto make. I got the error: gzip.c:29:26: sys/resource.h: No such file or directory gzip.c:30:22: sys/wait.h: No such file or directory did a search for these in the mailing list. Did find that there are a few options to get these libraries going in msys. Though the way to go about these solutions escapes me. Any help and/or updates on how to get these headers I would greatly appreciate. Thank you... of coarse. > > Hope that helps. > > Cheers, > Ralf > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Keith M. <kei...@us...> - 2009-04-09 17:21:39
|
On Thursday 09 April 2009 01:54:47 Jamie Lahowetz wrote: > onto make. I got the error: > gzip.c:29:26: sys/resource.h: No such file or directory > gzip.c:30:22: sys/wait.h: No such file or directory These headers are system specific, (usually *nix specific). If your application can't do without them, then that's a sure indication that you have some porting effort in front of you. > did a search for these in the mailing list. Did find that there > are a few options to get these libraries going in msys. Though > the way to go about these solutions escapes me. Any help and/or > updates on how to get these headers I would greatly appreciate. You don't "get" these headers; you port the code, so they aren't required. In the case of sys/wait.h, you should be looking to use the APIs declared in process.h; (for GPL code, you may also find MinGW's execwrap code helpful). In the case of sys/resource.h, well, you just have to try and work around the dependencies. > Thank you... of coarse. You're welcome. Sorry it isn't more helpful; welcome to the world of *nix to MSW porting. -- Regards, Keith. |
From: Jamie L. <jla...@gm...> - 2009-04-11 00:45:32
|
On Thu, Apr 9, 2009 at 3:16 AM, Keith Marshall <kei...@us...> wrote: > On Thursday 09 April 2009 01:54:47 Jamie Lahowetz wrote: >> onto make. I got the error: >> gzip.c:29:26: sys/resource.h: No such file or directory >> gzip.c:30:22: sys/wait.h: No such file or directory > > These headers are system specific, (usually *nix specific). If your > application can't do without them, then that's a sure indication > that you have some porting effort in front of you. > >> did a search for these in the mailing list. Did find that there >> are a few options to get these libraries going in msys. Though >> the way to go about these solutions escapes me. Any help and/or >> updates on how to get these headers I would greatly appreciate. > > You don't "get" these headers; you port the code, so they aren't > required. In the case of sys/wait.h, you should be looking to use > the APIs declared in process.h; (for GPL code, you may also find > MinGW's execwrap code helpful). In the case of sys/resource.h, > well, you just have to try and work around the dependencies. I have decided to uncomment them and work as far as I can without them. Don't know what they do. Don't even know if they are important. I guess I will find out. I went and make with them commented out: Making all in examples make[2]: Entering directory `/rsl-v1.40/examples' /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o any_to_gif.exe -static any_to_gif.o -L/usr/local/trmm/GVBOX/lib -ljpeg -lz -lm ../.libs/librsl.a -L/usr/local/trmm/GVBOX/lib -ljpeg -lz -lm libtool: link: gcc -g -O2 -o any_to_gif.exe any_to_gif.o -L/usr/local/trmm/GVBOX/lib ../.libs/librsl.a -ljpeg -lz c:\camelbox\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: cannot find -lz collect2: ld returned 1 exit status make[2]: *** [any_to_gif.exe] Error 1 make[2]: Leaving directory `/rsl-v1.40/examples' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/rsl-v1.40' make: *** [all] Error 2 I need zlib so I built it from source in msys. libz.a was put into /usr/local/lib. Why is it looking into camelbox for ld? I did not mount a mingw directory. I'm really not sure where it is looking for libz.a or do I have it in the wrong place? > >> Thank you... of coarse. > > You're welcome. Sorry it isn't more helpful; welcome to the world > of *nix to MSW porting. > > -- > > Regards, > Keith. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > -- > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- Jamie Ryan Lahowetz University of Nebraska - Lincoln Graduate Student - Geosciences 402.304.0766 jla...@gm... |
From: Jnonathan <10...@gm...> - 2009-04-11 02:05:53
|
On 4/11/09, Jamie Lahowetz <jla...@gm...> wrote: > On Thu, Apr 9, 2009 at 3:16 AM, Keith Marshall > <kei...@us...> wrote: >> On Thursday 09 April 2009 01:54:47 Jamie Lahowetz wrote: >>> onto make. I got the error: >>> gzip.c:29:26: sys/resource.h: No such file or directory >>> gzip.c:30:22: sys/wait.h: No such file or directory >> >> These headers are system specific, (usually *nix specific). If your >> application can't do without them, then that's a sure indication >> that you have some porting effort in front of you. >> >>> did a search for these in the mailing list. Did find that there >>> are a few options to get these libraries going in msys. Though >>> the way to go about these solutions escapes me. Any help and/or >>> updates on how to get these headers I would greatly appreciate. >> >> You don't "get" these headers; you port the code, so they aren't >> required. In the case of sys/wait.h, you should be looking to use >> the APIs declared in process.h; (for GPL code, you may also find >> MinGW's execwrap code helpful). In the case of sys/resource.h, >> well, you just have to try and work around the dependencies. > > I have decided to uncomment them and work as far as I can without > them. Don't know what they do. Don't even know if they are important. > I guess I will find out. > > I went and make with them commented out: > Making all in examples > make[2]: Entering directory `/rsl-v1.40/examples' > /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o > any_to_gif.exe -static any_to_gif.o -L/usr/local/trmm/GVBOX/lib -ljpeg > -lz -lm ../.libs/librsl.a -L/usr/local/trmm/GVBOX/lib -ljpeg -lz -lm > libtool: link: gcc -g -O2 -o any_to_gif.exe any_to_gif.o > -L/usr/local/trmm/GVBOX/lib ../.libs/librsl.a -ljpeg -lz > c:\camelbox\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: > cannot find -lz > collect2: ld returned 1 exit status > make[2]: *** [any_to_gif.exe] Error 1 > make[2]: Leaving directory `/rsl-v1.40/examples' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/rsl-v1.40' > make: *** [all] Error 2 > > I need zlib so I built it from source in msys. libz.a was put into > /usr/local/lib. Why is it looking into camelbox for ld? I did not > mount a mingw directory. I'm really not sure where it is looking for > libz.a or do I have it in the wrong place? > > Hi, Move libz.a to /mingw/lib or add "-L/local/lib" to the gcc link command. |