Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 146450 - sys-apps/less-394 failed epatch
Summary: sys-apps/less-394 failed epatch
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: ARM Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-05 13:32 UTC by Alexey Shvetsov
Modified: 2007-01-31 13:31 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Shvetsov archtester gentoo-dev 2006-09-05 13:32:59 UTC
Every time I tryed to compile under chroot on arm handheld (iPAQ hx4700)
emerge fails on patching sources
Comment 1 Alexey Shvetsov archtester gentoo-dev 2006-09-05 13:33:53 UTC
hp ~ # emerge -v1 less
Calculating dependencies... done!

>>> Emerging (1 of 1) sys-apps/less-394 to /
 * code2color MD5 ;-) ...                                                                                                  [ ok ]
 * code2color RMD160 ;-) ...                                                                                               [ ok ]
 * code2color SHA1 ;-) ...                                                                                                 [ ok ]
 * code2color SHA256 ;-) ...                                                                                               [ ok ]
 * code2color size ;-) ...                                                                                                 [ ok ]
 * less-394.tar.gz MD5 ;-) ...                                                                                             [ ok ]
 * less-394.tar.gz RMD160 ;-) ...                                                                                          [ ok ]
 * less-394.tar.gz SHA1 ;-) ...                                                                                            [ ok ]
 * less-394.tar.gz SHA256 ;-) ...                                                                                          [ ok ]
 * less-394.tar.gz size ;-) ...                                                                                            [ ok ]
 * checking ebuild checksums ;-) ...                                                                                       [ ok ]
 * checking auxfile checksums ;-) ...                                                                                      [ ok ]
 * checking miscfile checksums ;-) ...                                                                                     [ ok ]
 * checking less-394.tar.gz ;-) ...                                                                                        [ ok ]
 * checking code2color ;-) ...                                                                                             [ ok ]
>>> Unpacking source...
>>> Unpacking less-394.tar.gz to /var/tmp/portage/less-394/work
 * Applying code2color.patch ...

 * Failed Patch: code2color.patch !
 *  ( /usr/portage/sys-apps/less/files/code2color.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/less-394/temp/code2color.patch-4367.out


!!! ERROR: sys-apps/less-394 failed.
Call stack:
  ebuild.sh, line 1543:   Called dyn_unpack
  ebuild.sh, line 709:   Called src_unpack
  less-394.ebuild, line 24:   Called epatch '/usr/portage/sys-apps/less/files/code2color.patch'
  eutils.eclass, line 341:   Called die

!!! Failed Patch: code2color.patch!
!!! If you need support, post the topmost build error, and the call stack if relevant.

hp ~cat /var/tmp/portage/less-394/temp/code2color.patch-4367.out
***** code2color.patch *****

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

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/less/files/code2color.patch

============================
patching file code2color
Hunk #3 succeeded at 3193 (offset 1 line).
============================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/less/files/code2color.patch

============================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- code2color
|+++ code2color
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
============================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/less/files/code2color.patch

============================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- code2color
|+++ code2color
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
============================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/less/files/code2color.patch

============================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- code2color
|+++ code2color
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
============================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/less/files/code2color.patch

============================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- code2color
|+++ code2color
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
Comment 2 Alexey Shvetsov archtester gentoo-dev 2006-09-05 13:35:12 UTC
hp ~ # emerge --info
Portage 2.1.1_rc1-r2 (default-linux/arm, gcc-4.1.1, glibc-2.4-r3, 2.6.15-hh2 armv5tel)
=================================================================
System uname: 2.6.15-hh2 armv5tel unknown
Gentoo Base System version 1.12.4
Last Sync: Mon, 04 Sep 2006 01:54:01 +0000
distcc 2.18.3 armv5te-softfloat-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.4.3-r3
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.16
ACCEPT_KEYWORDS="arm ~arm"
AUTOCLEAN="yes"
CBUILD="armv5te-softfloat-linux-gnu"
CFLAGS="-Os -pipe -ftree-vectorize -fomit-frame-pointer"
CHOST="armv5te-softfloat-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-Os -pipe -ftree-vectorize -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distcc distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LDFLAGS="-Wl,-O1 -Wl,--sort-common"
LINGUAS=""
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="arm bitmap-fonts cli crypt dlloader elibc_glibc fortran input_devices_evdev input_devices_keyboard input_devices_mouse kernel_linux ncurses nls nptl nptlonly pam pcre perl pppd profile python readline reflection session spl ssl tcpd truetype-fonts type1-fonts unicode userland_GNU userlocales video_cards_ati video_cards_chips video_cards_dummy video_cards_fbdevglint video_cards_mga video_cards_nv video_cards_s3 video_cards_s3virge video_cards_savage video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_trident video_cards_v4l video_cards_vga video_cards_voodoo zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Comment 3 SpanKY gentoo-dev 2006-09-05 19:22:18 UTC
my guess is you cross-compiled bash

re-emerge bash *natively* and things should just start working
Comment 4 Lari Korpi 2007-01-30 17:54:26 UTC
(In reply to comment #3)
> my guess is you cross-compiled bash
> 
> re-emerge bash *natively* and things should just start working
> 

Mine is and the target system is Linksys NSLU2. The nest question is .. How can one emerge packages by hand? I can du the patch:ing on shell, but not via emerge.
Comment 5 SpanKY gentoo-dev 2007-01-31 04:51:23 UTC
edit the ebuild so it doesnt apply the patches

once you have that bash installed, restore the ebuild with the patches and emerge it like normal
Comment 6 Lari Korpi 2007-01-31 13:31:51 UTC
(In reply to comment #5)
> edit the ebuild so it doesnt apply the patches
> 
> once you have that bash installed, restore the ebuild with the patches and
> emerge it like normal
> 

Well for my system I had to do the same for the grep first and for the bash after that.

With the bash natively compiled the gentoo magic kicked in and system is now emerging packages wonderfully. Thanks!