mozilla's install hanging on amd64
Mikhail.Teterin at murex.com
Mon Apr 11 13:45:30 PDT 2005
> > My whole point, Scott, is that there is nothing special about "my gcc
> > flags". NOTHING. Setting CPUTYPE to match one's processor flavor is a
> > long-documented way to do things -- fact. Such setting results in the
> > corresponding -march=XXX automatically -- fact. All ports must handle
> > this. Those that can not are broken. Plan and simple. There is
> > nothing to argue: `-O -pipe -march=opteron' must work.
> This is a very agressive aproach. -march=opteron is supported in
> previous versions of gcc(3)? I think no. Can you try a more
> conservative approach like -march=pentium-mmx -mtune=optetron?
Now that -- setting -march manually -- would, indeed, be "playing with
unsupported gcc flags" and as such qualify for immediate dismissal of any and
all bug reports.
I'll stick to setting CPUTYPE to the processor I have, and leave the rest to
More information about the freebsd-ports