I haven't seen that error (I'm using ubuntu maverik).
The only difference is that I'm using a separate build directory. I
usually do something like this:
$ cd hugin.hg
$ mkdir build_release
$ cd build_release
$ cmake ..
$ make
ciao
Pablo
--
You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Ok, obviously my version of ubuntu (9.10) is causing me problems. I'm going to upgrade to 10.10.
But wait - 32 bit or 64 bit? I have 2x cpu's and 8GB ram.
Hi Jeffrey
Am 28.01.2011 15:53, schrieb Jeffrey Martin:
>
> I get these errors.
>
> Err http://ppa.launchpad.net karmic/main Packages
> 404 Not Found
> Fetched 20.9kB in 0s (26.9kB/s)
> W: Failed to fetch
> http://ppa.launchpad.net/hugin/nightly/ubuntu/dists/karmic/main/binary-amd64/Packages.gz
> 404 Not Found
>
>
> is there any point in continuing?
These error messages are caused by the fact that you tried to use the
nightly builds from the hugin builders ppa. This would have resultet in
binary packages being installed, so you would have been able to use a
recent huging build without having to build it yourself.
However, there are no such builds for karmic. Therefore, I advise you to
remove the hugin/nightly entries from your sources.
As there is AFAIK no command line tool for removing apt entries, yoi
will euther have to do that in the GUI (System -> Administration ->
Software Sources) or by manually editing /etc/apt/sources.list.
However, this has nothing to do with the compiling. In other words, this
error message has no relation to the problems you face trying to compile
your own, actual hugin version.
Regards
Stefan
- --
In theory there is no difference between theory and practice. In
practice there is.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNQtwcAAoJEBgqi52L7+L/Th4H/0orrC2zv2P41xFdP1J2UJQD
mQZsOgcRCiicZHa1qndvX8RqnOYgnNO2SZhtHEyI68QIg1utrxeNvzINm0ujZy5H
vep6cwYrWe9n80kXuHGlLTVLSLNUW9+B2r7ZSlqPbbWBEgzfO/RVKWVwsJRmqs6A
f2FPM0KvvQXRl8U5pUGqZ/g4GQ0dq4ie0liRm1Z9zlVR2lComX4i083mUJL7u4ER
zPGUCXDbnQB/KILAzGoiKajtaMSz9qV+Th/yoGcRG/ISZE1wHDXgGnufMfY8ibEx
hy/cEM/QW39pu5VJs1t4tnyPXoXICRf8kqLx0ZvNpRJYVfMkMGWU0N2JF+1NR5w=
=QWpb
-----END PGP SIGNATURE-----
Am Freitag, 28. Januar 2011 schrieb Jeffrey Martin:
> Ok, obviously my version of ubuntu (9.10) is causing me problems. I'm going
> to upgrade to 10.10.
If you upgrade than consider that on 10.10 the cmake is erroneous.
(try somehow to downgrade cmake from 2.8.2 to version 2.8.0.)
> But wait - 32 bit or 64 bit? I have 2x cpu's and 8GB ram.
This depends on your cpu obviously. Try to master own compile ...
Kornel
I had the same error with flann_cpp (I'm also building in a separate
subdirectory). No cache files to be deleted. I had given up and checked out
the stable 2010.4 branch which built fine.
So now I started looking at it again, and found during the configure process
the following:
CMake Error: CMake can not determine linker language for target:flann_cpp
CMake Error: Cannot determine link language for target "flann_cpp".
which seems to be the reason for the missing make rule. Maybe some cmake-Guru
knows how to proceed there.
My system is a 64-bit Opensuse 11.2
Cheers,
Pit
> --
> You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugi...@googlegroups.com
> To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
--
Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit
Institute for Solar Physics
Tel.: +34 922 405 590 (Spain) P.Suet...@royac.iac.es
+46 8 5537 8507 (Sweden) Peter.Su...@astro.su.se
I had the same error with flann_cpp (I'm also building in a separate
subdirectory). No cache files to be deleted. I had given up and checked out
the stable 2010.4 branch which built fine.
My system is a 32-bit Uhu-Linux 2.1. The hugin is 2011.0.0 beta 2.
Any idea?
Lajos
see the 'Hugin-2011.0_beta2 released' thread - you'll have to upgrade cmake.
Pit
Creating debian package with "make package" will create a deb file which includes a tar file.
This tar file normally includes directories and regular files.
But cpack from the 2.8.2 version of cmake creates only the regular files.
That is, installing with dpkg is ok if the destination directories are already there.
The target directory creation is missing.
> Kay
>
Kornel
...is just more broken than in previous and latest version. AFAIK it has
always been "broken" in that the Debian packages build with CMake/CPack don't
pass basic Debian tests / policies. Google for a thread in this list where
Andreas Metzler gives the details.
Using the combination of
make package && sudo dpkg -i <NAME_OF_THE_GENERATED PACKAGE>
is barely better than using
make && sudo make install
If you are serious about building debian packages use dpkg-buildpackage
Some instructions (geared at producing a package for a PPA on Launchpad) are
at [0].
Theoretically it would be possible to follow the above instructions and build
binary snapshot of any version of Hugin including development branches; and
distribute them from a Launchpad PPA (any Launchpad member can have their own
PPA), but so far nobody has gone there yet.
Yuv
Am Dienstag, 1. März 2011 schrieb Yuval Levy:
> On March 1, 2011 04:40:09 am Kornel Benko wrote:
> > Am Dienstag, 1. März 2011 schrieb kfj:
> > > On 28 Jan., 17:45, Kornel Benko <Kornel.Be...@berlin.de> wrote:
> > > > If you upgrade than consider that on 10.10 the cmake is erroneous.
> > > > (try somehow to downgrade cmake from 2.8.2 to version 2.8.0.)
> > >
> > > In what way erroneous? I've been using cmake 2.8.2 on my Kubuntu 10.10
> > > system for months and it has always done precisely what it's supposed
> > > to do.
> >
> > Creating debian package with "make package" ...
>
> ...is just more broken than in previous and latest version. AFAIK it has
> always been "broken" in that the Debian packages build with CMake/CPack
> don't pass basic Debian tests / policies. Google for a thread in this
> list where Andreas Metzler gives the details.
It is. But still I am using this build-process without problems. (Until now I was using the 2.8.0 version, but since some days I use the 2.8.4 version on ubuntu 10.10)
(Got it from "ftp://ftp.debian.org/debian/pool/main/c/cmake/"
cmake_2.8.4-2_amd64.deb
cmake-data_2.8.4-2_all.deb
cmake-qt-gui_2.8.4-2_amd64.deb
)
> Using the combination of
> make package && sudo dpkg -i <NAME_OF_THE_GENERATED PACKAGE>
> is barely better than using
> make && sudo make install
Naturally I don't follow you here. Installing through package makes it easy to deinstall also.
Ok, maybe it's valid for me only ...
...
> Yuv
>
Kornel
An alternative which I use is checkinstall, which works even when the
make package doesn't. I'm sure it's not the best solution, but it
works for me (and as Kornel says, it's easier to de-install).
Seb
Now another problem, when i use help->about, hugin crash.
Lajos
> Now another problem, when i use help->about, hugin crash.
Same here (with the 2011.0.0 beta2 tarball)
Pit
Confirmed, that one(*) also doesn't crash for me.
Pit
(*) hg identify -i = f3a428981466
Yes. Suppose you make a new build, with different (maybe renamed) files or directories.
Now the `sudo make uninstall` would try to uninstall the _new_ data, leaving some old data installed.
Kornel