Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - F... io-pkt!!!!: Page 1 of 2 (26 Items)
   
F... io-pkt!!!!  
I have been trying to install the io-pkt package on the qnx 6.3.2 for nearly a week and I am still stuck. I thing I'll 
go crazy if someone does not help me.
I have downloaded  io-pkt.zip with svn then I have transferred it on qnx target and unzipped it 
I did not create any staging area, because I don't care if I have to resintall qnx.
So I open io-pkt with cd...
then when I prompt make CPULIST=x86 install 
I get the message error:
cannot find recurse.mk
Sure I can do a find / -name "recurse.mk", then copy/paste into io-pkt.
But then I have got other files : qtargets.mk, qconfig.mk... that cannot be found
And when I have finally included all the necessary files I get
the message:

unknow target 'gcc_ntox86' 
no targets defined in etc/qcc

which is linked to the instruction
qcc -Vgcc_ntox86 -c ...assptinf.c 
which seems correct to me.
So i assumed the problem came from my qnx installation and I reinstalled qnx. But that does not change anything I have 
the sam damn 
cannot find recurse.mk

So now I don't know what to do.

io-pkt build problems  
A little bit of forum etiquette...  Starting off a post with a subject line
such as the one that you did is inappropriate (even given the fact that you
didn't spell it out).  We'd like these forums to be a place of
professionalism and respect and that's not the way to achieve it.

OK.  Off my soap box and on to the problem...

I'm quite confused by what it is you seem to have done.  There aren't any
zip files available that contain source.  The only way to download the
source is 

http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Source
_Guide

"How do I get the source?"

svn checkout --username <userid>
http://community.qnx.com/svn/repos/core_networking/trunk


Regardless of whether or not you mind about re-installing the OS, you should
create and use a staging area since otherwise you're doing everything as
root, and one bad command will ruin your day.

Once you've done the source checkout, what does your tree look like?  You
should be able to "cd trunk" and see a number of directories and files:

trunk -
	common
	crypto
	dist
	dist2
	lib
	services
	sys
	utils
	GUIDELINES
	io-pkt.mk
	Makefile

Typing make in the trunk directory should "just work"



	Robert.





-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Monday, March 17, 2008 6:45 AM
To: builds-networking
Subject: F... io-pkt!!!!

I have been trying to install the io-pkt package on the qnx 6.3.2 for nearly
a week and I am still stuck. I thing I'll go crazy if someone does not help
me.
I have downloaded  io-pkt.zip with svn then I have transferred it on qnx
target and unzipped it 
I did not create any staging area, because I don't care if I have to
resintall qnx.
So I open io-pkt with cd...
then when I prompt make CPULIST=x86 install 
I get the message error:
cannot find recurse.mk
Sure I can do a find / -name "recurse.mk", then copy/paste into io-pkt.
But then I have got other files : qtargets.mk, qconfig.mk... that cannot be
found
And when I have finally included all the necessary files I get
the message:

unknow target 'gcc_ntox86' 
no targets defined in etc/qcc

which is linked to the instruction
qcc -Vgcc_ntox86 -c ...assptinf.c 
which seems correct to me.
So i assumed the problem came from my qnx installation and I reinstalled
qnx. But that does not change anything I have the sam damn 
cannot find recurse.mk

So now I don't know what to do.



_______________________________________________
Builds
http://community.qnx.com/sf/go/post5852
io-pkt build problems.  
A little bit of forum etiquette...  Starting off a post with a subject line
such as the one that you did is inappropriate (even given the fact that you
didn't spell it out).  We'd like these forums to be a place of
professionalism and respect and that's not the way to achieve it.

OK.  Off my soap box and on to the problem...

I'm quite confused by what it is you seem to have done.  There aren't any
zip files available that contain source.  The only way to download the
source is 

http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Source
_Guide

"How do I get the source?"

svn checkout --username <userid>
http://community.qnx.com/svn/repos/core_networking/trunk


Regardless of whether or not you mind about re-installing the OS, you should
create and use a staging area since otherwise you're doing everything as
root, and one bad command will ruin your day.

Once you've done the source checkout, what does your tree look like?  You
should be able to "cd trunk" and see a number of directories and files:

trunk -
	common
	crypto
	dist
	dist2
	lib
	services
	sys
	utils
	GUIDELINES
	io-pkt.mk
	Makefile

Typing make in the trunk directory should "just work"



	Robert.


-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Monday, March 17, 2008 6:45 AM
To: builds-networking
Subject: F... io-pkt!!!!

I have been trying to install the io-pkt package on the qnx 6.3.2 for nearly
a week and I am still stuck. I thing I'll go crazy if someone does not help
me.
I have downloaded  io-pkt.zip with svn then I have transferred it on qnx
target and unzipped it 
I did not create any staging area, because I don't care if I have to
resintall qnx.
So I open io-pkt with cd...
then when I prompt make CPULIST=x86 install 
I get the message error:
cannot find recurse.mk
Sure I can do a find / -name "recurse.mk", then copy/paste into io-pkt.
But then I have got other files : qtargets.mk, qconfig.mk... that cannot be
found
And when I have finally included all the necessary files I get
the message:

unknow target 'gcc_ntox86' 
no targets defined in etc/qcc

which is linked to the instruction
qcc -Vgcc_ntox86 -c ...assptinf.c 
which seems correct to me.
So i assumed the problem came from my qnx installation and I reinstalled
qnx. But that does not change anything I have the sam damn 
cannot find recurse.mk

So now I don't know what to do.



_______________________________________________
Builds
http://community.qnx.com/sf/go/post5852
Re: io-pkt build problems.  
Sorry about the title of the post (mea culpa)
Now for my problem, I followed the source guide instructions, I got the trunk. But my problem is that, when I type in 
the trunk directory 
make CPULIST=x86 install, that just doesn't work.
Maybe there is a specific repertory where to place trunk so that it can find the files it needs.
I have begun to copy/paste the files "make" could not find and it is quite long and tedious.
Now my last error message is about -lcacheS which cannot be found.
Do you have an idea about this?
Re: io-pkt build problems.  
I'm still trying to find out where things have gone wrong.  There certainly shouldn't be any need to copy and paste 
things in.  We have seen some problems with strict firewalls preventing svn from getting to the repository and 
downloading the files.  What does your top level trunk directory look like?  Were there any errors when you did the svn 
checkout?

Lib cache is a standard OS library located int /usr/lib.  If the build isn't picking things up, then it's also quite 
possible that your PATH and LD_LIBRARY_PATH environment variables aren't being properly set.

What is the full output after you type the make install (cut and paste so that we can see what's being called)?
Re: io-pkt build problems.  
On Mon, Mar 17, 2008 at 11:45:35AM -0400, j v wrote:
> Sorry about the title of the post (mea culpa)
> Now for my problem, I followed the source guide instructions, I got the trunk. But my problem is that, when I type in 
the trunk directory 
> make CPULIST=x86 install, that just doesn't work.
> Maybe there is a specific repertory where to place trunk so that it can find the files it needs.
> I have begun to copy/paste the files "make" could not find and it is quite long and tedious.
> Now my last error message is about -lcacheS which cannot be found.
> Do you have an idea about this?

Are you trying to build on a host or target?  You should
build on a host for a particular target and then build an
image with / copy over the resulting binaries.

-seanb
Re: io-pkt build problems.  
Hello,

I have found out why it does not work properly. I had downloaded the wrong source files, not the stable release.
So I think I 'll just try the stable version.
To answer your questions I got the message 

# cd /home/pc236
# ls
.                         Exemple_ecriture          trunk.zip
..                        io-pkt-so
Exemple_Lecture           trunk
# cd ./trunk
# make
Makefile:3: recurse.mk: No such file or directory
make: *** No rule to make target `recurse.mk'.  Stop.
#

And I build self hosted.
Thanks
Re: io-pkt build problems.  
There version of source that you should download is the trunk version.  If
you do an ls inside of trunk what do you get?  It doesn't look like the
build is doing anything which is very strange.



----- Original Message -----
From: j v <jeanmarieverret@gmail.com>
To: builds-networking <post5931@community.qnx.com>
Sent: Wed Mar 19 05:02:49 2008
Subject: Re: io-pkt build problems.

Hello,

I have found out why it does not work properly. I had downloaded the wrong
source files, not the stable release.
So I think I 'll just try the stable version.
To answer your questions I got the message 

# cd /home/pc236
# ls
.                         Exemple_ecriture          trunk.zip
..                        io-pkt-so
Exemple_Lecture           trunk
# cd ./trunk
# make
Makefile:3: recurse.mk: No such file or directory
make: *** No rule to make target `recurse.mk'.  Stop.
#

And I build self hosted.
Thanks

_______________________________________________
Builds
http://community.qnx.com/sf/go/post5931
Re: io-pkt build problems.  
I don't understand, I should download the trunk version?
Because it is said in the source guide 
"we can't guarantee that the trunk source will a) build and b) if it does build, work" and that
"branches directory will contain stable release code"
If I am correct it means I should download the branch version.
In the first place, I downloaded the trunk version. And I got the errors I told you So I tediously copy/paste all the 
necessary files and finally succeeded in compiling.
But when I slay io-net and launched io-pkt it did not work, I coud not communicate with the network anymore. But I did 
not use, then, a staging directory.

So, I reinstalled QNX, I read again the source guide, found out that I should download the branch version, I did it, and
 declared the toplevel as a staging directory. 
And now, when I compile, I get the same errors (can't find recurse.mk...). 
I noticed that, for instance, recurse.mk is originally in
/usr/qnx630/target/qnx6/usr/include/mk, and is not found.
But when I copy/paste it into usr/include/mk (which is originally empty)
the error disappear: recurse.mk is found.
And the same principle goes for many following errors.
So I wonder, is my installation of QNX weird?

PS: I am confused about which version I should download.Which one shoul I work with?

PPS: I dowload the files from a Windows station and then copy them on my QNX host.
Re: io-pkt build problems.  
On Wed, Mar 19, 2008 at 08:32:45AM -0400, j v wrote:
> I don't understand, I should download the trunk version?
> Because it is said in the source guide 
> "we can't guarantee that the trunk source will a) build and b) if it does build, work" and that
> "branches directory will contain stable release code"
> If I am correct it means I should download the branch version.
> In the first place, I downloaded the trunk version. And I got the errors I told you So I tediously copy/paste all the 
necessary files and finally succeeded in compiling.
> But when I slay io-net and launched io-pkt it did not work, I coud not communicate with the network anymore. But I did
 not use, then, a staging directory.
> 
> So, I reinstalled QNX, I read again the source guide, found out that I should download the branch version, I did it, 
and declared the toplevel as a staging directory. 
> And now, when I compile, I get the same errors (can't find recurse.mk...). 
> I noticed that, for instance, recurse.mk is originally in
> /usr/qnx630/target/qnx6/usr/include/mk, and is not found.
> But when I copy/paste it into usr/include/mk (which is originally empty)
> the error disappear: recurse.mk is found.
> And the same principle goes for many following errors.
> So I wonder, is my installation of QNX weird?
> 
> PS: I am confused about which version I should download.Which one shoul I work with?
> 
> PPS: I dowload the files from a Windows station and then copy them on my QNX host.

Work with the trunk for now.  It's fairly stable at the moment.

Is your environment set up correctly?

# set | egrep "QNX_TARGET|QNX_HOST|MAKEFLAGS"
MAKEFLAGS=-I/usr/qnx632/target/qnx6/usr/include
QNX_HOST=/usr/qnx632/host/qnx6/x86
QNX_TARGET=/usr/qnx632/target/qnx6

-seanb
RE: io-pkt build problems.  
Ahhhhhh... If you had to copy files into /usr/qnx630/target, then this is
nothing at all to do with io-pkt.  Sounds like your install is either
non-standard or incomplete.

In terms of download version, you could indeed download one of the tagged
source bases.  Given where we are in terms of development at this point (and
the fact that we haven't created a release branch just yet), I'd recommend
using trunk since it contains the most up to date code.  The wiki is correct
in that there are no guarantees about trunk, but given that there isn't a
release branch yet, it's the best thing to use.


-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Wednesday, March 19, 2008 8:33 AM
To: builds-networking
Subject: Re: io-pkt build problems.

I don't understand, I should download the trunk version?
Because it is said in the source guide 
"we can't guarantee that the trunk source will a) build and b) if it does
build, work" and that
"branches directory will contain stable release code"
If I am correct it means I should download the branch version.
In the first place, I downloaded the trunk version. And I got the errors I
told you So I tediously copy/paste all the necessary files and finally
succeeded in compiling.
But when I slay io-net and launched io-pkt it did not work, I coud not
communicate with the network anymore. But I did not use, then, a staging
directory.

So, I reinstalled QNX, I read again the source guide, found out that I
should download the branch version, I did it, and declared the toplevel as a
staging directory. 
And now, when I compile, I get the same errors (can't find recurse.mk...). 
I noticed that, for instance, recurse.mk is originally in
/usr/qnx630/target/qnx6/usr/include/mk, and is not found.
But when I copy/paste it into usr/include/mk (which is originally empty)
the error disappear: recurse.mk is found.
And the same principle goes for many following errors.
So I wonder, is my installation of QNX weird?

PS: I am confused about which version I should download.Which one shoul I
work with?

PPS: I dowload the files from a Windows station and then copy them on my QNX
host.

_______________________________________________
Builds
http://community.qnx.com/sf/go/post5938
Re: RE: io-pkt build problems.  
I have followed your counsels, I have taken the trunk version. I have built it, though I had to go through some make -I 
include, and copy /paste of libraries. I cannot imagine what's wrong with my qnx installation, since I merely use a 
standard cd of QNX 6.3.2 runtime , and download tcdump through qnx installer.
I made the built in a staging area with the instructions:
USE_INSTALL_ROOT=1
INSTALL_ROOT_nto=/pathoftrunk/
Then, I copied/pasted the necessary files into /root/io-pkt (as it is told in the wiki pages)
Now with 
export LD_LIBRARY_PATH=/root/io-pkt:$LD_LIBRARY_PATH
export PATH=/root/io-pkt:$PATH
and
io-pkt-v4-hc -d i82544 -p tcpip
I should have correctly launched io-pkt anbd ifconfig should work anyway.
But I get the following result (it is not working out unfortunately)

bash-2.05a# io-pkt-v4-hc -d i82544 -p tcpip
bash-2.05a# ifconfig
unknown symbol: _in6addr_any
unknown symbol: get_media_options
unknown symbol: get_media_option_string
unknown symbol: get_media_mode_string
unknown symbol: get_media_subtype_string
unknown symbol: get_media_type_string
unknown symbol: ioctl_socket
unknown symbol: get_media_subtype
unknown symbol: get_media_mode
Could not resolve all symbols
RE: RE: io-pkt build problems.  
The INSTALL_ROOT_nto shouldn't be pointing to the source trunk.  It should
be point at an installation directory, separate from the source directory.
I'd recommend creating a directory in your home directory called "stage".
What you'll probably find is that under your trunk directory, you now have a
bunch of directories (x86, ppc, etc.) that contain the binaries which is
probably OK, but has your installation and source tree mixed.

With regards to the error, I think you're picking up the wrong libsocket
which means that the io-pkt libsocket isn't in the LD_LIBRARY_PATH.  So...
you can either copy io-pkt's x86/lib/libsocket*  into the /root/io-pkt
directory OR:

From
http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Source
_Guide


export
LD_LIBRARY_PATH=$HOME/stage/x86/lib:$HOME/stage/x86/lib/dll:$LD_LIBRARY_PATH
export 

PATH=$HOME/stage/x86/bin:$HOME/stage/x86/sbin:$HOME/stage/x86/usr/bin:$HOME/
stage/x86/usr/sbin:$PATH

Note the inclusion of "/x86/lib" and "/x86/lib/dll".  Likewise for the PATH
(note how there are four directories there).  If you've installed stuff
under your source trunk directory, your "$HOME/stage" directory is now
"pathtotrunk" instead (and you should see a pathtotrunk/x86/lib directory
that contains libsocket).


	Robert.



-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Wednesday, March 26, 2008 12:53 PM
To: builds-networking
Subject: Re: RE: io-pkt build problems.

I have followed your counsels, I have taken the trunk version. I have built
it, though I had to go through some make -I include, and copy /paste of
libraries. I cannot imagine what's wrong with my qnx installation, since I
merely use a standard cd of QNX 6.3.2 runtime , and download tcdump through
qnx installer.
I made the built in a staging area with the instructions:
USE_INSTALL_ROOT=1
INSTALL_ROOT_nto=/pathoftrunk/
Then, I copied/pasted the necessary files into /root/io-pkt (as it is told
in the wiki pages)
Now with 
export LD_LIBRARY_PATH=/root/io-pkt:$LD_LIBRARY_PATH
export PATH=/root/io-pkt:$PATH
and
io-pkt-v4-hc -d i82544 -p tcpip
I should have correctly launched io-pkt anbd ifconfig should work anyway.
But I get the following result (it is not working out unfortunately)

bash-2.05a# io-pkt-v4-hc -d i82544 -p tcpip
bash-2.05a# ifconfig
unknown symbol: _in6addr_any
unknown symbol: get_media_options
unknown symbol: get_media_option_string
unknown symbol: get_media_mode_string
unknown symbol: get_media_subtype_string
unknown symbol: get_media_type_string
unknown symbol: ioctl_socket
unknown symbol: get_media_subtype
unknown symbol: get_media_mode
Could not resolve all symbols


_______________________________________________
Builds
http://community.qnx.com/sf/go/post6153
Re: RE: io-pkt build problems.  
On Wed, Mar 26, 2008 at 12:53:06PM -0400, j v wrote:
> I have followed your counsels, I have taken the trunk version. I have built it, though I had to go through some make -
I include, and copy /paste of libraries. I cannot imagine what's wrong with my qnx installation, since I merely use a 
standard cd of QNX 6.3.2 runtime , and download tcdump through qnx installer.
> I made the built in a staging area with the instructions:

The issue may be that you're using bash and your environment
is not set up correctly as mentioned before.  You should have:

# set | egrep "QNX_HOST|QNX_TARGET|MAKEFLAGS"
MAKEFLAGS=-I/usr/qnx632/target/qnx6/usr/include
QNX_HOST=/usr/qnx632/host/qnx6/x86
QNX_TARGET=/usr/qnx632/target/qnx6

Try the folowing then re-check your environment in bash
or try using the default shell.
# cp /etc/profile.d/qnxsdk.sh /etc/profile.d/qnxsdk.bash

> USE_INSTALL_ROOT=1
> INSTALL_ROOT_nto=/pathoftrunk/
> Then, I copied/pasted the necessary files into /root/io-pkt (as it is told in the wiki pages)
> Now with 
> export LD_LIBRARY_PATH=/root/io-pkt:$LD_LIBRARY_PATH
> export PATH=/root/io-pkt:$PATH
> and
> io-pkt-v4-hc -d i82544 -p tcpip
> I should have correctly launched io-pkt anbd ifconfig should work anyway.
> But I get the following result (it is not working out unfortunately)
> 
> bash-2.05a# io-pkt-v4-hc -d i82544 -p tcpip
> bash-2.05a# ifconfig
> unknown symbol: _in6addr_any
> unknown symbol: get_media_options
> unknown symbol: get_media_option_string
> unknown symbol: get_media_mode_string
> unknown symbol: get_media_subtype_string
> unknown symbol: get_media_type_string
> unknown symbol: ioctl_socket
> unknown symbol: get_media_subtype
> unknown symbol: get_media_mode
> Could not resolve all symbols

It's find ing the io-pkt ifconfig but not the
io-pkt libsocket.  Is libsocket actually under
/root/io-pkt or the usual /root/io-pkt/x86/lib/?

-seanb
Re: RE: io-pkt build problems.  
Thanks a lot. I'll try that and let you know the results
Re: RE: io-pkt build problems.  
You were right Sean, MAKEFLAGS was not set correctly .
Now when I type make CPULIST=x86 install it just works out.
But I am still having problems.
When I type
USE_INSTALL_ROOT=1
INSTALL_ROOT_nto=/home/pc236/stage
I see that, after the compilation, stage is still empty.
And libsocket.so, for instance, is found in /home/pc236/trunk/lib/socket/x86/so.
So I copy/paste from the trunk directory the necessary files into /root/io-pkt then set LD_LIBRARY_PATH and PATH to /
root/io-pkt.
But  I still get with ifconfig 

bash-2.05a# ifconfig
unknown symbol: _in6addr_any
unknown symbol: get_media_options
unknown symbol: get_media_option_string
unknown symbol: get_media_mode_string
unknown symbol: get_media_subtype_string
unknown symbol: get_media_type_string
unknown symbol: ioctl_socket
unknown symbol: get_media_subtype
unknown symbol: get_media_mode
Could not resolve all symbols

bash-2.05a# echo $LD_LIBRARY_PATH
/root/io-pkt:/proc/boot:/lib:/usr/lib:/lib/dll:/opt/lib:/usr/photon/lib:/usr/photon/dll:/usr/local/lib:/opt/X
11R6/lib:/usr/X11R6/lib
bash-2.05a# echo $PATH
/root/io-pkt:/sbin:/usr/sbin:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/local/bin:/opt/bin:/opt/sbin:/usr/qnx630/
host/qnx6/x86/usr/bin:/opt/bin:/usr/photon/bin:/usr/photon/appbuilder:/opt/X11R6/bin:/usr/X11R6/bin
bash-2.05a# cd /root/io-pkt
bash-2.05a# ls
.                    devnp-shim.so        io-pkt-v4-hc         netstat
..                   dhcp.client          io-pkt-v6-hc         nicinfo
devnp-i82544.so      ifconfig             libsocket.so
RE: RE: io-pkt build problems.  
Hey!  We're getting closer...
If the stage is empty, then the problem is your QCONF_OVERRIDE likely isn't
being set properly.  It looks like things are still being placed in your
original location.  Are you setting the env vars in the same shell that
you're doing your build in?

Out of curiosity, are you using a qconf-override.mk file?
If you "echo $QCONF_OVERRIDE" does it indicate the correct qconf-override.mk
file? (Or does the file contain the correct values?)

If you copy paste the files, then have you copied all of the io-pkt
libsocket files into the directory?  You're still picking up the io-net
libsocket.	

-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Thursday, March 27, 2008 9:11 AM
To: builds-networking
Subject: Re: RE: io-pkt build problems.

You were right Sean, MAKEFLAGS was not set correctly .
Now when I type make CPULIST=x86 install it just works out.
But I am still having problems.
When I type
USE_INSTALL_ROOT=1
INSTALL_ROOT_nto=/home/pc236/stage
I see that, after the compilation, stage is still empty.
And libsocket.so, for instance, is found in
/home/pc236/trunk/lib/socket/x86/so.
So I copy/paste from the trunk directory the necessary files into
/root/io-pkt then set LD_LIBRARY_PATH and PATH to /root/io-pkt.
But  I still get with ifconfig 

bash-2.05a# ifconfig
unknown symbol: _in6addr_any
unknown symbol: get_media_options
unknown symbol: get_media_option_string
unknown symbol: get_media_mode_string
unknown symbol: get_media_subtype_string
unknown symbol: get_media_type_string
unknown symbol: ioctl_socket
unknown symbol: get_media_subtype
unknown symbol: get_media_mode
Could not resolve all symbols

bash-2.05a# echo $LD_LIBRARY_PATH
/root/io-pkt:/proc/boot:/lib:/usr/lib:/lib/dll:/opt/lib:/usr/photon/lib:/usr
/photon/dll:/usr/local/lib:/opt/X
11R6/lib:/usr/X11R6/lib
bash-2.05a# echo $PATH
/root/io-pkt:/sbin:/usr/sbin:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/local/bi
n:/opt/bin:/opt/sbin:/usr/qnx630/
host/qnx6/x86/usr/bin:/opt/bin:/usr/photon/bin:/usr/photon/appbuilder:/opt/X
11R6/bin:/usr/X11R6/bin
bash-2.05a# cd /root/io-pkt
bash-2.05a# ls
.                    devnp-shim.so        io-pkt-v4-hc         netstat
..                   dhcp.client          io-pkt-v6-hc         nicinfo
devnp-i82544.so      ifconfig             libsocket.so

_______________________________________________
Builds
http://community.qnx.com/sf/go/post6191
RE: RE: io-pkt build problems.  
On a 6.3.x box, I use a script (shown below) so that each time you open a
terminal, run ". ./this_script" then you have environment set ready for your
running anything related to io-pkt. E.g, each "make install" will install
into your stage; each of running "ifconfig" or looking for a so library will
be using the one in your stage instead of the one on the host 6.3.x box. 

In the following script, I assume the stage is at /community/svn/stage. I
have my /community/svn/qconf-override.mk (shown below) point to the stage.
My script exports the QCONF_OVERRIDE pointing to the qconf-override. Modify
it to your case. No need to mention again that you should run ".
./your_script" instead of running "./your_script" because the later case
will set the environment to the child shell instead of the one you are
working on. 

Hope it be helpful. 

Thanks. 

Weijie

PS: (1) my script. 
#================ start ===============
export QCONF_OVERRIDE=/community/svn/qconf-override.mk
cm=/community/svn/stage/x86
export
PATH=$cm/bin:$cm/sbin:$cm/usr/bin:$cm/usr/sbin:$cm/usr/local/bin:$cm/usr/loc
al/sbin:$PATH
export
LD_LIBRARY_PATH=$cm/lib:$cm/lib/dll:$cm/usr/local/lib:/usr/qnx630/target/qnx
6/x86/usr/local/lib:$LD_LIBRARY_PATH
#================ end =====================
(2) the qconf-override.mk. It contains the following two lines. 

INSTALL_ROOT_nto := /community/svn/stage
USE_ROOT_nto := /community/svn/stage


-----Original Message-----
From: Robert Craig 
Sent: March 27, 2008 10:07 AM
To: builds-networking
Subject: RE: RE: io-pkt build problems.

Hey!  We're getting closer...
If the stage is empty, then the problem is your QCONF_OVERRIDE likely isn't
being set properly.  It looks like things are still being placed in your
original location.  Are you setting the env vars in the same shell that
you're doing your build in?

Out of curiosity, are you using a qconf-override.mk file?
If you "echo $QCONF_OVERRIDE" does it indicate the correct qconf-override.mk
file? (Or does the file contain the correct values?)

If you copy paste the files, then have you copied all of the io-pkt
libsocket files into the directory?  You're still picking up the io-net
libsocket.	

-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Thursday, March 27, 2008 9:11 AM
To: builds-networking
Subject: Re: RE: io-pkt build problems.

You were right Sean, MAKEFLAGS was not set correctly .
Now when I type make CPULIST=x86 install it just works out.
But I am still having problems.
When I type
USE_INSTALL_ROOT=1
INSTALL_ROOT_nto=/home/pc236/stage
I see that, after the compilation, stage is still empty.
And libsocket.so, for instance, is found in
/home/pc236/trunk/lib/socket/x86/so.
So I copy/paste from the trunk directory the necessary files into
/root/io-pkt then set LD_LIBRARY_PATH and PATH to /root/io-pkt.
But  I still get with ifconfig 

bash-2.05a# ifconfig
unknown symbol: _in6addr_any
unknown symbol: get_media_options
unknown symbol: get_media_option_string
unknown symbol: get_media_mode_string
unknown symbol: get_media_subtype_string
unknown symbol: get_media_type_string
unknown symbol: ioctl_socket
unknown symbol: get_media_subtype
unknown symbol: get_media_mode
Could not resolve all symbols

bash-2.05a# echo $LD_LIBRARY_PATH
/root/io-pkt:/proc/boot:/lib:/usr/lib:/lib/dll:/opt/lib:/usr/photon/lib:/usr
/photon/dll:/usr/local/lib:/opt/X
11R6/lib:/usr/X11R6/lib
bash-2.05a# echo $PATH
/root/io-pkt:/sbin:/usr/sbin:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/local/bi
n:/opt/bin:/opt/sbin:/usr/qnx630/
host/qnx6/x86/usr/bin:/opt/bin:/usr/photon/bin:/usr/photon/appbuilder:/opt/X
11R6/bin:/usr/X11R6/bin
bash-2.05a# cd /root/io-pkt
bash-2.05a# ls
.                    devnp-shim.so        io-pkt-v4-hc         netstat
..                   dhcp.client          io-pkt-v6-hc         nicinfo
devnp-i82544.so      ifconfig            ...
View Full Message
Re: RE: RE: io-pkt build problems.  
Let me answer your questions:
Echo $QCONF_OVERRIDE do not contain anything.
I set the env vars in a different shell that the one I built in.
So I lose the content of MAKEFLAGS (and other env vars) but I thought it was not necessary anymore since the build was 
done.
I do not use any qconf-override.mk. And after the build, in my new shell
I cannot find any "qconf-override.mk".
Do you mean I have to set MAKEFLAGS, QCONF_OVERRIDE and , all of this in the same shell, build the source code ?
And finally what do you mean by copying all the io-pkt libsocket files in the directory ? As you can see, in my post 
just above (see cd /root/io-pkt),  I just copied libsocket.so in root/io-pkt is it not enough?
By the way, if there are other env vars to set, tell me. I am under the impressions that all my problems come from there
.

RE: RE: RE: io-pkt build problems.  
Hi:
	In: 
	
http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Source
_Guide

the first paragraph points you to:
http://community.qnx.com/sf/wiki/do/viewPage/projects.core_os/wiki/BuildTheO
SSource

which covers setting up a staging area and how to create and set up a
qconf-override.mk file.


Going back to the Networking source, it indicates that modifying the
.profile lets you set up these env vars for all of your shells as they are
created.

Shell environment variables are shell specific.  They are only inherited
from the parent shell so setting them in one shell doesn't set them in the
other.

So yes...  If you are manually setting the vars, you have to do it in the
same shell that you're both building in AND running in (since the
LD_LIBRARY_PATH and PATH vars won't apply to other shells).


For copying files, you also need libsocket.so.2 copied over.

	Robert.




-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Thursday, March 27, 2008 10:33 AM
To: builds-networking
Subject: Re: RE: RE: io-pkt build problems.

Let me answer your questions:
Echo $QCONF_OVERRIDE do not contain anything.
I set the env vars in a different shell that the one I built in.
So I lose the content of MAKEFLAGS (and other env vars) but I thought it was
not necessary anymore since the build was done.
I do not use any qconf-override.mk. And after the build, in my new shell
I cannot find any "qconf-override.mk".
Do you mean I have to set MAKEFLAGS, QCONF_OVERRIDE and , all of this in the
same shell, build the source code ?
And finally what do you mean by copying all the io-pkt libsocket files in
the directory ? As you can see, in my post just above (see cd /root/io-pkt),
I just copied libsocket.so in root/io-pkt is it not enough?
By the way, if there are other env vars to set, tell me. I am under the
impressions that all my problems come from there.



_______________________________________________
Builds
http://community.qnx.com/sf/go/post6202
Re: RE: RE: RE: io-pkt build problems.  
Hey guys 

The situation is improving, thanks to your counsels I managed to set up a staging directory and set up the env vars in 
the script .profile (adapting script Wei)
So ifconfig is ok, but when I try to launch io-pkt-v4-hc with

io-pkt-v4-hc -d i82544 -p tcpip

I get no results, though my computer is an intel simple core and I thought that was the good driver to open ethernet 
adapter with io-pkt.
Have you any idea bout why it doesn't work? 
Re: RE: RE: RE: io-pkt build problems.  
My ethernet adapter is actually an amd device (as it is shown by pci), maybe that's the reason why io-pkt-v4-hc is not 
working.
But which driver should I choose to open a io-pkt ethernet interface?
Is there one acutally in the trunk package?
Re: RE: RE: RE: io-pkt build problems.  
Ok, forget what I have said just above. 
I'll make a small resume.
Ifconfig: ok
give the result

lo0:......
SIOCGIADDRPREF: invalid argument

io-pkt-v4-hc: not ok  or ok ? I don't know
I have slayed io-net (by the way how do you "unslay" a process) with
slay io-net.
And now I want to launch an ethernet interface for my ethernet device which is AMD 79c970 (following infos given by pci)
. Following the site I need pcnet driver.
So with the instruction io-pkt-v4-hc -d pcnet -p tcpip it should be ok.
But it's not, with ifconfig I can see no wm0 interface, only lo0.
What can I do ?
RE: RE: RE: RE: io-pkt build problems.  
Nope.  Looks like things still aren't set up properly.  Just to make sure,
did you slay io-net as root?  This error would be typical if you used the
io-pkt ifconfig with io-net running.  Does pidin show that io-net is not
running?

In terms of the driver not being picked up, either you're LD_LIBRARY_PATH
doesn't include /lib/dll (which is where the legacy pcnet driver lives) or
that's the wrong driver for your hardware

Try 
io-pkt-v4-hc -d /lib/dll/devn-pcnet.so verbose -p tcpip

and 

sloginfo

and see if anything gets reported.






-----Original Message-----
From: j v [mailto:jeanmarieverret@gmail.com] 
Sent: Monday, March 31, 2008 4:34 AM
To: builds-networking
Subject: Re: RE: RE: RE: io-pkt build problems.

Ok, forget what I have said just above. 
I'll make a small resume.
Ifconfig: ok
give the result

lo0:......
SIOCGIADDRPREF: invalid argument

io-pkt-v4-hc: not ok  or ok ? I don't know
I have slayed io-net (by the way how do you "unslay" a process) with
slay io-net.
And now I want to launch an ethernet interface for my ethernet device which
is AMD 79c970 (following infos given by pci). Following the site I need
pcnet driver.
So with the instruction io-pkt-v4-hc -d pcnet -p tcpip it should be ok.
But it's not, with ifconfig I can see no wm0 interface, only lo0.
What can I do ?


_______________________________________________
Builds
http://community.qnx.com/sf/go/post6287
Re: RE: RE: RE: RE: io-pkt build problems.  
Thank you Robert
You just pointed out the good things.
Io-net was slayed but /lib/dll/ was not in the LD_LIBRARY_PATH.

Finally I need to check one thing, during the build I got one mistake,  cannot find "strlcpy.h" which is called in 
ftpcmd.y. Indeed this file is nowhere to be seen in my installation. After a bit of research on the internet, I found 
out that it belongs to the tcpreplay package.
I assumed, since it was linked to ftp protocol that this file was not necessary, so i just put in comments the 
instruction "#include "strlcpy.h" but am I right?
Do i have to install the tcpreplay package ,