On Thursday 13 March 2003 09:13, Paul Seelig wrote:
>
> Just to release everone's suspense about my proceedings: Thanks to
> your support everything finally compiled just fine!
Good to hear that. :-)
--
José Abílio
[EMAIL PROTECTED] (Paul Seelig) writes:
> Now everything's currently compiling and i have to wait for the
> results. I'll see tonight when i'm coming home again whether
> everything went right.
>
Just to release everone's suspense about my proceedings: Thanks to
your support everything finally com
On Tue, Mar 11, 2003 at 10:48:17AM +, Jos? Matos wrote:
> AFAIR you need autoconf 2.5x to build the qt frontend. I think that the same
> applies to any qt 3.x application.
Nope ... (autoconf has nothing to do particularly with Qt, so ...).
You do need automake 1.5 or higher though
john
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
> Paul Seelig <[EMAIL PROTECTED]> writes:
>
>
> | [ after doing a CVS update: ]
>
> Are you sure you are really up to date?
>
I updated it right before producing the script session.
But i've acted on both Angus' and José's comments, created a .
On Tuesday 11 March 2003 10:37, Paul Seelig wrote:
> Is this a Debian/unstable problem, is it me, or any one of you or,
> speaking with the Monthy Pythons, something completely different?
>
> I haven't been able compiling CVS since some time around release of
> 1.3.0 (which compiled fine).
>
> [ af
Paul Seelig wrote:
> Is this a Debian/unstable problem, is it me, or any one of you or,
> speaking with the Monthy Pythons, something completely different?
>
> I haven't been able compiling CVS since some time around release of
> 1.3.0 (which compiled fine).
You have to tell cvs to Prune old dir
Paul Seelig <[EMAIL PROTECTED]> writes:
| Is this a Debian/unstable problem, is it me, or any one of you or,
| speaking with the Monthy Pythons, something completely different?
|
| I haven't been able compiling CVS since some time around release of
| 1.3.0 (which compiled fine).
| [ after doing
