FreeBSD Port: subversion-1.1.3

David Xu davidxu at freebsd.org
Thu Apr 7 18:53:38 PDT 2005


I heard only -O works, -O2 does not work, -Os sometimes is a higher 
optimization
level than -O2.

Mike Schroll wrote:

> what specifically should I avoid? and/or is there a different GCC I 
> should be using?
> I've had no problem compiling all the other ports I use (239) with the 
> -Os -pipe and CPUTYPE=p4
> the only one I can tell so far that had a problem was subversion
>
> David Xu wrote:
>
>> There is rumor that that GCC can not generate useful P4 code, better
>> to avoid it at the present.
>>
>> David Xu
>>
>> Mike Schroll wrote:
>>
>>> Subversion 1.1.4 is out, and I'm curious if it fixes this issue that 
>>> I submitted to the subversion devel mailing list:
>>>
>>> Configuring Subversion on a new i386 FreeBSD 5.3-RELEASE box I decided
>>> to turn on the following optimizations in make.conf:
>>>
>>> CPUTYPE?=p4
>>> CFLAGS= -Os -pipe
>>>
>>> gcc (GCC) 3.4.2 [FreeBSD] 20040728
>>>
>>> While compiling the subversion port subversion-1.1.3 with these flags,
>>> compilation succeeds w/o error, however errors occur during execution.
>>> While using TortoiseSVN on windows, and doing an svn+ssh checkout I
>>> consistently get 'svn: Malformed network data' errors at a point, 
>>> and am
>>> unable to further the checkout process on repeated attempts.
>>>
>>> I've found the only way to resolve this issue was by recompiling
>>> subversion with the following:
>>>
>>> CPUTYPE?=p4
>>> CFLAGS= -O -pipe
>>>
>>> This information may be handy for anyone else getting this nondescript
>>> error from subversion.  I'm not knowledgeable enough in debugging to 
>>> try
>>> to tackle where the problem might be.  I encourage anyone else to 
>>> try to
>>> duplicate this issue. I get the same issue when doing -O2.
>>>
>>> P.S.
>>> from IRC: OneOfOne <irc://irc.freenode.net/OneOfOne,isnick>
>>> -march=pentium4 -mtune=pentium4 -O2 -ftracer -pipe -fomit-frame-pointer
>>> -mfpmath=sse -ffast-math -funit-at-a-time << my cflags (gcc 
>>> v3.4.3-20050110)
>>> In some quick, informal testing, no errors are apparant.
>>> This may lead to being a FreeBSD issue, or perhaps just my particular
>>> system.
>>>
>>> -Mike Schroll
>>>
>>> Applied Networking System Administration Major
>>> Rochester Institute of Technology
>>> Rochester, NY
>>>
>>> Information Sciences and Technology Major
>>> Penn State University
>>> University Park, PA
>>>
>>> FreeBSD at LogicX.us
>>> AIM: L0g1cX
>>> http://MSchroll.com
>>>
>>> _______________________________________________
>>> freebsd-ports at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>> To unsubscribe, send any mail to 
>>> "freebsd-ports-unsubscribe at freebsd.org"
>>>
>>>
>>
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>
>



More information about the freebsd-ports mailing list