Re: [gentoo-user] Bluetooth head phone

[Mart Raudsepp]

Ühel kenal päeval, E, 17.07.2017 kell 12:10, kirjutas Raphael MD:
> Hi everyone,
> I'm suffering a lot to put sound on my Bluetooth's head phone.
> The Bluez5 recognize my bt device.
> The pulseaudio is working normally, but A2DP protocol do not appear
> in pavucontrol options.
> I've followed the gentoo wiki, and looked at arch wiki to.
> Anyone have a path to this be difficult task bt+headphone
> Thanks

emerge --info pulseaudio please? Especially the "was built with the
following USE flags" part

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[IceAmber]

Actually, this is the c++ 11 abi bug, read the news

And you can solve it by `revdep-rebuild --library 'libstdc++.so.6' --
--exclude gcc`

On Mon, Jul 17, 2017 at 5:02 PM, Mart Raudsepp  wrote:

> Ühel kenal päeval, E, 17.07.2017 kell 12:00, kirjutas Mart Raudsepp:
> > Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> > > Hello,
> > >
> > > > undefined reference to
> > >
> > > `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11:
> > > :b
> > > asic_string , std::allocator > const&)'
> > >
> > > Seems to be the error, maybe you have to recompile llvm with c++11
> >
> > And without any VIDEO_CARDS set, you are only getting llvmpipe with
> > USE=llvm. If you don't need that with Xpra, you don't need that (and
> > USE=gallium). I'm not sure if Xpra can make use of it or not, but if
> > GL
> > is sent over the wire or something, then probably not at the server-
> > side.
> > What llvmpipe is is described here:
> > https://www.mesa3d.org/llvmpipe.html
>
> Actually to be fully correct, I believe USE=gallium might build more
> stuff even without any VIDEO_CARDS, e.g some state trackers and
> whatnot, but nothing useful to really make use of it if you don't have
> any VIDEO_CARDS for mesa or any other packages.
>
>
>

Re: [gentoo-user] Re: What to set in kernel for hi-res console terminal

[Mick]

On Monday 17 Jul 2017 18:27:04 Harry Putnam wrote:
> R0b0t1  writes:
> > On Sun, Jul 16, 2017 at 3:18 PM, Harry Putnam  wrote:
> >> I'm starting a new vbox install of gentoo using the minimal ISO from
> >> 07/13
> >> 
> >> When it gets to the kernel setup... I cannot figure out what to set
> >> to make my console terminal high resolution.  Something along the line
> >> of 1600x1200.
> >> 
> >> I understand this can all be done in the kernel now.  But cannot
> >> really get a good fix googling on what is needed there.
> > 
> > I was unable to figure this out either - can you comment on whether or
> > not Mick's suggestions work for you? The documentation I followed
> > about a year ago didn't seem to work.
> 
> I used to use old grub, of course, and used this on the kernel line:
> 
> (from 2010)
> 
>   title 2.6.32-r1
>   root (hd0,0)
>   kernel /vmlinuz  root=/dev/hda5 vga=0x31b video=vesfb:mtrr:3,ywrap
> 
> > I assume your goal is to have VTs that look like they do on Ubuntu, etc?
> 
>  Don't know dupe about Ubuntu...
> 
> My goal is a nice big fat high resolution console mode.
> Something on the order of 1600x1200
> 
> Didn't dig into kernel docs just now... but long long ago using old
> grub I dug up the chart Mick mentions .. It might have changed by now
> but probably not.
> 
> I kept it in comments on /boot/grub.conf down thru many installs
> and several different OS's.  Here is one from 2010 gentoo (On the same
> grub.conf as the title, root and kernel line above)
> 
> ## 640x480 800x600 1024x768 1280x1024
> ##   256 0x301   0x303   0x3050x307
> ##   32k 0x310   0x313   0x3160x319
> ##   64k 0x311   0x314   0x3170x31A
> ##   16M 0x312   0x315   0x3180x31B
> 
> So, I can probably figure out where to put stuff like that using Grub2
> but what I wanted to know about is using the Kernel modes KVM alone.
> 
> Hence the subject line about what to set `in kernel'.

Try adding this at the end of your kernel line options in GRUB:

video=1600x1200

If you are lucky your video card driver will cooperate.[1]  If not you may 
need to either add the refresh frequency, e.g. video=1600x1200@60Hz, or if 
your video drivers won't cooperate you'll have to add 'nomodeset' to disable 
KMS and specify your vga resolution of choice.

I tried this on with radeon card and it works.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: What to set in kernel for hi-res console terminal

[Harry Putnam]

R0b0t1  writes:

> On Sun, Jul 16, 2017 at 3:18 PM, Harry Putnam  wrote:
>> I'm starting a new vbox install of gentoo using the minimal ISO from
>> 07/13
>>
>> When it gets to the kernel setup... I cannot figure out what to set
>> to make my console terminal high resolution.  Something along the line
>> of 1600x1200.
>>
>> I understand this can all be done in the kernel now.  But cannot
>> really get a good fix googling on what is needed there.
>>
>
> I was unable to figure this out either - can you comment on whether or
> not Mick's suggestions work for you? The documentation I followed
> about a year ago didn't seem to work.

I used to use old grub, of course, and used this on the kernel line:

(from 2010)

  title 2.6.32-r1
  root (hd0,0)
  kernel /vmlinuz  root=/dev/hda5 vga=0x31b video=vesfb:mtrr:3,ywrap


> I assume your goal is to have VTs that look like they do on Ubuntu, etc?

 Don't know dupe about Ubuntu...

My goal is a nice big fat high resolution console mode.
Something on the order of 1600x1200

Didn't dig into kernel docs just now... but long long ago using old
grub I dug up the chart Mick mentions .. It might have changed by now
but probably not.

I kept it in comments on /boot/grub.conf down thru many installs
and several different OS's.  Here is one from 2010 gentoo (On the same
grub.conf as the title, root and kernel line above)

## 640x480 800x600 1024x768 1280x1024
##   256 0x301   0x303   0x3050x307
##   32k 0x310   0x313   0x3160x319
##   64k 0x311   0x314   0x3170x31A
##   16M 0x312   0x315   0x3180x31B

So, I can probably figure out where to put stuff like that using Grub2
but what I wanted to know about is using the Kernel modes KVM alone.

Hence the subject line about what to set `in kernel'.

Guess I should have specified using KVM and made it a bit clearer.
Since there are kernel settings related to using the stuff above too.

I may need to post again with a better subject line.

Re: [gentoo-user] Bluetooth head phone

[Raphael MD]

On Mon, Jul 17, 2017 at 7:21 PM, Mick  wrote:

> On Monday 17 Jul 2017 18:23:02 Raphael MD wrote:
> ​>​
> > I've used Bluedevil under KDE.
> ​>​
> >
> ​>​
> > My headphone is correctly paired, both headphone and PC are connected.
> ​>​
> >
> ​>​
> > But I do not have any sound through headphone.
> ​>​
> >
> ​>​
> > I've read some Arch forums and they tell about PulseAudio 10 bug, when
> ​>​
> > Pavucontrol does not detect A2DP sink profile.
> ​>​
> >
> ​>> ​The problem is the solutions proposed does not work.​
>
> ​>​
> I don't have your bt headphone to know what works, but have you tried using
> ​>​
> bluetoothctl to manage the bt controller on your PC and set up the
> connection?


   I've tried bluetoothctl, and it can connect without problem, but no
sound.​

Re: [gentoo-user] Bluetooth head phone

[Mick]

On Monday 17 Jul 2017 18:23:02 Raphael MD wrote:
> I've used Bluedevil under KDE.
> 
> My headphone is correctly paired, both headphone and PC are connected.
> 
> But I do not have any sound through headphone.
> 
> I've read some Arch forums and they tell about PulseAudio 10 bug, when
> Pavucontrol does not detect A2DP sink profile.
> 
> ​The problem is the solutions proposed does not work.​

I don't have your bt headphone to know what works, but have you tried using 
bluetoothctl to manage the bt controller on your PC and set up the connection?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bluetooth head phone

[Raphael MD]

I've used Bluedevil under KDE.

My headphone is correctly paired, both headphone and PC are connected.

But I do not have any sound through headphone.

I've read some Arch forums and they tell about PulseAudio 10 bug, when
Pavucontrol does not detect A2DP sink profile.

​The problem is the solutions proposed does not work.​

Re: [gentoo-user] Something wrong when emerging librime

[Andrew Savchenko]

Hi,

On Mon, 17 Jul 2017 16:38:00 + IceAmber wrote:
> Hi, everyone
> 
> There is an error when I emerging the fcitx-rime.
> Here is the build.log
> 
> Is it the bug of c++ 11 ABI?

This is not a C++11 ABI bug, see
https://bugs.gentoo.org/show_bug.cgi?id=624370

Just another compilation failure. I had not studied close what is
wrong there, but likely some unhandled API change.



Best regards,
Andrew Savchenko


pgpnmtkE_hnSc.pgp
Description: PGP signature

Re: [gentoo-user] Why does Java-Runtime want to print and X and all that?

[Matthias Hanft]

Michael Orlitzky wrote:
> 
> Try turning off USE="gtk" and turning on USE="headless-awt" for icedtea-bin.

Thanks. With a total of "-alsa -cups -gtk headless-awt -webstart", it reduces to

--- cut here ---

home01 ~ # emerge -pv jre

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] app-eselect/eselect-java-0.3.0::gentoo  14 KiB
[ebuild  N ] sys-apps/baselayout-java-0.1.0::gentoo  71 KiB
[ebuild  N ] dev-java/java-config-2.2.0-r3:2::gentoo  USE="{-test}" 
PYTHON_TARGETS="python2_7 python3_4 (-python3_5) (-python3_6)" 51 KiB
[ebuild  N ] dev-java/icedtea-bin-3.4.0:8::gentoo  USE="headless-awt -alsa 
-cups -doc -examples -gtk -multilib -nsplugin -pulseaudio (-selinux) -source 
-webstart" ABI_X86="(64) -32 (-x32)" 60397 KiB
[ebuild  N ] virtual/jdk-1.8.0-r3:1.8::gentoo  0 KiB
[ebuild  N ] virtual/jre-1.8.0-r1:1.8::gentoo  0 KiB

Total: 6 packages (6 new), Size of downloads: 60532 KiB

--- cut here ---

This looks pretty reasonable.

Ironically, in the meantime I found a better suitable package which doesn't
need Java at all :-) Thanks anyway...

-Matt

[gentoo-user] Something wrong when emerging librime

[IceAmber]

Hi, everyone

There is an error when I emerging the fcitx-rime.
Here is the build.log

Is it the bug of c++ 11 ABI?
I had got a bug of c++ 11 ABI before, and solved by the command `revdep-rebuild
--library 'libstdc++.so.6' -- --exclude gcc`

Re: [gentoo-user] Bluetooth head phone

[Alexey Eschenko]

Did you just paired your headset or initiated A2DP connection too? It can be made from BT GUI like blueman AFAIR.18:11, July 17, 2017, Raphael MD :Hi everyone,
I'm suffering a lot to put sound on my Bluetooth's head phone.
The Bluez5 recognize my bt device.
The pulseaudio is working normally, but A2DP protocol do not appear in pavucontrol options.
I've followed the gentoo wiki, and looked at arch wiki to.
Anyone have a path to this be difficult task bt+headphone
Thanks
-- Sent from Yandex.Mail for mobile

[gentoo-user] Bluetooth head phone

[Raphael MD]

Hi everyone,

I'm suffering a lot to put sound on my Bluetooth's head phone.

The Bluez5 recognize my bt device.
The pulseaudio is working normally, but A2DP protocol do not appear in
pavucontrol options.

I've followed the gentoo wiki, and looked at arch wiki to.

Anyone have a path to this be difficult task bt+headphone

Thanks

Re: [gentoo-user] Why does Java-Runtime want to print and X and all that?

[R0b0t1]

On Mon, Jul 17, 2017 at 8:52 AM, Matthias Hanft  wrote:
>
> This can't be true, can it? Do I really need all this just to run
> some simple Java software? I can't believe this...
>

The "headless-awt" flag disables some functionality, but per the name
it only affects the Abstract Window Toolkit. E.g. it doesn't get rid
of printing, so cups and the graphics libraries will probably remain.

R0b0t1.

Re: [gentoo-user] Why does Java-Runtime want to print and X and all that?

[Michael Orlitzky]

On 07/17/2017 09:52 AM, Matthias Hanft wrote:
> 
> [ebuild  N ] dev-java/icedtea-bin-3.4.0:8::gentoo  USE="alsa cups
> gtk webstart -doc -examples -headless-awt -multilib -nsplugin
> -pulseaudio (-selinux) -source" ABI_X86="(64) -32 (-x32)" 60397 KiB

Try turning off USE="gtk" and turning on USE="headless-awt" for icedtea-bin.

[gentoo-user] Why does Java-Runtime want to print and X and all that?

[Matthias Hanft]

Hi,

I'm thinking of installing a software (not in tree) which needs
a Java Runtime Environment. I guess I need "virtual/jre" for this,
but it wants to install 57 packages, including cups and many x11-
proto packages, including "cups" and "X" USE flags, and "cairo"
keyword failure:

--- cut here ---

home01 ~ # emerge -pv jre

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] dev-libs/vala-common-0.34.8::gentoo  2714 KiB
[ebuild  N ] media-libs/giflib-5.1.4:0/7::gentoo  USE="-doc -static-libs" 
ABI_X86="(64) -32 (-x32)" 625 KiB
[ebuild  N ] x11-themes/hicolor-icon-theme-0.15::gentoo  50 KiB
[ebuild  N ] sys-apps/baselayout-java-0.1.0::gentoo  71 KiB
[ebuild  N ] app-text/qpdf-5.1.1-r1:0/13::gentoo  USE="-doc -examples -perl 
-static-libs {-test}" 7484 KiB
[ebuild  N ] dev-java/java-config-2.2.0-r3:2::gentoo  USE="{-test}" 
PYTHON_TARGETS="python2_7 python3_4 (-python3_5) (-python3_6)" 51 KiB
[ebuild  N ] app-eselect/eselect-java-0.3.0::gentoo  14 KiB
[ebuild  N ] media-libs/alsa-lib-1.1.2::gentoo  USE="python -alisp -debug 
-doc" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7" 926 KiB
[ebuild  N ] dev-util/gdbus-codegen-2.50.3::gentoo  
PYTHON_TARGETS="python2_7 python3_4 (-python3_5)" 0 KiB
[ebuild  N ] x11-proto/xproto-7.0.31::gentoo  USE="-doc" ABI_X86="(64) -32 
(-x32)" 294 KiB
[ebuild  N ] x11-proto/xextproto-7.3.0::gentoo  USE="-doc" ABI_X86="(64) 
-32 (-x32)" 0 KiB
[ebuild  N ] x11-proto/inputproto-2.3.2::gentoo  ABI_X86="(64) -32 (-x32)" 
197 KiB
[ebuild  N ] x11-proto/renderproto-0.11.1-r1::gentoo  ABI_X86="(64) -32 
(-x32)" 104 KiB
[ebuild  N ] media-fonts/font-util-1.3.1::gentoo  0 KiB
[ebuild  N ] x11-misc/util-macros-1.19.1::gentoo  82 KiB
[ebuild  N ] x11-proto/damageproto-1.2.1-r1::gentoo  ABI_X86="(64) -32 
(-x32)" 97 KiB
[ebuild  N ] x11-proto/compositeproto-0.4.2-r1::gentoo  ABI_X86="(64) -32 
(-x32)" 99 KiB
[ebuild  N ] x11-proto/kbproto-1.0.7::gentoo  ABI_X86="(64) -32 (-x32)" 0 
KiB
[ebuild  N ] x11-proto/xf86bigfontproto-1.2.0-r1::gentoo  ABI_X86="(64) -32 
(-x32)" 0 KiB
[ebuild  N ] x11-libs/xtrans-1.3.5::gentoo  USE="-doc" 0 KiB
[ebuild  N ] dev-libs/libpthread-stubs-0.4::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 57 KiB
[ebuild  N ] x11-proto/recordproto-1.14.2-r1::gentoo  USE="-doc" 
ABI_X86="(64) -32 (-x32)" 121 KiB
[ebuild  N ] x11-proto/randrproto-1.5.0::gentoo  ABI_X86="(64) -32 (-x32)" 
139 KiB
[ebuild  N ] x11-proto/xcb-proto-1.12-r2::gentoo  ABI_X86="(64) -32 (-x32)" 
PYTHON_TARGETS="python2_7 python3_4 (-python3_5) (-python3_6)" 151 KiB
[ebuild  N ] x11-proto/fixesproto-5.0-r1::gentoo  ABI_X86="(64) -32 (-x32)" 
99 KiB
[ebuild  N ] x11-libs/libXau-1.0.8::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N ] x11-libs/libXdmcp-1.1.2-r1::gentoo  USE="-doc -static-libs" 
ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N ] dev-libs/libcroco-0.6.12-r1:0.6::gentoo  USE="{-test}" 
ABI_X86="(64) -32 (-x32)" 471 KiB
[ebuild  N ] x11-libs/gdk-pixbuf-2.36.6:2::gentoo  USE="introspection -X 
-debug -jpeg -jpeg2k {-test} -tiff" ABI_X86="(64) -32 (-x32)" 5046 KiB
[ebuild  N ] dev-libs/atk-2.22.0::gentoo  USE="introspection nls {-test}" 
ABI_X86="(64) -32 (-x32)" 729 KiB
[ebuild  N ] x11-libs/libxcb-1.12-r2:0/1.12::gentoo  USE="-doc (-selinux) 
-static-libs {-test} -xkb" ABI_X86="(64) -32 (-x32)" 600 KiB
[ebuild  N ] gnome-base/gsettings-desktop-schemas-3.22.0::gentoo  
USE="introspection" 585 KiB
[ebuild  N ] x11-libs/libX11-1.6.5::gentoo  USE="ipv6 -doc -static-libs 
{-test}" ABI_X86="(64) -32 (-x32)" 2307 KiB
[ebuild  N ] x11-themes/gnome-themes-standard-3.22.3::gentoo  2837 KiB
[ebuild  N ] dev-util/gtk-update-icon-cache-3.22.2::gentoo  358 KiB
[ebuild  N ] x11-libs/libXext-1.3.3::gentoo  USE="-doc -static-libs" 
ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N ] x11-libs/libXrender-0.9.10::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 302 KiB
[ebuild  N ] x11-libs/libXfixes-5.0.3::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 288 KiB
[ebuild  N ] x11-libs/libXi-1.7.9::gentoo  USE="-doc -static-libs" 
ABI_X86="(64) -32 (-x32)" 475 KiB
[ebuild  N ] x11-libs/libXcomposite-0.4.4-r1::gentoo  USE="-doc 
-static-libs" ABI_X86="(64) -32 (-x32)" 278 KiB
[ebuild  N ] x11-libs/libXcursor-1.1.14::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 305 KiB
[ebuild  N ] x11-libs/libXdamage-1.1.4-r1::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 273 KiB
[ebuild  N ] x11-libs/libXrandr-1.5.1::gentoo  USE="-static-libs" 
ABI_X86="(64) -32 (-x32)" 309 KiB
[ebuild  N ] x11-libs/libXtst-1.2.3::gentoo  USE="-doc -static-libs" 
ABI_X86="(64) -32 (-x32)" 315 KiB
[ebuild  N ] app-text/poppler-0.45.0:0/62::gentoo  USE="curl cxx 
introspection jpeg jpeg2k lcms utils -cairo (-cairo-qt) -cjk -debug -doc -nss 
-png -qt4 -qt5 -tiff" 1636

Re: [gentoo-user] What to set in kernel for hi-res console terminal

[Mick]

On Monday 17 Jul 2017 00:06:53 Mick wrote:
> On Sunday 16 Jul 2017 17:46:11 R0b0t1 wrote:
> > On Sun, Jul 16, 2017 at 3:18 PM, Harry Putnam  wrote:
> > > I'm starting a new vbox install of gentoo using the minimal ISO from
> > > 07/13
> > > 
> > > When it gets to the kernel setup... I cannot figure out what to set
> > > to make my console terminal high resolution.  Something along the line
> > > of 1600x1200.
> > > 
> > > I understand this can all be done in the kernel now.  But cannot
> > > really get a good fix googling on what is needed there.
> > 
> > I was unable to figure this out either - can you comment on whether or
> > not Mick's suggestions work for you? The documentation I followed
> > about a year ago didn't seem to work.
> > 
> > I assume your goal is to have VTs that look like they do on Ubuntu, etc?
> 
> Found it!  Have a look at your kernel documentation, which refers to the VGA
> options:
> 
> /usr/src/linux/Documentation/svga.txt
> 
> I couldn't find anything about changing the display mode with modesetting
> though.

Something else to play with if you are booting with GRUB.  Drop to the GRUB 
command line and run:

vbeinfo

I assume these will be used for booting too, not just the GRUB menu, but I am 
not sure.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Mart Raudsepp]

Ühel kenal päeval, E, 17.07.2017 kell 12:00, kirjutas Mart Raudsepp:
> Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> > Hello,
> > 
> > > undefined reference to
> > 
> > `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11:
> > :b
> > asic_string , std::allocator > const&)' 
> > 
> > Seems to be the error, maybe you have to recompile llvm with c++11
> 
> And without any VIDEO_CARDS set, you are only getting llvmpipe with
> USE=llvm. If you don't need that with Xpra, you don't need that (and
> USE=gallium). I'm not sure if Xpra can make use of it or not, but if
> GL
> is sent over the wire or something, then probably not at the server-
> side.
> What llvmpipe is is described here:
> https://www.mesa3d.org/llvmpipe.html

Actually to be fully correct, I believe USE=gallium might build more
stuff even without any VIDEO_CARDS, e.g some state trackers and
whatnot, but nothing useful to really make use of it if you don't have
any VIDEO_CARDS for mesa or any other packages.

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Mart Raudsepp]

Ühel kenal päeval, E, 17.07.2017 kell 03:46, kirjutas Rasmus Thomsen:
> Hello,
> 
> > undefined reference to
> `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11::b
> asic_string , std::allocator > const&)' 
> 
> Seems to be the error, maybe you have to recompile llvm with c++11

And without any VIDEO_CARDS set, you are only getting llvmpipe with
USE=llvm. If you don't need that with Xpra, you don't need that (and
USE=gallium). I'm not sure if Xpra can make use of it or not, but if GL
is sent over the wire or something, then probably not at the server-
side.
What llvmpipe is is described here:
https://www.mesa3d.org/llvmpipe.html

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Joerg Schilling]

Grant Edwards  wrote:

> Well, the return type for time() changed from "int" (or was it long?)
> to "time_t" many years back.  That said, the actual underlying
> representation has never changed on 32-bit Linux systems.  Posix
> requires it to be signed, and on 32-bit Linux systems, it's still
> going to overflow in 2038 -- same as it ever was.

time() did always return a long, in special since it counts only in seconds.

Unfortunately Tru64 from DEC changed that to an int and Linux copied the bug.

FreeBSD was going to make the same mistake, but I warned them and they delayed 
their 64bit kernel until they had tested everything well enough.

Jörg

-- 
 EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'

Re: [gentoo-user] Can't compile media-libs/mesa - do I need gallium?

[Rasmus Thomsen]

Hello,

> undefined reference to 
> `llvm::RTDyldMemoryManager::getSymbolAddressInProcess(std::__cxx11::basic_string
>  , std::allocator > const&)'

Seems to be the error, maybe you have to recompile llvm with c++11

Regards,
Rasmus

 Original Message 
On 17 Jul 2017, 02:43, Stroller wrote:

> This system is headless, but I have x11-wm/xpra installed on it so I can run 
> X11 apps remotely.
>
> Recent emerges of world have been failing at media-libs/mesa
>
> Currently I have mesa-13.0.5 installed; I have this problem with mesa-17.0.6 
> (current stable) and mesa-17.1.4 (latest in the tree when I tried this a few 
> days ago).
>
> The error says I should post this if I need support:
>
> $ emerge -pqv '=media-libs/mesa-17.0.6::gentoo'
> [ebuild U ] media-libs/mesa-17.0.6 [13.0.5] USE="classic dri3 egl gallium gbm 
> llvm nptl -bindist -d3d9 -debug -gles1 -gles2 -opencl -openmax -osmesa 
> -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland -xa 
> -xvmc (-gcrypt%) (-libressl%) (-nettle%*) (-openssl%*)" ABI_X86="(64) -32 
> (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -imx% -intel -nouveau -r100 
> -r200 -r300 -r600 -radeon
> -radeonsi (-vc4) (-vivante) -vmware"
> $
>
> The build.log doesn't point me towards any obvious solutions, or maybe I just 
> don't know how to read it.
>
> All I can make out is that it's a problem with gallium. The current version 
> of mesa appears to have gallium enabled, though.
>
> I know nothing about mesa, not even really what it's for, so I don't know if 
> I should just try disabling gallium and trying again.
>
> I'm grateful for any thoughts,
>
> Stroller.
>
> Tail end of /var/tmp/portage/media-libs/mesa-17.0.6/temp/build.log follows:
>
> /bin/sh ../../../../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ 
> -march=native -O2 -pipe -Wall -fno-math-errno -fno-trapping-math -shared 
> -shrext .so -module -no-undefined -avoid-version -Wl,--gc-sections 
> -Wl,--no-undefined 
> -Wl,--version-script=/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6/src/gallium/targets/dri/dri.sym
>  
> -Wl,--dynamic-list=/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6/src/gallium/targets/dri-vdpau.dyn
>  -L/usr/lib64 -Wl,-O1 -Wl,--as-needed -o gallium_dri.la -rpath /usr/lib64/dri 
> gallium_dri_la-target.lo ../../../../src/mesa/libmesagallium.la 
> ../../../../src/mesa/drivers/dri/common/libdricommon.la 
> ../../../../src/mesa/drivers/dri/common/libmegadriver_stub.la 
> ../../../../src/gallium/state_trackers/dri/libdri.la 
> ../../../../src/gallium/auxiliary/libgalliumvl.la 
> ../../../../src/gallium/auxiliary/libgallium.la 
> ../../../../src/gallium/drivers/ddebug/libddebug.la 
> ../../../../src/gallium/drivers/noop/libnoop.la 
> ../../../../src/gallium/drivers/rbug/librbug.la 
> ../../../../src/gallium/drivers/trace/libtrace.la 
> ../../../../src/mapi/shared-glapi/libglapi.la -lexpat -ldrm -lm -lpthread 
> -ldl -ldrm 
> ../../../../src/gallium/auxiliary/pipe-loader/libpipe_loader_static.la 
> ../../../../src/gallium/winsys/sw/null/libws_null.la 
> ../../../../src/gallium/winsys/sw/wrapper/libwsw.la 
> ../../../../src/gallium/winsys/sw/dri/libswdri.la 
> ../../../../src/gallium/winsys/sw/kms-dri/libswkmsdri.la -ldrm 
> ../../../../src/gallium/drivers/softpipe/libsoftpipe.la 
> ../../../../src/gallium/drivers/llvmpipe/libllvmpipe.la -lLLVMX86Disassembler 
> -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter 
> -lLLVMDebugInfoCodeView -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine 
> -lLLVMInstrumentation -lLLVMTransformUtils -lLLVMX86Desc -lLLVMMCDisassembler 
> -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMMCJIT 
> -lLLVMExecutionEngine -lLLVMTarget -lLLVMRuntimeDyld -lLLVMObject 
> -lLLVMMCParser -lLLVMBitReader -lLLVMMC -lLLVMBitWriter -lLLVMAnalysis 
> -lLLVMProfileData -lLLVMCore -lLLVMSupport
> libtool: link: x86_64-pc-linux-gnu-g++ -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/../../../../lib64/crti.o 
> /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/crtbeginS.o 
> .libs/gallium_dri_la-target.o -Wl,--whole-archive 
> ../../../../src/mesa/.libs/libmesagallium.a 
> ../../../../src/mesa/drivers/dri/common/.libs/libdricommon.a 
> ../../../../src/mesa/drivers/dri/common/.libs/libmegadriver_stub.a 
> ../../../../src/gallium/state_trackers/dri/.libs/libdri.a 
> ../../../../src/gallium/auxiliary/.libs/libgalliumvl.a 
> ../../../../src/gallium/auxiliary/.libs/libgallium.a 
> ../../../../src/gallium/drivers/ddebug/.libs/libddebug.a 
> ../../../../src/gallium/drivers/noop/.libs/libnoop.a 
> ../../../../src/gallium/drivers/rbug/.libs/librbug.a 
> ../../../../src/gallium/drivers/trace/.libs/libtrace.a 
> ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_static.a 
> ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a 
> ../../../../src/gallium/winsys/sw/wrapper/.libs/libwsw.a 
> ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a 
> ../../../../src/gallium/winsys/sw/kms-dri/.li