public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
Date: Tue, 2 Oct 2018 23:18:16 +0300	[thread overview]
Message-ID: <CA+t6X7d=RSUQ9icNhKz5PC5b6KWYFOOFBaJmb6EcB8mLzaF2XQ@mail.gmail.com> (raw)
In-Reply-To: <CA+t6X7fbyN-5JBkPDjkjE+aKV1Ktp0JfWGxKS0VdkWbn7+3QsA@mail.gmail.com>

вт, 2 окт. 2018 г. в 22:45, gevisz <gevisz@gmail.com>:
>
> So, mmxext flag is indeed absent here.
>
> I have not yet included it in CPU_FLAGS_X86 and think that
> it produces a strange error messages when I try emerge some
> packages like firefox:
>
> # emerge firefox
> These are the packages that would be merged, in order:
> Calculating dependencies... done!
>
> !!! The ebuild selected to satisfy
> ">=media-video/ffmpeg-1.2.6-r1:0[X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]"
> has unmet requirements.
> - media-video/ffmpeg-3.3.6::gentoo USE="X alsa bzip2 encode gpl
> hardcoded-tables iconv mp3 network opengl postproc sdl threads
> truetype vdpau vorbis x264 xcb xvid zlib (-altivec) -amr -amrenc
> -bluray -bs2b -cdio (-celt) -chromaprint -chromium -cpudetection
> -debug -doc -fdk -flite -fontconfig -frei0r -fribidi -gcrypt -gme -gmp
> -gnutls -gsm -iec61883 -ieee1394 -jack -jpeg2k -kvazaar -ladspa
> -libass -libcaca -libilbc -librtmp -libsoxr -libv4l -lzma (-mipsdspr1)
> (-mipsdspr2) (-mipsfpu) (-mmal) -modplug -nvenc -openal -openh264
> -openssl -opus -oss -pic -pulseaudio -rubberband -samba -schroedinger
> -snappy -sofalizer -speex -ssh -static-libs -test -theora -twolame
> -v4l -vaapi -vpx -wavpack -webp -x265 -zeromq -zimg -zvbi"
> ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="mmx sse sse2 sse3 ssse3
> -3dnow -3dnowext -aes -avx -avx2 -fma3 -fma4 -mmxext -sse4_1 -sse4_2
> -xop" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt
> graph2dot ismindex pktdumper qt-faststart sidxindex trasher"
>
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     cpu_flags_x86_sse? ( cpu_flags_x86_mmxext )
>
>   The above constraints are a subset of the following complete expression:
>     libv4l? ( v4l ) fftools_cws2fws? ( zlib ) test? ( encode )
> postproc? ( gpl ) frei0r? ( gpl ) cdio? ( gpl ) samba? ( gpl ) encode?
> ( x264? ( gpl ) x265? ( gpl ) xvid? ( gpl ) X? ( !xcb? ( gpl ) ) )
> arm64? ( cpu_flags_arm_v8 ) cpu_flags_arm_v8? ( cpu_flags_arm_vfpv3
> cpu_flags_arm_neon ) cpu_flags_arm_neon? ( cpu_flags_arm_thumb2
> cpu_flags_arm_vfp ) cpu_flags_arm_vfpv3? ( cpu_flags_arm_vfp )
> cpu_flags_arm_thumb2? ( cpu_flags_arm_v6 ) cpu_flags_arm_v6? (
> cpu_flags_arm_thumb ) cpu_flags_x86_avx2? ( cpu_flags_x86_avx )
> cpu_flags_x86_fma4? ( cpu_flags_x86_avx ) cpu_flags_x86_fma3? (
> cpu_flags_x86_avx ) cpu_flags_x86_xop? ( cpu_flags_x86_avx )
> cpu_flags_x86_avx? ( cpu_flags_x86_sse4_2 ) cpu_flags_x86_aes? (
> cpu_flags_x86_sse4_2 ) cpu_flags_x86_sse4_2? ( cpu_flags_x86_sse4_1 )
> cpu_flags_x86_sse4_1? ( cpu_flags_x86_ssse3 ) cpu_flags_x86_ssse3? (
> cpu_flags_x86_sse3 ) cpu_flags_x86_sse3? ( cpu_flags_x86_sse2 )
> cpu_flags_x86_sse2? ( cpu_flags_x86_sse ) cpu_flags_x86_sse? (
> cpu_flags_x86_mmxext ) cpu_flags_x86_mmxext? ( cpu_flags_x86_mmx )
> cpu_flags_x86_3dnowext? ( cpu_flags_x86_3dnow ) cpu_flags_x86_3dnow? (
> cpu_flags_x86_mmx )
>
> (dependency required by "virtual/ffmpeg-9-r2::gentoo" [ebuild])
> (dependency required by "www-client/firefox-60.2.0::gentoo" [ebuild])
> (dependency required by "firefox" [argument])
>
> I will try to include mmxext into CPU_FLAGS_X86 and see if this error
> message appears again.

Indeed, I have included mmxext into CPU_FLAGS_X86
and the above error message disappeared.

My guess is that CPU_FLAGS_X86 is used only when
emerging x32 libraries while -match=native is used
for x64 libraries. When both x32 and x64 libraries
appear in the same package, portage somehow
notices the conflict and reports it.


  reply	other threads:[~2018-10-02 20:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  7:22 [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor gevisz
2018-09-18 19:44 ` George Kettleborough
2018-09-19 21:45   ` gevisz
2018-09-19 21:54     ` Jack
2018-09-19 22:08       ` gevisz
2018-09-20  0:33       ` Andrew Udvare
2018-09-18 21:52 ` james
2018-09-19 21:52   ` gevisz
2018-09-19  8:37 ` Walter Dnes
2018-09-19 22:00   ` gevisz
2018-09-23  7:09     ` Walter Dnes
2018-09-24 15:49       ` james
2018-09-25  4:07       ` gevisz
2018-09-25  4:10         ` gevisz
2018-09-25  8:11         ` gevisz
2018-09-28  4:04           ` Walter Dnes
2018-09-28  9:33             ` Marc Joliet
2018-10-03  4:36               ` Mike Gilbert
2018-10-02 19:45   ` gevisz
2018-10-02 20:18     ` gevisz [this message]
2018-10-03  9:49     ` Walter Dnes
2018-10-03 11:03       ` gevisz
     [not found] <wziCm-7RE-3@gated-at.bofh.it>
     [not found] ` <wzGbE-4TG-5@gated-at.bofh.it>
     [not found]   ` <wzSPv-407-1@gated-at.bofh.it>
     [not found]     ` <wB6Qp-6uG-1@gated-at.bofh.it>
2018-09-24 15:30       ` james

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+t6X7d=RSUQ9icNhKz5PC5b6KWYFOOFBaJmb6EcB8mLzaF2XQ@mail.gmail.com' \
    --to=gevisz@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox