Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] app-text/mupdf-1.9a fails to emerge
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 4:36 am    Post subject: [SOLVED] app-text/mupdf-1.9a fails to emerge Reply with quote

Code:
load-jpx.c:(.text+0x6a4): undefined reference to `opj_image_destroy'
load-jpx.c:(.text+0x6c4): undefined reference to `opj_destroy_codec'
load-jpx.c:(.text+0x6e4): undefined reference to `opj_stream_destroy'
load-jpx.c:(.text+0x6ec): undefined reference to `opj_destroy_codec'
load-jpx.c:(.text+0x71f): undefined reference to `opj_image_destroy'
load-jpx.c:(.text+0x73c): undefined reference to `opj_image_destroy'
load-jpx.c:(.text+0x759): undefined reference to `opj_image_destroy'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/../../../../x86_64-pc-linux-gnu/bin/ld: build/debug/libmupdf.so.1.9: hidden symbol `opj_stream_destroy' isn't defined
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/../../../../x86_64-pc-linux-gnu/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make: *** [Makefile:398: build/debug/libmupdf.so.1.9] Error 1
 * ERROR: app-text/mupdf-1.9a::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'

>>> Failed to emerge app-text/mupdf-1.9a, Log file:

>>>  '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'

 * Messages for package app-text/mupdf-1.9a:

 * ERROR: app-text/mupdf-1.9a::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'


Failed to emerge app-text/mupdf-1.9a how to fix?


Last edited by farmer.ro on Sat Oct 29, 2016 2:15 pm; edited 1 time in total
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 4:41 am    Post subject: Reply with quote

here is the build log:

https://paste.pound-python.org/show/9dDzIDVn5umtixzTxgyX/

can not upgrade the Gentoo system at this point :(
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Oct 29, 2016 4:55 am    Post subject: Reply with quote

use patch form bugzilla
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 4:57 am    Post subject: Reply with quote

what do you mean?
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Oct 29, 2016 5:21 am    Post subject: Reply with quote

there is a bug-report about that error, it has patch attached, use it
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 5:30 am    Post subject: Reply with quote

i tried Google Search with no result, where can i find this patch?
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Oct 29, 2016 5:38 am    Post subject: Reply with quote

omg.
https://bugs.gentoo.org/show_bug.cgi?id=595406
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 7:36 am    Post subject: Reply with quote

the patch provided does not seem to work.

portage still seems to fail on app-text/mupdf-1.9a
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Oct 29, 2016 8:12 am    Post subject: Reply with quote

patch works
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 23553
Location: here

PostPosted: Sat Oct 29, 2016 8:21 am    Post subject: Reply with quote

farmer.ro wrote:
the patch provided does not seem to work.

portage still seems to fail on app-text/mupdf-1.9a

How you have applied the patch?
You have created file /etc/portage/bashrc with content
Code:
pre_src_prepare() {
    [[ ${EAPI:-0} == [012345] ]] || return
    if ! type epatch_user > /dev/null 2>&1; then
        local names="EPATCH_USER_SOURCE epatch_user epatch evar_push evar_push_set evar_pop estack_push estack_pop"
        source <(awk "/^# @(FUNCTION|VARIABLE): / { p = 0 } /^# @(FUNCTION|VARIABLE): (${names// /|})\$/ { p = 1 } p { print }" ${PORTDIR}/eclass/eutils.eclass)
    fi

    epatch_user

    for name in $names; do
        unset $name
    done
}
:?:
This is necessary because epatch_user function is not mandatory on EAPI 5
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 10:14 am    Post subject: Reply with quote

i indeed forgot the bashrc file thank you for mentioning.

however when i placed the .patch in the right directory things got a bit more complicated:

Code:
Calculating dependencies... done!
[ebuild  N     ] app-text/mupdf-1.9a  USE="X curl opengl openssl -libressl -static -static-libs -vanilla"
[ebuild     U  ] net-print/cups-filters-1.11.5 [1.11.4] USE="pdf%*"

Would you like to merge these packages? [Yes/No] yes

>>> Verifying ebuild manifests

>>> Emerging (1 of 2) app-text/mupdf-1.9a::gentoo
 * mupdf-1.9a.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                        [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/mupdf-1.9a/work
 * Applying user patches from /etc/portage/patches//app-text/mupdf-1.9a ...
 *   noob.patch ...                                                                                              [ ok ]
 * Done with patching
>>> Preparing source in /var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a ...
 * Applying mupdf-1.9a-CFLAGS.patch ...                                                                          [ ok ]
 * Applying mupdf-1.9a-debug-build.patch ...                                                                     [ ok ]
 * Applying mupdf-1.5-old-debian-files.patch ...                                                                 [ ok ]
 * Applying mupdf-1.3-pkg-config.patch ...                                                                       [ ok ]
 * Applying mupdf-1.5-Makerules-openssl-curl.patch ...                                                           [ ok ]
 * Applying mupdf-1.9a-no-thirdlibs.patch ...                                                                    [ ok ]
 * Applying mupdf-1.8-system-glfw.patch ...                                                                      [ ok ]
 * Applying mupdf-1.5-openjpeg-2.1.patch ...

 * Failed Patch: mupdf-1.5-openjpeg-2.1.patch !
 *  ( /usr/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.5-openjpeg-2.1.patch.out

 * ERROR: app-text/mupdf-1.9a::gentoo failed (prepare phase):
 *   Failed Patch: mupdf-1.5-openjpeg-2.1.patch!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2362:  Called epatch '/usr/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch'
 *   environment, line  911:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::gentoo'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'

>>> Failed to emerge app-text/mupdf-1.9a, Log file:

>>>  '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'

 * Messages for package app-text/mupdf-1.9a:

 * Failed Patch: mupdf-1.5-openjpeg-2.1.patch !
 *  ( /usr/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.5-openjpeg-2.1.patch.out
 * ERROR: app-text/mupdf-1.9a::gentoo failed (prepare phase):
 *   Failed Patch: mupdf-1.5-openjpeg-2.1.patch!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2362:  Called epatch '/usr/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch'
 *   environment, line  911:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::gentoo'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'


i can just NOT seem to patch mupdf
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Oct 29, 2016 10:17 am    Post subject: Reply with quote

with mentioned patch, mupdf-1.5-openjpeg-2.1.patch is deprecated, so you'd better use your own local overlay
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 10:18 am    Post subject: Reply with quote

ls /usr/portage/app-text/mupdf/files/
Code:
mupdf-1.3-CFLAGS.patch                  mupdf-1.5-format-security-error.patch  mupdf-1.8-system-glfw.patch
mupdf-1.3-pkg-config.patch              mupdf-1.5-old-debian-files.patch       mupdf-1.9a-CFLAGS.patch
mupdf-1.3-zoom-2.patch                  mupdf-1.5-openjpeg-2.1.patch           mupdf-1.9a-debug-build.patch
mupdf-1.5-Makerules-openssl-curl.patch  mupdf-1.7a-system-mujs.patch           mupdf-1.9a-no-thirdlibs.patch


the patch is in:
Code:
ls /etc/portage/patches/app-text/mupdf-1.9a
mupdf.patch


and i made the bashrc file in /etc/portage/

things got a bit confusing now.
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 10:20 am    Post subject: Reply with quote

Perfect Gentleman wrote:
with mentioned patch, mupdf-1.5-openjpeg-2.1.patch is deprecated, so you'd better use your own local overlay


how would i do this?
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 23553
Location: here

PostPosted: Sat Oct 29, 2016 10:22 am    Post subject: Reply with quote

farmer.ro wrote:
Perfect Gentleman wrote:
with mentioned patch, mupdf-1.5-openjpeg-2.1.patch is deprecated, so you'd better use your own local overlay


how would i do this?

Howto create local overlay
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 10:42 am    Post subject: Reply with quote

fedeliallalinea wrote:
farmer.ro wrote:
Perfect Gentleman wrote:
with mentioned patch, mupdf-1.5-openjpeg-2.1.patch is deprecated, so you'd better use your own local overlay


how would i do this?

Howto create local overlay


i created the local overlay, do i need to add the .ebuild or something?

what steps do i need to take after creating the local overlay?

i am still pretty stuck :(
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 11:28 am    Post subject: Reply with quote

i added the mupdf.ebuild to my local overlay:
Code:
These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] app-text/mupdf-1.9a:0/1.9::k03kj3spl4n33t  USE="X curl opengl openssl -libressl -static -static-libs -vanilla" 0 KiB

Total: 1 package (1 new), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No]


Code:
>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-text/mupdf-1.9a::k03kj3spl4n33t
 * mupdf-1.9a.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                         [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/mupdf-1.9a/work
 * Applying user patches from /etc/portage/patches//app-text/mupdf-1.9a ...
 *   noob.patch ...                                                                               [ ok ]
 * Done with patching
>>> Preparing source in /var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a ...

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *
 *   /usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch
 *   ( mupdf-1.9a-CFLAGS.patch )

 * ERROR: app-text/mupdf-1.9a::k03kj3spl4n33t failed (prepare phase):
 *   Cannot find $EPATCH_SOURCE!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2370:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-debug-build.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-old-debian-files.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.3-pkg-config.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-Makerules-openssl-curl.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-no-thirdlibs.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.8-system-glfw.patch'
 *   environment, line  742:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch'
 *   environment, line  769:  Called die
 * The specific snippet of code:
 *                   die "Cannot find \$EPATCH_SOURCE!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::k03kj3spl4n33t'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::k03kj3spl4n33t'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'

>>> Failed to emerge app-text/mupdf-1.9a, Log file:

>>>  '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'

 * Messages for package app-text/mupdf-1.9a:

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *
 *   /usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch
 *   ( mupdf-1.9a-CFLAGS.patch )
 * ERROR: app-text/mupdf-1.9a::k03kj3spl4n33t failed (prepare phase):
 *   Cannot find $EPATCH_SOURCE!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2370:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-debug-build.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-old-debian-files.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.3-pkg-config.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-Makerules-openssl-curl.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-no-thirdlibs.patch' '/usr/local/portage/app-text/mupdf/files/mupdf-1.8-system-glfw.patch'
 *   environment, line  742:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.9a-CFLAGS.patch'
 *   environment, line  769:  Called die
 * The specific snippet of code:
 *                   die "Cannot find \$EPATCH_SOURCE!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::k03kj3spl4n33t'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::k03kj3spl4n33t'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'


i have never been so stuck on something in my entire life !
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 12:07 pm    Post subject: Reply with quote

this is how far i got:
Code:
These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] app-text/mupdf-1.9a:0/1.9::k03kj3spl4n33t  USE="X curl opengl openssl -libressl -static -static-libs -vanilla" 0 KiB

Total: 1 package (1 new), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] yes

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-text/mupdf-1.9a::k03kj3spl4n33t
 * mupdf-1.9a.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                         [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/mupdf-1.9a/work
 * Applying user patches from /etc/portage/patches//app-text/mupdf-1.9a ...
 *   noob.patch ...                                                                               [ ok ]
 * Done with patching
>>> Preparing source in /var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a ...
 * Applying mupdf-1.9a-CFLAGS.patch ...                                                           [ ok ]
 * Applying mupdf-1.9a-debug-build.patch ...                                                      [ ok ]
 * Applying mupdf-1.5-old-debian-files.patch ...                                                  [ ok ]
 * Applying mupdf-1.3-pkg-config.patch ...                                                        [ ok ]
 * Applying mupdf-1.5-Makerules-openssl-curl.patch ...                                            [ ok ]
 * Applying mupdf-1.9a-no-thirdlibs.patch ...                                                     [ ok ]
 * Applying mupdf-1.8-system-glfw.patch ...                                                       [ ok ]
 * Applying mupdf-1.5-openjpeg-2.1.patch ...

 * Failed Patch: mupdf-1.5-openjpeg-2.1.patch !
 *  ( /usr/local/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.5-openjpeg-2.1.patch.out

 * ERROR: app-text/mupdf-1.9a::k03kj3spl4n33t failed (prepare phase):
 *   Failed Patch: mupdf-1.5-openjpeg-2.1.patch!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2372:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch'
 *   environment, line  921:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::k03kj3spl4n33t'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::k03kj3spl4n33t'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'

>>> Failed to emerge app-text/mupdf-1.9a, Log file:

>>>  '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'

 * Messages for package app-text/mupdf-1.9a:

 * Failed Patch: mupdf-1.5-openjpeg-2.1.patch !
 *  ( /usr/local/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.5-openjpeg-2.1.patch.out
 * ERROR: app-text/mupdf-1.9a::k03kj3spl4n33t failed (prepare phase):
 *   Failed Patch: mupdf-1.5-openjpeg-2.1.patch!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2372:  Called epatch '/usr/local/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch'
 *   environment, line  921:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::k03kj3spl4n33t'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::k03kj3spl4n33t'`.
 * !!! User patches were applied to this build!
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'


still seems to fail, i might just leave it as it is and wait for the developers to fix this cause i am too dumb for it.
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 12:20 pm    Post subject: Reply with quote

7 hours i tried to fix this problem with 0 result.

i might just go back to Debian i am so done with Gentoo.
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 23553
Location: here

PostPosted: Sat Oct 29, 2016 12:49 pm    Post subject: Reply with quote

I think, to solve problem, is to remove mupdf-1.5-openjpeg-2.1.patch, download new patch and edit ebuild
Code:
# rm /usr/local/portage/app-text/mupdf/files/mupdf-1.5-openjpeg-2.1.patch
# cd  /usr/local/portage/app-text/mupdf/files/
# wget "https://595406.bugs.gentoo.org/attachment.cgi?id=450200" -O mupdf-1.9a-openjpeg2.patch
# nano -w mupdf-1.9a.ebuild

Change line
Code:
                epatch \
                        "${FILESDIR}"/${PN}-1.5-openjpeg-2.1.patch

with
Code:
                epatch \
                        "${FILESDIR}"/${PN}-1.9a-openjpeg2.patch

Now you need to recreate manifest and install
Code:
# cd  /usr/local/portage/app-text/mupdf/
# ebuild mupdf-1.5-openjpeg-2.1.patch manifest
# emerge -1 =app-text/mupdf-1.9a::k03kj3spl4n33t

_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
prffzc
Tux's lil' helper
Tux's lil' helper


Joined: 22 Sep 2005
Posts: 105

PostPosted: Sat Oct 29, 2016 12:56 pm    Post subject: Reply with quote

I have a similar problem.

Code:

>>> Emerging (1 of 1) app-text/mupdf-1.9a::gentoo
 * mupdf-1.9a.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                                                   [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/mupdf-1.9a/work
 * Applying user patches from /etc/portage/patches//app-text/mupdf-1.9a ...
 *   mupdf-1.9a-openjpeg2.patch ...

 * Failed Patch: mupdf-1.9a-openjpeg2.patch !
 *  ( /etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.9a-openjpeg2.patch.out

 * ERROR: app-text/mupdf-1.9a::gentoo failed (prepare phase):
 *   Failed Patch: mupdf-1.9a-openjpeg2.patch!
 *
 * Call stack:
 *     ebuild.sh, line 115:  Called pre_src_prepare
 *        bashrc, line   8:  Called epatch_user
 *   environment, line 949:  Called epatch
 *   environment, line 921:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=app-text/mupdf-1.9a::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/mupdf-1.9a::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/mupdf-1.9a/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'
 * S: '/var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a'



The output from /var/tmp/portage/app-text/mupdf-1.9a/temp/mupdf-1.9a-openjpeg2.patch.out
Code:


***** mupdf-1.9a-openjpeg2.patch *****
PWD: /var/tmp/portage/app-text/mupdf-1.9a/work/mupdf-1.9a
PATCH TOOL: patch -> /usr/bin/patch
VERSION INFO:
GNU patch 2.7.5
Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc.
Copyright (C) 1988 Larry Wall

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Larry Wall and Paul Eggert

======================================

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch'

======================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|---
| Makerules              |  4 ++--
| source/fitz/load-jpx.c | 10 +---------
| 2 files changed, 3 insertions(+), 11 deletions(-)
|
|diff --git a/Makerules b/Makerules
|index 766ad53..a93b9cf 100644
|--- a/Makerules
|+++ b/Makerules
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/source/fitz/load-jpx.c b/source/fitz/load-jpx.c
|index 6b92e5c..72dea50 100644
|--- a/source/fitz/load-jpx.c
|+++ b/source/fitz/load-jpx.c
--------------------------
No file to patch.  Skipping patch.
patch unexpectedly ends in middle of line
2 out of 2 hunks ignored

patch program exited with status 1
======================================
PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch'

======================================
checking file Makerules
checking file source/fitz/load-jpx.c
patch unexpectedly ends in middle of line
Hunk #2 FAILED at 109.
1 out of 2 hunks FAILED

patch program exited with status 1
======================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch'

======================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|---
| Makerules              |  4 ++--
| source/fitz/load-jpx.c | 10 +---------
| 2 files changed, 3 insertions(+), 11 deletions(-)
|
|diff --git a/Makerules b/Makerules
|index 766ad53..a93b9cf 100644
|--- a/Makerules
|+++ b/Makerules
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/source/fitz/load-jpx.c b/source/fitz/load-jpx.c
|index 6b92e5c..72dea50 100644
|--- a/source/fitz/load-jpx.c
|+++ b/source/fitz/load-jpx.c
--------------------------
No file to patch.  Skipping patch.
patch unexpectedly ends in middle of line
2 out of 2 hunks ignored

patch program exited with status 1
======================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch'

======================================
.....
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 23553
Location: here

PostPosted: Sat Oct 29, 2016 1:20 pm    Post subject: Reply with quote

Ok the problem is that the download link of patch include some code not needed. Remove these lines
Code:
Edit patch file and remove this lines
From: =?utf-8?q?=22Kan-Ru_Chen_=28=E9=99=B3=E4=BE=83=E5=A6=82=29=22?=
 <koster@debian.org>
Date: Sat, 20 Sep 2014 12:33:08 +0800
Subject: Fix build with libopenjp2

---
 Makerules              |  4 ++--
 source/fitz/load-jpx.c | 10 +---------
 2 files changed, 3 insertions(+), 11 deletions(-)

The patch need to start with diff --git a/Makerules b/Makerules line
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Sat Oct 29, 2016 1:24 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Ok the problem is that the download link of patch include some code not needed. Remove these lines
Code:
Edit patch file and remove this lines
From: =?utf-8?q?=22Kan-Ru_Chen_=28=E9=99=B3=E4=BE=83=E5=A6=82=29=22?=
 <koster@debian.org>
Date: Sat, 20 Sep 2014 12:33:08 +0800
Subject: Fix build with libopenjp2

---
 Makerules              |  4 ++--
 source/fitz/load-jpx.c | 10 +---------
 2 files changed, 3 insertions(+), 11 deletions(-)

The patch need to start with diff --git a/Makerules b/Makerules line


is it still necessary to install from the local overlay?
Back to top
View user's profile Send private message
bathtor
n00b
n00b


Joined: 13 Jun 2015
Posts: 6

PostPosted: Sat Oct 29, 2016 1:29 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Ok the problem is that the download link of patch include some code not needed. Remove these lines
Code:
Edit patch file and remove this lines
From: =?utf-8?q?=22Kan-Ru_Chen_=28=E9=99=B3=E4=BE=83=E5=A6=82=29=22?=
 <koster@debian.org>
Date: Sat, 20 Sep 2014 12:33:08 +0800
Subject: Fix build with libopenjp2

---
 Makerules              |  4 ++--
 source/fitz/load-jpx.c | 10 +---------
 2 files changed, 3 insertions(+), 11 deletions(-)

The patch need to start with diff --git a/Makerules b/Makerules line


It works fine from local overlay, though, even with those extra lines.
Back to top
View user's profile Send private message
prffzc
Tux's lil' helper
Tux's lil' helper


Joined: 22 Sep 2005
Posts: 105

PostPosted: Sat Oct 29, 2016 1:31 pm    Post subject: Reply with quote

I'm not using an overlay. Just the patch in /etc/portage/patches/....

I have the same error
Code:

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/etc/portage/patches//app-text/mupdf-1.9a/mupdf-1.9a-openjpeg2.patch'

======================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/Makerules b/Makerules
|index 766ad53..a93b9cf 100644
|--- a/Makerules
|+++ b/Makerules
--------------------------
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum