Martin, thank you very much for your explicit suggestion.
I've committed a modified finkinfo to unstable. If it works,
I will move it to stable, too.

Tomoaki Okayama

At Thu, 06 May 2010 23:06:36 +0200,
Martin Costabel wrote:
> 
> Robert Wyatt wrote:
> > Walt Mankowski wrote:
> >> On Mon, May 03, 2010 at 01:07:01PM -0400, Walt Mankowski wrote:
> >>    
> >>> I'm running fink on an old Intel Core Duo iMac.  This is an i386 box.
> >>> I'm running OSX 10.6.3, the latest version of Snow Leopard.
> >>>
> >>> This morning I tried to build rxvt-unicode.  The build failed with a
> >>> number of x86_64 warnings and errors.  I've attached the output of
> >>> running
> >>>
> >>>    fink -v install rxvt-unicode
> >>>
> >>> It looks like it detects the build and host type properly
> >>> (i386-apple-darwin10.3.0).  But when it tries to build rxvtperl.C it's
> >>> saying "-arch x86_64".
> >>>
> >>> Walt
> >>>      
> >> As a followup, I've also tried to install rxvt-unicode on a new Core 2
> >> Duo macbook running snow leopard.  The CPU is 64 bits, but I'm running
> >> i386 versions of the fink code.  The build fails with similar
> >> messages.
> >>
> >> I'm guessing the package is assuming x86_64, and is currently broken
> >> for i386.
> >>
> >> Walt
> > 
> > fwiw, rxvt-unicode does build and install without errors on my 64-bit 
> > fink Snow Leopard installation (MBP Intel Core2 2.33GHz). So perhaps 
> > that assessment is correct, Walt.
> 
> This is easy to fix: In the patch file, there are 4 lines containing the 
> expression
> 
>    sed -e 's|-arch i386||g' -e 's|-arch ppc||g'
> 
> If you edit the file and add
> 
>    -e 's|-arch x86_64||g'
> 
> then rxvt-unicode builds on 10.6/32bit. Since the package has a 
> maintainer, I'll leave this to them.
> 
> -- 
> Martin
> 
> 
> 
> 

------------------------------------------------------------------------------

_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to