20 Apr
2012
20 Apr
'12
8:50 p.m.
I'm missing something obvious, but I can't get these packages to build on 64-bit.
They can't find $PREFIX/lib64.
I appreciate help.
Darrell
20 Apr
20 Apr
9:01 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
On 04/20/2012 03:50 PM, Darrell Anderson wrote:
I'm missing something obvious, but I can't get
these packages to build on 64-bit. They can't find $PREFIX/lib64.
I appreciate help.
Darrell
---------------------------------------------------------------------
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 messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I'm building python-tqt as follows:
[ "$QTDIR" = "" ] && . /etc/profile.d/tqt3.sh
[ "$TDEDIR" = "" ] && . /etc/profile.d/trinity.sh
cd ${srcdir}/${pkgname#*-}
echo yes | python2 configure.py \
CFLAGS="${CFLAGS} -I/usr/include/tqt -I${TDEDIR}/include -I${QTDIR}/include
-fpermissive" \
CXXFLAGS="${CXXFLAGS} -I/usr/include/tqt -I${TDEDIR}/include
-I${QTDIR}/include -fpermissive"
sed -i '/#define _qtAPI_H/s|$|\n#define SIP_MODULE_NAME "sip"|'
${srcdir}/python-tqt/qt/sipAPIqt.h
make VERBOSE=1
I think your probably missing the sed statement. I had forgotten about it until
your post. It will need to be evaluated for pushing.
--
David C. Rankin, J.D.,P.E.
9:50 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
I'm building python-tqt as follows:
[ "$QTDIR" = "" ] && .
/etc/profile.d/tqt3.sh
[ "$TDEDIR" = "" ] && .
/etc/profile.d/trinity.sh
cd ${srcdir}/${pkgname#*-}
echo yes | python2 configure.py \
CFLAGS="${CFLAGS} -I/usr/include/tqt
-I${TDEDIR}/include -I${QTDIR}/include
-fpermissive" \
CXXFLAGS="${CXXFLAGS} -I/usr/include/tqt
-I${TDEDIR}/include
-I${QTDIR}/include -fpermissive"
sed -i '/#define _qtAPI_H/s|$|\n#define SIP_MODULE_NAME "sip"|'
${srcdir}/python-tqt/qt/sipAPIqt.h
make VERBOSE=1
I think your probably missing the sed statement. I had
forgotten about it until your post. It will need to be evaluated for pushing.
Thanks. The sed string confuses me. There is no such file in the directory, nor any such
text string. I can't find anything in the source tree resembling what is in that sed
statement.
Darrell
10:25 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
On 04/20/2012 04:50 PM, Darrell Anderson wrote:
Thanks. The sed string confuses me. There is no such
file in the directory, nor any such text string. I can't find anything in the source
tree resembling what is in that sed statement.
Darrell
Oops forgot to tell you I was running the sed (post-configure) on the generated
sipAPIqt.h.... :)
--
David C. Rankin, J.D.,P.E.
10:33 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
I'm not getting that far. The build fails immediately at the beginning:
Error: No TQt libraries could be found in /opt/trinity/lib.
make: *** No targets specified and no makefile found. Stop.
Darrell
--- On Fri, 4/20/12, David C. Rankin <drankinatty(a)suddenlinkmail.com> wrote:
From: David C. Rankin
<drankinatty(a)suddenlinkmail.com>
Subject: Re: [trinity-devel] python-tqt, python-trinity on 64-bit
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Friday, April 20, 2012, 5:25 PM
On 04/20/2012 04:50 PM, Darrell
Anderson wrote:
Thanks. The sed string confuses me. There is no
such
file in the directory, nor any such text string. I can't
find anything in the source tree resembling what is in that
sed statement.
Darrell
Oops forgot to tell you I was running the sed
(post-configure) on the generated
sipAPIqt.h.... :)
--
David C. Rankin, J.D.,P.E.
---------------------------------------------------------------------
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 messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:49 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
On 04/20/2012 05:33 PM, Darrell Anderson wrote:
I'm not getting that far. The build fails
immediately at the beginning:
Error: No TQt libraries could be found in /opt/trinity/lib.
make: *** No targets specified and no makefile found. Stop.
Darrell
cd ${srcdir}/${pkgname#*-}
echo yes | python2 configure.py \
CFLAGS="${CFLAGS} -I/usr/include/tqt -I${TDEDIR}/include -I${QTDIR}/include
-fpermissive" \
CXXFLAGS="${CXXFLAGS} -I/usr/include/tqt -I${TDEDIR}/include
-I${QTDIR}/include -fpermissive"
# patch SIP_MODULE_NAME (build faile 4/5/12) in sipAPIqt.h
# locate #define _qtAPI_H, then add
#define SIP_MODULE_NAME "sip"
msg "Patching (post-configure) sipAPIqt.h...."
sed -i '/#define _qtAPI_H/s|$|\n#define SIP_MODULE_NAME "sip"|'
${srcdir}/${pkgname#*-}/qt/sipAPIqt.h
are you giving the full python2 configure:
echo yes | python2 configure.py \
CFLAGS="${CFLAGS}.... \
CXXFLAGS="${CXXFLAGS}....
that's all I'm doing.
http://www.3111skyline.com/dl/dt/tde/src/tde-python-tqt.tar.gz
--
David C. Rankin, J.D.,P.E.
11:15 p.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
I'm not
getting that far. The build fails immediately
at the beginning:
Error: No TQt libraries could be found in /opt/trinity/lib.
make: *** No targets specified and no makefile found. Stop.
21 Apr
21 Apr
12:36 a.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
On 04/20/2012 06:15 PM, Darrell Anderson wrote:
The build does not get out of the gate. The build
can't find the TQt libraries, which with 64-bit are not stored in /opt/trinity/lib but
/opt/trinity/lib64.
Darrell
Well, how did they get there?? All mine get put in 'lib'. Why not just soft-link
them for the time being??
pmql tde-tqt3 | grep lib
tde-tqt3 /opt/tqt3/lib/
tde-tqt3 /opt/tqt3/lib/libdesignercore.a
tde-tqt3 /opt/tqt3/lib/libdesignercore.prl
tde-tqt3 /opt/tqt3/lib/libeditor.a
tde-tqt3 /opt/tqt3/lib/libeditor.prl
tde-tqt3 /opt/tqt3/lib/libqassistantclient.a
tde-tqt3 /opt/tqt3/lib/libqassistantclient.prl
tde-tqt3 /opt/tqt3/lib/libtqt-mt.la
tde-tqt3 /opt/tqt3/lib/libtqt-mt.prl
tde-tqt3 /opt/tqt3/lib/libtqt-mt.so
tde-tqt3 /opt/tqt3/lib/libtqt-mt.so.3
tde-tqt3 /opt/tqt3/lib/libtqt-mt.so.3.3
tde-tqt3 /opt/tqt3/lib/libtqt-mt.so.3.3.8
tde-tqt3 /opt/tqt3/lib/libtqui.prl
tde-tqt3 /opt/tqt3/lib/libtqui.so
tde-tqt3 /opt/tqt3/lib/libtqui.so.1
tde-tqt3 /opt/tqt3/lib/libtqui.so.1.0
tde-tqt3 /opt/tqt3/lib/libtqui.so.1.0.0
tde-tqt3 /opt/tqt3/lib/pkgconfig/
tde-tqt3 /opt/tqt3/lib/pkgconfig/tqt-mt.pc
tde-tqt3 /opt/tqt3/plugins/designer/libcppeditor.so
tde-tqt3 /opt/tqt3/plugins/designer/libdlgplugin.so
tde-tqt3 /opt/tqt3/plugins/designer/libgladeplugin.so
tde-tqt3 /opt/tqt3/plugins/designer/libkdevdlgplugin.so
tde-tqt3 /opt/tqt3/plugins/designer/librcplugin.so
tde-tqt3 /opt/tqt3/plugins/designer/libwizards.so
tde-tqt3 /opt/tqt3/plugins/imageformats/libqjpeg.so
tde-tqt3 /opt/tqt3/plugins/imageformats/libqmng.so
tde-tqt3 /opt/tqt3/plugins/imageformats/libqpng.so
tde-tqt3 /opt/tqt3/plugins/inputmethods/libqimsw-multi.so
tde-tqt3 /opt/tqt3/plugins/inputmethods/libqimsw-none.so
tde-tqt3 /opt/tqt3/plugins/inputmethods/libqsimple.so
tde-tqt3 /opt/tqt3/plugins/inputmethods/libqxim.so
tde-tqt3 /opt/tqt3/plugins/sqldrivers/libqsqlite.so
tde-tqt3 /opt/tqt3/plugins/sqldrivers/libqsqlmysql.so
tde-tqt3 /opt/tqt3/plugins/sqldrivers/libqsqlodbc.so
tde-tqt3 /opt/tqt3/plugins/sqldrivers/libqsqlpsql.so
--
David C. Rankin, J.D.,P.E.
1:25 a.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
Well, how did they get there?? All mine get put in
'lib'.
Why not just soft-link them for the time being??
Because lib64 is where the lib files belong. That is how things are done on 64-bit.
Sym linking doesn't work and is an incorrect way of resolving the problem anyway.
Darrell
2:40 a.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
On 04/20/2012 08:25 PM, Darrell Anderson wrote:
Because lib64 is where the lib files belong. That is
how things are done on 64-bit.
Sym linking doesn't work and is an incorrect way of resolving the problem anyway.
Darrell
Nope... 64 bit libs go just fine in 'lib', it's just a matter of choice.
Unless
you are building both 64-bit apps and 32-bit apps in the same install - it
doesn't matter where they go as long as they can be found. On arch, all 64-bit
libs go in 'libs' and my stuff builds fine. On opensuse 64-bit libs go in lib64,
things build just fine there as well. So it's just a matter of choice, but it
has to be a consistent choice.
If you patched your tde build to put things in lib64 -- that's probably the
source of your issue. There is part of tde or tqt that doesn't know to look in
lib64. Just unpatch any of your tde files that you changed, and leave the libs
in lib and I'll bet your 64bit builds work fine.
I don't know where the flag is that controls where the build looks for libs, but
I think you hit it, and I don't know how to tell a python configure to search
for --with-extra-libs '/xyz', so I don't mess with it :)
--
David C. Rankin, J.D.,P.E.
2:46 a.m.
New subject: [trinity-devel] python-tqt, python-trinity on 64-bit
Nope... 64 bit libs go just fine in 'lib',
it's just a
matter of choice. Unless
you are building both 64-bit apps and 32-bit apps in the
same install - it
doesn't matter where they go as long as they can be found.
On arch, all 64-bit
libs go in 'libs' and my stuff builds fine. On opensuse
64-bit libs go in lib64,
things build just fine there as well. So it's just a matter
of choice, but it
has to be a consistent choice.
If you patched your tde build to put things in lib64 --
that's probably the
source of your issue. There is part of tde or tqt that
doesn't know to look in
lib64. Just unpatch any of your tde files that you changed,
and leave the libs
in lib and I'll bet your 64bit builds work fine.
I don't know where the flag is that controls where the build
looks for libs, but
I think you hit it, and I don't know how to tell a python
configure to search
for --with-extra-libs '/xyz', so I don't mess with it :)
Many Slackware users use multi-lib on their 64 bit systems, which means keeping lib and
lib64 separated. Upstream has adopted that directory structure. I need to support that
structure.
I don't know how to control the python packages either. The tqca and tqca-tls packages
have the same problem.
Otherwise I am building everything else with no problems regarding the lib64 location.
I wish fixing this stuff was straightforward. I get tired of filing bug reports.
Darrell
4399
days inactive
4400
days old
10 comments
2 participants
participants (2)
-
Darrell Anderson -
David C. Rankin