On Jul 8, 2004, at 2:05 PM, Alexander K. Hansen wrote:
Actually, Dave M. put the BuildConflict line deliberately: I had a
similar build problem with libgda-1.0.3-15, and it turned out that I
had to remove openjade to get it to build successfully.
I realize well _ that's why I said to add " --dis
I think the BuildConflicts code isn't really implemented.
On Jul 8, 2004, at 9:22 AM, Dominique Dhumieres wrote:
On Jul 8, 2004, at 8:05 AM, Alex hansen wrote:
Actually, Dave M. put the BuildConflict line deliberately: I had a
similar build problem with libgda-1.0.3-15, and it turned out that I
ha
On Jul 8, 2004, at 8:05 AM, Alex hansen wrote:
> Actually, Dave M. put the BuildConflict line deliberately: I had a
> similar build problem with libgda-1.0.3-15, and it turned out that I
> had to remove openjade to get it to build successfully.
>
> > Reinstall openjade to get your installation
Actually, Dave M. put the BuildConflict line deliberately: I had a
similar build problem with libgda-1.0.3-15, and it turned out that I
had to remove openjade to get it to build successfully.
On Jul 8, 2004, at 6:47 AM, jfm wrote:
Dominique,
Reinstall openjade to get your installation back in a
Dominique,
Reinstall openjade to get your installation back in a kosher
state, then remove the BuildConflict line in libgda.info _
seems anyway not a proper use of it _ , and add
" --disable-gtk-doc" at the end of the ConfigureParams line.
Jean-Francois
Updating libgda-1.0.4-1 failed. I first did through an update-all and I
got:
...
> cd . && \
> gtkdoc-scan --module=libgda --source-dir=../../libgda --ignore-headers="config.h
> acconfig.h gda-intl.h gda-marshal.h" --source-dir=../../report/libgda-report
> touch scan-build.stamp
> *** Rebuild
