Your message dated Tue, 22 May 2012 10:34:31 +0200 with message-id <4FBB4F97.7090706@iem.at> and subject line Re: Bug#670044: assimp: FTBFS on ppc64: Please support ppc64 has caused the Debian Bug report #670044, regarding assimp: FTBFS on ppc64: Please support ppc64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 670044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670044 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: assimp: FTBFS on ppc64: Please support ppc64
- From: Hiroyuki Yamamoto <yama1066@gmail.com>
- Date: Sun, 22 Apr 2012 23:00:09 +0900
- Message-id: <4F940EE9.8060906@gmail.com>
Source: assimp Version: 2.0.863+dfsg-2 Severity: wishlist Tags: patch Please support ppc64. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=assimp&suite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DCdiff -Nurd assimp-2.0.863+dfsg.orig/debian/libassimp2.symbols assimp-2.0.863+dfsg/debian/libassimp2.symbols --- assimp-2.0.863+dfsg.orig/debian/libassimp2.symbols 2011-09-26 19:17:07.000000000 +0900 +++ assimp-2.0.863+dfsg/debian/libassimp2.symbols 2012-04-22 22:33:22.000000000 +0900 @@ -33,10 +33,10 @@ (c++)"Assimp::ProgressHandler::~ProgressHandler()@Base" 2.0.863 (c++)"Assimp::Intern::AllocateFromAssimpHeap::operator delete[](void*)@Base" 2.0.863 (c++)"Assimp::Intern::AllocateFromAssimpHeap::operator delete(void*)@Base" 2.0.863 - (c++|subst)"Assimp::Intern::AllocateFromAssimpHeap::operator new[]({c++:size_t})@Base" 2.0.863 - (c++|subst)"Assimp::Intern::AllocateFromAssimpHeap::operator new[]({c++:size_t}, std::nothrow_t const&)@Base" 2.0.863 - (c++|subst)"Assimp::Intern::AllocateFromAssimpHeap::operator new({c++:size_t})@Base" 2.0.863 - (c++|subst)"Assimp::Intern::AllocateFromAssimpHeap::operator new({c++:size_t}, std::nothrow_t const&)@Base" 2.0.863 + (c++|subst|arch=!ppc64)"Assimp::Intern::AllocateFromAssimpHeap::operator new[]({c++:size_t})@Base" 2.0.863 + (c++|subst|arch=!ppc64)"Assimp::Intern::AllocateFromAssimpHeap::operator new[]({c++:size_t}, std::nothrow_t const&)@Base" 2.0.863 + (c++|subst|arch=!ppc64)"Assimp::Intern::AllocateFromAssimpHeap::operator new({c++:size_t})@Base" 2.0.863 + (c++|subst|arch=!ppc64)"Assimp::Intern::AllocateFromAssimpHeap::operator new({c++:size_t}, std::nothrow_t const&)@Base" 2.0.863 (c++)"Assimp::Logger::info(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 2.0.863 (c++)"Assimp::Logger::warn(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 2.0.863 (c++)"Assimp::Logger::debug(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 2.0.863 @@ -59,7 +59,7 @@ (c++)"Assimp::Importer::UnregisterLoader(Assimp::BaseImporter*)@Base" 2.0.863 (c++)"Assimp::Importer::UnregisterPPStep(Assimp::BaseProcess*)@Base" 2.0.863 (c++)"Assimp::Importer::SetPropertyString(char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool*)@Base" 2.0.863 - (c++|subst)"Assimp::Importer::ReadFileFromMemory(void const*, {c++:size_t}, unsigned int, char const*)@Base" 2.0.863 + (c++|subst|arch=!ppc64)"Assimp::Importer::ReadFileFromMemory(void const*, {c++:size_t}, unsigned int, char const*)@Base" 2.0.863 (c++)"Assimp::Importer::SetProgressHandler(Assimp::ProgressHandler*)@Base" 2.0.863 (c++)"Assimp::Importer::SetPropertyInteger(char const*, int, bool*)@Base" 2.0.863 (c++)"Assimp::Importer::ApplyPostProcessing(unsigned int)@Base" 2.0.863 @@ -90,6 +90,11 @@ (c++)"Assimp::Importer::GetMemoryRequirements(aiMemoryInfo&) const@Base" 2.0.863 (c++)"Assimp::Importer::IsDefaultProgressHandler() const@Base" 2.0.863 (c++)"Assimp::Importer::GetScene() const@Base" 2.0.863 + (arch=ppc64)_ZN6Assimp6Intern22AllocateFromAssimpHeapnaEm@Base 2.0.863 + (arch=ppc64)_ZN6Assimp6Intern22AllocateFromAssimpHeapnaEmRKSt9nothrow_t@Base 2.0.863 + (arch=ppc64)_ZN6Assimp6Intern22AllocateFromAssimpHeapnwEm@Base 2.0.863 + (arch=ppc64)_ZN6Assimp6Intern22AllocateFromAssimpHeapnwEmRKSt9nothrow_t@Base 2.0.863 + (arch=ppc64)_ZN6Assimp8Importer18ReadFileFromMemoryEPKvmjPKc@Base 2.0.863 aiApplyPostProcessing@Base 2.0.863 aiAttachLogStream@Base 2.0.863 aiCreateQuaternionFromMatrix@Base 2.0.863
--- End Message ---
--- Begin Message ---
- To: 670044-done@bugs.debian.org
- Cc: Hiroyuki Yamamoto <yama1066@gmail.com>
- Subject: Re: Bug#670044: assimp: FTBFS on ppc64: Please support ppc64
- From: IOhannes m zmoelnig <zmoelnig@iem.at>
- Date: Tue, 22 May 2012 10:34:31 +0200
- Message-id: <4FBB4F97.7090706@iem.at>
- In-reply-to: <4FBA5195.1080909@iem.at>
- References: <4F940EE9.8060906@gmail.com> <4FBA5195.1080909@iem.at>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 the version of pkg-kde-tools (0.14.4) currently found in unstable (uploaded yesterday) has fixed support for ppc64 and sparc64. the assimp package uses pkg-kde-tools for building it's libassimp2.symbols file, to the fix should allow assimp to properly build on ppc64 (and sparc64). thanks gamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+7T5MACgkQkX2Xpv6ydvSJxwCfdbIvIKcg/GrqekICZtrk4yyD jWoAni9tOYzgI9Xl+kcq5Wnl1M4JWx29 =oO9/ -----END PGP SIGNATURE-----Attachment: smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---