[opensuse-factory] Plasma 5
Hi, I'm considering trying OpeSuse, is (/when it will be) Plasma 5 default(?)-Desktop? Regards, Tatu -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op donderdag 26 februari 2015 22:35:38 schreef Tatu Hammarén:
Hi,
I'm considering trying OpeSuse, is (/when it will be) Plasma 5 default(?)-Desktop?
Both is possible, depends on the main purpose of your system. Desktop -> desktop, server -> default. But considering, you want to use Plasma 5, desktop seems a better choice. Standard Plasma 5 will not be installed, but you can search for package plasma5_basis, which when chosen to be installed, will remove conflicting KDE 4 packages and install the Plasma 5 desktop. Only 13.2 and Tumbleweed provide Plasma 5. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks!
On 26 February 2015 at 23:02, Freek de Kruijf
Op donderdag 26 februari 2015 22:35:38 schreef Tatu Hammarén:
Hi,
I'm considering trying OpeSuse, is (/when it will be) Plasma 5 default(?)-Desktop?
Both is possible, depends on the main purpose of your system. Desktop -> desktop, server -> default. But considering, you want to use Plasma 5, desktop seems a better choice. Standard Plasma 5 will not be installed, but you can search for package plasma5_basis, which when chosen to be installed, will remove conflicting KDE 4 packages and install the Plasma 5 desktop. Only 13.2 and Tumbleweed provide Plasma 5.
-- fr.gr.
Freek de Kruijf
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
It seems the Xine headers aren't compatible with the new GCC. [ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2 Mar 2015, Ilya Chernykh wrote:
It seems the Xine headers aren't compatible with the new GCC.
[ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op...
Sounds like they are eventually auto-generated by preprocessing and $stuff
where $stuff doesn't expect extra #line directives GCC now emits.
The fix is to do the preprocessign step with -P (do not emit #line
directives).
Richard.
--
Richard Biener
On Mon, Mar 02, 2015 at 02:45:32PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Ilya Chernykh wrote:
It seems the Xine headers aren't compatible with the new GCC.
[ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op...
Sounds like they are eventually auto-generated by preprocessing and $stuff where $stuff doesn't expect extra #line directives GCC now emits. The fix is to do the preprocessign step with -P (do not emit #line directives).
I tried building it, and that specific line has static inline void somefunction() and I think it chokes on the inline. Probably due to the new XINE 1.2.6 Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2 Mar 2015, Marcus Meissner wrote:
On Mon, Mar 02, 2015 at 02:45:32PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Ilya Chernykh wrote:
It seems the Xine headers aren't compatible with the new GCC.
[ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op...
Sounds like they are eventually auto-generated by preprocessing and $stuff where $stuff doesn't expect extra #line directives GCC now emits. The fix is to do the preprocessign step with -P (do not emit #line directives).
I tried building it, and that specific line has
static inline void somefunction()
and I think it chokes on the inline.
Did you look at preprocessed source?
Probably due to the new XINE 1.2.6
Ciao, Marcus
--
Richard Biener
On Mon, Mar 02, 2015 at 05:13:19PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Marcus Meissner wrote:
On Mon, Mar 02, 2015 at 02:45:32PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Ilya Chernykh wrote:
It seems the Xine headers aren't compatible with the new GCC.
[ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op...
Sounds like they are eventually auto-generated by preprocessing and $stuff where $stuff doesn't expect extra #line directives GCC now emits. The fix is to do the preprocessign step with -P (do not emit #line directives).
I tried building it, and that specific line has
static inline void somefunction()
and I think it chokes on the inline.
Did you look at preprocessed source?
In file included from /usr/include/xine/audio_out.h:30:0, from audio_fifo_out.c:22: /usr/include/xine/xineutils.h:149:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’ static inline void _x_freep(void *ptr) { ^ code around that is: void *xine_xcalloc(size_t nmemb, size_t size) __attribute__((__malloc__)) ; static inline void _x_freep(void *ptr) { void **p = (void **)ptr; free (*p); *p = ((void *)0); } it is building with: -std=iso9899:1990 gcc -DHAVE_CONFIG_H -I. -I.. -I/opt/kde3/include/arts -I/opt/kde3/include -I/usr/lib/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -U__STRICT_ANSI__ -std=iso9899:1990 -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing -Wformat-security -Wmissing-format-attribute -MT audio_fifo_out.lo -MD -MP -MF .deps/audio_fifo_out.Tpo -c -o audio_fifo_out.lo audio_fifo_out.c The above std setting blocks the "inline" keyword, if I remove it from the gcc line, it builds. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2 Mar 2015, Marcus Meissner wrote:
On Mon, Mar 02, 2015 at 05:13:19PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Marcus Meissner wrote:
On Mon, Mar 02, 2015 at 02:45:32PM +0100, Richard Biener wrote:
On Mon, 2 Mar 2015, Ilya Chernykh wrote:
It seems the Xine headers aren't compatible with the new GCC.
[ 498s] In file included from /usr/include/xine/audio_out.h:30:0, [ 498s] from audio_fifo_out.c:22: [ 498s] /usr/include/xine/xineutils.h:149:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdemultimedia3/op...
Sounds like they are eventually auto-generated by preprocessing and $stuff where $stuff doesn't expect extra #line directives GCC now emits. The fix is to do the preprocessign step with -P (do not emit #line directives).
I tried building it, and that specific line has
static inline void somefunction()
and I think it chokes on the inline.
Did you look at preprocessed source?
In file included from /usr/include/xine/audio_out.h:30:0, from audio_fifo_out.c:22: /usr/include/xine/xineutils.h:149:15: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’ static inline void _x_freep(void *ptr) { ^
code around that is:
void *xine_xcalloc(size_t nmemb, size_t size) __attribute__((__malloc__)) ;
static inline void _x_freep(void *ptr) { void **p = (void **)ptr; free (*p); *p = ((void *)0); }
it is building with: -std=iso9899:1990
gcc -DHAVE_CONFIG_H -I. -I.. -I/opt/kde3/include/arts -I/opt/kde3/include -I/usr/lib/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -U__STRICT_ANSI__ -std=iso9899:1990 -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing -Wformat-security -Wmissing-format-attribute -MT audio_fifo_out.lo -MD -MP -MF .deps/audio_fifo_out.Tpo -c -o audio_fifo_out.lo audio_fifo_out.c
The above std setting blocks the "inline" keyword, if I remove it from the gcc line, it builds.
The C89 standard doesn't have inline. You'd get inline with -std=gnu89
though.
Richard.
--
Richard Biener
The C89 standard doesn't have inline. You'd get inline with -std=gnu89 though.
The CUPS headers also seem be incompatible with the new GCC: https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdelibs3/openSUSE... I wonder, should I specify the older C standard in the compiler options or the headers are going to be fixed? [ 400s] In file included from /usr/include/cups/cups.h:34:0, [ 400s] from ./kdeprint/cups/cupsdconf2/cupsdconf.cpp:30, [ 400s] from ./kdeprint/cups/cupsdconf2/libkdeinit_cupsdconf_la_all_cpp.cpp:3: [ 400s] /usr/include/cups/ipp.h:674:16: error: forward declaration of 'ipp_attribute_t {aka struct _ipp_attribute_s}' [ 400s] typedef struct _ipp_attribute_s ipp_attribute_t; [ 400s] ^ [ 400s] In file included from ./kdeprint/cups/cupsdconf2/libkdeinit_cupsdconf_la_all_cpp.cpp:3:0: [ 400s] ./kdeprint/cups/cupsdconf2/cupsdconf.cpp:650:65: error: invalid use of incomplete type 'ipp_attribute_t {aka struct _ipp_attribute_s}' [ 400s] else if (strcmp(attr->name, "printer-type") == 0) type = attr->values[0].integer; [ 400s] ^ [ 400s] In file included from /usr/include/cups/cups.h:34:0, [ 400s] from ./kdeprint/cups/cupsdconf2/cupsdconf.cpp:30, [ 400s] from ./kdeprint/cups/cupsdconf2/libkdeinit_cupsdconf_la_all_cpp.cpp:3: [ 400s] /usr/include/cups/ipp.h:674:16: error: forward declaration of 'ipp_attribute_t {aka struct _ipp_attribute_s}' [ 400s] typedef struct _ipp_attribute_s ipp_attribute_t; [ 400s] ^ [ 400s] In file included from ./kdeprint/cups/cupsdconf2/libkdeinit_cupsdconf_la_all_cpp.cpp:3:0: [ 400s] ./kdeprint/cups/cupsdconf2/cupsdconf.cpp:651:15: error: invalid use of incomplete type 'ipp_attribute_t {aka struct _ipp_attribute_s}' -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2 Mar 2015 20:20, Ilya Chernykh
The C89 standard doesn't have inline. You'd get inline with -std=gnu89 though.
The CUPS headers also seem be incompatible with the new GCC: https: //build.opensuse.org/package/live_build_log/KDE:KDE3/kdelibs3/openSUSE_Factory/i586
I wonder, should I specify the older C standard in the compiler options or the headers are going to be fixed?
[snip] If you look at the last snapshot announcement, you find some remarks about using gnu89 and gnu99 for some programs. GCC 5 defaults to some things that many projects aren't equipped to handle gracefully if at all. Either poor defaults upstream (gcc), or upstream (project) or distro (here openSUSE / SLE) - Yamaban. -- Cx11: it's like y2k all over again. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 02.03.2015 um 20:20 schrieb Ilya Chernykh:
The C89 standard doesn't have inline. You'd get inline with -std=gnu89 though.
The CUPS headers also seem be incompatible with the new GCC: https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdelibs3/openSUSE...
You always talk about "the new GCC" - there was no gcc update in Factory. So what are you talking about? Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 02.03.2015 um 20:20 schrieb Ilya Chernykh:
The C89 standard doesn't have inline. You'd get inline with -std=gnu89 though.
The CUPS headers also seem be incompatible with the new GCC: https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdelibs3/openSUSE...
You always talk about "the new GCC" - there was no gcc update in Factory. So what are you talking about?
Well. Why then xine and cups headers do not compile? Why xine headers require olde C standard specified, if all them was building well under 13.2? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-03-03 at 01:13 +0300, Ilya Chernykh wrote:
Am 02.03.2015 um 20:20 schrieb Ilya Chernykh:
The C89 standard doesn't have inline. You'd get inline with -std=gnu89 though.
The CUPS headers also seem be incompatible with the new GCC: https://build.opensuse.org/package/live_build_log/KDE:KDE3/kdelibs3/openSUSE...
You always talk about "the new GCC" - there was no gcc update in Factory. So what are you talking about?
Well. Why then xine and cups headers do not compile? Why xine headers require olde C standard specified, if all them was building well under 13.2?
Your problem is not that XINE and CUPS do not build on openSUSE
Tumbleweed, but that you're maintaining an old codebase (KDE3) that just
does not know how to deal with modern code (it is KDE that specifies
-std=iso9899:1990 as compiler parameters, while the rest of the world
moved on).
Xine and CUPS both had updates in Factory in the last couple days.
Nothing wrong with any of the two.
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger
Your problem is not that XINE and CUPS do not build on openSUSE Tumbleweed, but that you're maintaining an old codebase (KDE3) that just does not know how to deal with modern code (it is KDE that specifies -std=iso9899:1990 as compiler parameters, while the rest of the world moved on).
Xine and CUPS both had updates in Factory in the last couple days. Nothing wrong with any of the two.
If the problem is with the parameter, I will fix it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Your problem is not that XINE and CUPS do not build on openSUSE Tumbleweed, but that you're maintaining an old codebase (KDE3) that just does not know how to deal with modern code (it is KDE that specifies -std=iso9899:1990 as compiler parameters, while the rest of the world moved on).
Xine and CUPS both had updates in Factory in the last couple days. Nothing wrong with any of the two.
Well, with xine specifying -std=gnu89 works, with cups does not. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Mar 03, 2015 at 08:59:55AM +0300, Ilya Chernykh wrote:
Your problem is not that XINE and CUPS do not build on openSUSE Tumbleweed, but that you're maintaining an old codebase (KDE3) that just does not know how to deal with modern code (it is KDE that specifies -std=iso9899:1990 as compiler parameters, while the rest of the world moved on).
Xine and CUPS both had updates in Factory in the last couple days. Nothing wrong with any of the two.
Well, with xine specifying -std=gnu89 works, with cups does not.
Feel free to point us to the failing package and/or error message to help. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Tatu Hammarén wrote:
I'm considering trying OpeSuse, is (/when it will be) Plasma 5 default(?)-Desktop?
Speaking as part of the community KDE team, on the matter of Plasma 5 as default (as opposed to 4.x), some observations on that regard: - First, we (where "we" means mostly me, Raymond, and Hrvoje) are evaluating P5: it is likely that Plasma 5.3 (out in a couple of months) will possibly be a good candidate. - Secondly, the trend towards "graceful integration" of kdelibs 4.x and KF5 based apps is continuing, so nowadays is mostly no problem to have a mixed setup (it is expected to be like this for at least a year more) - Dates on the 13.2+1 schedule (so we can see how we can handle upstream release cycles), once they are established, would also help with planning. OTOH, to make this a reality even after all the "preflight checks" are in place, requires help from everyone from the community, especially with regards to openQA, which will likely require a good deal of tests redone. Plus some bits from openSUSE may need porting (personally I'm toying with the idea of doing the KDE greeter on first boot using Qt5's QtQuick). I'm hoping to have a more firm plan out at a later point in time. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Dimstar / Dominique Leuenberger -
Freek de Kruijf -
Ilya Chernykh -
Luca Beltrame -
Marcus Meissner -
Richard Biener -
Stephan Kulow -
Tatu Hammarén -
Yamaban