trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: [trinity-devel] [SOLVED] Re: [trinity-devel] tqt3 build failure In member function 'virtual int TQODBCResult::numRowsAffected() rror: cannot convert 'SQLINTEGER* {aka int*}' to 'SQLLEN* {aka long int*}

From: Darrell Anderson <humanreadable@...>
Date: Wed, 29 Feb 2012 07:56:10 -0800 (PST)
> arch! But, now I need to successfully package it :)
> 
> make[3]: Entering directory
> `/build/src/tqt3/plugins/src/styles'
> make[3]: Nothing to be done for `install'.
> make[3]: Leaving directory
> `/build/src/tqt3/plugins/src/styles'
> make[2]: Leaving directory `/build/src/tqt3/plugins/src'
> make[1]: Leaving directory `/build/src/tqt3'
> 
> (Build Completed!, Now to package it...)
> 
> ==> Cleaning package...
> sed: can't read /build/pkg/opt/tqt3/lib/*.prl: No such file
> or directory
> 
> Bummer :)

The configure options affect how the package is built. Your build script should define elsewhere where to install with something like this:

make install DESTDIR=$PKG || exit 1

Figure out where $PKG is located and verify files are there. Then your distro (Arch) will have a command that takes those files to build a distributable package. In Slackware that is makepkg, but I don't know the equivalent in Arch.

If the files are not in $PKG then figure out why not.

As you were interested in mimicking your TQt3 build script from your Qt3 build script, look for transposition errors. For example, possibly your build script is performing make install to $TMP/tqt3 but the build script's "makepkg" command is looking in $TMP/qt3.

Darrell