First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 137434
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Scott Price <prices@dflytech.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
testpatch suggested patch for that single character too much :) patch Heiko Rosemann 2006-12-16 11:35 0000 471 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 137434 depends on: Show dependency tree
Bug 137434 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-06-20 15:06 0000
I am trying to use static-dev in an embedded environment.  It is being built in
a chroot'd environment into a different root ($ROOT is set).  Neither the
chroot environment nor the target root have either udev nor devfs installed.  

The offending line (16) is:

 if [[ -d /dev/.udev/ || ! -c /dev/.devfs ]]; then

in pkg_setup.  It seems to be saying that if /dev/.udev is a directory, or
/dev/.devfs is not a character device then run the code that complains of udev
or devfs being installed.  On my system neither /dev/.udev nor /dev/.devfs
exist, therefore the logic is coming out true because /dev/.devfs is not a
character device.

Also, it seems like it should be looking in ${ROOT}/dev/ instead of just /dev/. 



thing2 static-dev # emerge --info
Portage 2.0.54-r2 (uclibc/x86/2005.1, gcc-3.4.5, uclibc-0.9.28-r0, 2.6.15.1
i686)
=================================================================
System uname: 2.6.15.1 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
Gentoo Base System version 1.6.14
dev-lang/python:     2.3.4-r1, 2.4.2
dev-python/pycrypto: [Not Present]
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/gcc-config: 1.3.13-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i586-gentoo-linux-uclibc"
CFLAGS="-march=i586 -O2 -pipe"
CHOST="i586-gentoo-linux-uclibc"
CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config
/usr/kde/3.4/shutdown /usr/kde/3.5                                         
/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/X11/xkb
/usr/lib64/mozilla/defaults/                                          pref
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=i586 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig buildpkg distlocks nodoc noinfo noman sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gent                         
                oo"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages/i586-uclibc"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/scripts/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 berkdb bitmap-fonts bzip2 cli dri expat jpeg mmx mysql ncurses pcre
perl png python readl                                          ine reflection
session spl ssl truetype truetype-fonts type1-fonts uclibc uclibc-compat xorg
zlib                                           userland_GNU kernel_linux
elibc_uclibc"
Unset:  CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS,
PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_R                                         
SYNC_OPTS

------- Comment #1 From David Guerizec 2006-10-25 01:07:47 0000 -------
Confirmed.
Removing the ! before -c seems to fix the bug, but I don't know what the .devfs
file should be when using devfs.

Note: I checked on a debian box, and /dev/.devfs does not exist, but
/dev/.devfsd do and is a character device.

------- Comment #2 From Heiko Rosemann 2006-12-16 11:35:19 0000 -------
Created an attachment (id=104154) [edit]
suggested patch for that single character too much :)

Main bug confirmed on my system.

But my eBuild of static-dev-0.1 has the {$ROOT} in there.

------- Comment #3 From SpanKY 2007-10-01 01:48:21 0000 -------
thanks, fixed in the tree

First Last Prev Next    No search results available      Search page      Enter new bug