Quoting justus rufus <[EMAIL PROTECTED]>:

> Hi,
>
> Derek Atkins <[EMAIL PROTECTED]> writes:
>> hi,
>>
>> Please don't forget to CC the list on all replies...
>
> I am sending this mail only to the list address
> (gnucash-devel@gnucash.org). Is that the right way?

That certainly is acceptable..

>> [snip]
>> Okay... So if you run the 'install.sh' from this working directory
>> does it still fail?
>
> I tried it all over again but it still fails. What I did:
> - cd into c:\soft\
> - "svn co http://svn.gnucash.org/repo/gnucash/trunk/packaging/win32/ 
> downloads"

No, don't put it here..

> - copied my custom.sh (just the QTDIR) to c:\soft\downloads
> - copied some packages and directories from the last try to c:\soft\
> and c:\soft\downloads respectively (wget-1.9.1-mingwPORT.tar.bz2,
> swigwin-1.3.31.zip, OpenSP-1.5.2.tar.gz, libofx-0.8.3.tar.gz,
> gwenhywfar-2.6.2.tar.gz, ktoblzcheck-1.14.tar.gz) since the download
> from source forge was not working and I did not want to install MSYS a
> second time
> - started MSYS
> - "/c/soft/downloads/install.sh"
> - when building AqBAnking did not succeed, even after some retries, I
> copied the whole directory aqbanking from the last successful run to
> c:\soft.
> - "/c/soft/downloads/install.sh"

You need to be in the <packaging> directory and run:

  ./install.sh

> When the build of GnuCash started I got the same message again: "...
> /autogen.sh: No such file or directory".
>
> When should these script be downloaded? Is that somewhere in the
> install.sh? Or am I doing something wrong?

It's downloaded by the svn co within install.sh.

> Justus

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [EMAIL PROTECTED]                        PGP key available

_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to