Public bug reported:
Binary package hint: gcc-4.4
Compiling with -fopenmp causes the following error:
g++ -o
/home/blender/trunk/build/linux2_debug/intern/elbeem/intern/solver_main.o
-c -pipe -fPIC -funsigned-char -fno-strict-aliasing -fopenmp -Wno-
invalid-offsetof -Wno-sign-compare -pipe
source code for bug (generated with g++ -E)
** Attachment added: gcc-bug
http://launchpadlibrarian.net/36542769/gcc-bug
--
gcc fails when using -fopenmp
https://bugs.launchpad.net/bugs/493702
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Since I upgraded to 8.10 I've been having this same problem. Sometimes
the log shows CPU#0 stuck and sometimes it doesn't. It's done this with
the stock nvidia-glx-177 drivers from Ubuntu, and drivers 180.08 and
180.11 installed from nvidia. I'm not using compiz, just the standard
Gnome window
Same problem here. Running Linux Mint11 (Katya) 64-bit, and a HTC
smartphone with USB mass storage gives the same problem whether I do
Eject or Safely Remove Drive.
Unable to stop drive:
Error detaching: helper exited with exit code 1: Detaching device /dev/sdb
USB device:
*** This bug is a duplicate of bug 1767703 ***
https://bugs.launchpad.net/bugs/1767703
I encountered this today while trying to install 18.04.2. I previously
installed Linux Mint 19.1 on the same UEFI SSD with Secure Boot enabled with no
issues.
1) After the 18.04.2 failed I deleted the
*** This bug is a duplicate of bug 1767703 ***
https://bugs.launchpad.net/bugs/1767703
I was able to successfully install after writing the 18.04.2 ISO file to
the raw USB drive. After booting into the Live environment, gdisk
report that the partition table is an invalid GPT:
root@ubuntu:~#
This patch was reverted about a month ago, and made its way into the 5.1
kernel recently. The issue now showing up on my Dell Latitude 7400.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
