Francisco Ares | 4 Nov 00:12
Picon
Gravatar

reduced X11 - how to?

Hi, All

I use Gentoo in a simple machine.  Nowadays it uses a hard drive, but
I would like to use a small IDE flash drive.  I found the embedded
Gentoo guide, which resulted in a very low size system, but when I
include X, it more than doubles its size.

How can I make X "thinner"?  The system doesn't need a window manager,
so I didn't install any.  The machine application is the X shell.  It
uses Python and WxPython.

Thanks
Francisco

--

-- 
"If you have an apple and I have an apple and we exchange apples then
you and I will still each have one apple. But if you have an idea and
I have one idea and we exchange these ideas, then each of us will have
two ideas." - George Bernard Shaw
Vladimir Pouzanov | 4 Nov 19:33
Picon
Gravatar

Re: reduced X11 - how to?

On 11/4/06, Francisco Ares <frares@...> wrote:
> How can I make X "thinner"?  The system doesn't need a window manager,
> so I didn't install any.  The machine application is the X shell.  It
> uses Python and WxPython.

You can try USE=kdrive (kdrive is X11 mode for embedded devices),
AFAIK it reduces it's size by removing useless features.

--

-- 
Sincerely,
Vladimir "Farcaller" Pouzanov
http://hackndev.com
Hanni Ali | 5 Nov 01:14
Picon

Re: reduced X11 - how to?

obviously select only the modular parts you actually need don't just emerge xorg-x11 (this pulls down loads of unnecessary stuff)

determine the exact dependencies necessary

in addition to kdrive (which I'm not hugely familiar with but search "xorg kdrive" on google and i found some useful mailing lists etc.) USE="minimal" reduces unneceassary stuff i use minimal as a global for a lot of packages when building livecd/usb's

I use gentoo-portage to check what use flags do, also actually reading the ebuild in question can tell you a lot

http://gentoo-portage.com/x11-base/xorg-server/USE#ptabs

check the bottom of the page it mentions

minimal
Global: Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features)

i haven't tried kdrive yet but will at some point

Hanni


On 04/11/06, Vladimir Pouzanov <farcaller-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > wrote:
On 11/4/06, Francisco Ares <frares-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > wrote:
> How can I make X "thinner"?  The system doesn't need a window manager,
> so I didn't install any.  The machine application is the X shell.  It
> uses Python and WxPython.

You can try USE=kdrive (kdrive is X11 mode for embedded devices),
AFAIK it reduces it's size by removing useless features.

--
Sincerely,
Vladimir "Farcaller" Pouzanov
http://hackndev.com
--
gentoo-embedded-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org mailing list




--
E-mail: hanni.ali-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Mobile: 07985580147
Website: www.ainkaboot.co.uk
Colin Bell | 8 Nov 22:54
Picon
Favicon

Can't get /dev/sda to mount

Hi all

I've managed to build my first Gentoo embedded disk on VMware using the instructions from the wiki. It all boots and loads up but the /boot and the /mount/dongle mounts fail. The wiki has instructions for a usb dongle, but I modified the fstab slightly to work for a drive.

If I try fdisk /dev/sda it says it can't find /dev/sda. /dev/sda and /dev/sda* (1-4) exist in the /dev directory. I have also tried deleting them and using mknod and mdev instead without success.

I have added the scsi drivers in the kernel (as vmware emulates scsi).

I get no errors in the /var/log/messages.

/etc/fstab is

none                    /tmp            tmpfs           defaults        0 0
none                    /proc           proc            defaults        0 0
/dev/sda1               /boot           ext2            noauto,ro       0 0
/dev/sda2               /mnt/dongle     ext2            defaults        0 0


I would really appreciate some pointers.

Many thanks

Colin
Colin Bell | 9 Nov 11:17
Picon
Favicon

Re: Can't get /dev/sda to mount

Ok, have solved part of it. For my version of VMware you have to  
compile the Buslogic driver into the kernel.

I also modified my fstab

/dev/sda1   /boot        ext2    defaults,noatime     1 2
/dev/sda2   none         swap    sw                   0 0
/dev/sda3   /            ext2    noatime             0 1

proc        /proc        proc    defaults             0 0
shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0

Problem is, /dev/sda3 mounts as read only ?

Anyone ?
Colin Bell | 10 Nov 11:02
Picon
Favicon

Re: Can't get /dev/sda to mount

Solved the mount problem. I was missing /etc/mtab

Don't you love user groups where you have to solve your own  
problems.... unsubscribe
Wolfgang Meyerle | 7 Nov 18:06
Picon

crossdev mipsel toolchain compile problems

Hello,

does anybody of you know why gcc fails in emerging gcc stage 2 in mipsel
toolchain. I tried to emerge this with the 

crossdev --target mipsel-linux-uclibc

and I always get the strange error message from gcc, specially from
libstdc++ which seems to be included in gcc, 

I really need this toolchain as I'm currently developing a port knocker
daemon which should run on my linksys router. I use libpcap for this
purposes. 

How can I include libpcap in this toolchain if it would compile?
There must be a way of including software witout too much configuration
stuff...

Thanks for your attention, perhaps you can help me out of this mess

Wolfgang Meyerle

Mike Frysinger | 11 Nov 11:33
Picon
Favicon
Gravatar

Re: crossdev mipsel toolchain compile problems

On 11/7/06, Wolfgang Meyerle <rotlicht@...> wrote:
> does anybody of you know why gcc fails in emerging gcc stage 2 in mipsel
> toolchain.

no real information here ... `crossdev mipsel-gentoo-linux-uclibc`
works fine for me
-mike
Wolfgang Meyerle | 7 Nov 18:16
Picon
Favicon

crossdev mipsel toolchain compile problems

Hello,

does anybody of you know why gcc fails in emerging gcc stage 2 in mipsel
toolchain. I tried to emerge this with the 

crossdev --target mipsel-linux-uclibc

and I always get the strange error message from gcc, specially from
libstdc++ which seems to be included in gcc:

Checking multilib configuration...
/bin/sh
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/gcc-4.1.1/mkinstalldirs
mipsel-linux-uclibc/libstdc++-v3 ; \
rm -f mipsel-linux-uclibc/libstdc++-v3/Makefile || : ; \
cp multilib.out mipsel-linux-uclibc/libstdc++-v3/multilib.out
mkdir -p -- mipsel-linux-uclibc/libstdc++-v3
Configuring in mipsel-linux-uclibc/libstdc++-v3
configure: creating cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... mipsel-unknown-linux-uclibc
checking target system type... mipsel-unknown-linux-uclibc
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for mipsel-linux-uclibc-strip... mipsel-linux-uclibc-strip
checking for mipsel-linux-uclibc-gcc...
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include accepts -g... yes
checking for /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include option to
accept ANSI C... none needed
checking for mipsel-linux-uclibc-g++... 
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-shared-libgcc -B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc
-nostdinc++
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src/.libs
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include
checking whether we are using the GNU C++ compiler... yes
checking whether 
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-shared-libgcc -B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc
-nostdinc++
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src/.libs
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include accepts -g... yes
checking whether ln -s works... yes
checking for mipsel-linux-uclibc-as... /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/as
checking for mipsel-linux-uclibc-ar... mipsel-linux-uclibc-ar
checking for mipsel-linux-uclibc-ranlib... mipsel-linux-uclibc-ranlib
checking whether to enable maintainer-specific portions of Makefiles... no
configure: CPU config directory is cpu/mips
configure: OS config directory is os/uclibc
checking for ld used by GCC... /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/collect-ld
checking if the linker
(/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/collect-ld) is
GNU ld... yes
checking for
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/collect-ld option
to reload object files... -r
checking for BSD-compatible nm... /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/nm
checking how to recognise dependant libraries... pass_all
checking the maximum length of command line arguments... none
checking for mipsel-linux-uclibc-ranlib... (cached) mipsel-linux-uclibc-ranlib
checking for mipsel-linux-uclibc-strip... (cached) mipsel-linux-uclibc-strip
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking for objdir... .libs
checking for /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
option to produce PIC... -fPIC -DPIC
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc PIC
flag -fPIC -DPIC works... yes
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
static flag -static works... no
finding the maximum length of command line arguments... 49153
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
supports -c -o file.o... yes
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
supports -fno-rtti -fno-exceptions ... no
checking whether the linker
(/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/collect-ld)
supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... uClibc ld.so
checking command to parse
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/nm output... failed
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
creating libtool
updating cache ./config.cache
configure: loading cache ./config.cache
checking how to run the C++ preprocessor... 
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-shared-libgcc -B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc
-nostdinc++
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src
-L/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/mipsel-linux-uclibc/libstdc++-v3/src/.libs
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include -E
loading cache ./config.cache within ltconfig
checking host system type... mipsel-unknown-linux-uclibc
checking build system type... x86_64-pc-linux-gnu
checking for objdir... .libs
checking for /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
option to produce PIC... -fPIC -DPIC
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc PIC
flag -fPIC -DPIC works... yes
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
static flag -static works... no
finding the maximum length of command line arguments... (cached) 49153
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
supports -c -o file.o... (cached) yes
checking if /var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
supports -fno-rtti -fno-exceptions ... yes
checking whether the linker
(/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/collect-ld)
supports shared libraries... 
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... uClibc ld.so
checking command to parse
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/nm output... failed
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
appending configuration tag "CXX" to libtool
checking for exception model to use... call frame
checking for compiler with PCH support... yes
checking for enabled PCH... yes
checking for underlying I/O to use... stdio
checking how to run the C preprocessor...
/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/xgcc
-B/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build/./gcc/
-B/usr/mipsel-linux-uclibc/bin/ -B/usr/mipsel-linux-uclibc/lib/ -isystem
/usr/mipsel-linux-uclibc/include -isystem /usr/mipsel-linux-uclibc/sys-include -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for C locale to use... uclibc
checking for msgfmt... yes
checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking for library containing gettext... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/var/tmp/cross/mipsel-linux-uclibc/portage/gcc-4.1.1-r1/work/build'
make: *** [all] Error 2

!!! ERROR: cross-mipsel-linux-uclibc/gcc-4.1.1-r1 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  ebuild.sh, line 1255:   Called toolchain_src_compile
  toolchain.eclass, line 24:   Called gcc_src_compile
  toolchain.eclass, line 1535:   Called gcc_do_make
  toolchain.eclass, line 1409:   Called die

!!! emake failed with all
!!! If you need support, post the topmost build error, and the call stack if relevant.

!!! This ebuild is from an overlay: '/usr/local/portage'
... done!

>>> Emerging (1 of 1) cross-mipsel-linux-uclibc/gcc-4.1.1-r1 to /
 * gcc-4.1.1.tar.bz2 MD5 ;-) ...                                          [ ok ]
 * gcc-4.1.1.tar.bz2 RMD160 ;-) ...                                       [ ok ]
 * gcc-4.1.1.tar.bz2 SHA1 ;-) ...                                         [ ok ]
 * gcc-4.1.1.tar.bz2 SHA256 ;-) ...                                       [ ok ]
 * gcc-4.1.1.tar.bz2 size ;-) ...                                         [ ok ]
 * gcc-4.1.1-uclibc-patches-1.1.tar.bz2 MD5 ;-) ...                       [ ok ]
 * gcc-4.1.1-uclibc-patches-1.1.tar.bz2 RMD160 ;-) ...                    [ ok ]
 * gcc-4.1.1-uclibc-patches-1.1.tar.bz2 SHA1 ;-) ...                      [ ok ]
 * gcc-4.1.1-uclibc-patches-1.1.tar.bz2 SHA256 ;-) ...                    [ ok ]
 * gcc-4.1.1-uclibc-patches-1.1.tar.bz2 size ;-) ...                      [ ok ]
 * gcc-4.1.1-patches-1.7.tar.bz2 MD5 ;-) ...                              [ ok ]
 * gcc-4.1.1-patches-1.7.tar.bz2 RMD160 ;-) ...                           [ ok ]
 * gcc-4.1.1-patches-1.7.tar.bz2 SHA1 ;-) ...                             [ ok ]
 * gcc-4.1.1-patches-1.7.tar.bz2 SHA256 ;-) ...                           [ ok ]
 * gcc-4.1.1-patches-1.7.tar.bz2 size ;-) ...                             [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking gcc-4.1.1.tar.bz2 ;-) ...                                     [ ok ]
 * checking gcc-4.1.1-uclibc-patches-1.1.tar.bz2 ;-) ...                  [ ok ]
 * checking gcc-4.1.1-patches-1.7.tar.bz2 ;-) ...                         [ ok ]

I really need this toolchain as I'm currently developing a port knocker
daemon which should run on my linksys router. I use libpcap for this
purposes. 

How can I include libpcap in this toolchain if it would compile?
There must be a way of including software witout too much configuration
stuff...

Thanks for your attention, perhaps you can help me out of this mess

Wolfgang Meyerle

Mike Frysinger | 11 Nov 11:40
Picon
Favicon
Gravatar

Re: crossdev mipsel toolchain compile problems

On 11/7/06, Wolfgang Meyerle <procrash@...> wrote:
> checking for library containing gettext... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

ah that sucks ... that's like the kiss of death for cross-compilers

this failure could be caused by a number of things and generally it
goes away "by itself" so i havent spent any real time on tracking it
down
-mike

Gmane