Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
Jon
Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
Jon
My guess would be that the qt4 in EL-5 is just not new enough.
On Wed, 30 Jan 2008 08:43:05 -0600 (CST), Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
ui_branchpropwindow.h: In member function 'void Ui_BranchPropertyWindow::setupUi(QWidget*)': ui_branchpropwindow.h:80: error: 'class QVBoxLayout' has no member named 'setLeftMargin' ui_branchpropwindow.h:81: error: 'class QVBoxLayout' has no member named 'setTopMargin' ui_branchpropwindow.h:82: error: 'class QVBoxLayout' has no member named 'setRightMargin'
Actually, setLeftMargin is not a member of QVBoxLayout. It's not listed as inherited either. It's in Qt 3 QTable (or Qt 4's Q3Table) or QTextBlockFormat). The code wants Qt4 with Qt3 compatibility (-DQT3_SUPPORT). Have you built it locally yet where you can examine the source files generated by Qt's user interface compiler to find out in what context exactly it calls these members?
On Wed, 30 Jan 2008 08:43:05 -0600 (CST), Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
ui_branchpropwindow.h: In member function 'void Ui_BranchPropertyWindow::setupUi(QWidget*)': ui_branchpropwindow.h:80: error: 'class QVBoxLayout' has no member named 'setLeftMargin' ui_branchpropwindow.h:81: error: 'class QVBoxLayout' has no member named 'setTopMargin' ui_branchpropwindow.h:82: error: 'class QVBoxLayout' has no member named 'setRightMargin'
Actually, setLeftMargin is not a member of QVBoxLayout. It's not listed as inherited either. It's in Qt 3 QTable (or Qt 4's Q3Table) or QTextBlockFormat). The code wants Qt4 with Qt3 compatibility (-DQT3_SUPPORT). Have you built it locally yet where you can examine the source files generated by Qt's user interface compiler to find out in what context exactly it calls these members?
Not in pursuit of this issue, no. I'll see what I can find. Do you think adding -DQT3_SUPPORT in the build flags will correct this? I'm a bit of a qt-n00b.
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
On Wed, 30 Jan 2008 08:43:05 -0600 (CST), Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
ui_branchpropwindow.h: In member function 'void Ui_BranchPropertyWindow::setupUi(QWidget*)': ui_branchpropwindow.h:80: error: 'class QVBoxLayout' has no member named 'setLeftMargin' ui_branchpropwindow.h:81: error: 'class QVBoxLayout' has no member named 'setTopMargin' ui_branchpropwindow.h:82: error: 'class QVBoxLayout' has no member named 'setRightMargin'
Actually, setLeftMargin is not a member of QVBoxLayout. It's not listed as inherited either. It's in Qt 3 QTable (or Qt 4's Q3Table) or QTextBlockFormat). The code wants Qt4 with Qt3 compatibility (-DQT3_SUPPORT). Have you built it locally yet where you can examine the source files generated by Qt's user interface compiler to find out in what context exactly it calls these members?
Not in pursuit of this issue, no. I'll see what I can find. Do you think adding -DQT3_SUPPORT in the build flags will correct this? I'm a bit of a qt-n00b.
Weird, a quick grep fails to find setLeftMargin in anything save several .o files. Not sure what to do here.
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
-- novus ordo absurdum
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
On Tue, 5 Feb 2008 12:26:48 -0600 (CST), Jon Ciesla wrote:
On Wed, 30 Jan 2008 08:43:05 -0600 (CST), Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
ui_branchpropwindow.h: In member function 'void Ui_BranchPropertyWindow::setupUi(QWidget*)': ui_branchpropwindow.h:80: error: 'class QVBoxLayout' has no member named 'setLeftMargin' ui_branchpropwindow.h:81: error: 'class QVBoxLayout' has no member named 'setTopMargin' ui_branchpropwindow.h:82: error: 'class QVBoxLayout' has no member named 'setRightMargin'
Actually, setLeftMargin is not a member of QVBoxLayout. It's not listed as inherited either. It's in Qt 3 QTable (or Qt 4's Q3Table) or QTextBlockFormat). The code wants Qt4 with Qt3 compatibility (-DQT3_SUPPORT). Have you built it locally yet where you can examine the source files generated by Qt's user interface compiler to find out in what context exactly it calls these members?
Not in pursuit of this issue, no. I'll see what I can find. Do you think adding -DQT3_SUPPORT in the build flags will correct this? I'm a bit of a qt-n00b.
Weird, a quick grep fails to find setLeftMargin in anything save several .o files. Not sure what to do here.
grep for just "leftMargin" as it is a layout property. It's gone in later Qt 4 versions, and uic replaces it with the setContentsMargin method. As Orion in this thread guessed, it looks much like qt4-devel is not new enough and suffers from a uic code generation bug.
If you like to try a work-around, load the offending *.ui forms into RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
On Tue, 5 Feb 2008 12:26:48 -0600 (CST), Jon Ciesla wrote:
On Wed, 30 Jan 2008 08:43:05 -0600 (CST), Jon Ciesla wrote:
Trying to update vym for EL-5, and it won't build. Any suggestions? Marek and I are stumped:
https://bugzilla.redhat.com/show_bug.cgi?id=429508
I feel like we're missing something obvious.
ui_branchpropwindow.h: In member function 'void Ui_BranchPropertyWindow::setupUi(QWidget*)': ui_branchpropwindow.h:80: error: 'class QVBoxLayout' has no member named 'setLeftMargin' ui_branchpropwindow.h:81: error: 'class QVBoxLayout' has no member named 'setTopMargin' ui_branchpropwindow.h:82: error: 'class QVBoxLayout' has no member named 'setRightMargin'
Actually, setLeftMargin is not a member of QVBoxLayout. It's not
listed
as inherited either. It's in Qt 3 QTable (or Qt 4's Q3Table) or QTextBlockFormat). The code wants Qt4 with Qt3 compatibility (-DQT3_SUPPORT). Have you built it locally yet where you can examine
the
source files generated by Qt's user interface compiler to find out in what context exactly it calls these members?
Not in pursuit of this issue, no. I'll see what I can find. Do you
think
adding -DQT3_SUPPORT in the build flags will correct this? I'm a bit
of a
qt-n00b.
Weird, a quick grep fails to find setLeftMargin in anything save several .o files. Not sure what to do here.
grep for just "leftMargin" as it is a layout property. It's gone in later Qt 4 versions, and uic replaces it with the setContentsMargin method. As Orion in this thread guessed, it looks much like qt4-devel is not new enough and suffers from a uic code generation bug.
If you like to try a work-around, load the offending *.ui forms into RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
I don't have a copy of RHEL. :)
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
On Tue, 5 Feb 2008 14:36:37 -0600 (CST), Jon Ciesla wrote:
If you like to try a work-around, load the offending *.ui forms into RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
I don't have a copy of RHEL. :)
Then use CentOS 5.1. You cannot maintain a package in EPEL if you don't use at least CentOS.
On Tue, 5 Feb 2008 14:36:37 -0600 (CST), Jon Ciesla wrote:
If you like to try a work-around, load the offending *.ui forms into RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
I don't have a copy of RHEL. :)
Then use CentOS 5.1. You cannot maintain a package in EPEL if you don't use at least CentOS.
I don't have a machine to spare for CentOS, nor one running anything else with enough juice for virtualization. I support some of my packages for EPEL because I've had requests, or because I think they will be useful there. If someone would be willing to contribute a shell account on a CentOS machine, I'd be more than happy to test there (as well as grateful).
Or, if someone has some old hardware they don't want and are in NE Illinois, USA. . .:)
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
On Feb 5, 2008 1:52 PM, Jon Ciesla limb@jcomserv.net wrote:
On Tue, 5 Feb 2008 14:36:37 -0600 (CST), Jon Ciesla wrote:
If you like to try a work-around, load the offending *.ui forms into RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
I don't have a copy of RHEL. :)
Then use CentOS 5.1. You cannot maintain a package in EPEL if you don't use at least CentOS.
I don't have a machine to spare for CentOS, nor one running anything else with enough juice for virtualization. I support some of my packages for EPEL because I've had requests, or because I think they will be useful there. If someone would be willing to contribute a shell account on a CentOS machine, I'd be more than happy to test there (as well as grateful).
Or, if someone has some old hardware they don't want and are in NE Illinois, USA. . .:)
No hardware.. let me see what I can set up here though in the meantime... will know by Friday.
On Feb 5, 2008 1:52 PM, Jon Ciesla limb@jcomserv.net wrote:
On Tue, 5 Feb 2008 14:36:37 -0600 (CST), Jon Ciesla wrote:
If you like to try a work-around, load the offending *.ui forms
into
RHEL5's designer4, save them, diff against the pristine vym-1.10.0 to create a patch, and then build the patched vym.
I don't have a copy of RHEL. :)
Then use CentOS 5.1. You cannot maintain a package in EPEL if you
don't
use at least CentOS.
I don't have a machine to spare for CentOS, nor one running anything else with enough juice for virtualization. I support some of my packages for EPEL because I've had requests, or because I think they will be useful there. If someone would be willing to contribute a shell account on a CentOS machine, I'd be more than happy to test there (as well as grateful).
Or, if someone has some old hardware they don't want and are in NE Illinois, USA. . .:)
No hardware.. let me see what I can set up here though in the meantime... will know by Friday.
Thanks. :)
-- Stephen J Smoogen. -- CSIRT/Linux System Administrator How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice"
epel-devel@lists.fedoraproject.org
-
Jon Ciesla -
Michael Schwendt -
Orion Poplawski -
Stephen John Smoogen