SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why dont you guys have a Live -current usb/hdd install so if something breaks you just delete the persistent stuff and start over?
To be specific- You would also have to rebuild the image with each successful upgrade...that may be time consuming...a script could drive all that...or you could forcibly remove the broken stuff from the persistence file/folder as I said. Being that the system is read only without persistence it cannot be broken actually, only when persistent changes are applide, even then you can boot up in fresh mode no persistence.
For example lets say youre using Slackware-Live or my Slackerc Live and it breaks in persistent mode on upgrade- just reboot in fresh mode and delete the pkgs from the persistent file and wait till it does work.
during GIMPLE pass: wrestrict
En la función ‘copy_bootdata’:
en pp_format, en pretty-print.c:1393
377 | static void __init copy_bootdata(char *real_mode_data)
| ^~~~~~~~~~~~~
CC [M] fs/cifs/readdir.o
Por favor, envíe un informe completo de errores,
con el código preprocesado si es apropiado.
Véase <https://gcc.gnu.org/bugs/> para instrucciones.
make[2]: *** [scripts/Makefile.build:303: arch/x86/kernel/head64.o] Error 1
make[1]: *** [scripts/Makefile.build:544: arch/x86/kernel] Error 2
make: *** [Makefile:1051: arch/x86] Error 2
CC [M] fs/cifs/ioctl.o
CC [M] fs/cifs/sess.o
CC [M] fs/cifs/export.o
CC crypto/skcipher.o
CC [M] fs/cifs/smb1ops.o
Last edited by USUARIONUEVO; 05-05-2019 at 11:34 AM.
I first used the script in the earlier post but the packages it output wasn't usable, they where missing 9.1.0_multilib in the package name also links was wrong in the packages.
Instead i downloaded https://slackware.nl/people/alien/mu...e/current/gcc/ which built packages that looks right (haven't had time to test them yet).
Last edited by Nille_kungen; 05-05-2019 at 04:11 PM.
Seems Alien Bob has kindly updated his packages now.
Code:
Sun May 5 19:31:44 UTC 2019
14.2/slackware64-compat32: Refreshed the *compat32 packages.
current/slackware64-compat32: Refreshed the *compat32 packages.
gcc-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-brig-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-g++-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-gdc-9.1.0_multilib-x86_64-2alien.txz: Added.
This package contains the newly added D language support.
gcc-gfortran-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-gnat-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-go-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
gcc-objc-9.1.0_multilib-x86_64-2alien.txz: Upgraded.
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/tigervnc-1.9.0/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/tigervnc-1.9.0/build/CMakeFiles/CMakeError.log".
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
used as include directory in directory /tmp/SBo/tigervnc-1.9.0/tests
-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/tigervnc-1.9.0/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/tigervnc-1.9.0/build/CMakeFiles/CMakeError.log".
I have a very similar output as yours if I don't install tigervnc's dependency, fltk
Code:
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
FLTK_BASE_LIBRARY
linked by target "vncviewer" in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
linked by target "fbperf" in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
FLTK_IMAGES_LIBRARY
linked by target "vncviewer" in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
linked by target "fbperf" in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
FLTK_INCLUDE_DIR
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/vncviewer
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
used as include directory in directory /tmp/tmp-tigervnc/tigervnc-1.9.0/tests
-- Configuring incomplete, errors occurred!
See also "/tmp/tmp-tigervnc/tigervnc-1.9.0/CMakeFiles/CMakeOutput.log".
See also "/tmp/tmp-tigervnc/tigervnc-1.9.0/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found. Stop.
make: *** No targets specified and no makefile found. Stop.
The top example has affected at least one program I use.
Quote:
C language issues
Block scope compound literal's lifetime
The C standard says that compound literals which occur inside of the body of a function have automatic storage duration associated with the enclosing block. Older GCC releases were putting such compound literals into the scope of the whole function, so their lifetime actually ended at the end of containing function. This has been fixed in GCC 9. Code that relied on this extended lifetime needs to be fixed, move the compound literals to whatever scope they need to accessible in.
Code:
struct S { int a, b; };
int foo(void) {
// The following line no longer compiles
struct S *p = &({ (struct S) { 1, 2 }; });
struct S *q;
{
q = &(struct S) { 3, 4 };
}
// This is invalid use after lifetime of the compound literal
// ended.
return q->b;
}
Compiler output
make[1]: se entra en el directorio '/home/kernel/linux-4.19.42'
Using /usr/src/linux-4.19.42 as source for kernel
GEN ./Makefile
CALL /usr/src/linux-4.19.42/scripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC arch/x86/kernel/head64.o
during GIMPLE pass: wrestrict
En la función ‘copy_bootdata’:
en pp_format, en pretty-print.c:1393
377 | static void __init copy_bootdata(char *real_mode_data)
| ^~~~~~~~~~~~~
Por favor, envíe un informe completo de errores,
con el código preprocesado si es apropiado.
Véase <https://gcc.gnu.org/bugs/> para instrucciones.
make[3]: *** [/usr/src/linux-4.19.42/scripts/Makefile.build:304: arch/x86/kernel/head64.o] Error 1
make[2]: *** [/usr/src/linux-4.19.42/scripts/Makefile.build:544: arch/x86/kernel] Error 2
make[1]: *** [/usr/src/linux-4.19.42/Makefile:1051: arch/x86] Error 2
make[1]: se sale del directorio '/home/kernel/linux-4.19.42'
make: *** [Makefile:146: sub-make] Error 2
It did break KDE4 actually, but only if you had multilib enabled. A fix was released after a few hours, but in my case it took over 24 hrs to go into the mirror I was using
Compiler output
make[1]: se entra en el directorio '/home/kernel/linux-4.19.42'
Using /usr/src/linux-4.19.42 as source for kernel
GEN ./Makefile
CALL /usr/src/linux-4.19.42/scripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC arch/x86/kernel/head64.o
during GIMPLE pass: wrestrict
En la función ‘copy_bootdata’:
en pp_format, en pretty-print.c:1393
377 | static void __init copy_bootdata(char *real_mode_data)
| ^~~~~~~~~~~~~
Por favor, envíe un informe completo de errores,
con el código preprocesado si es apropiado.
Véase <https://gcc.gnu.org/bugs/> para instrucciones.
make[3]: *** [/usr/src/linux-4.19.42/scripts/Makefile.build:304: arch/x86/kernel/head64.o] Error 1
make[2]: *** [/usr/src/linux-4.19.42/scripts/Makefile.build:544: arch/x86/kernel] Error 2
make[1]: *** [/usr/src/linux-4.19.42/Makefile:1051: arch/x86] Error 2
make[1]: se sale del directorio '/home/kernel/linux-4.19.42'
make: *** [Makefile:146: sub-make] Error 2
I get the same issue since gcc9 , and im not encounter where is the problem , probably some gcc bug , im cant build kernels , in two machines i7 6700k and i7 7500u.
I get the same issue since gcc9 , and im not encounter where is the problem , probably some gcc bug , im cant build kernels , in two machines i7 6700k and i7 7500u.
I'm telling you in Spanish because this affects the users of our language:
Abres el archivo Makefile del paquete del kernel y comentas la línea unexport LC_ALL. Luego, en la terminal estableces la variable de entorno que esa línea anula antes de ejecutar make:
Code:
$ export LC_ALL=C
Este fallo ya se producía con GCC 8 y Wine (que con GCC 9 no da). El problema ahora, es que se ha extendido a otros paquetes, hoy mismo me ha pasado a mí con Python3 y es un problema de GCC con las locales. Da igual que uses UTF-8 o ISO-8859-1 o 15, el problema sólo se soluciona estableciendo las locales a C.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.