Re: [CentOS] Learning to build applications
On 11/18/20 4:38 PM, H wrote: I am a beginner when it comes to compiling applications and would appreciate suggestion how to fix the above. Thank you. Looks like a build failure that was mentioned here: https://github.com/pgmodeler/pgmodeler/issues/1259 I believe this reply is relevant: "It's not yet documented but you have to use the latest Qt version 5.11 or 5.12 and have C++14 enabled on your compiler. Make sure to use at least gcc 5.0 to get full support to C++14." I believe CentOS 7 includes Qt 5.9, so I wouldn't expect this application to build, there. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Learning to build applications
I have managed to get through the qtmake stage of compiling the current github
version of pgmodeler on CentOS 7 but make && make install fails with:
make && make install
cd libutils/ && ( test -e Makefile || /bin/qmake-qt5 -o Makefile
/home/h/pgmodeler/libutils/libutils.pro CONFIG+=release PREFIX= BINDIR=
PRIVATEBINDIR= PRIVATELIBDIR=/lib ) && make -f Makefile
make[1]: Entering directory /home/h/pgmodeler/libutils' g++ -c -pipe -O2 -g
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O2
-std=gnu++1y -Wall -W -D_REENTRANT -fPIC -DBUILDNUM=\"20201030\" -DBINDIR=\"\"
-DPLUGINSDIR=\"/lib/pgmodeler/plugins\" -DPRIVATEBINDIR=\"\"
-DCONFDIR=\"/share/pgmodeler/conf\" -DDOCDIR=\"/share/pgmodeler\"
-DLANGDIR=\"/share/pgmodeler/lang\" -DSAMPLESDIR=\"/share/pgmodeler/samples\"
-DSCHEMASDIR=\"/share/pgmodeler/schemas\" -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB
-DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I.
-isystem /usr/include/libxml2 -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem
/usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -Imoc -isystem
/usr/include/libdrm -I/usr/lib64/qt5/mkspecs/linux-g++ -o obj/exception.o
src/exception.cpp In file included from src/exception.cpp:18:0:
src/exception.h:41:11: error: ‘underlying_type_t’ in namespace ‘std’ does not
name a type constexpr std::underlying_type_t enum_cast (Enum obj_type)
noexcept ^ src/exception.cpp: In constructor ‘Exception::Exception(ErrorCode,
const QString&, const QString&, int, Exception*, const QString&)’:
src/exception.cpp:295:86: error: ‘enum_cast’ was not declared in this scope
configureException(QApplication::translate("Exception",messages[enum_cast(error_code)][ErrorMessage].toStdString().c_str(),"",
-1), ^ src/exception.cpp: In constructor ‘Exception::Exception(ErrorCode,
const QString&, const QString&, int, std::vector&, const QString&)’:
src/exception.cpp:314:86: error: ‘enum_cast’ was not declared in this scope
configureException(QApplication::translate("Exception",messages[enum_cast(error_code)][ErrorMessage].toStdString().c_str(),"",-1),
^ src/exception.cpp: In static member function ‘static QString
Exception::getErrorMessage(ErrorCode)’: src/exception.cpp:371:25: error:
‘enum_cast’ was not declared in this scope if(enum_cast(error_code) <
ErrorCount) ^ src/exception.cpp: In static member function ‘static QString
Exception::getErrorCode(ErrorCode)’: src/exception.cpp:382:25: error:
‘enum_cast’ was not declared in this scope if(enum_cast(error_code) <
ErrorCount) ^ src/exception.cpp: In static member function ‘static QString
Exception::getErrorMessage(ErrorCode)’: src/exception.cpp:378:1: warning:
control reaches end of non-void function [-Wreturn-type] } ^ src/exception.cpp:
In static member function ‘static QString Exception::getErrorCode(ErrorCode)’:
src/exception.cpp:386:1: warning: control reaches end of non-void function
[-Wreturn-type] } ^ make[1]: *** [obj/exception.o] Error 1 make[1]: Leaving
directory /home/hakan/pgmodeler/libutils'
make: *** [sub-libutils-make_first-ordered] Error 2
I am a beginner when it comes to compiling applications and would appreciate
suggestion how to fix the above. Thank you.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with VirtualBox on CentOS 7
I haven't experienced this error yet. Did you update the "Extension Pack"? Em qua, 18 de nov de 2020 19:00, Jerry Geis escreveu: > Any Virtualbox on CentOS guru's out there? > > I only have 1 VM on my linux host. in the update process to virtualbox > 6.1.16 my config was lost. When I run Virtualbox my VM does not show. So I > desire to add it back. > > My structure is this. > ls -l /home/silentm/vmware/CentOS\ 64-bit\ LSI/ > -rw--- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram > -rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd > -rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx > -rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf > -rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit > LSI.vmdk > -rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx > -rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log > -rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log > -rw-r--r-- 1 silentm silentm 256013 May 31 10:09 vmware-2.log > -rw-r--r-- 1 silentm silentm 322239 Aug 13 08:31 vmware.log > > When I click add and goto the directory above - IT ONLY wants to add *.xml > and *.vbox. So that is no good. > When I click New and Enter my name, and use existing disk - it does not > like that either. > > How can I get this same VM to be in my menu and run again ? > Thanks, > Jerry > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with VirtualBox on CentOS 7
Hi Frank - Thanks. Gosh crazy of me. The Vmware icon was missing on the left hot menu. So I was mistakenly running Virtual Box (of which I never had added anything)... I re-added the vmware player - and my files are there like always. Long day. Thanks for the knock in the head. Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with VirtualBox on CentOS 7
On Wed, 18 Nov 2020 16:46:43 -0500
Jerry Geis wrote:
> When I run Virtualbox my VM does not show. So I
> desire to add it back.
My Centos 8 Virtualbox image directory contains the following files:
$ ls -R
.:
'Centos 8.vbox' 'Centos 8.vbox-prev' 'Centos 8.vdi' Logs Snapshots
./Logs:
VBox.log VBox.log.1 VBox.log.2 VBox.log.3
./Snapshots:
2020-11-06T23-19-52-568532000Z.sav {be3832a9-9a12-474b-b1dc-74841335520a}.vdi
You don't appear to have any .vbox or .vdi files in your directory, so whatever
you have ain't Virtualbox.
It says vmware in your log filenames, so maybe you should be setting up vmware
instead of Virtualbox. (They are different things.)
--
Can we uninstall 2020 and install it again? This one has a virus.
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] Help with VirtualBox on CentOS 7
Any Virtualbox on CentOS guru's out there? I only have 1 VM on my linux host. in the update process to virtualbox 6.1.16 my config was lost. When I run Virtualbox my VM does not show. So I desire to add it back. My structure is this. ls -l /home/silentm/vmware/CentOS\ 64-bit\ LSI/ -rw--- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram -rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd -rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx -rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf -rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit LSI.vmdk -rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx -rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log -rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log -rw-r--r-- 1 silentm silentm 256013 May 31 10:09 vmware-2.log -rw-r--r-- 1 silentm silentm 322239 Aug 13 08:31 vmware.log When I click add and goto the directory above - IT ONLY wants to add *.xml and *.vbox. So that is no good. When I click New and Enter my name, and use existing disk - it does not like that either. How can I get this same VM to be in my menu and run again ? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] (C8) root on mdraid
Mon, 16 Nov 2020 14:28:54 -0800 Gordon Messmer : > On 11/15/20 10:40 PM, Łukasz Posadowski wrote: > > > Sun, 15 Nov 2020 14:16:48 -0800 Gordon Messmer > > : > > > > > >> Use metadata version 1.2 instead of 0.9. > >> > > Thanks, I'll try that. I'm use to metadata 0.9, because GRUB have > > (had?) some issue with the newer ones. > > > If that doesn't work, and you need to use metadata 0.9, then check > /etc/default/grub and make sure that GRUB_CMDLINE_LINUX contains > "rd.md.uuid=". T.H.A.N.K Y.O.U. :) I was sure I had to pass uuid of the partition, not md0. It is working now. One last thing: since Linux Rescue CD does not recognize selinux, / mounted itself as read-only. Disabling SeLinux helped. I think I need to relabel all the files on a new host. So generally: - edit /etc/default/grub and grub2-mkconfig, - generate mdadm.conf (I think a copy of it resides inside initramfs), - fstab (root mounts anyway, so just for swap patition), - disable selinux, - generate initramfs with dracut. Big thanks to all of you. It was rough, but it's done. -- Łukasz Posadowski ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel RST RAID 1, partition tables and UUIDs
> On Nov 18, 2020, at 2:51 AM, hw wrote: > > On Tue, 2020-11-17 at 08:01 -0600, Valeri Galtsev wrote: >> >>> On Nov 17, 2020, at 1:07 AM, hw wrote: >> [...] >>> If you don't require Centos, you could go for Fedora instead. Fedora has >>> btrfs >>> as default file system now which has software raid built-in, and Fedora can >>> have >>> advantages over Centos. >>> >> >> There are advantages in a bleeding edge one can find useful. There is some >> bleeding too, plausible, so don’t be surprised. > > There is bleeding with Centos 7, too, and Centos 8 is probably no different. > One can always be surprised. And that is why my servers run FreeBSD. But when I switched from Fedora to CentOS (quite a while back), it made noticeable difference. Valeri > I'm not so much referring to bleeding but advantages like packages being > available > in Fedora that aren't available in Centos. And not being able to upgrade a > distribution when a new release comes out is a killer for Centos since there > are > things in Centos 8 that make me wonder why I shouldn't go for Fedora right > away. At > least I have the goodies when I do that. And that is designed into the way distributions are maintained. Some of them are like “sliding release”, like Fedora, Debian… And with those you often get surprises just upon routine update something breaks, as package is replaced with higher version which has different internals. But these are a charm to “upgrade” to next release. One can also mention FreeBSD and MacOS as being close to this, IMHO. Others are “Enterprise” very long life. They are being patched by back porting fixes (very effort consuming), but they mostly “unchanged” packages internal wise, so during 10 years of such system’s life cycle, it is only rarely you may have things broken. But when it comes to life cycle end, you effectively have to build new system, as virtually neither of software packages can just step up from release 10years old to todays. You effectively do at once all you did for 10 years of "sliding release” system. Examples of this style are: RedHat Enterprise, CentOS (“binary replica” of the former). With all bad one can say about Microsoft, I would mention MS Windows system on which something you install when it release, will still work when the system maintenance ends 10 years later. So, it is one’s choice, which style of system to install and maintain. I for one chose CentOS for number crunchers and workstations, which takes less of my time to maintain (but FreeBSD for servers, but that is different story). Your choice appears to be different, and we both are right in our choices based of our goals. > But then, there are now things in Fedora that make we wonder if I should > switch to > arch. Like how retarded is it to forcefully enable swapping to RAM by > default. > Either you have plenty RAM and swapping has no disadvantages, or you don't and > swapping to RAM makes it only worse. I can see that it might have an > advantages > for when you don't create a swap partition, but that's already a bad idea in > the > first place unless you have special requirements that are far from any > default. > I don't even dare wondering if it can get any more stupid, because > unfortunately, > there is no limit to stupidity and the only thing helps against it is more > stupidity. > > And systemd ursurping the functionality of crond? The last thing we need is > systemd to become even more cryptic by that --- and how can I check if I am > getting > an email when a failed disk is detected, or when errors are being detected by > raid-check? I can do that with crond, but not with systemd. Systemd has resembling portion of code in mainstream Linux kernel (I bet experts will correct me where I’m wrong). You can try to go with systemd-free Linux distro like devuan (fork of Debian that happened when Debian went systemd way). Or you can try one of BSD descendants, which being such are closer to original UNIX philosophy: FreeBSD, NetBSD, OpenBSD (and variety of others standing quite close to these, or slightly more apart, your duckduckgo search will be as good as mine). Valeri > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] (C8) root on mdraid
Mon, 16 Nov 2020 10:29:17 + Tony Mountifield : > In article > <20201115123245.db62b8248e1f248afe028...@lukaszposadowski.pl>, Lukasz > Posadowski wrote: > > > > Hello everyone. > > > > I'm trying to install CentOS 8 with root and swap partitions on > > software raid. The plan is: > > - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, > > using Linux Rscue CD, > > - install CentOS 8 with Virtual Box on my laptop, > > - rsync CentOS 8 root partition on /dev/md0p1, > > - chroot in CentOS 8 root partition, > > - configure /etc/mdadm.conf, grub.cfg, initramfs, install > > bootloader on both sda and sdb drives. > > > > I think I can do first four of the above, but my CentOS installation > > acts strange after rebooting the server. It recognizes the raid, but > > boots randomly with root on /dev/sda1 (and recognizes raid > > with /dev/sdb disk), or with root on /dev/sdb1 (and recognizes raid > > with /dev/sda disk). When booting from Linux Rescue CD, the raid > > with two disk is recognized. > > I thought it was much more usual to partition both disks to give > sda1,2,3 and sdb1,2,3, and then create /dev/md0 from > sda1/sdb1, /dev/md1 from sda2/sdb3, and so on. > > That's the way I have always done it, and have never had any problems. > Never seen an attempt to partition an md device before. In that case, > how would the kernel and initrd be found in order to assemble the > RAID? It totaly works either way - raid on partitions and raid on disks. I'm use to mirroring whole disks. -- Łukasz Posadowski ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Best practice preparing for disk restoring system
> On Nov 18, 2020, at 3:27 AM, J Martin Rushton via CentOS > wrote: > > I'd agree with you John. I'm trying to get away from Amanda's > unpredictability and go back to using scripts to drive dump (for ext2/3/4) > and xfsdump (for xfs). > There is enterprise class open source backup software worth mentioning: bareos (and bacula which it forked from). I use them for over a decade, bacula first, then I switched over to bareos. I back up using bareos UNIXes (FreeBSD), Linuxes (CentOS), MS Windows. Valeri > Is there any easy way to tell rear to include xfsdump and dump capability? > If the commands are there then its trivial to restore data. > > What I've done in the past is before the nightly backup write a small file to > the root of each filesystem giving disk geometries. You can then use any > recovery DVD to partition and reload the OS. If rear can do this for me it > would be __much__ neater! > > On 18/11/2020 08:24, John Pierce wrote: >> I'm old school, but I always liked using dump/restore on unix file >> systems. e2dump or whatever for linux, zfs send/recieve for zfs, ufsdump >> on freebsd ufs, etc etc. >> then I just need to know what file systems they are, and where they should >> be mounted, and its trivial to set tha tup on new hardware. >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > J Martin Rushton MBCS > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Best practice preparing for disk restoring system
Thanks for that. I only picked up on rear this morning, I suppose if you don't go looking for it you'll never find it. A combination of the paper Site Management Guide and the nightly disk summary have worked for over 20 years on *NIX! VMS before that was totally different, but we still kept paper copies of configuration. On 18/11/2020 12:47, Felix Kölzow wrote: What I've done in the past is before the nightly backup write a small file to the root of each filesystem giving disk geometries. You can then use any recovery DVD to partition and reload the OS. If rear can do this for me it would be __much__ neater! According to rear webpage: https://relax-and-recover.org/about/ Extensive disk layout implementation, incl. * HWRAID (HP SmartArray) * SWRAID * LVM * multipathing * DRBD * iSCSI * LUKS (encrypted partitions and filesystems) I personally used rear to restore lvm volume groups and several logical volumes with success. I will test a more complicated layout until the end of this year and can let you know about the findings. Regards, Felix ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Best practice preparing for disk restoring system
What I've done in the past is before the nightly backup write a small file to the root of each filesystem giving disk geometries. You can then use any recovery DVD to partition and reload the OS. If rear can do this for me it would be __much__ neater! According to rear webpage: https://relax-and-recover.org/about/ Extensive disk layout implementation, incl. * HWRAID (HP SmartArray) * SWRAID * LVM * multipathing * DRBD * iSCSI * LUKS (encrypted partitions and filesystems) I personally used rear to restore lvm volume groups and several logical volumes with success. I will test a more complicated layout until the end of this year and can let you know about the findings. Regards, Felix ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Best practice preparing for disk restoring system
I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the root of each filesystem giving disk geometries. You can then use any recovery DVD to partition and reload the OS. If rear can do this for me it would be __much__ neater! On 18/11/2020 08:24, John Pierce wrote: I'm old school, but I always liked using dump/restore on unix file systems. e2dump or whatever for linux, zfs send/recieve for zfs, ufsdump on freebsd ufs, etc etc. then I just need to know what file systems they are, and where they should be mounted, and its trivial to set tha tup on new hardware. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel RST RAID 1, partition tables and UUIDs
On Tue, 2020-11-17 at 08:01 -0600, Valeri Galtsev wrote: > > > On Nov 17, 2020, at 1:07 AM, hw wrote: > [...] > > If you don't require Centos, you could go for Fedora instead. Fedora has > > btrfs > > as default file system now which has software raid built-in, and Fedora can > > have > > advantages over Centos. > > > > There are advantages in a bleeding edge one can find useful. There is some > bleeding too, plausible, so don’t be surprised. There is bleeding with Centos 7, too, and Centos 8 is probably no different. One can always be surprised. I'm not so much referring to bleeding but advantages like packages being available in Fedora that aren't available in Centos. And not being able to upgrade a distribution when a new release comes out is a killer for Centos since there are things in Centos 8 that make me wonder why I shouldn't go for Fedora right away. At least I have the goodies when I do that. But then, there are now things in Fedora that make we wonder if I should switch to arch. Like how retarded is it to forcefully enable swapping to RAM by default. Either you have plenty RAM and swapping has no disadvantages, or you don't and swapping to RAM makes it only worse. I can see that it might have an advantages for when you don't create a swap partition, but that's already a bad idea in the first place unless you have special requirements that are far from any default. I don't even dare wondering if it can get any more stupid, because unfortunately, there is no limit to stupidity and the only thing helps against it is more stupidity. And systemd ursurping the functionality of crond? The last thing we need is systemd to become even more cryptic by that --- and how can I check if I am getting an email when a failed disk is detected, or when errors are being detected by raid-check? I can do that with crond, but not with systemd. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Best practice preparing for disk restoring system
I'm old school, but I always liked using dump/restore on unix file systems. e2dump or whatever for linux, zfs send/recieve for zfs, ufsdump on freebsd ufs, etc etc. then I just need to know what file systems they are, and where they should be mounted, and its trivial to set tha tup on new hardware. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
