mingw-msys Mailing List for MinGW - Minimalist GNU for Windows

Hi Rajneesh,

Please post plain text only, and do not top post; if you ignore this 
request, in further posts, I will not reply.

On Tuesday 25 November 2008 07:14:52 raj...@wi... 
> To the first part of this query, I would like to bring out that I
> set up some of the Include directories by setting the environment
> variables such as INCLUDE_DIR and then passing it to my compiler
> through -I option.
>
> In some instances I have a directory structure where in I have sub
> directories as well. For example in have a following directory
> structure such as
>
> include/dir1/dir2 and the header file.
>
> In this case I specify the root directory as include/dir1 while in
> my C code I will have the #include "dir2/header.h"
>
> [...snip...]
>
> Please help me through this.

Sorry, but unless you give us a minimal self-contained test case, to 
demonstrate your problem, we cannot help you.  Based on what you've 
given us so far, here is mine, which works perfectly, exactly as I 
would expect:--

  $ mkdir -p foo/include/foobar/foo

  $ cd foo

  $ echo '#define FOO_SUCCESS  0' > include/foobar/foo/foo.h

  $ echo '#include "foo/foo.h"
      int main() { return FOO_SUCCESS; }' > foo.c

  $ echo 'foo.exe: foo.c ${LOCAL_INCLUDES}/foo/foo.h
  <TAB>   gcc -I${LOCAL_INCLUDES} -o $@ foo.c' > Makefile

  $ export LOCAL_INCLUDES=`pwd`/include/foobar

  $ make foo.exe
  gcc -I/home/keith/foo/include/foobar -o foo.exe foo.c

and FTR,

  $ gcc -I$LOCAL_INCLUDES -o foo.exe foo.c

works silently, and just as well as `make foo.exe'.

Regards,
Keith.

Hi Keith,

 

To the first part of this query, I would like to bring out that I set up
some of the Include directories by setting the environment variables
such as INCLUDE_DIR and then passing it to my compiler through -I
option.

 

In some instances I have a directory structure where in I have sub
directories as well. For example in have a following directory structure
such as 

 

include/dir1/dir2 and the header file.

 

In this case I specify the root directory as include/dir1 while in my C
code I will have the #include "dir2/header.h"

 

While the compiler is compiling it is searching for a path like
include/dir1\dir2/header.h in this case the path conversion is
controlling the linkage between path we passed as environment variable
and that included in the code.

 

Another place I have checked is where in like I have just preprocessed
the files and I got lot on above instances where in the path specified
is a mixture of Unix and Windows path and ultimately not finding the
path. That file is not include in the preprocessed file and just
indicates the path which has been included.

 

Also, if I give the complete path in Windows format, then it is
including the path and is able to compile successfully. But I don't want
to modify the code, least it will loose its platform independency. 

 

I hope, This is not the expected behavior of msys.

 

Please help me through this.

 

With Regards,

 

Rajneesh 

 

 

Re: [Mingw-msys] msys Path Conversion Problems

From: Keith Marshall <keithmarshall@us...> - 2008-11-21 20:35 

On Friday 21 November 2008 12:06:49 rajneeshraju.vetukuri@wi... 
wrote:
> I am facing a problem where in my .c source
> files are not able to find the header files which are located in
> the other directories.

There has been an almost identical query, within the last week, on the 
MinGW-Users list, (which is probably where this would have been best 
asked too).

> In some location in .c source files we have definitions such as
> #include "dir/header.h"

Are you saying that your compiler cannot find these header files, when 
you try to compile the code? If so, then this has nothing to do with 
MSYS path translation; `dir/header.h' must be a relative path, which 
is relative to the directory in which the source file containing the 
`#include "dir/header.h" directive is to be found.

Otherwise...

> Due to this when msys tries to find the file

...you will have to explain, preferably by means of a minimal self 
contained example, exactly what you mean by this. You need to show 
us what is happening, to lead you to the conclusion that `MSYS cannot 
find the header files'. How have you actually instructed MSYS, 
rather than your compiler, to look for them?

Regards,
Keith.

 

Dear Sirs/Madams,

I have downloaded and extracted autoconf-2.63.tar.bz2   automake-1.10.1.tar.bz2  & libtool-2.2.6a.tar.gz.

I have used configure liike cd make ; path/to/source/configure --prefix=/mingw ; make ; make install ; make check.

All three produce failures.

I am following the instructions in the wiki/msys

Have I still got mingw/msys misconfigured?

Stephen Grant Brown

On Saturday 22 November 2008 11:16:14 Stephen Grant Brown wrote:
> In msys
>
> GNUCash@ELSHADAI /mingw
> $ tar -tjf /z/gnucash_downloads/m4-1.4.7-MSYS.tar.bz2
> usr/bin/m4.exe

Why is your current directory `/mingw'?  There is no legitimate reason 
to ever be working there, unless you are in the process of updating 
*MinGW* components.

> usr/bin is not in path

No, but `/usr/bin' is, because MSYS makes `/usr' a loopback mount of 
`/', and `/bin' *is* in the PATH.

> Over which part of the existing installation do I extract it?

$ (cd /; tar xjf /path/to/m4-1.4.7-MSYS.tar.bz2)

is what you want.

Regards,
Keith.

Hi Caleb

In msys

GNUCash@ELSHADAI /mingw
$ tar -tjf /z/gnucash_downloads/m4-1.4.7-MSYS.tar.bz2
usr/bin/m4.exe

GNUCash@ELSHADAI /mingw
$ env
...
PATH=.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program 
Files/Subversion/bin
_=/bin/env

GNUCash@ELSHADAI /mingw
$

usr/bin is not in path

Over which part of the existing installation do I extract it?

Stephen Grant Brown

----- Original Message ----- 
From: "Caleb Cushing" <xen...@gm...>
To: "MSYS Discussion List" <min...@li...>
Sent: Saturday, November 22, 2008 8:37 PM
Subject: Re: [Mingw-msys] wiki/msys questions


>> How do I set the enviroment variable HOME to C:\msys\1.0\home?
>
> edit /etc/profile
>
>> How do I install the m4 update?
>
> educated guess: extract over top of the existing installation
>
>
> -- 
> Caleb Cushing
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great 
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the 
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Mingw-msys mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
>
> 

> How do I set the enviroment variable HOME to C:\msys\1.0\home?

edit /etc/profile

> How do I install the m4 update?

educated guess: extract over top of the existing installation


-- 
Caleb Cushing

Dear Sirs/Madams

How do I set the enviroment variable HOME to C:\msys\1.0\home?

How do I install the m4 update?

Yours Sincerely Stephen Grant Brown

On Friday 21 November 2008 12:06:49 raj...@wi... 
wrote:
> I am facing a problem where in my .c source
> files are not able to find the header files which are located in
> the other directories.

There has been an almost identical query, within the last week, on the 
MinGW-Users list, (which is probably where this would have been best 
asked too).

> In some location in .c source files we have definitions such as
> #include "dir/header.h"

Are you saying that your compiler cannot find these header files, when 
you try to compile the code?  If so, then this has nothing to do with 
MSYS path translation; `dir/header.h' must be a relative path, which 
is relative to the directory in which the source file containing the 
`#include "dir/header.h" directive is to be found.

Otherwise...

> Due to this when msys tries to find the file

...you will have to explain, preferably by means of a minimal self 
contained example, exactly what you mean by this.  You need to show 
us what is happening, to lead you to the conclusion that `MSYS cannot 
find the header files'.  How have you actually instructed MSYS, 
rather than your compiler, to look for them?

Regards,
Keith.

Hi,

 

I am facing problems with my compilations. Due to unforeseen issues with
my compiler in Unix and I am forced to compile my embedded projects in
Windows. I am using the msys environment since lots of my make file
contains the sh scripts. I am able to successfully change the
environment to msys. I am facing a problem where in my .c source files
are not able to find the header files which are located in the other
directories. 

 

In some location in .c source files we have definitions such as #include
"dir/header.h"

 

Due to this when msys tries to find the file, it jumbles up the path and
complains that it is not able to fetch the corresponding header file.
Hence the compilation fails.

 

Is there any way I can control the Path conversion. I tried to get the
info from the mailing list but couldn't find any. I want the msys to
disable the path conversion and use only the pure Unix based path. Or
there is any other way I can do this.

 

Your inputs will help to great extend.

 

With Regards,

 

Rajneesh V 

On 11/20/2008 05:23, Keith Marshall wrote:
> On Wednesday 19 November 2008 12:29:42 JonY wrote:
>> please avoid top posting next time, thanks.
>
> Hear, hear!  Well, actually it isn't really a matter of avoiding it;
> please just don't do it!
>

Maybe the Etiquette section needs to be moved up, before the Mailing 
List section. Adding quote fix for OE users 
<http://home.in.tum.de/~jain/software/oe-quotefix/> should be useful too.

>> Where did you get 1.4.9 from? Did you compile it yourself?
>
> Seems likely, and this indeed would be the problem; a natively
> compiled m4 would emit CRLF delimited output, but autom4te *needs* to
> have just LF -- that means you *must* use the m4-1.4.7 compiled as an
> MSYS component.
>
> This has been discussed several times before.  I don't know if Ralf
> Wildenhues watches this list, but if so, he may be able to offer some
> more authoritative info on the issue; IIRC, there was some talk of
> making autom4te more tolerant of this issue.
>
>> m4 devs claim MinGW strtod() is broken, hence it won't function
>> properly.
>> <http://www.mail-archive.com/m4-...@gn.../msg00200.html>
>
> Well, that's a rather glib statement, lacking any detail of what the
> claimed issues may be...
>
>> I'm not sure if it had been fixed with the recent runtime update.
>
> ...but AFAIK, the latest runtime provides a fully standards compliant
> strtod().  In any case, I fairly certain the current problem isn't
> related to this; it is much more likely to be the m4 CRLF issue.
>

My bad for jumping to conclusions.

> BTW, there is a further problem lurking in the OP's procedure, yet to
> be discovered.  This...
>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>> $ ./configure --prefix=/mingw
>> checking for a BSD-compatible install... /bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>>
>> etecera
>
> ...indicates that he is following the instructions on the original
> wiki page, and performing an `in-source' build, in spite of the
> comment I added to that page, warning against it; in fact, it's poor
> advice in *any* case, but in the case of autoconf it falls foul of a
> Makefile conflict between the file `INSTALL', and the phoney
> `install' target, (fixed in the git repository, but not yet in any
> released version).  You can work around it, by using `csmake', (or
> `cpmake'), instead of `make', but it doesn't arise at all, if you
> adopt the much preferred option of building in a separate directory,
> outside of the source tree.
>

Install instructions for autotools, automake and libtool in MSYS wiki 
entry updated.

On Wednesday 19 November 2008 12:29:42 JonY wrote:
> please avoid top posting next time, thanks.

Hear, hear!  Well, actually it isn't really a matter of avoiding it; 
please just don't do it!

> Where did you get 1.4.9 from? Did you compile it yourself?

Seems likely, and this indeed would be the problem; a natively 
compiled m4 would emit CRLF delimited output, but autom4te *needs* to 
have just LF -- that means you *must* use the m4-1.4.7 compiled as an 
MSYS component.

This has been discussed several times before.  I don't know if Ralf 
Wildenhues watches this list, but if so, he may be able to offer some 
more authoritative info on the issue; IIRC, there was some talk of 
making autom4te more tolerant of this issue.

> m4 devs claim MinGW strtod() is broken, hence it won't function
> properly.
> <http://www.mail-archive.com/m4-...@gn.../msg00200.html>

Well, that's a rather glib statement, lacking any detail of what the 
claimed issues may be...

> I'm not sure if it had been fixed with the recent runtime update.

...but AFAIK, the latest runtime provides a fully standards compliant 
strtod().  In any case, I fairly certain the current problem isn't 
related to this; it is much more likely to be the m4 CRLF issue.

BTW, there is a further problem lurking in the OP's procedure, yet to 
be discovered.  This...

> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
> $ ./configure --prefix=/mingw
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
>
> etecera

...indicates that he is following the instructions on the original 
wiki page, and performing an `in-source' build, in spite of the 
comment I added to that page, warning against it; in fact, it's poor 
advice in *any* case, but in the case of autoconf it falls foul of a 
Makefile conflict between the file `INSTALL', and the phoney 
`install' target, (fixed in the git repository, but not yet in any 
released version).  You can work around it, by using `csmake', (or 
`cpmake'), instead of `make', but it doesn't arise at all, if you 
adopt the much preferred option of building in a separate directory, 
outside of the source tree.

Regards,
Keith.

On 11/19/2008 20:00, Stephen Grant Brown wrote:
> Hi JonY
>
> Do I use msys or msydvlpr?
>
> msys =>
>
> GNUCash@ELSHADAI ~
> $ m4 --version
> m4 (GNU M4) 1.4.9
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv2+: GNU GPL version 2 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Rene' Seindal.
>
> GNUCash@ELSHADAI ~
>
> I am using a later version. Should I try M4 1.4.7?
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
> $ csmake
> csmake  all-recursive
> csmake[1]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> Making all in bin
> csmake[2]: Entering directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
> csmake[2]: Nothing to be done for `all'.
> csmake[2]: Leaving directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
> Making all in .
> csmake[2]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> csmake[2]: Nothing to be done for `all-am'.
> csmake[2]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> Making all in lib
> csmake[2]: Entering directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
> Making all in Autom4te
> csmake[3]: Entering directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/Autom4te'
> csmake[3]: Nothing to be done for `all'.
> csmake[3]: Leaving directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/Autom4te'
> Making all in m4sugar
> csmake[3]: Entering directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
> autom4te_perllibdir='../..'/lib AUTOM4TE_CFG='../../lib/autom4te.cfg'
> ../../bin/autom4te -B '../..'/lib -B '../..'/lib
> \
>                  --language=m4sugar                      \
>                  --freeze                        \
>                  --output=m4sugar.m4f
> autom4te: freezing produced output:
> autom4te:
> autom4te:
> autom4te:
>
> ... more of same
>
> autom4te:
> csmake[3]: *** [m4sugar.m4f] Error 1
> csmake[3]: Leaving directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
> csmake[2]: *** [all-recursive] Error 1
> csmake[2]: Leaving directory
> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
> csmake[1]: *** [all-recursive] Error 1
> csmake[1]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> csmake: *** [all] Error 2
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>
> Yours Sinecerely Stephen Grant Brown
>

Hi,
please avoid top posting next time, thanks.

Where did you get 1.4.9 from? Did you compile it yourself?

m4 devs claim MinGW strtod() is broken, hence it won't function 
properly. <http://www.mail-archive.com/m4-...@gn.../msg00200.html>

I'm not sure if it had been fixed with the recent runtime update. In the 
mean time, you can try 1.4.7. The download link is under the msydvlpr 
section.

Hi JonY

Do I use msys or msydvlpr?

msys =>

GNUCash@ELSHADAI ~
$ m4 --version
m4 (GNU M4) 1.4.9
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Rene' Seindal.

GNUCash@ELSHADAI ~

I am using a later version. Should I try M4 1.4.7?

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
$ csmake
csmake  all-recursive
csmake[1]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
Making all in bin
csmake[2]: Entering directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
csmake[2]: Nothing to be done for `all'.
csmake[2]: Leaving directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
Making all in .
csmake[2]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
csmake[2]: Nothing to be done for `all-am'.
csmake[2]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
Making all in lib
csmake[2]: Entering directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
Making all in Autom4te
csmake[3]: Entering directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/Autom4te'
csmake[3]: Nothing to be done for `all'.
csmake[3]: Leaving directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/Autom4te'
Making all in m4sugar
csmake[3]: Entering directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
autom4te_perllibdir='../..'/lib AUTOM4TE_CFG='../../lib/autom4te.cfg' 
../../bin/autom4te -B '../..'/lib -B '../..'/lib 
\
                --language=m4sugar                      \
                --freeze                        \
                --output=m4sugar.m4f
autom4te: freezing produced output:
autom4te:
autom4te:
autom4te:

... more of same

autom4te:
csmake[3]: *** [m4sugar.m4f] Error 1
csmake[3]: Leaving directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
csmake[2]: *** [all-recursive] Error 1
csmake[2]: Leaving directory 
`/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
csmake[1]: *** [all-recursive] Error 1
csmake[1]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
csmake: *** [all] Error 2

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63

Yours Sinecerely Stephen Grant Brown

----- Original Message ----- 
From: "JonY" <10...@gm...>
To: "MSYS Discussion List" <min...@li...>
Sent: Wednesday, November 19, 2008 10:23 PM
Subject: Re: [Mingw-msys] Making autoconf


> On 11/19/2008 18:43, Stephen Grant Brown wrote:
>> Hi All,
>>
>> I am following through the instructions in
>>
>> http://www.mingw.org/wiki/msys
>>
>> Instead of c:/msys/1.0 I use c:/soft/msys
>>
>> Instead of c:/Mingw I use c:/soft/mingw
>>
>> In msys, mount =>
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>> $ mount
>> C:\DOCUME~1\GNUCash\LOCALS~1\Temp on /tmp type user (binmode,noumount)
>> c:\soft\mingw on /mingw type user (binmode)
>> c:\soft\msys on / type user (binmode,noumount)
>> c:\soft\msys on /usr type user (binmode,noumount)
>> a: on /a type user (binmode,noumount)
>> c: on /c type user (binmode,noumount)
>> d: on /d type user (binmode,noumount)
>> z: on /z type user (binmode,noumount)
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>>
>>
>> ....
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf
>> $ tar -xvjf /z/downloads/gnu/autoconf-2.63.tar.bz2
>> autoconf-2.63/
>> autoconf-2.63/.prev-version
>> autoconf-2.63/.tarball-version
>> autoconf-2.63/.version
>> autoconf-2.63/aclocal.m4
>>
>> etcetera
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>> $ ./configure --prefix=/mingw
>> checking for a BSD-compatible install... /bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>>
>> etecera
>>
>> config.status: creating lib/Autom4te/Makefile
>> config.status: creating lib/autoscan/Makefile
>> config.status: creating lib/m4sugar/Makefile
>> config.status: creating lib/autoconf/Makefile
>> config.status: creating lib/autotest/Makefile
>> config.status: creating bin/Makefile
>> config.status: executing tests/atconfig commands
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>> $ csmake
>> csmake  all-recursive
>> csmake[1]: Entering directory 
>> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
>> Making all in bin
>> csmake[2]: Entering directory 
>> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
>>
>> etcera
>>
>> autom4te:
>> autom4te:
>> autom4te:
>> autom4te:
>> csmake[3]: *** [m4sugar.m4f] Error 1
>> csmake[3]: Leaving directory 
>> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
>> csmake[2]: *** [all-recursive] Error 1
>> csmake[2]: Leaving directory 
>> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
>> csmake[1]: *** [all-recursive] Error 1
>> csmake[1]: Leaving directory 
>> `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
>> csmake: *** [all] Error 2
>>
>> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>>
>> Why is not autoconf-2.63 making sucesfully?
>>
>> PS I am wanting to use msys to  compile gnucash and it keeps coming up 
>> with errors.
>>
>> Yours Sincerely Stephen Grant Brown
>>
>>
>
> Hi,
> MSYS m4 probably needs updating. What's your installed m4 version? Mine
> says:
>
>> $ m4 --version
>> GNU M4 1.4.7
>> Copyright (C) 2006 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is 
>> NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
>> PURPOSE.
>>
>> Written by Rene' Seindal.
>
> If it still doesn't work, please submit the last 25 or so lines from 
> "make".
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great 
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the 
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Mingw-msys mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
> 

On 11/19/2008 18:43, Stephen Grant Brown wrote:
> Hi All,
>
> I am following through the instructions in
>
> http://www.mingw.org/wiki/msys
>
> Instead of c:/msys/1.0 I use c:/soft/msys
>
> Instead of c:/Mingw I use c:/soft/mingw
>
> In msys, mount =>
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
> $ mount
> C:\DOCUME~1\GNUCash\LOCALS~1\Temp on /tmp type user (binmode,noumount)
> c:\soft\mingw on /mingw type user (binmode)
> c:\soft\msys on / type user (binmode,noumount)
> c:\soft\msys on /usr type user (binmode,noumount)
> a: on /a type user (binmode,noumount)
> c: on /c type user (binmode,noumount)
> d: on /d type user (binmode,noumount)
> z: on /z type user (binmode,noumount)
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>
>
> ....
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf
> $ tar -xvjf /z/downloads/gnu/autoconf-2.63.tar.bz2
> autoconf-2.63/
> autoconf-2.63/.prev-version
> autoconf-2.63/.tarball-version
> autoconf-2.63/.version
> autoconf-2.63/aclocal.m4
>
> etcetera
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
> $ ./configure --prefix=/mingw
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
>
> etecera
>
> config.status: creating lib/Autom4te/Makefile
> config.status: creating lib/autoscan/Makefile
> config.status: creating lib/m4sugar/Makefile
> config.status: creating lib/autoconf/Makefile
> config.status: creating lib/autotest/Makefile
> config.status: creating bin/Makefile
> config.status: executing tests/atconfig commands
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
> $ csmake
> csmake  all-recursive
> csmake[1]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> Making all in bin
> csmake[2]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'
>
> etcera
>
> autom4te:
> autom4te:
> autom4te:
> autom4te:
> csmake[3]: *** [m4sugar.m4f] Error 1
> csmake[3]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
> csmake[2]: *** [all-recursive] Error 1
> csmake[2]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
> csmake[1]: *** [all-recursive] Error 1
> csmake[1]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
> csmake: *** [all] Error 2
>
> GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
>
> Why is not autoconf-2.63 making sucesfully?
>
> PS I am wanting to use msys to  compile gnucash and it keeps coming up with errors.
>
> Yours Sincerely Stephen Grant Brown
>
>

Hi,
MSYS m4 probably needs updating. What's your installed m4 version? Mine 
says:

> $ m4 --version
> GNU M4 1.4.7
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Written by Rene' Seindal.

If it still doesn't work, please submit the last 25 or so lines from "make".

Hi Caleb

Thanks

Stephen
----- Original Message ----- 
From: "Caleb Cushing" <xen...@gm...>
To: "MSYS Discussion List" <min...@li...>
Sent: Wednesday, November 19, 2008 5:44 AM
Subject: Re: [Mingw-msys] Untaring msysCORE


> I've always used 7-zip to extract on windows... you could try that.
>
>
> -- 
> Caleb Cushing
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great 
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the 
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Mingw-msys mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
>
> 

Hi All,

I am following through the instructions in 

http://www.mingw.org/wiki/msys

Instead of c:/msys/1.0 I use c:/soft/msys

Instead of c:/Mingw I use c:/soft/mingw

In msys, mount =>

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
$ mount
C:\DOCUME~1\GNUCash\LOCALS~1\Temp on /tmp type user (binmode,noumount)
c:\soft\mingw on /mingw type user (binmode)
c:\soft\msys on / type user (binmode,noumount)
c:\soft\msys on /usr type user (binmode,noumount)
a: on /a type user (binmode,noumount)
c: on /c type user (binmode,noumount)
d: on /d type user (binmode,noumount)
z: on /z type user (binmode,noumount)

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63


....

GNUCash@ELSHADAI ~/src/gnu/autoconf
$ tar -xvjf /z/downloads/gnu/autoconf-2.63.tar.bz2
autoconf-2.63/
autoconf-2.63/.prev-version
autoconf-2.63/.tarball-version
autoconf-2.63/.version
autoconf-2.63/aclocal.m4

etcetera

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
$ ./configure --prefix=/mingw
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p

etecera

config.status: creating lib/Autom4te/Makefile
config.status: creating lib/autoscan/Makefile
config.status: creating lib/m4sugar/Makefile
config.status: creating lib/autoconf/Makefile
config.status: creating lib/autotest/Makefile
config.status: creating bin/Makefile
config.status: executing tests/atconfig commands

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63
$ csmake
csmake  all-recursive
csmake[1]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
Making all in bin
csmake[2]: Entering directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/bin'

etcera

autom4te: 
autom4te: 
autom4te: 
autom4te: 
csmake[3]: *** [m4sugar.m4f] Error 1
csmake[3]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib/m4sugar'
csmake[2]: *** [all-recursive] Error 1
csmake[2]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63/lib'
csmake[1]: *** [all-recursive] Error 1
csmake[1]: Leaving directory `/home/GNUCash/src/gnu/autoconf/autoconf-2.63'
csmake: *** [all] Error 2

GNUCash@ELSHADAI ~/src/gnu/autoconf/autoconf-2.63

Why is not autoconf-2.63 making sucesfully?

PS I am wanting to use msys to  compile gnucash and it keeps coming up with errors.

Yours Sincerely Stephen Grant Brown

I've always used 7-zip to extract on windows... you could try that.


-- 
Caleb Cushing

Hi, 

on XP when starting a certain external program (third-party plain C calculation 
program which communicates via stdout/fs) from the msys (1.0.11) bash shell the
external program crashes. It does not if started directly from the XP command 
prompt. The only things I find worth mentioning from the windows debugging 
message is that FileVer and ProdVer of msvrct.dll differ, I am no windows 
expert though. I will provide the complete debug message if needed.

Any ideas? 


Thanks, Christian 

Hi All,

I have msys in c:\soft\msys and mingw in c:\soft\mingw

The following is from an msys window

GNUCash@ELSHADAI /c/soft/msys
$ tar -xjf /z/gnucash_downloads/msysCORE-1.0.11-2007.01.19-1.tar.bz2
tar: bin/bzip2.exe: Cannot open: File exists
tar: bin/libW11.dll: Cannot open: File exists
tar: bin/msys-1.0.dll: Cannot open: File exists
tar: bin/rxvt.exe: Cannot open: File exists
tar: bin/sh.exe: Cannot open: File exists
tar: bin/tar.exe: Cannot open: File exists
tar: etc/profile: Cannot open: No such file or directory
tar: etc/termcap: Cannot utime: No such file or directory
tar: Error exit delayed from previous errors

GNUCash@ELSHADAI /c/soft/msys

I realize that all of this programs/files are in use.

I find this instruction on http://www.mingw.org/wiki/msys

a.. Install MSYS Core 1.0.11. It is an archive. Untar it in C:\msys\1.0. 

 How do I do this?

Thanks in advance for your help

Yours sincerely Stephen Grant Briown

Hello,

Stephen Grant Brown wrote:

> What is the difference between automake-bin.tar.bz2 and
> automake1.10-1.10-1-.bin.tar.bz2

As you may know, Automake takes Makefile.am files and generates the
Makefile.in files which contains some standard targets like install,
clean, distcheck, etc.

Unfortunately, each developer may have used different Automake features,
specific for a certain Automake version. So, each Makefile.am file can
be processed only by specific version of Automake.

To solve this, several versions of Automake are installed side-by-side,
with names like 'automake-1.9' and 'automake-1.10'. Then, a wrapper
script, called 'automake', will forward the call to a specific Automake
version, depending on the needs of the Makefile.am it detects.

So, the Automake versions 1.9 and 1.10 are contained in
automake1.10-1.10-1-bin.tar.bz2 and automake1.9-1.9.6-2-bin.tar.bz2
In automake-3-1-bin.tar.bz2, we have the wrapper script version 3.

The same above applies to Autoconf.

So, the best is to install all versions of Automake and Autoconf available.

Hope this clears up things.

Regards,
Cesar