16 Sep
2011
16 Sep
'11
8:34 p.m.
Hello, I'm trying to build kdelibs 3.5.12 on RHEL 5 (which is getting a
bit old, but still supported by RH, and widely used in companies).
When compiling krandr, it fails with the following output:
make[2]: entrant dans le répertoire «
/home/albator/rpmbuild/BUILD/kdelibs/krandr »
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I.. -I../dcop -I../kdecore -I../kio/kssl -I../kjs -I./.. -I../dcop
-I../libltdl -I../kdefx -I../kdecore -I../kdecore -I../kdecore/network
-I../kdeui -I../kio -I../kio/kio -I../kio/kfile -I..
-I/usr/lib64/qt-3.3/include -include tqt.h -I. -I/opt/trinity/include
-I/opt/trinity/include/tqt -DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG
-O2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o
lowlevel_randr.lo lowlevel_randr.c
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../kdecore -I../kio/kssl
-I../kjs -I./.. -I../dcop -I../libltdl -I../kdefx -I../kdecore
-I../kdecore -I../kdecore/network -I../kdeui -I../kio -I../kio/kio
-I../kio/kfile -I.. -I/usr/lib64/qt-3.3/include -include tqt.h -I.
-I/opt/trinity/include -I/opt/trinity/include/tqt -DQT_THREAD_SUPPORT
-D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64
-mtune=generic -c lowlevel_randr.c -fPIC -DPIC -o .libs/lowlevel_randr.o
In file included from lowlevel_randr.c:23:
lowlevel_randr.h:102:7: warning: no newline at end of file
In file included from lowlevel_randr.c:24:
lowlevel_randr.h:29: error: expected specifier-qualifier-list before
'RRCrtc'
lowlevel_randr.h:44: error: expected specifier-qualifier-list before
'RROutput'
lowlevel_randr.h:55: error: expected specifier-qualifier-list before
'XRRScreenResources'
lowlevel_randr.h:90: error: expected '=', ',', ';', 'asm'
or
'__attribute__' before '*' token
lowlevel_randr.h:91: error: expected ')' before '*' token
lowlevel_randr.h:92: error: expected ')' before '*' token
lowlevel_randr.h:93: error: expected declaration specifiers or '...'
before 'RROutput'
[...]
and so on ... (the full log is attached to this mail)
It seems that RHEL5 Xrandr version (1.1.1) is too old for krandr.
I have no idea of what is the most reasonable way to go:
Should I try to compile a newer version of Xrandr ? Is that even
possible without compiling a lot of other stuff ?
Should I disable krandr in kdelibs makefile ? What will be the
consequences on further compiled packages ?
Should I revert all krandr-related patches to recover older KDE3
functionalities ?
Thanks in advance for your enlightenment :-)
Francois Andriot
18 Sep
18 Sep
8 p.m.
New subject: [trinity-devel] kdelibs: krandr and older xrandr version
Le Fri, 16 Sep 2011 22:34:12 +0200,
François ANDRIOT <francois.andriot(a)free.fr> a écrit :
Hello, I'm trying to build kdelibs 3.5.12 on RHEL
5 (which is getting
a bit old, but still supported by RH, and widely used in companies).
When compiling krandr, it fails with the following output:
make[2]: entrant dans le répertoire «
/home/albator/rpmbuild/BUILD/kdelibs/krandr »
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I. -I.. -I../dcop -I../kdecore -I../kio/kssl -I../kjs -I./..
-I../dcop -I../libltdl -I../kdefx -I../kdecore -I../kdecore
-I../kdecore/network -I../kdeui -I../kio -I../kio/kio -I../kio/kfile
-I.. -I/usr/lib64/qt-3.3/include -include tqt.h -I.
-I/opt/trinity/include -I/opt/trinity/include/tqt
-DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -c -o lowlevel_randr.lo
lowlevel_randr.c gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop
-I../kdecore -I../kio/kssl -I../kjs -I./.. -I../dcop -I../libltdl
-I../kdefx -I../kdecore -I../kdecore -I../kdecore/network -I../kdeui
-I../kio -I../kio/kio -I../kio/kfile -I.. -I/usr/lib64/qt-3.3/include
-include tqt.h -I. -I/opt/trinity/include -I/opt/trinity/include/tqt
-DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -c lowlevel_randr.c
-fPIC -DPIC -o .libs/lowlevel_randr.o In file included from
lowlevel_randr.c:23: lowlevel_randr.h:102:7: warning: no newline at
end of file In file included from lowlevel_randr.c:24:
lowlevel_randr.h:29: error: expected specifier-qualifier-list before
'RRCrtc'
lowlevel_randr.h:44: error: expected specifier-qualifier-list before
'RROutput'
lowlevel_randr.h:55: error: expected specifier-qualifier-list before
'XRRScreenResources'
lowlevel_randr.h:90: error: expected '=', ',', ';', 'asm'
or
'__attribute__' before '*' token
lowlevel_randr.h:91: error: expected ')' before '*' token
lowlevel_randr.h:92: error: expected ')' before '*' token
lowlevel_randr.h:93: error: expected declaration specifiers or '...'
before 'RROutput'
[...]
and so on ... (the full log is attached to this mail)
It seems that RHEL5 Xrandr version (1.1.1) is too old for krandr.
XRandR 1.1.1
doesn't support multiple monitors, which is the cause for
the failed compilation of lowlevel_randr.{h,c} which uses multi-monitor
support from XRandR 1.2+.
I have no idea of what is the most reasonable way to
go:
Should I try to compile a newer version of Xrandr ? Is that even
possible without compiling a lot of other stuff ?
XRandR is a protocol extension of
the X11 protocol, so using XRandR 1.2
would require to update the X server (and also, according to Phoronix
the NVIDIA drivers just don't support XrandR 1.2 as of July 2011).
Did anyone try to use the new Trinity XRandR functionality with the
proprietary NVIDIA drivers ?
Should I disable krandr in kdelibs makefile ? What
will be the
consequences on further compiled packages ?
You will probably have some problems to
compile KRandRTray :)
Should I revert all krandr-related patches to recover
older KDE3
functionalities ?
This is perhaps the simplest way to build a working Trinity on
RHEL5,
but the problem is the resulting kdelibs you will get will be
incompatible with standard Trinity kdelibs.
IMHO the right thing to do would be to enable conditional
compilation of XRandR 1.2+ multi-monitor capabilities and to support
it with kconfig.h.
Thanks in advance for your enlightenment :-)
Francois Andriot
9:06 p.m.
New subject: [trinity-devel] kdelibs: krandr and older xrandr version
Le 18/09/2011 22:00, /dev/ammo42 a écrit :
Thanks for your reply,
I've finally managed to compile kdelibs without krandr support, then
kdebase by disabling 'krandrtray' and 'iccconfig', both of which seemed
to require 'krandr' . I did not have to revert Trinity patches.
The resulting TDE 3.5.12 desktop on RHEL5 seems to be running fine so
far (I've not compiled the further packages yet - but I'll be doing it
very soon)
Francois Andriot
Should I disable krandr in kdelibs makefile ?
What will be the
consequences on further compiled packages ?
You will probably have some problems
to compile KRandRTray :)
Should I revert all krandr-related patches to
recover older KDE3
functionalities ?
This is perhaps the simplest way to build a working Trinity on
RHEL5,
but the problem is the resulting kdelibs you will get will be
incompatible with standard Trinity kdelibs.
IMHO the right thing to do would be to enable conditional
compilation of XRandR 1.2+ multi-monitor capabilities and to support
it with kconfig.h. 
19 Sep
19 Sep
6:56 a.m.
New subject: [trinity-devel] kdelibs: krandr and older xrandr version
I don't know if it helps, but I'm using Trinity 3.5.12 on Debian
Squeeze with the NVIDIA proprietary drivers. I don't have multiple
monitors, but randr seems to work fine. I can resize from the tray
icon anyway.
On Sun, Sep 18, 2011 at 3:00 PM, /dev/ammo42 <mickeytintincolle(a)yahoo.fr> wrote:
Le Fri, 16 Sep 2011 22:34:12 +0200,
François ANDRIOT <francois.andriot(a)free.fr> a écrit :
Hello, I'm trying to build kdelibs 3.5.12 on
RHEL 5 (which is getting
a bit old, but still supported by RH, and widely used in companies).
When compiling krandr, it fails with the following output:
make[2]: entrant dans le répertoire «
/home/albator/rpmbuild/BUILD/kdelibs/krandr »
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I. -I.. -I../dcop -I../kdecore -I../kio/kssl -I../kjs -I./..
-I../dcop -I../libltdl -I../kdefx -I../kdecore -I../kdecore
-I../kdecore/network -I../kdeui -I../kio -I../kio/kio -I../kio/kfile
-I.. -I/usr/lib64/qt-3.3/include -include tqt.h -I.
-I/opt/trinity/include -I/opt/trinity/include/tqt
-DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -c -o lowlevel_randr.lo
lowlevel_randr.c gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop
-I../kdecore -I../kio/kssl -I../kjs -I./.. -I../dcop -I../libltdl
-I../kdefx -I../kdecore -I../kdecore -I../kdecore/network -I../kdeui
-I../kio -I../kio/kio -I../kio/kfile -I.. -I/usr/lib64/qt-3.3/include
-include tqt.h -I. -I/opt/trinity/include -I/opt/trinity/include/tqt
-DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -O2 -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -c lowlevel_randr.c
-fPIC -DPIC -o .libs/lowlevel_randr.o In file included from
lowlevel_randr.c:23: lowlevel_randr.h:102:7: warning: no newline at
end of file In file included from lowlevel_randr.c:24:
lowlevel_randr.h:29: error: expected specifier-qualifier-list before
'RRCrtc'
lowlevel_randr.h:44: error: expected specifier-qualifier-list before
'RROutput'
lowlevel_randr.h:55: error: expected specifier-qualifier-list before
'XRRScreenResources'
lowlevel_randr.h:90: error: expected '=', ',', ';', 'asm'
or
'__attribute__' before '*' token
lowlevel_randr.h:91: error: expected ')' before '*' token
lowlevel_randr.h:92: error: expected ')' before '*' token
lowlevel_randr.h:93: error: expected declaration specifiers or '...'
before 'RROutput'
[...]
and so on ... (the full log is attached to this mail)
It seems that RHEL5 Xrandr version (1.1.1) is too old for krandr.
XRandR 1.1.1
doesn't support multiple monitors, which is the cause for
the failed compilation of lowlevel_randr.{h,c} which uses multi-monitor
support from XRandR 1.2+.
I have no idea of what is the most reasonable way
to go:
Should I try to compile a newer version of Xrandr ? Is that even
possible without compiling a lot of other stuff ?
XRandR is a protocol extension
of the X11 protocol, so using XRandR 1.2
would require to update the X server (and also, according to Phoronix
the NVIDIA drivers just don't support XrandR 1.2 as of July 2011).
Did anyone try to use the new Trinity XRandR functionality with the
proprietary NVIDIA drivers ?
Should I disable krandr in kdelibs makefile ?
What will be the
consequences on further compiled packages ?
You will probably have some problems
to compile KRandRTray :)
Should I revert all krandr-related patches to
recover older KDE3
functionalities ?
This is perhaps the simplest way to build a working Trinity on
RHEL5,
but the problem is the resulting kdelibs you will get will be
incompatible with standard Trinity kdelibs.
IMHO the right thing to do would be to enable conditional
compilation of XRandR 1.2+ multi-monitor capabilities and to support
it with kconfig.h.
Thanks in advance for your enlightenment :-)
Francois Andriot
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
7:04 a.m.
New subject: [trinity-devel] kdelibs: krandr and older xrandr version
I don't know if it helps, but I'm using
Trinity 3.5.12 on Debian
Squeeze with the NVIDIA proprietary drivers. I don't have multiple
monitors, but randr seems to work fine. I can resize from the tray
icon anyway.
Using nVidia here as well. In fact, my primary development machines use
nVidia cards. :-)
While nVidia does not have XRandr 1.3+ support (and therefore cannot
handle multiple monitors, etc.) this does not break Trinity. The
appropriate configuration options only become available if the underlying
hardware supports them.
If you really want multiple monitors via XRandr with nVidia cards, try the
nouveau drivers. Be aware that they do not support 3D well at all at this
time however.
Tim
7:06 a.m.
New subject: [trinity-devel] kdelibs: krandr and older xrandr version
I don't
know if it helps, but I'm using Trinity 3.5.12 on Debian
Squeeze with the NVIDIA proprietary drivers. I don't have multiple
monitors, but randr seems to work fine. I can resize from the tray
icon anyway.
Using nVidia here as well. In fact, my primary development machines use
nVidia cards. :-)
While nVidia does not have XRandr 1.3+ support (and therefore cannot
handle multiple monitors, etc.) this does not break Trinity. The
appropriate configuration options only become available if the underlying
hardware supports them.
If you really want multiple monitors via XRandr with nVidia cards, try the
nouveau drivers. Be aware that they do not support 3D well at all at this
time however.
Tim
4845
days inactive
4848
days old
5 comments
5 participants
participants (5)
-
/dev/ammo42 -
Christopher J Kleinschmidt -
Francois Andriot -
François ANDRIOT
-
Timothy Pearson