[ELDK] RE : RE : How can I build agin the toolchain ? (ELDK)
Marie Reine SARAZIN
mr.sarazin at actiasodielec.fr
Tue Aug 17 17:08:03 CEST 2010
Hi Detlev and Wolfgang,
--------------------------------------------------------------------------------------------------------------------------------------------
***********************************************SOLUTION N°1**************************************************************************
--------------------------------------------------------------------------------------------------------------------------------------------
I followed the steps on this link http://www.denx.de/wiki/DULG/AN2009_02_EldkReleaseBuildEnvironment with QEMU.
when launching QEMU as told in the link :
# qemu -m 1024 -net nic,model=rtl8139 -net tap,script=/etc/ifup-build -hda root-rh-7.3.img -hdc /dev/vg0/eldk_build
I got these errors :
/etc/ifup-build: could not launch network script
Could not initialize device 'tap'
The ifup-build file exists and I have not done modifications in it. Concerning the device tap : I tried before launching QEMU :
# tunctl -d tap0
Set 'tap0' nonpersistent
# tunctl -u alberix -t tap0
Set 'tap0' persistent and owned by uid 1000
and then :
qemu -m 1024 -net nic,model=rtl8139 -net tap,fd=tap0,script=/etc/ifup-build -hda root-rh-7.3.img -hdc /dev/vg0/eldk_build
The next steps worked pretty well (I have done exactly what it's told in the link above) till I tried to access the VBH from the host with this command line as explain on the link :
$ cd /net/eldk-build/opt/eldk/
It says No such file or directory
On my envirronment host, I use Ubuntu : there is not directory /net so it's normal. How can I reach /opt/ ? Is there any command to do from the host to make him being able to see /opt/ ? (When I look for /opt/, it doesn't fing anything)
I thought it may comes from tap0.
after this command line :
ifconfig tap0 10.100.0.1 netmask 255.255.255.252
I have this network configuration on the host :
eth0 Link encap:Ethernet HWaddr 00:1d:60:db:26:31
inet adr:192.93.121.5 Bcast:192.93.121.255 Masque:255.255.255.0
adr inet6: fe80::21d:60ff:fedb:2631/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:26937 erreurs:0 :0 overruns:0 frame:0
TX packets:14684 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:15018512 (15.0 MB) Octets transmis:2484870 (2.4 MB)
Interruption:23 Adresse de base:0x800
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
Packets reçus:70 erreurs:0 :0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:5344 (5.3 KB) Octets transmis:5344 (5.3 KB)
tap0 Link encap:Ethernet HWaddr da:51:cd:da:d4:58
inet adr:10.100.0.1 Bcast:10.100.0.3 Masque:255.255.255.252
adr inet6: fe80::d851:cdff:feda:d458/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:0 errors:0 dropped:38 overruns:0 carrier:0
collisions:0 lg file transmission:500
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)
virbr0 Link encap:Ethernet HWaddr 06:d2:63:22:e6:a3
inet adr:192.168.122.1 Bcast:192.168.122.255 Masque:255.255.255.0
adr inet6: fe80::4d2:63ff:fe22:e6a3/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:0 (0.0 B) Octets transmis:4528 (4.5 KB)
And this network configuration on the VBH :
eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet adr:10.100.0.2 Bcast:10.100.0.3 Masque:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX Packets:0 erreurs:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5760 (5.6 Kb)
Interrupt:11 Base address:0x9000
lo Link encap:Local Loopback
inet adr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX Packets:98 erreurs:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7808 (7.6 Kb) TX bytes:7808 (7.6 Kb)
I should be able to ping the VBH from the host (the same in the inverse way) but I don't.
PING 10.100.0.2 (10.100.0.2) 56(84) bytes of data.
More information about the eldk
mailing list