Skip to Content.
Sympa Menu

svadev - Re: [svadev] SAFECode Mainline Ready for Development

svadev AT lists.siebelschool.illinois.edu

Subject: Svadev mailing list

List archive

Re: [svadev] SAFECode Mainline Ready for Development


Chronological Thread 
  • From: "Martin Richtarsky" <ps1 AT martinien.de>
  • To: "svadev AT cs.uiuc.edu" <svadev AT cs.uiuc.edu>
  • Subject: Re: [svadev] SAFECode Mainline Ready for Development
  • Date: Tue, 18 Sep 2012 00:23:22 +0200
  • Importance: Normal
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/svadev/>
  • List-id: <svadev.cs.uiuc.edu>


John Criswell schrieb:
> On 9/17/12 4:09 PM, Martin Richtarsky wrote:
>> John Criswell schrieb:
>>> Dear All,
>>>
>>> I'm writing to let everyone know that SAFECode mainline (which works
>>> with LLVM mainline) is now ready for development. All SAFECode
>>> developers should submit new patches and commits to mainline SAFECode;
>>> we're freezing the release_30 branch of SAFECode.
>>
>> I'm getting a linker error when building current LLVM trunk together
>> with
>> SAFECode trunk. Anyone has seen this before?
>>
>> llvm[4]: Linking Release+Asserts Shared Library libclang.so
>> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
>> anonymous version tag cannot be combined with other version tags
>> collect2: ld returned 1 exit status
>> make[4]: ***
>> [/local/mar_/buildsafecode/projects/safecode/Release+Asserts/lib/libclang.so]
>> Error 1
>
> I haven't seen this error. I usually use Debug builds; I'm running a
> Release+Asserts build right now to see if that causes the issue to show
> up.
>
> In the meantime, can you tell me what version of GCC (or Clang) and ld
> you're using? We should make sure they're not one of the versions that
> can't build LLVM.


I was using:

gcc (SUSE Linux) 4.3.4 [gcc-4_3-branch revision 152973]

and these two ld's

GNU ld (GNU Binutils; SUSE Linux Enterprise 11) 2.20.0.20100122-0.7.9
GNU ld (GNU Binutils) 2.22.52


This gcc version did show a problem building LLVM before, but I have added
a workaround for that (change -O3 to -O2 in the configure script). This
was a known problem on clang-dev.

I will also try a debug build tomorrow.

Best regards,
Martin




Archive powered by MHonArc 2.6.16.

Top of Page