[Digikam-devel] Need some help in installation (again :))

[Achim Bohnet]

On Wednesday, 28. March 2007, Vardhman Jain wrote:

Hi, I remember this problem in dapper.  I was never able to figure
out what's going on.  This only happens with svn builds.  Tarballs
were always fine.

The hack I used as to comment out the 3 AC_OUTPUT lines in
utilities/hotplug/Makefile.in


Achim
> On 3/28/07, Gilles Caulier <caulier.gilles at gmail.com> wrote:
> >
> > Are you updated "admin" folder too ? Witch version of automake/autoconf
> > you use ?
> 
> 
> Yes I did update the admin folder. My automake version is 1.8 and autoconf
> is 2.59
> 
> regards,
> Vardhman
> 
> 2007/3/28, Vardhman Jain <vardhman at gmail.com >:
> > >
> > > Hi Gilles
> > >
> > > >
> > > > Ah, you is back. thanks Vardhman. Flicker Export plugin need to be
> > > > updated (:=)))...
> > > >
> > >
> > > Thanks for the welcome, this time I am focussing on Picasa though :)
> > > Well hopefully Flickr Export will get some improvements too. :)
> > >
> > > >
> > > > > I couldn't understand why configure.in gets 3 copies of these lines
> > > > >
> > > > > AC_OUTPUT(digikam/utilities/hotplug/digikam- download.desktop)
> > > > > AC_OUTPUT(digikam/utilities/hotplug/digikam- gphoto2-camera.desktop)
> > > > > AC_OUTPUT(digikam/utilities/hotplug/digikam-
> > > > > mount-and-download.desktop)
> > > > >
> > > > > Could someone suggest me a solution or workaround for this ?
> > > >
> > > >
> > > >
> > > > It's not reproductile here. Are you tried to clean up and re-checkout
> > > > digikam from scratch. There are a lots of changes in digiKam core next
> > > > week...
> > > >
> > >
> > > I have checkout digikam again and again from scratch the error just
> > > seems coming all the time. I have found similar problems faced by others
> > > (via google in some other softwares not digikam specifically) and the
> > > problem was that configure.in file had multiple copies of the AC_OUTPUT
> > > lines. However "make -f Makefile.cvs" will always create a new
> > > configure.in so editing configure.in to remove those lines is not
> > > helpful.
> > >
> > > How does this line get inside configure.in (I mean which file produces
> > > them is something that should help me finding a workaround).
> > >
> > > regards,
> > > Vardhman
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Digikam-devel mailing list
> > > > Digikam-devel at kde.org
> > > > https://mail.kde.org/mailman/listinfo/digikam-devel
> > > >
> > > >
> > >
> > >
> > > --
> > > Blogs: http://vardhman.blogspot.com
> > >
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > Digikam-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> > >
> > >
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > Digikam-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> >
> 
> 
> -- 
> Blogs: http://vardhman.blogspot.com
> 



-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy at lion.austin.ibm.com