Hi Gaius,
>> I meant to give a build with gm2 included a try on Solaris, but ended up
>> pretty much confused:
>>
>> * I've started with the gm2 repo on savannah. Running the combine-trees
>> script on master tried to combine gm2 with gcc 4.7.4. Trying again
>> with configure --with-gcc=none (no branch, for trunk?) didn't work
>> either (don't remember the details off-hand).
>>
>> * Next, I discovered and tried the gcc_trunk branch there. While it
>> matches the patch set you sent here, it lacks most of the compiler
>> proper, which only lives on master!? In addition, the patches in
>> there lack support for building libgm2. Those are present on the
>> master branch (which has both trunk and trunc in
>> gcc-versionno/gcc/gm2/patches/gcc). I tried to merge the trees and
>> apply the patches manually, but failed again later.
>>
>> At this point, I gave up. Am I missing something fundamental here?
>>
>> Thanks.
>> Rainer
>
> Hi Rainer,
>
> it rather depends upon what you want, if you want the latest complete
> gm2 grafting onto the svn gcc trunk then these two scripts will create a
> patched tree and also rebuild gm2.
that's my goal: I'd like to see if gm2 and libgm2 build on Solaris and
pass at least a reasonable number of tests.
> [however please be careful with the scripts - they do assume that
> everything will be built in $HOME/GM2 - read and adapt as necessary].
Ok, I will give it a try.
> These will build a complete gm2 (from the master) - whereas the gcc_trunk
> branch is used to track the patches which are posted to gcc-patches
> (which are currently minimal and just build the gm2 driver).
That explains the difference. While the driver are certainly important
for review, they don't help much by themselves when building the code...
> these tarballs are created using combine-trees, hope this helps,
Certainly. Thanks a lot.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
