gnucash on Intel Macs again

[Jed Diem]

David, 

Is the path after   --prefix=   the path to where the gnucash source 
files are?

Thanks,

--jed

David Hampton wrote:
> On Sun, 2006-06-18 at 07:49 -0500, Jed Diem wrote:
>
>   
>> Somehow I think the problem is that the guile 1.6 files have names like 
>> guile-1.6*  and not just guile*.   I suppose that I could chase them 
>> down and either rename them of make symbolic links.  I'm reluctant to 
>> try that since I doing this on a production box that I don't want to 
>> mess up.  Somehow there must be way to install guile-1.6 and the related 
>> dev files as guile files.
>>     
>
> No, no you shouldn't do that.  You need to prefix each 'real' command
> with guile16-build.  Yes, its a PITA.  Here are the commands I use to
> compile on my MacPPC:
>
> export LIBTOOL="glibtool"
> export PATH="/sw/bin:$PATH"
> export PKG_CONFIG_CHECK=/sw/lib/pkgconfig
> export ACLOCAL_FLAGS="-I /sw/share/aclocal"
>
> guile16-build env LIBRARY_PATH=/sw/lib/ CPATH=/sw/include ./autogen.sh 
> guile16-build env LIBRARY_PATH=/sw/lib/ CPATH=/sw/include ./configure \
>    --prefix=/opt/gnucash
> guile16-build env LIBRARY_PATH=/sw/lib/ CPATH=/sw/include make
>
> The 2nd and 3rd line from the end are one single command.  There may be
> an easier way to do this but I haven't spent any tome looking for it.
> (I'm mainly a linux person.)   These are the commands provided to me
> when I asked someone how to compile gnucash on a mac.
>
> David
>
>