On Feb 11, 2010, at 7:36 PM, Ryan Schmidt wrote:

> Hmm. Well, the lack of -arch flags in LDFLAGS is a bug in MacPorts 1.8.0 
> through 1.8.2. You can install MacPorts from the 1.8 branch to get the fix 
> for this. But I don't understand why it would default to i386. gcc should be 
> defaulting to x86_64 on a 64-bit Mac running Snow Leopard.

Recommended procedure?  Open a ticket, open a ticket stub so someone more 
knowledgeable than me can fill in the blanks?

In another email, Ryan wrote on February 11, 2010 7:36:59 PM PST
>     Hmm. Well, the lack of -arch flags in LDFLAGS is a bug in MacPorts 
>     1.8.0 through 1.8.2. You can install MacPorts from the 1.8 branch to 
>     get the fix for this. But I don't understand why it would default to 
>     i386. gcc should be defaulting to x86_64 on a 64-bit Mac running Snow 
>     Leopard.

Can you point me to docs or something that tells me how to so this?  Is this 
like a CVD or git type of pull, or is there an easy way for me to move on this. 
 I just want to be able to work it locally here, I will not release the 
Portfile until the official is out, which should solve this.

Though I would love to know why it is defaulting to 1386 when I am clearly not 
on that architecture, and none of the other 12 or so p5's had issues, and there 
were about 6 or so more, which I suspect are going to go in clean as well.

Any general guidance is appreciated.

-- 
Scott * If you contact me off list replace talklists@ with scott@ * 

_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to