Bug 264294 – app-admin/syslog-ng-2.1.4 ebuild failed: undefined reference to `_intel_fast_memset'

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Alex Meng 2009-03-30 13:50:54 UTC]

Failed to compile syslog-ng-2.1.4 on my x86 computer.  Emake failed.  

Reproducible: Always

[Comment 1 Alex Meng 2009-03-30 13:52:14 UTC]

Created attachment 186750 [details]
You can see the build log of syslog-ng-2.1.4 in the attachment

You can see the build log of syslog-ng-2.1.4 in the attachment

[Comment 2 Alex Legler (RETIRED) 2009-03-30 14:00:47 UTC]

*** Bug 264293 has been marked as a duplicate of this bug. ***

[Comment 3 Alex Meng 2009-03-30 14:03:56 UTC]

Created attachment 186752 [details]
Sorry, the previous attachment's locale is Simplified Chinese, I have changed the locale into English in this attachment

[Comment 4 David Abbott (RETIRED) 2009-03-31 03:00:58 UTC]

Can you post emerge --info

[Comment 5 David Abbott (RETIRED) 2009-03-31 03:25:09 UTC]

Based on these undefined references, looks like something may have been compiled with the Intel C compiler (icc)

[Comment 6 Alex Meng 2009-03-31 04:25:10 UTC]

Created attachment 186827 [details]
Messages from "emerge --info"

Yes, I add "icc" to my USE flags.  But I don't tend to compile it with icc (I don't add the syslog-ng to the /etc/portage/package.icc).

[Comment 7 Matthias M Weber 2009-03-31 08:29:49 UTC]

I can confirm this bug on my Intel x86_64 box.  It does not happen with syslog-ng 2.0.9 which compiles fine. I do not have the icc USE flag.

[Comment 8 Mr. Bones. (RETIRED) 2009-04-01 20:07:13 UTC]

does nm /usr/lib/libglib-2.0.a | grep intel give you back anything?

[Comment 9 Alex Meng 2009-04-02 01:01:05 UTC]

(In reply to comment #8)
> does nm /usr/lib/libglib-2.0.a | grep intel give you back anything?
> 

         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memcmp
         U _intel_fast_memcpy
         U __intel_VEC_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcmp
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memcpy
         U _intel_fast_memset
         U _intel_fast_memcmp
         U _intel_fast_memcpy

Thanks

[Comment 10 Mr. Bones. (RETIRED) 2009-04-02 01:51:01 UTC]

re-emerge glib.  You built it with icc.

[Comment 11 Alex Meng 2009-04-02 03:01:32 UTC]

(In reply to comment #10)
> re-emerge glib.  You built it with icc.

Oh, Thanks.  The problem has been solved after I re-emerge glib without icc.