Sourceforge has recently added mercurial support to their code hosting:
http://apps.sourceforge.net/wordpress/sourceforge/2009/03/11/bazaar-and-mercurial-scm-services-launched/
Not sure if that makes it easier, since you'd still want just the subset
of the onnv repo published to the sourceforge repo, but at least it's one
toolchain instead of too.
-Alan Coopersmith- alan.coopersm...@sun.com
Sun Microsystems, Inc. - X Window System Engineering
Andrew Wilson wrote:
> Jonathan,
> Yes, it hasn't been updated since we started developing under
> OpenSolaris. This is because Solaris uses a different source control
> language, Mercurial, and converting between Mercurial and CVS would
> require some scripts that no one has had time to write. Instead, we are
> converting the OpenSolaris version to the SourceForge build environment
> and uploading tarballs of the source. (Incidentally, that could use some
> automation too, but again, the folks who would be best at doing that
> have been too busy with other things).
>
> If anyone wants to try their hand at writing such a script, please do
> so! Or, learn Mercurial and become a regular OpenSolaris developer /
> contributor (:-). Sun adopted Mercurial a year ago so that Non Sun
> developers would have the same access to the source code, and be able to
> modify and update it, almost as easily as Sun employed developers.
>
> I think Sun should be commended for putting the resources they are into
> furthering the development of FileBench. We definitely want it to become
> a widely used benchmark, and welcome help from the community.
>
> Incidentally, we chose to move it to OpenSolaris, because the processes
> that are in place for development of Solaris tend to produce solid,
> maintainable, code. Yes, it does add a bit of pain to the development
> process, but FileBench's stability has increased dramatically as a result.
>
> I do appreciate all the comments, both good and bad, about FileBench,
> and am always happy to hear of another person using it. Sun's
> performance group uses it regularly, and immediately lets me know when
> they encounter problems. Between fixing bugs and adding features others
> have requested, I am trying to add features that I think are necessary
> to make it a really good network file server benchmark. The next step is
> inclusion of NFS client modules, which is being done by a co-worker of
> mine. So, stay tuned and keep those cards and letters coming (:-).
>
> Drew
>
>
> On 03/25/09 07:07 AM, Jonathan Edwards wrote:
>> incidentally Andrew .. the cvs tree seems to be *way* out of sync as
>> well on sf.net:
>> http://sourceforge.net/project/stats/detail.php?group_id=133644&ugn=filebench&type=cvs&mode=12months
>>
>>
>> On Mar 25, 2009, at 9:55 AM, Andrew Wilson wrote:
>>
>>> Frank,
>>> I can't see anything wrong with the parser_lex.l code, however there
>>> are a couple of extra semicolons in parser_gram.y that were reported
>>> a few days ago that might be the source of the problem. They have
>>> actually been there for a while, but are not caught by the regular
>>> Solaris compilers for some reason. Anyway, version 1.4.5 won't have
>>> them, and meanwhile you can edit parser_gram.y to remove the trailing
>>> semicolons from lines 1447 and 1527, and try compiling again. Let me
>>> know what happens please.
>>> Drew
>>>
>>> On 03/25/09 04:44 AM, Frank Zimmer wrote:
>>>> Hello
>>>>
>>>> when i try to compile filebench 1.4.4 on Sol10 with the Sun Studio
>>>> Compiler 12 i get the following :
>>>>
>>>>
>>>> cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit
>>>> programs
>>>> source='parser_gram.c' object='parser_gram.o' libtool=no \
>>>> depfile='.deps/parser_gram.Po' tmpdepfile='.deps/parser_gram.TPo' \
>>>> depmode=none /bin/bash ../config/depcomp \
>>>> cc -D_REENTRANT -I. -I. -I.. -I../intl
>>>> -DFILEBENCHDIR=\"/opt/filebench\" -g -xO3 -xarch=v9 -DYYDEBUG=1
>>>> -c `test -f 'parser_gram.c' || echo './'`parser_gram.c
>>>> cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit
>>>> programs
>>>> source='parser_lex.c' object='parser_lex.o' libtool=no \
>>>> depfile='.deps/parser_lex.Po' tmpdepfile='.deps/parser_lex.TPo' \
>>>> depmode=none /bin/bash ../config/depcomp \
>>>> cc -D_REENTRANT -I. -I. -I.. -I../intl
>>>> -DFILEBENCHDIR=\"/opt/filebench\" -g -xO3 -xarch=v9 -DYYDEBUG=1
>>>> -c `test -f 'parser_lex.c' || echo './'`parser_lex.c
>>>> cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit
>>>> programs
>>>> "parser_lex.l", line 212: syntax error before or at: <EOF>
>>>> cc: acomp failed for parser_lex.c
>>>> *** Error code 1
>>>> make: Fatal error: Command failed for target `parser_lex.o'
>>>> Current working directory /var/tmp/filebench-1.4.4/filebench
>>>> *** Error code 1
>>>> The following command caused the error:
>>>> set fnord $MAKEFLAGS; amf=$2; \
>>>> dot_seen=no; \
>>>> target=`echo all-recursive | sed s/-recursive//`; \
>>>>
>>>>
>>>>
>>>>
>>>> Any Ideas ?
>>>>
>>>> Frank
>>>>
>>>
>>> _______________________________________________
>>> perf-discuss mailing list
>>> perf-discuss@opensolaris.org
>>
>
> _______________________________________________
> perf-discuss mailing list
> perf-discuss@opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
