Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Installing xorg and lxde, new user
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 5:35 pm    Post subject: Reply with quote

I'm shocked to report that I think I've solved the issue, I've got it to begin emerging, BUT this error with opengl module happens. I've learned how the make= flags in make.conf and package.use files work.
It would appear I've learned to swim while drowning, so to speak :^) but, I'm not out of the woods yet.

>>> Installing (1 of 92) app-eselect/eselect-opengl-1.3.1-r4::gentoo
!!! Error: Can't load module opengl
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21357
Location: here

PostPosted: Sat Dec 09, 2017 5:36 pm    Post subject: Reply with quote

Remove libressl use flag to x11-base/xorg-server package. You cannot have openssl and libressl at same time
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13509

PostPosted: Sat Dec 09, 2017 6:42 pm    Post subject: Reply with quote

kenny_w wrote:
I thought Neddy was helping me with this but he hasn't replied in like an hour now...
Regrettably, Neddy is mortal and requires sleep and time away from the computer. Although you sometimes get lucky and get a near-interactive experience with helpers responding within minutes, it's possible that you may go hours or even several days before someone qualified to help you responds. Do not despair. Your thread will not be deleted for lack of activity. While it may become less noticeable if it falls off the front page, many users do read posts from later pages, especially if they were previously involved in a thread and took an interest in it.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 7:49 pm    Post subject: Reply with quote

Where is the Gentoo Forums based? It says like nearly midnight time, its not even 3pm here in Canada right now

Also, I installed pciutils, why isn't lspci working??? Can anybody please tell me what's wrong with it??? :/ I kinda need lspci in order to make my drivers work..
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 8:20 pm    Post subject: Reply with quote

kenny_w,

I was AFK for an unexpected family visit.
The forums are hosted in Canada. The server time is almost certainly set to UTC as that's traditional.

If you don't like the timestamps reported for posts, edit your profile to set your timezone.
I'll change it for you if you PM me with what you would like.

I'm in Scotland but not exactly where my profile position says I am :)

You are in good hands, it doesn't matter that I needed to leave for a wee while.

You won't drown we won't let that happen. You might go under a few times though.
It seems that you are over the worst already and have your first few fish.

-- edit --

kenny_w wrote:
Also, I installed pciutils, why isn't lspci working

That's not a good error report, so I'll make an educated guess.

lspci is in /usr/sbin/ That's not in a normal users path so (notice the $ prompt for a normal user)
Code:
$ lspci
bash: lspci: command not found

The root user has a different path that includes /usr/sbin
Thus
Code:
$ sudo lspci
works.

Code:
$ /usr/sbin/lspci
works too but some of the more verbose options will fail as the information they provide is not available to normal users.

That's based on your use of sudo to run emerge.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 9:10 pm    Post subject: Reply with quote

I just got lspci to work, this is what I did:

sudo chown root:root /usr/sbin/lspci

that didn't work, so I tried
cd /usr/sbin
cp lspci /usr/bin/
cp lspci /sbin/

and now it works :D It claims to be using the i915 driver, I have driver problems on Arch Linux, Void Linux, and a problem on FreeBSD but I managed to solve the issue on FreeBSD by disabling KMS or something of that sort, so I kind of am half-expecting that I may run into some sort of driver issue with Gentoo also. I really hope not, but we will see I suppose. Also, for my WiFi driver, how can I add the rtl8821ae driver without having to re-compile the kernel? recompiling the kernel takes quite a long time, I figure it'd be faster to just compile it from source, pretty certain its in https://github.com/lwfinger/rtlwifi_new.git , does the Gentoo kernel already have the headers installed? And I take it the equivalent to "build-essential" is already in there?

I'm currently sitting at 90 of 92 with emerge xorg-server, after I install LXDM + LXDE I'll hopefully be able to get the GUI started without too many issues, then I'll worry about the RTL8821AE driver.

Code:

lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03)
   Subsystem: Dell Mobile 945GSE Express Memory Controller Hub [1028:02f4]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
   Subsystem: Dell Mobile 945GSE Express Integrated Graphics Controller [1028:02f4]
   Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
   Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:02f4]
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
   Subsystem: Dell NM10/ICH7 Family High Definition Audio Controller [1028:02f4]
   Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02)
   Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 02)
   Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 3 [8086:27d4] (rev 02)
   Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02)
   Subsystem: Dell NM10/ICH7 Family USB UHCI Controller [1028:02f4]
   Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02)
   Subsystem: Dell NM10/ICH7 Family USB UHCI Controller [1028:02f4]
   Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02)
   Subsystem: Dell NM10/ICH7 Family USB UHCI Controller [1028:02f4]
   Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02)
   Subsystem: Dell NM10/ICH7 Family USB UHCI Controller [1028:02f4]
   Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02)
   Subsystem: Dell NM10/ICH7 Family USB2 EHCI Controller [1028:02f4]
   Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
   Subsystem: Dell 82801GBM (ICH7-M) LPC Interface Bridge [1028:02f4]
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 02)
   Subsystem: Dell 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [1028:02f4]
   Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 02)
   Subsystem: Dell NM10/ICH7 Family SMBus Controller [1028:02f4]
   Kernel driver in use: i801_smbus
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
   Subsystem: XAVi Technologies Corp. RTL8821AE 802.11ac PCIe Wireless Network Adapter [1b9a:2482]
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 02)
   Subsystem: Dell RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [1028:02f4]
   Kernel driver in use: r8169


Last edited by kenny_w on Sat Dec 09, 2017 9:22 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 9:20 pm    Post subject: Reply with quote

kenny_w,

Portage doesn't know that you have copied lspci all over the place.
That means when it gets updated, only the /usr/sbin/lspci will be updated.
That's a bad thing if you are not using that copy.

Learn that lspic is /usr/sbin/lspci and use it there.
If you really want to be able to access it in other paths, make symlinks. Then when /usr/sbin/lspci is updated, the symlinks all point to the updated lspci.
You can also make an alias in you .bash_profile.

The copies are making problems for the future.

Post your lspci output, so we can see how to set up your VIDEO_CARDS.

wgetpaste is your friend here, since you don't have a GUI yet.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 9:27 pm    Post subject: Reply with quote

Neddy, it seems to be giving me errors like "too many levels of symbolic links" when I tried to ln -s lspci /usr/bin/lspci

lspci -nnk is posted in the above post ^

even when I try to chown it, be it chown root:root /usr/sbin/lspci or chown kzn:kzn /usr/sbin/lspci, it still expects to find it in /usr/bin/ for some reason..
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 9:35 pm    Post subject: Reply with quote

kenny_w,

chown does make a file available in a different path.

Code:
$ ls -l /usr/sbin/lspci
-rwxr-xr-x 1 root root 81720 Dec  2 12:04 /usr/sbin/lspci
It changes the owner and optionally the group. Here root:root.

Code:
ln -s lspci /usr/bin/lspci
is not quite right.
Its
Code:
ls -s <real_path> <symbolic_path>
I keep getting that wrong too.

Code:
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
   Subsystem: Dell Mobile 945GSE Express Integrated Graphics Controller [1028:02f4]
   Kernel driver in use: i915
Thats the kernel driver, as you say.
As you only have the one graphics card. Your VIDEO_CARDS= can be simplified.
Code:
VIDEO_CARDS="amdgpu fbdev intel nouveau radeon radeonsi vesa dummy v4l"

Remove amdgpu nouveau radeon radeonsi dummy.
amdgpu nouveau radeon radeonsi are all for hardware you don't have.
dummy puts the pixel buffer into a chunk of main RAM with no way to get the image onto a display device. Its for testing/debugging.
vesa is a good fallback. To make the intel driver work, you have to get both the kernel and Xorg right at the same time.
vesa will just work.
You will probably never use fbdev or v4l but they are small and simple, so keep them if you want to.

Add in i915 i965. I have a feeling that in some places those drivers have been merged into intel but Xorg will pick the right one.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.


Last edited by NeddySeagoon on Sat Dec 09, 2017 9:48 pm; edited 1 time in total
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 9:37 pm    Post subject: Reply with quote

sudo ls -s /usr/sbin/lspci /usr/bin/lspci
ls: cannot access '/usr/bin/lspci': No such file or directory
76 /usr/sbin/lspci

??????? :/
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 9:49 pm    Post subject: Reply with quote

kenny_w,

Oops, /usr/sbin/lspci.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 9:51 pm    Post subject: Reply with quote

Umm... I don't understand what you're saying oops to.... I can't make the link work no matter what way I write it.

ls -s /usr/sbin/lspci /usr/bin/lspci
ls: cannot access '/usr/bin/lspci': No such file or directory
76 /usr/sbin/lspci

that's what I get when I try that command..
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 10:14 pm    Post subject: Reply with quote

kenny_w,

ls, for LiSt shows the directory tree structure.

ln, for LiNk makes links.

Code:
ln -s /usr/sbin/lspci lspci
makes a symbolic link called lspci in the current directory that points to /usr/sbin/lspci

Code:
roy@NeddySeagoon_Static ~ $ ln -s /usr/sbin/lspci lspci
roy@NeddySeagoon_Static ~ $ ls -l lspci
lrwxrwxrwx 1 roy roy 15 Dec  9 22:12 lspci -> /usr/sbin/lspci

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 10:27 pm    Post subject: Reply with quote

Lol this thing is gonna drive me nuts.

ls -l lspci
lrwxrwxrwx 1 kzn kzn 15 Dec 9 12:26 lspci -> /usr/sbin/lspci
kzn@kzn ~ $ lspci
-bash: lspci: command not found

-_-

I even tried doing ln -s lspci /usr/bin/lspci
just to see what would happen & that didn't make it work either(& then I deleted it)... I can use sudo lspci though, so whatever... Really frustrating how it can't just work with a link...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42592
Location: 56N 3W

PostPosted: Sat Dec 09, 2017 10:33 pm    Post subject: Reply with quote

kenny_w,

lspci -> /usr/sbin/lspci The link should be in cyan (pale blue)
If its in red, the target is missing.

Its not an error to make a link that poits to a file that does not exist.

This will be my last post tonight.
Good night.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 759

PostPosted: Sat Dec 09, 2017 10:34 pm    Post subject: Reply with quote

In what directory were you when you ran the ln command? In your home directory?

Your home directory is not in $PATH by default, so if you created the symlink in your folder, you wouldn't be able to call the command that way.

If so, try this instead:

Code:
$ ~/lspci
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 10:36 pm    Post subject: Reply with quote

Its in yellow - I see some blue ones, but most of its yellow, lspci included.

And thank you Neddy, have a good night! Hope to hear from you tomorrow lol


Last edited by kenny_w on Sat Dec 09, 2017 10:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 10:37 pm    Post subject: Reply with quote

superjaded wrote:
In what directory were you when you ran the ln command? In your home directory?

Your home directory is not in $PATH by default, so if you created the symlink in your folder, you wouldn't be able to call the command that way.

If so, try this instead:

Code:
$ ~/lspci



~/lspci works, so I've done something wrong??? That's strange, I made the links when I was cd'ed into /usr/sbin..
How do I undo what I've done wrong?
Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 759

PostPosted: Sat Dec 09, 2017 11:10 pm    Post subject: Reply with quote

Seems like it. Not quite sure what happened. You should have been in /usr/bin (not /usr/sbin) when creating the symlink anyhow, since I believe Neddy was trying to advise you to create a symlink in /usr/bin so it would be available to your regular user account.

That being said, where were you at with installing Xorg? From the output of lspci you posted earlier, you have an Intel card. I believe Neddy suggested that you put i915 and i965 your VIDEO_CARDS USE expand.

I would suggest to set your VIDEO_CARDS variable to the Intel drivers available. Xorg should pick the correct one.

Code:
VIDEO_CARDS="intel i915 i965"


I have a semi-recent System76 laptop on which I run gentoo which has an intel card, and I just have intel in my VIDEO_CARDS USE for that. Based on the Intel page in the Wiki, it seems "Intel" is for Xorg and i915/i965 is for Mesa (3D stuff). Still, including all three of the Intel cards and excluding all the non-Intel cards in your VIDEO_CARDS seems like a decent compromise.


I was going to mention earlier that it may not be a great idea to put so many things into your global USE flags when you were asking me about them earlier, especially if you are adding them in order to satisfy specific package dependencies. I tend to put mostly negation USE declarations (e.g. -networkmanager, -bluetooth, etc) and then use package specific USE declarations when I want to enable something unless I'm positive I want them enabled globally. This is my USE in my make.conf for example:

Code:
USE="cjk samba -ldap -kerberos -openldap -cups -printing pulseaudio -bluetooth -modemmanager -wireless"


As you can see, with the exception of cjk, samba and pulseaudio, it's all stuff I'm disabling. From there I enable USE flags on a per package basis by creating a directory called package.use in /etc/portage and then I put files in that directory named after what package I was enabling them for. Here are the contents of my /etc/portage/package.use for example. If I remember from earlier, package.use is currently a file for you, which is fine as well -- you'll just append your per-package USE changes to that file instead of creating a separate file.

In an ideal world, you would be to remove pretty much all of the flags you have in your make.conf USE variable for now, and add what you need per package as you need it. This may feel like a regression of sorts, but it'll work better in the long run. I don't know what your current USE variable looks like, but I would recommend setting it to something like this:

Code:
USE="mmx sse sse2"


This will cause a fair amount of the errors you've been receiving previously to come back, but what I would suggest is that you only add per package USE declarations as you need them. Portage will give you suggestions of what to do in order to progress. Sometimes it gives bad suggestions which is why most people would suggest to avoid using the autounmasking feature.

Regardless of what you decide to do with your make.conf USE variable, I'd say the next step is to make the aforementioned changes to your VIDEO_CARDS in your make.conf, possibly make the USE variable changes and then try again.

Also, I don't recall which profile you were using? Were you using a desktop profile or no?
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 11:32 pm    Post subject: Reply with quote

Here's the log, I put it in a pastebin
https://pastebin.com/sUQ3Syyn



Code:


>>> Emerging (39 of 180) sys-block/thin-provisioning-tools-0.4.1::gentoo
 * thin-provisioning-tools-0.4.1.tar.gz BLAKE2B SHA512 size ;-) ...                                                                                                                                         [ ok ]
>>> Unpacking source...
>>> Unpacking thin-provisioning-tools-0.4.1.tar.gz to /var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work
>>> Source unpacked in /var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work
>>> Preparing source in /var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1 ...
 * Running eautoreconf in '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1' ...
 * Running aclocal ...                                                                                                                               [ ok ]
 * Running autoconf --force ...                                                                                                                      [ ok ]
 * Running elibtoolize in: thin-provisioning-tools-0.4.1/
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1 ...
 * econf: updating thin-provisioning-tools-0.4.1/autoconf/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating thin-provisioning-tools-0.4.1/autoconf/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/lib --prefix=/ --bindir=/sbin --with-optimisation= --disable-testing
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for a BSD-compatible install... /usr/lib/portage/python3.5/ebuild-helpers/xattr/install -c
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking expat.h usability... yes
checking expat.h presence... yes
checking for expat.h... yes
checking iostream usability... yes
checking iostream presence... yes
checking for iostream... yes
checking libaio.h usability... yes
checking libaio.h presence... yes
checking for libaio.h... yes
checking boost/bind.hpp usability... yes
checking boost/bind.hpp presence... yes
checking for boost/bind.hpp... yes
checking boost/crc.hpp usability... yes
checking boost/crc.hpp presence... yes
checking for boost/crc.hpp... yes
checking boost/lexical_cast.hpp usability... yes
checking boost/lexical_cast.hpp presence... yes
checking for boost/lexical_cast.hpp... yes
checking boost/noncopyable.hpp usability... yes
checking boost/noncopyable.hpp presence... yes
checking for boost/noncopyable.hpp... yes
checking boost/optional.hpp usability... yes
checking boost/optional.hpp presence... yes
checking for boost/optional.hpp... yes
checking boost/shared_ptr.hpp usability... yes
checking boost/shared_ptr.hpp presence... yes
checking for boost/shared_ptr.hpp... yes
checking boost/static_assert.hpp usability... yes
checking boost/static_assert.hpp presence... yes
checking for boost/static_assert.hpp... yes
checking file owner...
checking group owner...
checking whether to enable debugging... no
checking for C++ optimisation flag...
checking whether to enable unit testing... no
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating unit-tests/Makefile
config.status: creating version.h
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1 ...
make -j3 V=
    [CXX] base/application.cc
    [CXX] base/base64.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/base64.o base/base64.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/application.o base/application.cc
    [CXX] base/endian_utils.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/endian_utils.o base/endian_utils.cc
    [DEP] base/endian_utils.cc
i686-pc-linux-gnu-g++ -MM -MT base/endian_utils.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/endian_utils.cc > base/endian_utils.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/endian_utils : Makefile ,g' < base/endian_utils.$$ > base/endian_utils.d; \
rm -f base/endian_utils.$$
    [CXX] base/error_state.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/error_state.o base/error_state.cc
    [DEP] base/error_state.cc
i686-pc-linux-gnu-g++ -MM -MT base/error_state.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/error_state.cc > base/error_state.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/error_state : Makefile ,g' < base/error_state.$$ > base/error_state.d; \
rm -f base/error_state.$$
    [CXX] base/progress_monitor.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/progress_monitor.o base/progress_monitor.cc
    [DEP] base/application.cc
i686-pc-linux-gnu-g++ -MM -MT base/application.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/application.cc > base/application.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/application : Makefile ,g' < base/application.$$ > base/application.d; \
rm -f base/application.$$
In file included from base/progress_monitor.cc:1:0:
./base/progress_monitor.h:18:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_progress_bar(std::string const &title);
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
In file included from base/progress_monitor.cc:1:0:
./base/progress_monitor.h:19:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_quiet_progress_monitor();
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
    [CXX] base/xml_utils.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/xml_utils.o base/xml_utils.cc
base/progress_monitor.cc:66:6: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
 std::auto_ptr<base::progress_monitor>
      ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
base/progress_monitor.cc: In function ‘std::auto_ptr<base::progress_monitor> base::create_progress_bar(const string&)’:
base/progress_monitor.cc:69:9: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  return auto_ptr<progress_monitor>(new progress_bar(title));
         ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
base/progress_monitor.cc: At global scope:
base/progress_monitor.cc:72:6: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
 std::auto_ptr<base::progress_monitor>
      ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
base/progress_monitor.cc: In function ‘std::auto_ptr<base::progress_monitor> base::create_quiet_progress_monitor()’:
base/progress_monitor.cc:75:9: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  return auto_ptr<progress_monitor>(new quiet_progress());
         ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/progress_monitor.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
    [DEP] base/progress_monitor.cc
i686-pc-linux-gnu-g++ -MM -MT base/progress_monitor.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/progress_monitor.cc > base/progress_monitor.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/progress_monitor : Makefile ,g' < base/progress_monitor.$$ > base/progress_monitor.d; \
rm -f base/progress_monitor.$$
    [CXX] block-cache/block_cache.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o block-cache/block_cache.o block-cache/block_cache.cc
In file included from base/xml_utils.h:4:0,
                 from base/xml_utils.cc:1:
./base/progress_monitor.h:18:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_progress_bar(std::string const &title);
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/xml_utils.h:4,
                 from base/xml_utils.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
In file included from base/xml_utils.h:4:0,
                 from base/xml_utils.cc:1:
./base/progress_monitor.h:19:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_quiet_progress_monitor();
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/xml_utils.h:4,
                 from base/xml_utils.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
    [DEP] base/base64.cc
i686-pc-linux-gnu-g++ -MM -MT base/base64.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/base64.cc > base/base64.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/base64 : Makefile ,g' < base/base64.$$ > base/base64.d; \
rm -f base/base64.$$
    [CXX] caching/cache_check.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o caching/cache_check.o caching/cache_check.cc
In file included from base/xml_utils.cc:1:0:
base/xml_utils.h:40:3: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
   auto_ptr<base::progress_monitor> create_monitor(bool quiet);
   ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/xml_utils.h:4,
                 from base/xml_utils.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
base/xml_utils.cc: In member function ‘void xml_utils::xml_parser::parse(const string&, bool)’:
base/xml_utils.cc:17:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<base::progress_monitor> monitor = create_monitor(quiet);
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/xml_utils.h:4,
                 from base/xml_utils.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
base/xml_utils.cc: At global scope:
base/xml_utils.cc:56:1: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
 auto_ptr<base::progress_monitor>
 ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./base/progress_monitor.h:4,
                 from base/xml_utils.h:4,
                 from base/xml_utils.cc:1:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
    [DEP] block-cache/block_cache.cc
i686-pc-linux-gnu-g++ -MM -MT block-cache/block_cache.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   block-cache/block_cache.cc > block-cache/block_cache.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo block-cache/block_cache : Makefile ,g' < block-cache/block_cache.$$ > block-cache/block_cache.d; \
rm -f block-cache/block_cache.$$
    [CXX] caching/cache_dump.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o caching/cache_dump.o caching/cache_dump.cc
In file included from ./persistent-data/transaction_manager.h:23:0,
                 from ./persistent-data/data-structures/btree.h:23,
                 from ./persistent-data/data-structures/array.h:23,
                 from ./caching/metadata.h:7,
                 from caching/cache_check.cc:18:
./persistent-data/space_map.h:125:9: error: deleted function ‘virtual persistent_data::space_map_detail::missing_counts::~missing_counts()’
   class missing_counts : public damage {
         ^~~~~~~~~~~~~~
./persistent-data/space_map.h:122:12: error: overriding non-deleted function ‘virtual persistent_data::space_map_detail::damage::~damage()’
    virtual ~damage() {}
            ^
./persistent-data/space_map.h:125:9: note: ‘virtual persistent_data::space_map_detail::missing_counts::~missing_counts()’ is implicitly deleted because the default definition would be ill-formed:
   class missing_counts : public damage {
         ^~~~~~~~~~~~~~
./persistent-data/space_map.h:125:9: error: ‘virtual persistent_data::space_map_detail::damage::~damage()’ is private within this context
./persistent-data/space_map.h:122:12: note: declared private here
    virtual ~damage() {}
            ^
    [DEP] base/xml_utils.cc
i686-pc-linux-gnu-g++ -MM -MT base/xml_utils.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   base/xml_utils.cc > base/xml_utils.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo base/xml_utils : Makefile ,g' < base/xml_utils.$$ > base/xml_utils.d; \
rm -f base/xml_utils.$$
In file included from ./persistent-data/block.h:152:0,
                 from ./caching/metadata.h:6,
                 from caching/cache_check.cc:18:
./persistent-data/block.tcc: In instantiation of ‘persistent_data::block_manager<BlockSize>::write_ref::~write_ref() [with unsigned int BlockSize = 4096u]’:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_pair.h:194:12:   required from here
./persistent-data/block.tcc:182:68: warning: throw will always call terminate() [-Wterminate]
     throw std::runtime_error("write_ref ref_count going below zero");
                                                                    ^
./persistent-data/block.tcc:182:68: note: in C++11 destructors default to noexcept
    [CXX] caching/cache_metadata_size.cc
i686-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o caching/cache_metadata_size.o caching/cache_metadata_size.cc
make: *** [Makefile:126: caching/cache_check.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from ./persistent-data/transaction_manager.h:23:0,
                 from ./persistent-data/data-structures/btree.h:23,
                 from ./persistent-data/data-structures/array.h:23,
                 from ./caching/mapping_array.h:4,
                 from caching/cache_dump.cc:8:
./persistent-data/space_map.h:125:9: error: deleted function ‘virtual persistent_data::space_map_detail::missing_counts::~missing_counts()’
   class missing_counts : public damage {
         ^~~~~~~~~~~~~~
./persistent-data/space_map.h:122:12: error: overriding non-deleted function ‘virtual persistent_data::space_map_detail::damage::~damage()’
    virtual ~damage() {}
            ^
./persistent-data/space_map.h:125:9: note: ‘virtual persistent_data::space_map_detail::missing_counts::~missing_counts()’ is implicitly deleted because the default definition would be ill-formed:
   class missing_counts : public damage {
         ^~~~~~~~~~~~~~
./persistent-data/space_map.h:125:9: error: ‘virtual persistent_data::space_map_detail::damage::~damage()’ is private within this context
./persistent-data/space_map.h:122:12: note: declared private here
    virtual ~damage() {}
            ^
In file included from ./caching/xml_format.h:4:0,
                 from caching/cache_dump.cc:11:
./base/progress_monitor.h:18:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_progress_bar(std::string const &title);
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./block-cache/block_cache.h:6,
                 from ./persistent-data/block.h:22,
                 from ./persistent-data/transaction_manager.h:22,
                 from ./persistent-data/data-structures/btree.h:23,
                 from ./persistent-data/data-structures/array.h:23,
                 from ./caching/mapping_array.h:4,
                 from caching/cache_dump.cc:8:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
In file included from ./caching/xml_format.h:4:0,
                 from caching/cache_dump.cc:11:
./base/progress_monitor.h:19:7: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
  std::auto_ptr<progress_monitor> create_quiet_progress_monitor();
       ^~~~~~~~
In file included from /usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/memory:81:0,
                 from /usr/include/boost/config/no_tr1/memory.hpp:21,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from ./block-cache/block_cache.h:6,
                 from ./persistent-data/block.h:22,
                 from ./persistent-data/transaction_manager.h:22,
                 from ./persistent-data/data-structures/btree.h:23,
                 from ./persistent-data/data-structures/array.h:23,
                 from ./caching/mapping_array.h:4,
                 from caching/cache_dump.cc:8:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^~~~~~~~
In file included from ./persistent-data/block.h:152:0,
                 from ./persistent-data/transaction_manager.h:22,
                 from ./persistent-data/data-structures/btree.h:23,
                 from ./persistent-data/data-structures/array.h:23,
                 from ./caching/mapping_array.h:4,
                 from caching/cache_dump.cc:8:
./persistent-data/block.tcc: In instantiation of ‘persistent_data::block_manager<BlockSize>::write_ref::~write_ref() [with unsigned int BlockSize = 4096u]’:
/usr/lib/gcc/i686-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_pair.h:194:12:   required from here
./persistent-data/block.tcc:182:68: warning: throw will always call terminate() [-Wterminate]
     throw std::runtime_error("write_ref ref_count going below zero");
                                                                    ^
./persistent-data/block.tcc:182:68: note: in C++11 destructors default to noexcept
make: *** [Makefile:126: caching/cache_dump.o] Error 1
    [DEP] caching/cache_metadata_size.cc
i686-pc-linux-gnu-g++ -MM -MT caching/cache_metadata_size.o -I. -I. -I./thin-provisioning  -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   caching/cache_metadata_size.cc > caching/cache_metadata_size.$$; \
sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo caching/cache_metadata_size : Makefile ,g' < caching/cache_metadata_size.$$ > caching/cache_metadata_size.d; \
rm -f caching/cache_metadata_size.$$
 * ERROR: sys-block/thin-provisioning-tools-0.4.1::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=sys-block/thin-provisioning-tools-0.4.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-block/thin-provisioning-tools-0.4.1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1'
 * S: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1'

>>> Failed to emerge sys-block/thin-provisioning-tools-0.4.1, Log file:

>>>  '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/temp/build.log'

 * Messages for package app-text/libpaper-1.1.24-r2:

 * run e.g. "paperconfig -p letter" as root to use letter-pagesizes

 * Messages for package sys-block/thin-provisioning-tools-0.4.1:

 * ERROR: sys-block/thin-provisioning-tools-0.4.1::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=sys-block/thin-provisioning-tools-0.4.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-block/thin-provisioning-tools-0.4.1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1'
 * S: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.4.1/work/thin-provisioning-tools-0.4.1'

 * Regenerating GNU info directory index...
 * Processed 98 info files.

Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 759

PostPosted: Sat Dec 09, 2017 11:51 pm    Post subject: Reply with quote

Are you planning on thin provisioning logical volumes with LVM? Are you even using LVM?

I've had issues with thin-provisioning-tools failing to compile in the past. I don't really use them (even though I do use device mapper/LVM), so for me it's easier to just disable the "thin" USE flag when it errors out. Seems like it's enabled by default.

Seems like this may be the problem area; I don't know enough C++ to be able to suggest a way to fix it:

Code:
./persistent-data/space_map.h:125:9: note: ‘virtual persistent_data::space_map_detail::missing_counts::~missing_counts()’ is implicitly deleted because the default definition would be ill-formed:
   class missing_counts : public damage {
         ^~~~~~~~~~~~~~
./persistent-data/space_map.h:125:9: error: ‘virtual persistent_data::space_map_detail::damage::~damage()’ is private within this context
./persistent-data/space_map.h:122:12: note: declared private here
    virtual ~damage() {}
            ^
    [DEP] base/xml_utils.cc


But like I said, it's probably easier just to add -thin to your package.use for sys-fs/lvm2, which is what pulls that package in:

Code:
sys-fs/lvm2 -thin
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sat Dec 09, 2017 11:57 pm    Post subject: Reply with quote

Oh cool so I don't need it?! Awesome. Its a package that seems to come along with lxde-meta...
Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 759

PostPosted: Sun Dec 10, 2017 12:14 am    Post subject: Reply with quote

I don't think you should need thin provisioning, no, especially not if you don't use LVs for your system. It's probably not applicable if you were following a guide. ;)

There are quite a few packages which seem to require sys-fs/lvm2 based on the USE flags so there's not much getting around that, but the thin USE flag is only useful if you are creating a logical volume with LVM that is thinly provisioned. If you aren't even using LVM, then just as well to disable it.


At some point, it may be worth it for you to install app-portage/gentoolkit. It has a command called "euse" which lets you do some different things with USE flags. The primary way in which I use the euse command is with the -i argument in order to get information regarding what a USE flag actually does. USE flags tend fairly straight forward once you have some knowledge of the general GNU/Linux ecosystem (e.g. the gtk and X USE flags compiles in optional support for the gtk library or X respectively), but there are plenty of obscure USE flags even to semi-experienced Gentoo users like myself.

For example:
Code:

# euse -i thin                                     
global use flags (searching: thin)                                             
************************************************************
no matching entries found

local use flags (searching: thin)
************************************************************
[-      ] thin                                                                 
    sys-fs/lvm2: Support for thin volumes                                     
        [+ B] 2.02.116 [gentoo]                                               
[bunch of other versions snipped


Gentoolkit has a bunch of useful tools, including equery.
Back to top
View user's profile Send private message
kenny_w
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2017
Posts: 83
Location: Toronto, Canada

PostPosted: Sun Dec 10, 2017 12:21 am    Post subject: Reply with quote

I've never understood the purpose for LVM, I made a 'default' install I think. I've got emerge started back up - 4 out of 139, I'm sure I'm going to run into another error or two along the way.

Hey guys... the headers and build-essential are already built into the system right?
Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 759

PostPosted: Sun Dec 10, 2017 1:58 am    Post subject: Reply with quote

kenny_w wrote:
Hey guys... the headers and build-essential are already built into the system right?


Not sure what you mean. Gentoo is made with an assumption that you will be building things from source, so all the basic stuff you need to compile stuff (what I assume you mean by build-essential) and compile against libraries (headers) come from the packages with which they are associated.

For example, the headers for your kernel come included when you install the associated kernel package (ie; gentoo-sources), so as long as you've got your kernel symlink set properly (ie; eselect kernel), applications will be able to compile against your kernel. If you install a library like gtk, openssl or whatever, the headers that are included with that package so dependent packages can properly be built from source. They aren't part of a separate package like binary based distributions, since a source based distro will necessarily need headers against which to compile dependent packages.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum