Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

hugin/enblend 4.0 problem

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
13 posts • Page 1 of 1
Author
Message
world
n00b
n00b
Posts: 38
Joined: Sun May 16, 2010 11:06 am

hugin/enblend 4.0 problem

  • Quote

Post by world » Sat Aug 06, 2011 1:52 pm

Hello,

i want to install hugin, but everytime the compiler stopped at the enblend 4.0 program.

Code: Select all

enblend.cc:1745:   instantiated from here
anneal.h:535: interner Compiler-Fehler: in tsubst_copy, bei cp/pt.c:8428
Bitte senden Sie einen vollständigen Fehlerbericht auf Englisch ein;
bearbeiten Sie die Quellen zunächst mit einem Präprozessor, wenn es
dienlich ist.
Fehler in der deutschen Übersetzung sind an translation-team-de@lists.sourceforge.net zu melden.

Gehen Sie gemäß den Hinweisen in <URL:http://bugs.gentoo.org/> vor.
Preprocessed source stored into /var/tmp/portage/media-gfx/enblend-4.0/temp/ccLgjMdL.out file, please attach this to your bugreport.
make[4]: *** [enblend-enblend.o] Fehler 1
make[4]: Leaving directory `/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d/src'
make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d/src'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d'
make: *** [all] Fehler 2
emake failed
 * ERROR: media-gfx/enblend-4.0 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 2174:  Called die
 * The specific snippet of code:
 *       emake -j1 || die;
 * 
 * If you need support, post the output of 'emerge --info =media-gfx/enblend-4.0',
 * the complete build log and the output of 'emerge -pqv =media-gfx/enblend-4.0'.
 * The complete build log is located at '/var/tmp/portage/media-gfx/enblend-4.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-gfx/enblend-4.0/temp/environment'.
 * S: '/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d'

>>> Failed to emerge media-gfx/enblend-4.0, Log file:

>>>  '/var/tmp/portage/media-gfx/enblend-4.0/temp/build.log'

 * Messages for package media-gfx/enblend-4.0:

 * the openmp and image-cache USE-flags are mutually exclusive
 * image-cache will be disabled in favour of openmp
 * ERROR: media-gfx/enblend-4.0 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 2174:  Called die
 * The specific snippet of code:
 *       emake -j1 || die;
 * 
 * If you need support, post the output of 'emerge --info =media-gfx/enblend-4.0',
 * the complete build log and the output of 'emerge -pqv =media-gfx/enblend-4.0'.
 * The complete build log is located at '/var/tmp/portage/media-gfx/enblend-4.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-gfx/enblend-4.0/temp/environment'.
 * S: '/var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d'

 * IMPORTANT: 10 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.
i don't know how i can fix it.

best regards
world
Top
Hu
Administrator
Administrator
Posts: 24401
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Sat Aug 06, 2011 4:57 pm

I think that is an ICE. Please post the output of emerge --info ; LC_ALL=C emerge --oneshot =media-gfx/enblend-4.0.
Top
Bowman
n00b
n00b
Posts: 19
Joined: Sun May 22, 2005 9:33 pm

  • Quote

Post by Bowman » Mon Aug 08, 2011 6:02 am

I'm having the same issue. Here is the error message that I get when media-gfx/enblend compile fails:

Code: Select all

png.cxx: In member function 'void vigra::PngDecoderImpl::init()':
png.cxx:331:87: error: invalid conversion from 'png_byte**' to 'char**'
png.cxx:331:87: error:   initializing argument 5 of 'png_uint_32 png_get_iCCP(const png_struct*, const png_info*, char**, int*, char**, png_uint_32*)'
png.cxx: In member function 'void vigra::PngEncoderImpl::finalize()':
png.cxx:600:63: warning: deprecated conversion from string constant to 'char*'
png.cxx:600:63: error: invalid conversion from 'vigra::ArrayVector<unsigned char, std::allocator<unsigned char> >::value_type*' to 'char*'
png.cxx:600:63: error:   initializing argument 5 of 'void png_set_iCCP(png_struct*, png_info*, char*, int, char*, png_uint_32)'
Top
Hu
Administrator
Administrator
Posts: 24401
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Mon Aug 08, 2011 11:38 pm

Bowman wrote:I'm having the same issue.
Why do you say that? Your error is in a different file and shows no sign of a compiler crash.
Top
Bowman
n00b
n00b
Posts: 19
Joined: Sun May 22, 2005 9:33 pm

  • Quote

Post by Bowman » Mon Aug 08, 2011 11:42 pm

Hu wrote:Why do you say that? Your error is in a different file and shows no sign of a compiler crash.
Same result then. I apologize if the error message isn't the same. If I understood it, I wouldn't be posting here would I? To me it looks like the same issue. I just thought I was being helpful. Serves me right I guess.
Top
b4max
n00b
n00b
Posts: 15
Joined: Tue Jun 14, 2005 12:56 am
Location: Germany

  • Quote

Post by b4max » Wed Aug 10, 2011 6:11 pm

Hi everybody,

while this post is definitely not about the original compiler crash, I think I can help at least with the latter issue. I filed bug#378677 and attached an updated ebuild to the bug that fixes some stuff with the upcoming libpng-1.5. Feel free to test it if you can't wait for an updated ebuild to hit the tree.

Please accept my apologies if this has been treated elsewhere already.

cheers,
Max
Top
Hu
Administrator
Administrator
Posts: 24401
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Thu Aug 11, 2011 3:52 am

Bowman wrote:If I understood it, I wouldn't be posting here would I? To me it looks like the same issue. I just thought I was being helpful.
Many people post with errors they do not understand. The problem is that if you post an unrelated error into an existing thread, it becomes harder to help either of you than it would be if you each had a separate thread, because it is less clear to readers whether any particular advice or request for information is directed at the OP, the latecomer, or both. (Posting a me-too can be helpful if you have the exact same error messages as the OP and your environment differs in some respect to the OP, since that can indicate that a problem is more widespread than previously believed.)

Also, as a general comment, whenever you have problems with a package failing to compile, it is a good idea to post the output of emerge --info category/package, so that readers can tell what flags you have enabled, what architecture you are using, and the version of the failed package.
Top
Bowman
n00b
n00b
Posts: 19
Joined: Sun May 22, 2005 9:33 pm

  • Quote

Post by Bowman » Thu Aug 11, 2011 4:19 am

Hu wrote:
Bowman wrote:If I understood it, I wouldn't be posting here would I? To me it looks like the same issue. I just thought I was being helpful.
Many people post with errors they do not understand. The problem is that if you post an unrelated error into an existing thread, it becomes harder to help either of you than it would be if you each had a separate thread, because it is less clear to readers whether any particular advice or request for information is directed at the OP, the latecomer, or both. (Posting a me-too can be helpful if you have the exact same error messages as the OP and your environment differs in some respect to the OP, since that can indicate that a problem is more widespread than previously believed.)

Also, as a general comment, whenever you have problems with a package failing to compile, it is a good idea to post the output of emerge --info category/package, so that readers can tell what flags you have enabled, what architecture you are using, and the version of the failed package.
My point is that it looks the same to me. But why do I bother? Obviously it's a waste of time to try and get help around here.
Top
Hu
Administrator
Administrator
Posts: 24401
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Fri Aug 12, 2011 4:13 am

Bowman wrote:My point is that it looks the same to me. But why do I bother? Obviously it's a waste of time to try and get help around here.
b4max already cited a bug that does have the same error message you posted. Although we lack adequate information about your system to be certain that you are experiencing the same problem, it seems likely that the bug he cited, which has a solution, is relevant. As such, I thought it prudent to explain why your post was misplaced, rather than reiterate the solution he had already located for you.
Top
|Quantum|
Tux's lil' helper
Tux's lil' helper
Posts: 133
Joined: Sat Jan 24, 2004 9:01 pm
Location: Belgium

  • Quote

Post by |Quantum| » Fri Aug 12, 2011 9:50 am

I have similar problems.
It appears that the libpng14 and 15 patches are always carried out regardless of the true installed version:

Code: Select all

# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/media-gfx/enblend/enblend-4.0.ebuild,v 1.9 2011/08/07 15:56:20 ssuominen Exp $

EAPI=2

inherit eutils

DESCRIPTION="Image Blending with Multiresolution Splines"
HOMEPAGE="http://enblend.sourceforge.net/"
SRC_URI="mirror://sourceforge/enblend/${PN}-enfuse-${PV/_rc/RC}.tar.gz"

LICENSE="GPL-2 VIGRA"
SLOT="0"
KEYWORDS="amd64 ppc x86"
IUSE="debug doc gpu +image-cache +openexr openmp"

RDEPEND="
	media-libs/glew
	=media-libs/lcms-1*
	>=media-libs/libpng-1.2.43
	media-libs/plotutils[X]
	media-libs/tiff
	virtual/jpeg
	gpu? ( media-libs/freeglut )
	openexr? ( >=media-libs/openexr-1.0 )"
DEPEND="${RDEPEND}
	>=dev-libs/boost-1.31.0
	dev-util/pkgconfig
	doc? (
		media-gfx/transfig
		sci-visualization/gnuplot
		virtual/latex-base
	)"

S="${WORKDIR}/${PN}-enfuse-4.0-753b534c819d"

pkg_setup() {
	if use image-cache && use openmp; then
		ewarn "the openmp and image-cache USE-flags are mutually exclusive"
		ewarn "image-cache will be disabled in favour of openmp"
	fi
}

src_prepare() {
	epatch "${FILESDIR}"/${P}-libpng1{4,5}.patch
}
src_configure() {
	local myconf=""
	if use image-cache && use openmp; then
		myconf="--disable-image-cache --enable-openmp"
	else
		myconf="$(use_enable image-cache) $(use_enable openmp)"
	fi

	use doc && myconf="${myconf} --with-gnuplot=$(type -p gnuplot)" \
		|| myconf="${myconf} --with-gnuplot=false"

	econf \
		--with-x \
		$(use_enable debug) \
		$(use_enable gpu gpu-support) \
		$(use_with openexr) \
		${myconf}
}

src_compile() {
	# forcing -j1 as every parallel compilation process needs about 1 GB RAM.
	emake -j1 || die
	if use doc; then
		cd doc
		make enblend.pdf enfuse.pdf || die
	fi
}

src_install() {
	emake DESTDIR="${D}" install || die
	dodoc AUTHORS ChangeLog NEWS README || die
	use doc && dodoc doc/en{blend,fuse}.pdf
}

Code: Select all

Californium diederik # emerge enblend
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-gfx/enblend-4.0
 * enblend-enfuse-4.0.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                              [ ok ]
 * Package:    media-gfx/enblend-4.0
 * Repository: gentoo
 * Maintainer: graphics@gentoo.org
 * USE:        amd64 elibc_glibc gpu image-cache kernel_linux multilib openexr openmp userland_GNU
 * FEATURES:   sandbox
 * the openmp and image-cache USE-flags are mutually exclusive
 * image-cache will be disabled in favour of openmp
>>> Unpacking source...
>>> Unpacking enblend-enfuse-4.0.tar.gz to /var/tmp/portage/media-gfx/enblend-4.0/work
>>> Source unpacked in /var/tmp/portage/media-gfx/enblend-4.0/work
>>> Preparing source in /var/tmp/portage/media-gfx/enblend-4.0/work/enblend-enfuse-4.0-753b534c819d ...
* Applying enblend-4.0-libpng14.patch ...                                                                [ ok ]
 * Applying enblend-4.0-libpng15.patch ...                                                                [ ok ]
>>> Source prepared.

Code: Select all

Californium enblend # ls -l /usr/lib64/libpng*
lrwxrwxrwx 1 root root     18 Aug 12 11:04 /usr/lib64/libpng14.so -> libpng14.so.14.8.0
lrwxrwxrwx 1 root root     18 Aug 12 11:04 /usr/lib64/libpng14.so.14 -> libpng14.so.14.8.0
-rwxr-xr-x 1 root root 170704 Aug 12 11:04 /usr/lib64/libpng14.so.14.8.0
lrwxrwxrwx 1 root root     11 Aug 12 11:04 /usr/lib64/libpng.so -> libpng14.so
Top
|Quantum|
Tux's lil' helper
Tux's lil' helper
Posts: 133
Joined: Sat Jan 24, 2004 9:01 pm
Location: Belgium

Re: hugin/enblend 4.0 problem

  • Quote

Post by |Quantum| » Fri Aug 12, 2011 9:57 am

UPDATE:

I changed the following line in /usr/portage/media-gfx/enblend/enblend-4.0.ebuild:

OLD:
src_prepare() {
epatch "${FILESDIR}"/${P}-libpng1{4,5}.patch
}

NEW:
src_prepare() {
epatch "${FILESDIR}"/${P}-libpng14.patch
}

after that:

ebuild enblend-4.0.ebuild digest
emerge enblend


It works!!

Ergo: this is a portage bug.


P.S.: I also tried to upgrade to libpng-1.5 with no success (i.e. emerge enblend fails even with the 1.5 patch applied).
Top
VoidMage
Watchman
Watchman
User avatar
Posts: 6196
Joined: Sat Oct 14, 2006 8:43 am

  • Quote

Post by VoidMage » Fri Aug 12, 2011 10:40 am

@|Quantum|:
1. You definitely didn't understand what Hu wrote.
2. Those two png patches are independent, so both should be applied.

Having said that, there really is a problem in enblend-4.0-libpng15.patch, but nothing a few #ifdefs can't fix.
Basically, png_{s,g}et_iCCP signature has changed in 1.5, so till 1.4 png_charpp is correct for profile, since 1.5 it should be png_bytepp (it's actually char* -> unsigned char* (on x86 - see pngconf.h)).
Top
|Quantum|
Tux's lil' helper
Tux's lil' helper
Posts: 133
Joined: Sat Jan 24, 2004 9:01 pm
Location: Belgium

  • Quote

Post by |Quantum| » Fri Aug 12, 2011 10:43 am

VoidMage wrote:@|Quantum|:
1. You definitely didn't understand what Hu wrote.
2. Those two png patches are independent, so both should be applied.

Having said that, there really is a problem in enblend-4.0-libpng15.patch, but nothing a few #ifdefs can't fix.
Basically, png_{s,g}et_iCCP signature has changed in 1.5, so till 1.4 png_charpp is correct for profile, since 1.5 it should be png_bytepp (it's actually char* -> unsigned char* (on x86 - see pngconf.h)).
I knew there is a patch, but it's not done automatically. I though of posting this as an intermediary solution until things are merged in the portage tree.
Top
Post Reply

13 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic