Feed for discussion Builds in project Networking.

post119761: sshd buildfile configuration, QNX7.0, x86_64-generic.build

2019-06-18T06:59:31Z

Hi All:  Though this question has probably been dealt with many times, I cannot find the answer in any of the discussions nor documentation.

I'm trying to get sshd to start on boot.  I keep getting the message "sshd re-exec requires execution with an absolute path."  Once booted, I can start sshd from the command line with no problem.  But of course, I want it to start at boot.

Attached is the buildfile for the x86_64-generic.build file.  In it, we can see that the directories

/var/chroot

/var/chroot/sshd

have been created, that a link to /usr/sbin/sshd was created, an entry for sshd user and group were created in /etc/passwd and /etc/group, respectively, and there is an entry in the PAM configuration block for sshd (this last  was in the default configuration for the buildfile).

I have tried starting /usr/sbin/sshd in a script (net-start.sh) and elsewhere.  Does anyone know what important step I left out?

Thanks very much for your help!

post117377: Re: Compilation Error Building BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6

2017-01-24T19:16:13Z

Will,

Thank you for the patch file. It fixes my problems and the entire BSP now compiles and links.

post117376: Re: Compilation Error Building BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6

2017-01-24T17:59:14Z

Hi Donald,

I think this might be the package you're looking for:

http://community.qnx.com/sf/go/projects.bsp/frs.patches_and_updates_for_qnx_sdp.psp_networking_br660_be660_977_0

-Will

On 2017-01-23 7:54 PM, Donald Mies wrote:

> I found a copy of this file on the web and copied it but I'd much rather have an "official" file.

>

> After creating that file, I get another error compiling on the same file:

>

>      In file included from /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/bsd_media.c:20:0:

>      /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/i82544.h:132:31: fatal error: netdrvr/nic_mutex.h: No such file or directory

>

> So there is another header file missing:  netdrvr/nic_mutex.h

>

> I have not been able to find any copies of that on the web.

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post117374

> To cancel your subscription to this discussion, please e-mail builds-networking-unsubscribe@community.qnx.com

>

post117374: Re: Compilation Error Building BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6

2017-01-24T00:54:40Z

I found a copy of this file on the web and copied it but I'd much rather have an "official" file.

After creating that file, I get another error compiling on the same file:

    In file included from /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/bsd_media.c:20:0:

    /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/i82544.h:132:31: fatal error: netdrvr/nic_mutex.h: No such file or directory

So there is another header file missing:  netdrvr/nic_mutex.h

I have not been able to find any copies of that on the web.

post117373: Re: Compilation Error Building BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6

2017-01-24T00:10:34Z

Sorry - The error message got truncated by my cut/paste... It should read:

/home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/i82544.h:126:25: fatal error: netdrvr/ptp.h: No such file or directory

compilation terminated.

post117372: Compilation Error Building BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6

2017-01-23T23:27:45Z

After installing BSP_nexcom-vtc1010-x86_br-660_be-660_SVN807536_JBN6.zip and unzipping it, the build stops with the following error:



    In file included from /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/bsd_media.c:20:

    /home/dmies/qnx/bsp/vtc1010/src/hardware/devnp/e1000/i82544.h:126:25: fatal error: netdrvr

    compilation terminated.

I manually invoked "make" from the top level directory if that makes a difference (after sourcing qnx660-env.sh).

Tried downloading the latest devnp/e1000 driver patches (from PSP_networking_br660_be660-727_net-core-x86-exp.tar) but none of them appear to include the ptp.h file that is missing.

Any suggestions where I can find this missing file?

post115004: _KERNEL and QNXNTO mutually exclusive?

2015-11-13T19:56:28Z

I'm working on a packet filter using io-pkt, and through several other messages in various discussion boards, it seems that the _KERNEL flag is required to expose certain functions (some of the m_xxx functions for instance). However, sys/malloc.h specifically throws a warning message when both __QNXNTO__ and _KERNEL are defined. Is this actually an issue? I don't see where __QNXNTO__ is being defined (my guess is by qcc?). I have a feeling I'm missing something fundamental.

post112814: QNX SP1

2015-01-05T10:19:00Z

Hi

I have to develop on QNX 6.5.0 SP1

My current Momentix environment is for QNX 6.5.0

Is there something to do to upgrade my Momentix environment for QNX 6.5.0 SP1 ?

Thank

Olivier

post111395: [Compilation Errors] wpa supplicant for 6.5 tool chain for auto project

2014-08-13T01:32:58Z

Hi,

I am trying to compile wpa supplicant - http://community.qnx.com/sf/go/frs64817

Project: Partner - Qualcomm

Folder: wpa supplicant 2.0 from svn 6.5.0 branch - build #6

frs64817: DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6.zip

Created on 08/12/2014 by Roland Lassaline

for audi builds (6.5 tool chain) and running into the following compilation issues..

DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6/src/lib/io-pkt/dist/wpa_new/src/crypto/tls_openssl.c:2339: undefined reference to `SSL_export_keying_material'

cc: /local/mnt/workspace/mkhanna/QNX/CRM_QXA.QA.1.0-01459-APQ8064-1/qnx_ap/prebuilt_QNX650/host/linux/x86/usr/bin/ntoarm-ld error 1

make[3]: *** [/local/mnt/workspace/mkhanna/QNX/wpa_supplicant_2.0_from_6.5/DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6/src/lib/io-pkt/services/wpa_new/hostapd_new/arm/o.le.v7/hostapd_new] Error 1

make[3]: Leaving directory `/local/mnt/workspace/mkhanna/QNX/wpa_supplicant_2.0_from_6.5/DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6/src/lib/io-pkt/services/wpa_new/hostapd_new/arm/o.le.v7'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/local/mnt/workspace/mkhanna/QNX/wpa_supplicant_2.0_from_6.5/DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6/src/lib/io-pkt/services/wpa_new/hostapd_new/arm'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/local/mnt/workspace/mkhanna/QNX/wpa_supplicant_2.0_from_6.5/DRVR_wpa-2.0_br-650_be650SP1_SVN751492_JBN6/src/lib/io-pkt/services/wpa_new/hostapd_new'

I am able to successfully compile for 6.6 tool chain.

Can you help?

Thanks

Mohit

post106294: Re: access to source

2013-10-28T02:17:17Z

QNX source licensing policy has changed several years ago.

You need to work with either your sales or technical support contact to resolve this request.

On Oct 27, 2013, at 5:16 PM, Alexander Zaleskiy <community-noreply@qnx.com>

wrote:

> Hi. I try to find sample of io-net manager, which recommended in qnx article, but I can't get access to load, or even

> view it. When i try to load http://community.qnx.com/sf/scm/do/listRepositories/projects.networking/scm (this link from

> source guide), this message appears: "You do not have permission to view this page.

> If you feel you have received this message in error, please contact the TeamForge administrator." But i'm registered and

> even join project.

>

> Help me please, I'm in despair

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post106291

> To cancel your subscription to this discussion, please e-mail builds-networking-unsubscribe@community.qnx.com

post106291: access to source

2013-10-27T08:16:19Z

Hi. I try to find sample of io-net manager, which recommended in qnx article, but I can't get access to load, or even

view it. When i try to load http://community.qnx.com/sf/scm/do/listRepositories/projects.networking/scm (this link from

source guide), this message appears: "You do not have permission to view this page.

If you feel you have received this message in error, please contact the TeamForge administrator." But i'm registered and

even join project.

Help me please, I'm in despair

post105309: PRIMERA Pacific Rim watch online free megavideo HQ

2013-09-23T10:01:55Z

CLICK HERE TO WATCH NOW ===>>> http://goto3.info/watchhd.php?idm=13

Movies Online Pacific Rim

free movies online Pacific Rim

watch online fantasy Pacific Rim

fiction movies Pacific Rim

Pacific Rim , watch free online mego kinoo

Pacific Rim  2013 online

Pacific Rim  free download

Pacific Rim  Watch Online HD

watch a movie Pacific Rim

Watch online Pacific Rim

Watch a movie as a Pacific Rim  hd

Pacific Rim  watch online as 720p hd 2013

Pacific Rim  watch online HD

Pacific Rim  Watch online zerx

watch in hd quality Pacific Rim

Pacific Rim  watch free online mega thriller

Pacific Rim  full movie

Pacific Rim  movie torrent

Pacific Rim  Pacific Rim  Watch online

Pacific Rim  2013 watch online tnt

Pacific Rim  good quality

Pacific Rim  2013 as a 720 Pacific Rim  hd watch online

Pacific Rim  Watch online kz

Pacific Rim  on live TV

Watch Pacific Rim

post105308: gddhd

2013-09-23T09:57:53Z

[url=http://goto3.info/watchhd.php?idm=12/][img]http://s10.postimg.org/f5bbori95/ranger.png[/img][/url]

post105307: watch The Lone Ranger online free 1channel in high quality

2013-09-23T09:56:57Z

<a href='http://goto3.info/watchhd.php?idm=12' target='_blank'><img src='http://s9.postimg.org/as6csmkv3/ranger.png' border='0' alt="ranger" /></a>

watch The Lone Ranger novamov

watch The Lone Ranger megashare HQ

The Lone Ranger watch free online HDQ

watch The Lone Ranger online free viooz

The Lone Ranger watch online free megashare HQ

watch The Lone Ranger 1 channel 720P HD

The Lone Ranger free download movie HDQ

watch The Lone Ranger free viooz HD

The Lone Ranger watch movie

watch The Lone Ranger free online megashare

watch The Lone Ranger streaming HQ

watch The Lone Ranger free online HDQ

The Lone Ranger watch streaming HQ

watch The Lone Ranger full online HD

The Lone Ranger watch movie online free

free The Lone Ranger online HD

watch The Lone Ranger full movie free

The Lone Ranger watch free movie HQ

watch The Lone Ranger ipad 1080P HD

post105306: watch The Lone Ranger free online viooz HDQ )))"Koolll

2013-09-23T09:54:10Z

[url=http://goto3.info/watchhd.php?idm=12/][img]http://s10.postimg.org/f5bbori95/ranger.png[/img][/url]

<a href='http://goto3.info/watchhd.php?idm=12' target='_blank'><img src='http://s9.postimg.org/as6csmkv3/ranger.png' border='0' alt="ranger" /></a>

watch The Lone Ranger novamov

watch The Lone Ranger megashare HQ

The Lone Ranger watch free online HDQ

watch The Lone Ranger online free viooz

The Lone Ranger watch online free megashare HQ

watch The Lone Ranger 1 channel 720P HD

The Lone Ranger free download movie HDQ

watch The Lone Ranger free viooz HD

The Lone Ranger watch movie

watch The Lone Ranger free online megashare

watch The Lone Ranger streaming HQ

watch The Lone Ranger free online HDQ

The Lone Ranger watch streaming HQ

watch The Lone Ranger full online HD

The Lone Ranger watch movie online free

free The Lone Ranger online HD

watch The Lone Ranger full movie free

The Lone Ranger watch free movie HQ

watch The Lone Ranger ipad 1080P HD

watch The Lone Ranger on megashare 1080P HD

watch The Lone Ranger online free 1080P HD

watch The Lone Ranger online free 1channel in high quality

watch The Lone Ranger hd online

watch The Lone Ranger online free sockshare HD

watch The Lone Ranger hd online 1080P HD

watch The Lone Ranger movie free online HDQ

post99934: Re: socket

2013-03-15T13:35:00Z

You need to link against libsocket.

Sent from my BlackBerry 10 smartphone.

From: pooja chahal

Sent: Friday, March 15, 2013 6:49 AM

To: builds-networking

Reply To: builds-networking@community.qnx.com

Subject: socket

rval= socket(AF_INET, SOCK_RAW,6);

I am trying to make socket by using above function but it is showing error " undefined reference to Socket"

.What does it mean?How to solve it.

Thanks

_______________________________________________

Builds

http://community.qnx.com/sf/go/post99922

To cancel your subscription to this discussion, please e-mail builds-networking-unsubscribe@community.qnx.com

post99922: socket

2013-03-15T10:49:06Z

rval= socket(AF_INET, SOCK_RAW,6);

I am trying to make socket by using above function but it is showing error " undefined reference to Socket"

.What does it mean?How to solve it.

Thanks

post99339: inetd won't start

2013-02-19T12:42:35Z

I'm having a problem with getting inetd to start on my SabreLite arm target.  I hope someone can help.

A colleague as set up Momentics to build a bootable image for the board that works perfectly.  He used the Team Share facility to check the whole BSP project into our SVN server.  I then checked this out and attempted to build it myself.  What my PC creates is bootable on the target and is nearly working find... I can start up our application which uses the network interface, I can use Momentics to connect via the network to view the processes and download new code, but I can't use FTP or TELNET to talk to the target because the inetd server hasn't started up.

If I try to start inetd from the command line, with the diagnostic "-d" option, nothing happens.  No error messages, no diagnostics, nothing is logged to slogger.  I simply don't get an inetd process in the process table.

The /etc/inet.conf, /etc/passwd etc files are identical to when my colleague builds the image.  It just doesn't want to work for me.

Any ideas?

post98787: QNX 6.5.0 + openPowerlink

2013-01-25T13:37:51Z

Hello everybody!

I need to use Ethernet PowerLink in QNX. Unfortunaly i have not any expirience with Powerlink and QNX. I've downloaded QNX 6.5.0 and openPowerlink from here http://sourceforge.net/projects/openpowerlink/

Tryed to compile it and got "cc: unknown option: -std=c99" error. My compiler is gcc-4.4.2. So, my questions is:

1. Could anybody help me to compile it?

2. Is it possible to use openPowerlink in QNX?

3. Is there any other soft or libs which allows to use powerlink in QNX?

post86891: Re: cannot get qnx 6.4.x networking source code using svn ... hmmm ...

2011-06-28T02:58:26Z

they deleted us :o

post84177: Re: cannot get qnx 6.4.x networking source code using svn ... hmmm ...

2011-03-22T15:45:21Z

Hello,

I tried to get the latest and greatest 6.4.x networking source code with svn. It does not work ... hmmm ...

I get:

"...

# pwd

.../6.4.0/trunk

# svn checkout --username [...] http://community.qnx.com/svn/repos/core_networking/branches/6.4.0/trunk

Authentication realm: <http://community.qnx.com:80> Authorization Realm Password for '[...]':

svn: PROPFIND request failed on '/svn/repos/core_networking/branches/6.4.0/trunk'

svn: PROPFIND of '/svn/repos/core_networking/branches/6.4.0/trunk': 403 Forbidden (http://community.qnx.com) # ..."

I did type in the password correctly. What could be the problem??

Andor

3/22/2011

post77961: Newbie: Couldn't download svn 6.4.0 GA code

2010-12-08T21:51:00Z

Hello,

I joined core-networking project recently.

I could not download 6.4.0 GA (or any other) from SVN. I get following errors

$ svn checkout --username myusername http://community.qnx.com/svn/repos/core_networking/tags/6.4.0/GA

Authentication realm: <http://community.qnx.com:80> Authorization Realm

Password for 'subodh.harmalkar@jhuapl.edu':

svn: PROPFIND request failed on '/svn/repos/core_networking/tags/6.4.0/GA'

svn: PROPFIND of '/svn/repos/core_networking/tags/6.4.0/GA': 403 Forbidden (http://community.qnx.com)

Is this due to any firewall issue on my side? I am using the same password I used to logging into the project.

Thanks.

post63326: Re: SNMP agent

2010-08-17T20:11:19Z

well i have a limitation, and am kind of stuck with 6.3.0.

will this work with 6.3.0?

post63322: Re: SNMP agent

2010-08-17T19:57:45Z

Check out this page:

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

6.3.0 is pretty old. You may have better luck on 6.4.1 or later.

Regards,

-seanb

On Tue, Aug 17, 2010 at 03:51:54PM -0400, Rashid Mirza wrote:

> guys, i have been trying to work with net-snmp-5.2.6, on a QNX momentics 6.3.0 platform.

> Been trying to follow the :

> a)./configure

> b)make

> c) make install

>

> Problems started when i was doing a make. Always i was getting libtools error:

>

> od: illegal option -x

>

> and termination in the compile process.

>

> I then changed my libtools, to version 2.2.4.

> Compilation seems better, but it reached:

>

> mibII/at.c: In function 'AP_Scan_Next':

> mibII/at.c:796: arithmetic on pointer to an incomplete type

> mibII/at.c:799: dereferencing pointer to incomplete type

> mibII/at.c: 801: 'ifIndex' undeclared (first use in function)

>

>

> is it worth spending time on this, to get net-snmp work on QNX or should i stop here?

> waiting for your comments and suggestions..

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post63319

>

post63319: Re: SNMP agent

2010-08-17T19:51:54Z

guys, i have been trying to work with net-snmp-5.2.6, on a QNX momentics 6.3.0 platform.

Been trying to follow the :

a)./configure

b)make

c) make install

Problems started when i was doing a make. Always i was getting libtools error:

od: illegal option -x

and termination in the compile process.

I then changed my libtools, to version 2.2.4.

Compilation seems better, but it reached:

mibII/at.c: In function 'AP_Scan_Next':

mibII/at.c:796: arithmetic on pointer to an incomplete type

mibII/at.c:799: dereferencing pointer to incomplete type

mibII/at.c: 801: 'ifIndex' undeclared (first use in function)

is it worth spending time on this, to get net-snmp work on QNX or should i stop here?

waiting for your comments and suggestions..

post63046: SNMP agent

2010-08-16T09:35:12Z

i would like to have a SNMP agent runing on a QNX Neutrino RTOS runtime 6.3.0 platform.

1) is this possible on this platform?

2) i wanted to use net-snmp-5.2.X.tar.gz, but ran into several errors ( this was on a QNX momentics 6.3.0 platform)

3) i have come across mentions of Emanate, Emanate/Lite in the neutrino documentation, but this needs to be purchased (dont know the costs as yet)

4) is there a free version of the agent that will work smoothly on the QNX Neutrino RTOS runtime 6.3.0 platform (am i asking for too much?!)

post47520: Re: RE: error building core_networking

2010-02-17T15:25:59Z

The libSocket.so is not a new one. But libCrypto.so.2 is with the new timestamp.

post47518: RE: error building core_networking

2010-02-17T15:19:54Z

I started the make CPULIST=ppc install from the io-pkt dir.

But the libSocket.so exists with new timestamps in my C:\qnx641\.... folder.

/LSkov

-----Original Message-----

From: Sean Boudreau [mailto:community-noreply@qnx.com]

Sent: 17. februar 2010 15:17

To: builds-networking

Subject: Re: error building core_networking

Build libsocket and libcrypto first.

If you do a 'make CPULIST="ppc" install'

from the root things should be built in

the correct order. It looks like you're

starting from the services directory.

Make sure you have a staging area set up

first.

-seanb

On Wed, Feb 17, 2010 at 04:09:29AM -0500, Lasse Skov wrote:

> I also got an error if i try to build core_networking.

>

> make CPULIST=ppc install

_______________________________________________

Builds

http://community.qnx.com/sf/go/post47501

post47501: Re: error building core_networking

2010-02-17T14:16:37Z

Build libsocket and libcrypto first.

If you do a 'make CPULIST="ppc" install'

from the root things should be built in

the correct order. It looks like you're

starting from the services directory.

Make sure you have a staging area set up

first.

-seanb

On Wed, Feb 17, 2010 at 04:09:29AM -0500, Lasse Skov wrote:

> I also got an error if i try to build core_networking.

>

> make CPULIST=ppc install

post47481: Re: error building core_networking

2010-02-17T09:09:29Z

I also got an error if i try to build core_networking.

make CPULIST=ppc install

make -j 1 -Cbind -fMakefile install

make[2]: Entering directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind'

make -j 1 -Ccheck -fMakefile install

make[3]: Entering directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check'

make -j 1 -Cnamed-checkconf -fMakefile install

make[4]: Entering directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf'

make -j 1 -Cppc -fMakefile install

make[5]: Entering directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc'

make -j 1 -Co.be -fMakefile install

make[6]: Entering directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be'

C:/QNX641/host/win32/x86/usr/bin/qcc -Vgcc_ntoppc -c -O -Wc,-Wall -Wc,-Wno-parentheses   -DNS_LOCALSTATEDIR='\"/var\"' -DNS_SYSCONFDIR='\"/etc\"' -DVE

RSION='\"9.6.1-P2\"' -DWANT_IPV6 -DOPENSSL -DISC_PLATFORM_USETHREADS -DNAMED_CONFFILE='\"/etc/named.conf\"' -DNDEBUG   -I. -ID:/SVN-DRIVE/QNX/core_net

working/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc

-ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist

/bin/check -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/li

b/dns/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/dns/unix/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/

external/bsd/bind/dist/lib/isc/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isc/unix/include -ID:/SVN-DRIVE/QNX/co

re_networking/lib/io-pkt/external/bsd/bind/dist/lib/bind9/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isccfg/incl

ude -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isccc/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/

bind/dist/lib/lwres/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/lwres/unix/include -ID:/SVN-DRIVE/QNX/core_networ

king/lib/io-pkt/external/bsd/bind/dist/lib/dns/sec/dst/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isc/pthreads/i

nclude -IC:/QNX641/target/qnx6/usr/include    -EB    -DVARIANT_be -DBUILDENV_qss  D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/b

in/check/check-tool.c

C:/QNX641/host/win32/x86/usr/bin/qcc -Vgcc_ntoppc -c -O -Wc,-Wall -Wc,-Wno-parentheses   -DNS_LOCALSTATEDIR='\"/var\"' -DNS_SYSCONFDIR='\"/etc\"' -DVE

RSION='\"9.6.1-P2\"' -DWANT_IPV6 -DOPENSSL -DISC_PLATFORM_USETHREADS -DNAMED_CONFFILE='\"/etc/named.conf\"' -DNDEBUG   -I. -ID:/SVN-DRIVE/QNX/core_net

working/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc

-ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist

/bin/check -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/li

b/dns/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/dns/unix/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/

external/bsd/bind/dist/lib/isc/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isc/unix/include -ID:/SVN-DRIVE/QNX/co

re_networking/lib/io-pkt/external/bsd/bind/dist/lib/bind9/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isccfg/incl

ude -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isccc/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/

bind/dist/lib/lwres/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/lwres/unix/include -ID:/SVN-DRIVE/QNX/core_networ

king/lib/io-pkt/external/bsd/bind/dist/lib/dns/sec/dst/include -ID:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/lib/isc/pthreads/i

nclude -IC:/QNX641/target/qnx6/usr/include    -EB    -DVARIANT_be -DBUILDENV_qss  D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/external/bsd/bind/dist/b

in/check/named-checkconf.c

C:/QNX641/host/win32/x86/usr/bin/rm -f  D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be/named-checkconf

C:/QNX641/host/win32/x86/usr/bin/qcc -Vgcc_ntoppc -Wl,--no-keep-memory   -oD:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-check

conf/ppc/o.be/named-checkconf    check-tool.o    named-checkconf.o   -L . -L C:/QNX641/target/qnx6/ppcbe/lib -L C:/QNX641/target/qnx6/ppcbe/usr/lib  -

Wl,--rpath-link . -Wl,--rpath-link C:/QNX641/target/qnx6/ppcbe/lib -Wl,--rpath-link C:/QNX641/target/qnx6/ppcbe/usr/lib   -lbind9    -ldns    -llwres

   -lisccfg    -lisccc    -lisc   -Bstatic -lnbutil -Bdynamic   -lcrypto   -EB

C:\QNX641\host\win32\x86\usr\bin\ntoppc-ld: warning: libsocket.so.2, needed by C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so, not found (try using

-rpath or -rpath-link)

check-tool.o: In function `checksrv':

check-tool.c:(.text+0x630): undefined reference to `getaddrinfo'

check-tool.c:(.text+0x718): undefined reference to `freeaddrinfo'

check-tool.c:(.text+0x784): undefined reference to `gai_strerror'

check-tool.o: In function `checkmx':

check-tool.c:(.text+0x898): undefined reference to `getaddrinfo'

check-tool.c:(.text+0x980): undefined reference to `freeaddrinfo'

check-tool.c:(.text+0x9ec): undefined reference to `gai_strerror'

check-tool.o: In function `checkns':

check-tool.c:(.text+0xc40): undefined reference to `getaddrinfo'

check-tool.c:(.text+0xd58): undefined reference to `gai_strerror'

check-tool.c:(.text+0x10d0): undefined reference to `freeaddrinfo'

C:/QNX641/target/qnx6/ppcbe/lib\libdns.a(rdata.o): In function `fromtext_in_wks':

rdata.c:(.text+0x26a68): undefined reference to `getprotobyname'

rdata.c:(.text+0x26bec): undefined reference to `getservbyname'

rdata.c:(.text+0x26c08): undefined reference to `getservbyname'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(entropy.o): In function `isc_entropy_createfilesource':

entropy.c:(.text+0x5f4): undefined reference to `connect'

entropy.c:(.text+0x7b4): undefined reference to `socket'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(entropy.o): In function `fillpool':

entropy.c:(.text+0x2718): undefined reference to `sendto'

entropy.c:(.text+0x279c): undefined reference to `sendto'

entropy.c:(.text+0x2820): undefined reference to `recvfrom'

entropy.c:(.text+0x28ac): undefined reference to `recv'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(netaddr.o): In function `isc_netaddr_any6':

netaddr.c:(.text+0x2a2): undefined reference to `in6addr_any'

netaddr.c:(.text+0x2a6): undefined reference to `in6addr_any'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(netscope.o): In function `isc_netscope_pton':

netscope.c:(.text+0x44): undefined reference to `if_nametoindex'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(sockaddr.o): In function `isc_sockaddr_any6':

sockaddr.c:(.text+0x14a): undefined reference to `in6addr_any'

sockaddr.c:(.text+0x14e): undefined reference to `in6addr_any'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_ipv6only':

socket.c:(.text+0x7e8): undefined reference to `setsockopt'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_getsockname':

socket.c:(.text+0x12e4): undefined reference to `getsockname'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_connect':

socket.c:(.text+0x1850): undefined reference to `connect'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_listen':

socket.c:(.text+0x1d20): undefined reference to `listen'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_cleanunix':

socket.c:(.text+0x239c): undefined reference to `socket'

socket.c:(.text+0x24c8): undefined reference to `connect'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `doio_send':

socket.c:(.text+0x2848): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x2850): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x2858): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x2860): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x28c8): undefined reference to `__cmsg_alignbytes'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o):socket.c:(.text+0x28d0): more undefined references to `__cmsg_alignbytes' follow

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `doio_send':

socket.c:(.text+0x2938): undefined reference to `sendmsg'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `doio_recv':

socket.c:(.text+0x397c): undefined reference to `recvmsg'

socket.c:(.text+0x3dcc): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x3dd4): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x3e7c): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x3e84): undefined reference to `__cmsg_alignbytes'

socket.c:(.text+0x3eb8): undefined reference to `__cmsg_alignbytes'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o):socket.c:(.text+0x3ec0): more undefined references to `__cmsg_alignbytes' follow

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `isc_socket_bind':

socket.c:(.text+0x54c8): undefined reference to `setsockopt'

socket.c:(.text+0x5524): undefined reference to `bind'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `opensocket':

socket.c:(.text+0x575c): undefined reference to `socket'

socket.c:(.text+0x5774): undefined reference to `socket'

socket.c:(.text+0x578c): undefined reference to `socket'

socket.c:(.text+0x5a58): undefined reference to `setsockopt'

socket.c:(.text+0x5b20): undefined reference to `setsockopt'

socket.c:(.text+0x5bac): undefined reference to `setsockopt'

socket.c:(.text+0x5bd0): undefined reference to `getsockopt'

socket.c:(.text+0x5c0c): undefined reference to `setsockopt'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `internal_accept':

socket.c:(.text+0x796c): undefined reference to `accept'

C:/QNX641/target/qnx6/ppcbe/lib\libisc.a(socket.o): In function `internal_connect':

socket.c:(.text+0x8f1c): undefined reference to `getsockopt'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `gethostbyname@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `getsockopt@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `recvfrom@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `getservbyname@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `shutdown@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `connect@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `socket@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `accept@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `listen@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `bind@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `setsockopt@libsocket.so.2'

C:/QNX641/target/qnx6/ppcbe/usr/lib/libcrypto.so: undefined reference to `sendto@libsocket.so.2'

cc: C:/QNX641/host/win32/x86/usr/bin/ntoppc-ld caught signal 1

make[6]: *** [D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be/named-checkconf] Error 1

make[6]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc/o.be'

make[5]: *** [install] Error 2

make[5]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf/ppc'

make[4]: *** [install] Error 2

make[4]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check/named-checkconf'

make[3]: *** [install] Error 2

make[3]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind/check'

make[2]: *** [install] Error 2

make[2]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services/bind'

make[1]: *** [install] Error 2

make[1]: Leaving directory `D:/SVN-DRIVE/QNX/core_networking/lib/io-pkt/services'

make: *** [install] Error 2

Anyone know how to solve this?

/LSkov

post46863: Re: error building core_networking

2010-02-08T21:44:31Z

Oh wait, that won't help.

I just looked at your build error and those symbols are in hw/sysinfo.h

for 6.4.1. It's likely that they aren't present in 6.4.0.

/P

> Hi,

> I'm trying to build latest core networking source on QNX6.4.0. I setup a staging environment, and use "make CPULIST=x86 install". Any suggestions on this?

>

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c: In function '_resolve_synonyms':

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: 'HWI_TAG_NAME_synonym' undeclared (first use in this function)

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: (Each undeclared identifier is reported only once

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: for each function it appears in.)

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:94: error: 'MAX_SYNONYM_COUNT' undeclared (first use in this function)

> /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:97: error: 'hwi_tag' has no member named 'synonym'

> cc: /usr/qnx640/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4/cc1 error 1

> make[5]: *** [hwi_find.o] Error 1

> make[5]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a'

> make[4]: *** [install] Error 2

> make[4]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86'

> make[3]: *** [install] Error 2

> make[3]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr'

> make[2]: *** [install] Error 2

> make[2]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib'

> make[1]: *** [install] Error 2

> make[1]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys'

> make: *** [install] Error 2

>

>

post46862: Re: error building core_networking

2010-02-08T21:40:22Z

On 08/02/10 04:19 PM, David Terry wrote:

> Hi,

> I'm trying to build latest core networking source on QNX6.4.0. I setup a staging environment, and use "make CPULIST=x86 install". Any suggestions on this

Does this post help?

http://community.qnx.com/sf/go/topc11935

/P

post46859: error building core_networking

2010-02-08T21:19:52Z

Hi,

I'm trying to build latest core networking source on QNX6.4.0. I setup a staging environment, and use "make CPULIST=x86 install". Any suggestions on this?

make[5]: Entering directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a'

/usr/qnx640/host/qnx6/x86/usr/bin/qcc -Vgcc_ntox86 -c -Wc,-Wall -Wc,-Wno-parentheses  -O -DNDEBUG   -I. -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86 -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr -I/home/terryd/core_network2/lib/io-pkt/sys -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/public -I/home/terryd/stage/usr/include -I/usr/qnx640/target/qnx6/usr/include       -DVARIANT_a -DBUILDENV_qss  /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/crc.c

/usr/qnx640/host/qnx6/x86/usr/bin/qcc -Vgcc_ntox86 -c -Wc,-Wall -Wc,-Wno-parentheses  -O -DNDEBUG   -I. -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86 -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr -I/home/terryd/core_network2/lib/io-pkt/sys -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/public -I/home/terryd/stage/usr/include -I/usr/qnx640/target/qnx6/usr/include       -DVARIANT_a -DBUILDENV_qss  /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/dma.c

/usr/qnx640/host/qnx6/x86/usr/bin/qcc -Vgcc_ntox86 -c -Wc,-Wall -Wc,-Wno-parentheses  -O -DNDEBUG   -I. -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86 -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr -I/home/terryd/core_network2/lib/io-pkt/sys -I/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/public -I/home/terryd/stage/usr/include -I/usr/qnx640/target/qnx6/usr/include       -DVARIANT_a -DBUILDENV_qss  /home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c: In function '_resolve_synonyms':

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: 'HWI_TAG_NAME_synonym' undeclared (first use in this function)

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: (Each undeclared identifier is reported only once

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:92: error: for each function it appears in.)

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:94: error: 'MAX_SYNONYM_COUNT' undeclared (first use in this function)

/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/hwi_find.c:97: error: 'hwi_tag' has no member named 'synonym'

cc: /usr/qnx640/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4/cc1 error 1

make[5]: *** [hwi_find.o] Error 1

make[5]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86/a'

make[4]: *** [install] Error 2

make[4]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr/x86'

make[3]: *** [install] Error 2

make[3]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib/libdrvr'

make[2]: *** [install] Error 2

make[2]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys/lib'

make[1]: *** [install] Error 2

make[1]: Leaving directory `/home/terryd/core_network2/lib/io-pkt/sys'

make: *** [install] Error 2

post46553: External header file dependencies of the day

2010-02-04T16:21:08Z

To build right now you'll need new sys/dcmd_misc.h, sys/iomsg.h in your stage.

You can get them from the CoreOS repository (in lib/c/public/):

http://community.qnx.com/sf/scm/do/listRepositories/projects.core_os/scm

To build e1000 and rtl18169 drivers you'll also need a new hw/pci.h. For now, just put Makefile.dnm to avoid building them.

See also http://community.qnx.com/sf/go/topc11930

/P

post43746: Re: Compilation warnings while include

2009-12-12T15:54:08Z

On Sat, Dec 12, 2009 at 05:11:44AM -0500, Senthil K wrote:

> Hi,

>

> I have compiled the network driver with the compilation flags -DKERNEL and -Wshadow(Mandatory flag).

>

> In my c file i included <io-pkt/iopkt_driver.h>.

>

> But i m getting the below warnings.

>

> Please tell me how to resolve the warnings.

>

We don't compile our stuff with that flag so that's an unsupported

configuration.  To get rid of it you'll have to:

- turn off that flag.

- edit libkern.h

- gcc has various -fno-builtin-* options.  Check the gcc docs

  to see if there's ones for the functions in question here.

Regards,

-seanb

post43744: Compilation warnings while include

2009-12-12T10:11:43Z

Hi,

I have compiled the network driver with the compilation flags -DKERNEL and -Wshadow(Mandatory flag).

In my c file i included <io-pkt/iopkt_driver.h>.

But i m getting the below warnings.

Please tell me how to resolve the warnings.

In file included from C:/QNX641/target/qnx6/usr/include/io-pkt/sys/systm.h:328,

                 from C:/QNX641/target/qnx6/usr/include/io-pkt/iopkt_driver.h:35,

                 from ./includes/pedriver.h:20,

                 from src/pedriver.c:17:

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:82: warning: declaration of 'abs' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:84: warning: declaration of 'isspace' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:85: warning: declaration of 'isascii' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:86: warning: declaration of 'isupper' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:87: warning: declaration of 'islower' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:88: warning: declaration of 'isalpha' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:89: warning: declaration of 'isdigit' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:90: warning: declaration of 'isxdigit' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:91: warning: declaration of 'toupper' shadows a built-in function

C:/QNX641/target/qnx6/usr/include/io-pkt/lib/libkern/libkern.h:92: warning: declaration of 'tolower' shadows a built-in function

Thanks and Regards

K.Senthil

post43300: Linking third party library xx.so file with network driver(devnp-xx.so).

2009-12-07T16:11:26Z

Hi,

I have a third party library in the format of xx.so.I want to invoke a function a from third party library in mynetwork driver ( devnp-xx.so).

so can you please tell me how to link xx.so(third party library) in to my network dirver(devnp-xx.so).

1.Where i have to place my xx.so (third party library) in QNX host for compilation?

2.How to add to link xx.so (third party library) in make file?

Please help me on this....

Thanks and Regards

K.Senthil

post42626: Error while compiling network driver in QNX monetics

2009-11-26T10:23:08Z

Hi,

I m trying to compile my network driver in momentics.I include <io-pkt/iopkt_driver.h> file.It throws the following error.

C:/QNX641/target/qnx6/usr/include/io-pkt/dev/mii/miivar.h:82: error: field 'mii_media' has incomplete type

Please help me on this.

Thanks and Regards

K.Senthil

Error Logs

======

########## Compiling code in devnp-pe.so ##########

qcc -g -c -M -V gcc_ntox86 -DHOST -w9 -Wpointer-arith -Wshadow -DBUILD_TIME='Thu Nov 26 15:51:55 IST 2009' -DPRIVATE_LABEL='' -DTARGET_x86 -IC:/ide-4.6-workspace/includes -I./includes -IC:/ide-4.6-workspace/software/includes -IC:/ide-4.6-workspace/ThirdParty/libxml2/include -IC:/ide-4.6-workspace/ThirdParty/curl/usr/include -IC:/ide-4.6-workspace/includes -IC:/ide-4.6-workspace/common IC:/QNX641/target/qnx6/usr/include/io-pkt -DNDEBUG -DVARIANT_dll -DBUILDENV_qss -shared -o objs/x86/pedriver.o -c src/pedriver.c

In file included from C:/QNX641/target/qnx6/usr/include/io-pkt/iopkt_driver.h:65,

from src/pedriver.c:16:

C:/QNX641/target/qnx6/usr/include/io-pkt/dev/mii/miivar.h:82: error: field 'mii_media' has incomplete type

post42219: Re: Compilation error - while compile mpc85xx code in QNX Core Networking source code

2009-11-19T10:42:34Z

Hi Sean,

Thanks a lot,Now we are able to compile the mpc85xx code.

Thanks and Regards

K.Senthil

post42150: Re: Compilation error - while compile mpc85xx code in QNX Core Networking source code

2009-11-18T14:13:47Z

This header should be installed for you when you

'make install' from io-pkt/sys/lib/libstartup.

If not you can also get it from the hw/bsp project:

http://community.qnx.com/svn/repos/bsp/trunk/hardware/startup/lib/public/hw

-seanb

On Wed, Nov 18, 2009 at 07:17:45AM -0500, Senthil K wrote:

> Hi

>

> I have compiled the mpc85xx network driver in the QNX Host using QNX Networking source code.

>

> I have entered /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx directory and i gave

>

> make CPULIST=ppc

>

> The following are the erros while buliding network driver

> =================================

>

> # make CPULIST=ppc

>

> make -j 1 -Cppc -fMakefile

>

> make[1]: Entering directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc'

>

> make -j 1 -Cdll.be -fMakefile

>

> make[2]: Entering directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be'

>

> /usr/qnx641/host/qnx6/x86/usr/bin/qcc -Vgcc_ntoppc -c -O -Wc,-Wall -Wc,-Wno-parentheses -D_KERNEL -fno-builtin-log -DNDEBUG -I. -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx -I/usr/qnx641/target/qnx6/usr/include/io-pkt -I/usr/qnx641/target/qnx6/usr/include/io-pkt/sys-nto -I/usr/qnx641/target/qnx6/usr/include/io-pkt -I/usr/qnx641/target/qnx6/usr/include/io-pkt/sys-nto -I/sys -I/sys/sys-nto -I/lib/socket/public -I/usr/qnx641/target/qnx6/usr/include -EB -shared -DVARIANT_dll -DVARIANT_be -DBUILDENV_qss /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:24:28: error: hw/hwinfo_85xx.h: No such file or directory

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c: In function 'ppc8xxx_get_syspage_params':

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: 'PPC85xx_HWI_eTSEC' undeclared (first use in this function)

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: (Each undeclared identifier is reported only once

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: for each function it appears in.)

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1341: warning: implicit declaration of function 'hwitag_find_nicaddr'

>

> /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1345: warning: implicit declaration of function 'hwitag_find_phyaddr'

>

> cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/powerpc-unknown-nto-qnx6.4.0/4.3.3/cc1 error 1

>

> make[2]: *** [detect.o] Error 1

>

> make[2]: Leaving directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be'

>

> make[1]: *** [all] Error 2

>

> make[1]: Leaving directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc'

>

> make: *** [all] Error 2

>

>

> Please help on this issue.

>

>

> Thanks and Regards

> K.Senthil

>

>

>

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post42140

>

post42140: Compilation error - while compile mpc85xx code in QNX Core Networking source code

2009-11-18T12:17:41Z

Hi

I have compiled the mpc85xx network driver in the QNX Host using QNX Networking source code.

I have entered /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx directory and i gave

make CPULIST=ppc

The following are the erros while buliding network driver

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

# make CPULIST=ppc

make -j 1 -Cppc -fMakefile

make[1]: Entering directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc'

make -j 1 -Cdll.be -fMakefile

make[2]: Entering directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be'

/usr/qnx641/host/qnx6/x86/usr/bin/qcc -Vgcc_ntoppc -c -O -Wc,-Wall -Wc,-Wno-parentheses -D_KERNEL -fno-builtin-log -DNDEBUG -I. -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc -I/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx -I/usr/qnx641/target/qnx6/usr/include/io-pkt -I/usr/qnx641/target/qnx6/usr/include/io-pkt/sys-nto -I/usr/qnx641/target/qnx6/usr/include/io-pkt -I/usr/qnx641/target/qnx6/usr/include/io-pkt/sys-nto -I/sys -I/sys/sys-nto -I/lib/socket/public -I/usr/qnx641/target/qnx6/usr/include -EB -shared -DVARIANT_dll -DVARIANT_be -DBUILDENV_qss /home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:24:28: error: hw/hwinfo_85xx.h: No such file or directory

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c: In function 'ppc8xxx_get_syspage_params':

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: 'PPC85xx_HWI_eTSEC' undeclared (first use in this function)

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: (Each undeclared identifier is reported only once

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1325: error: for each function it appears in.)

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1341: warning: implicit declaration of function 'hwitag_find_nicaddr'

/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/detect.c:1345: warning: implicit declaration of function 'hwitag_find_phyaddr'

cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/powerpc-unknown-nto-qnx6.4.0/4.3.3/cc1 error 1

make[2]: *** [detect.o] Error 1

make[2]: Leaving directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc/dll.be'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/senthil/QNX_6.4.1/sys/dev_qnx/mpc85xx/ppc'

make: *** [all] Error 2

Please help on this issue.

Thanks and Regards

K.Senthil

post42094: Re: Strange library loading issue (first posted in general)

2009-11-17T16:21:48Z

Yes.  One of the things mkxfs does is manipulate the physaddr field (that's how it does the

use-in-place stuff).

Liam Howlett wrote:

> Looking at the headers, there is a difference between the stripped and orig library.

>

>

>

> $ ntoppc-readelf -l liboamlib.so.orig

>

> Elf file type is DYN (Shared object file)

> Entry point 0x203c4

> There are 4 program headers, starting at offset 52

>

> Program Headers:

>   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

>   LOAD           0x000000 0x00000000 0x00000000 0x66ca0 0x66ca0 R E 0x1000

>   LOAD           0x066ca0 0x00067ca0 0x00067ca0 0x04884 0x06360 RWE 0x1000

>   DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

>   NOTE           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

>

>  Section to Segment mapping:

>   Segment Sections...

>    00     .hash .dynsym .dynstr .gnu.version .gnu.version_d .rela.data .rela.fixup .rela.gnu.linkonce.s._ZTISt9streambuf .rela.gnu.linkonce.s._ZTI20CIdNameLookupFunctor .rela.gnu.linkonce.s._ZTI16CManagementModel .rela.gnu.linkonce.s._ZTI22CMOAttributeDescriptor .rela.gnu.linkonce.s._ZTI15CTypeDescriptor .rela.gnu.linkonce.s._ZTI9CCallback .rela.gnu.linkonce.s._ZTIN3app15CXAciProtocolIfE .rela.gnu.linkonce.s._ZTI21CLightManagementModel .rela.got .rela.ctors .rela.dtors .rela.plt .rela.sdata .text .init .fini .rodata .gnu.linkonce.s._ZTSSt3ios .gnu.linkonce.s._ZTS6CDbmIf .gnu.linkonce.s._ZTS3CDn

>    01     .data .gnu.linkonce.s._ZTISt9streambuf .gnu.linkonce.s._ZN15SingletonHolderI28COamAttributeIdLookupFunctor14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTI20CIdNameLookupFunctor .gnu.linkonce.s._ZTI16CManagementModel .gnu.linkonce.s._ZTI22CMOAttributeDescriptor .gnu.linkonce.s._ZTI15CTypeDescriptor .gnu.linkonce.s._ZTI9CCallback .gnu.linkonce.s._ZN15SingletonHolderI12CSyncHandler14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTIN3app15CXAciProtocolIfE .gnu.linkonce.s._ZN15SingletonHolderI30CGeneratedLightManagementModel14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZN15SingletonHolderI25CGeneratedManagementModel14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTI21CLightManagementModel .dynamic .ctors .dtors .fixup .got .sdata .sbss .plt .bss

>    02     .dynamic

>    03

>

>

>

> And

>

>

> $ ntoppc-readelf -l liboamlib.so.stripped

>

> Elf file type is DYN (Shared object file)

> Entry point 0x203c4

> There are 4 program headers, starting at offset 52

>

> Program Headers:

>   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

>   LOAD           0x000000 0x00000000 0x00a8d000 0x66ca0 0x66ca0 R E 0x1000

>   LOAD           0x066ca0 0x00067ca0 0x00af3ca0 0x04884 0x06360 RWE 0x1000

>   DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

>   NULL           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

>

>

> Notice the orig has the first line:

> LOAD           0x000000 0x00000000 0x00000000 0x66ca0 0x66ca0 R E 0x1000

>

> The stripped reads:

> LOAD           0x000000 0x00000000 0x00a8d000 0x66ca0 0x66ca0 R E 0x1000

>

> Is it normal for the stripped header to have a PhysAddr different than the orig?

>

>

>

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post42091

>

--

cburgess@qnx.com

post42091: Re: Strange library loading issue (first posted in general)

2009-11-17T15:49:15Z

Looking at the headers, there is a difference between the stripped and orig library.

$ ntoppc-readelf -l liboamlib.so.orig

Elf file type is DYN (Shared object file)

Entry point 0x203c4

There are 4 program headers, starting at offset 52

Program Headers:

  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

  LOAD           0x000000 0x00000000 0x00000000 0x66ca0 0x66ca0 R E 0x1000

  LOAD           0x066ca0 0x00067ca0 0x00067ca0 0x04884 0x06360 RWE 0x1000

  DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

  NOTE           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

Section to Segment mapping:

  Segment Sections...

   00     .hash .dynsym .dynstr .gnu.version .gnu.version_d .rela.data .rela.fixup .rela.gnu.linkonce.s._ZTISt9streambuf .rela.gnu.linkonce.s._ZTI20CIdNameLookupFunctor .rela.gnu.linkonce.s._ZTI16CManagementModel .rela.gnu.linkonce.s._ZTI22CMOAttributeDescriptor .rela.gnu.linkonce.s._ZTI15CTypeDescriptor .rela.gnu.linkonce.s._ZTI9CCallback .rela.gnu.linkonce.s._ZTIN3app15CXAciProtocolIfE .rela.gnu.linkonce.s._ZTI21CLightManagementModel .rela.got .rela.ctors .rela.dtors .rela.plt .rela.sdata .text .init .fini .rodata .gnu.linkonce.s._ZTSSt3ios .gnu.linkonce.s._ZTS6CDbmIf .gnu.linkonce.s._ZTS3CDn

   01     .data .gnu.linkonce.s._ZTISt9streambuf .gnu.linkonce.s._ZN15SingletonHolderI28COamAttributeIdLookupFunctor14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTI20CIdNameLookupFunctor .gnu.linkonce.s._ZTI16CManagementModel .gnu.linkonce.s._ZTI22CMOAttributeDescriptor .gnu.linkonce.s._ZTI15CTypeDescriptor .gnu.linkonce.s._ZTI9CCallback .gnu.linkonce.s._ZN15SingletonHolderI12CSyncHandler14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTIN3app15CXAciProtocolIfE .gnu.linkonce.s._ZN15SingletonHolderI30CGeneratedLightManagementModel14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZN15SingletonHolderI25CGeneratedManagementModel14CreateUsingNewE10mpInstanceE .gnu.linkonce.s._ZTI21CLightManagementModel .dynamic .ctors .dtors .fixup .got .sdata .sbss .plt .bss

   02     .dynamic

   03

And

$ ntoppc-readelf -l liboamlib.so.stripped

Elf file type is DYN (Shared object file)

Entry point 0x203c4

There are 4 program headers, starting at offset 52

Program Headers:

  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

  LOAD           0x000000 0x00000000 0x00a8d000 0x66ca0 0x66ca0 R E 0x1000

  LOAD           0x066ca0 0x00067ca0 0x00af3ca0 0x04884 0x06360 RWE 0x1000

  DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

  NULL           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

Notice the orig has the first line:

LOAD           0x000000 0x00000000 0x00000000 0x66ca0 0x66ca0 R E 0x1000

The stripped reads:

LOAD           0x000000 0x00000000 0x00a8d000 0x66ca0 0x66ca0 R E 0x1000

Is it normal for the stripped header to have a PhysAddr different than the orig?

post42039: Re: Strange library loading issue (first posted in general)

2009-11-16T19:27:20Z

Okay, they are sent to your email address.

post42035: Re: Strange library loading issue (first posted in general)

2009-11-16T18:06:37Z

Could you possible send me the original library, and then the library as stripped by mkifs.

You can extract the lib from the image with dumpifs

Cheers,

Colin

Liam Howlett wrote:

> Would permissions in the buildifs file cause how the stripping of symbols occurs from the mkifs command?

>

> I'm trying to figure out why the library would be stripped incorrectly.

>

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post42031

>

--

cburgess@qnx.com

post42031: Re: Strange library loading issue (first posted in general)

2009-11-16T17:42:41Z

Would permissions in the buildifs file cause how the stripping of symbols occurs from the mkifs command?

I'm trying to figure out why the library would be stripped incorrectly.

post41975: Re: Strange library loading issue (first posted in general)

2009-11-13T21:01:22Z

the "bad" version. The one located in /proc/boot that caused the process to not run.

post41974: Re: Strange library loading issue (first posted in general)

2009-11-13T20:59:07Z

Hmmm, was the readelf you posted of the 'bad' version or the 'good' version?

Liam Howlett wrote:

> Actually mkifs says that I should not use +raw for shared objects:

>

> "Don't specify the +raw attribute for shared objects; it prevents them from being shared."

>

> So any ideas on how to proceed?

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post41973

>

--

cburgess@qnx.com

post41973: Re: Strange library loading issue (first posted in general)

2009-11-13T20:57:07Z

Actually mkifs says that I should not use +raw for shared objects:

"Don't specify the +raw attribute for shared objects; it prevents them from being shared."

So any ideas on how to proceed?

post41971: Re: Strange library loading issue (first posted in general)

2009-11-13T20:47:44Z

> That doesn't look so bad.  The size difference is because mkxfs stripps the

> section

> info etc etc from the elf binary.

>

> But the headers below show that the file is at least STORED as being the right

>  size.

> Try including the lib with the [+raw] option in the ifs.  If it still fails,

> do a cksum

> of the /proc/boot version and the /tmp versions.

Okay, that worked.  I ended up working around my build system though.  We generally create .so's and let mkifs link .so to .so.1.  With raw, that doesn't happen.. so I had to create one and edit by hand to test.

>

> Could it be that the image is too large, and this is the last file, or

> something crazy like that?

>

No, we search the project for libraries and bins to include them.  oamlib ends up somewhere in the middle.

I guess this means mkifs is striping too much?

Thanks,

Liam

post41964: Re: Strange library loading issue (first posted in general)

2009-11-13T20:21:11Z

That doesn't look so bad.  The size difference is because mkxfs stripps the section

info etc etc from the elf binary.

But the headers below show that the file is at least STORED as being the right size.

Try including the lib with the [+raw] option in the ifs.  If it still fails, do a cksum

of the /proc/boot version and the /tmp versions.

Could it be that the image is too large, and this is the last file, or something crazy like that?

Liam Howlett wrote:

> It does look that way, but I can't figure out how it happened (if it is the case)

>

> $ ntoppc-readelf -l liboamlib.so.1

>

> Elf file type is DYN (Shared object file)

> Entry point 0x203c4

> There are 4 program headers, starting at offset 52

>

> Program Headers:

>   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

>   LOAD           0x000000 0x00000000 0x00aa4000 0x66ca0 0x66ca0 R E 0x1000

>   LOAD           0x066ca0 0x00067ca0 0x00b0aca0 0x04884 0x06360 RWE 0x1000

>   DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

>   NOTE           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

>

>

> Thanks,

> Liam

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post41960

>

--

cburgess@qnx.com

post41960: Re: Strange library loading issue (first posted in general)

2009-11-13T19:57:55Z

It does look that way, but I can't figure out how it happened (if it is the case)

$ ntoppc-readelf -l liboamlib.so.1

Elf file type is DYN (Shared object file)

Entry point 0x203c4

There are 4 program headers, starting at offset 52

Program Headers:

  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align

  LOAD           0x000000 0x00000000 0x00aa4000 0x66ca0 0x66ca0 R E 0x1000

  LOAD           0x066ca0 0x00067ca0 0x00b0aca0 0x04884 0x06360 RWE 0x1000

  DYNAMIC        0x06adbc 0x0006bdbc 0x0006bdbc 0x000d0 0x000d0 RW  0x4

  NOTE           0x066ca0 0x00066ca0 0x00066ca0 0x00000 0x00000 R   0x10

Thanks,

Liam

post41958: Re: Strange library loading issue (first posted in general)

2009-11-13T19:48:50Z

The lib in /proc/boot appears to be corrupted.  What does readelf -l /proc/boot/liboamlib.so.1 show?

Liam Howlett wrote:

> Hello,

>

> I have been  having an issue with one of my processes loading one of my libraries that was included in my binary image by mkifs with compression 3.

>

> The included library is a different size as the one still in the compiled directory.  There were no errors on make or mkifs.

>

> The problem I see is this:

>

> # export DL_DEBUG=1

> # export LD_LIBRARY_PATH=/proc/boot

> # ls -la /proc/boot/liboamlib.so.1

> -rwxrwxr-x  1 508       508          446464 Nov 13  2009 /proc/boot/liboamlib.so.1

>

> Process 352276 (ls) exited status=0.

> # dbs

> load_object: attempt load of liboamutilities.so.1

> load_elf32: loaded lib at addr fe378000(text) fe38ac90(data)

> load_object: attempt load of libcommonSlSwLogLib.so.1

> load_elf32: loaded lib at addr fe38c000(text) fe39b500(data)

> load_object: attempt load of libutilities.so.1

> load_elf32: loaded lib at addr fe39d000(text) fe3b4740(data)

> load_object: attempt load of liboamlib.so.1

> load_elf32: mmaped, addr 0 67ca0 vaddr fe41eca0

> Could not find library liboamlib.so.1

>

> Process 360468 (dbs) exited status=1.

> # export LD_LIBRARY_PATH=/tmp:/proc/boot

> # ls -la /tmp/liboamlib.so.1

> -rw-r--r--  2 root      0            549491 Nov 13  2009 /tmp/liboamlib.so.1

>

> Process 376852 (ls) exited status=0.

> # dbs

> load_object: attempt load of liboamutilities.so.1

> load_elf32: loaded lib at addr fe378000(text) fe38ac90(data)

> load_object: attempt load of libcommonSlSwLogLib.so.1

> load_elf32: loaded lib at addr fe38c000(text) fe39b500(data)

> load_object: attempt load of libutilities.so.1

> load_elf32: loaded lib at addr fe39d000(text) fe3b4740(data)

> load_object: attempt load of liboamlib.so.1

> load_elf32: loaded lib at addr fe3b6000(text) fe41dca0(data)

> load_object: attempt load of liboamwaveready.so.1

> load_elf32: loaded lib at addr fe424000(text) fe4dac30(data)

> load_object: attempt load of libacilib.so.1

> load_elf32: loaded lib at addr fe4e3000(text) fe4f0660(data)

> load_object: attempt load of libcommonSlAppBaseLib.so.1

> load_elf32: loaded lib at addr fe4f2000(text) fe509d40(data)

> load_object: attempt load of libcommonRblPulseTimerLib.so.1

> load_elf32: loaded lib at addr fe50b000(text) fe514690(data)

> load_object: attempt load of libcommonRblUtilitiesLib.so.1

> load_elf32: loaded lib at addr fe515000(text) fe523c30(data)

> load_object: attempt load of libsocket.so.2

> load_elf32: loaded lib at addr fe525000(text) fe545a60(data)

> load_object: attempt load of libm.so.2

> load_elf32: loaded lib at addr fe550000(text) fe56edb0(data)

> load_object: attempt load of libham.so.2

> load_elf32: loaded lib at addr fe573000(text) fe57ce80(data)

> load_object: attempt load of libecpp-ne.so.4

> load_elf32: loaded lib at addr fe57e000(text) fe59b780(data)

>

>

> As you can see, the file in /tmp works much better than the one in /proc/boot.

>

> I am cross compiling from x86 linux to ppc QNX 6.3.2.  Our build environment is not trivial to further complicate the issue.

>

> Why are the libraries different sizes?

> Could whatever changed the size of the lib cause this issue?

> Is there anything else that could cause the issue?

>

> Thanks,

> Liam

>

>

>

>

>

> _______________________________________________

>

> Builds

> http://community.qnx.com/sf/go/post41956

>

--

cburgess@qnx.com

post41956: Strange library loading issue (first posted in general)

2009-11-13T19:36:24Z

Hello,

I have been  having an issue with one of my processes loading one of my libraries that was included in my binary image by mkifs with compression 3.

The included library is a different size as the one still in the compiled directory.  There were no errors on make or mkifs.

The problem I see is this:

# export DL_DEBUG=1

# export LD_LIBRARY_PATH=/proc/boot

# ls -la /proc/boot/liboamlib.so.1

-rwxrwxr-x  1 508       508          446464 Nov 13  2009 /proc/boot/liboamlib.so.1

Process 352276 (ls) exited status=0.

# dbs

load_object: attempt load of liboamutilities.so.1

load_elf32: loaded lib at addr fe378000(text) fe38ac90(data)

load_object: attempt load of libcommonSlSwLogLib.so.1

load_elf32: loaded lib at addr fe38c000(text) fe39b500(data)

load_object: attempt load of libutilities.so.1

load_elf32: loaded lib at addr fe39d000(text) fe3b4740(data)

load_object: attempt load of liboamlib.so.1

load_elf32: mmaped, addr 0 67ca0 vaddr fe41eca0

Could not find library liboamlib.so.1

Process 360468 (dbs) exited status=1.

# export LD_LIBRARY_PATH=/tmp:/proc/boot

# ls -la /tmp/liboamlib.so.1

-rw-r--r--  2 root      0            549491 Nov 13  2009 /tmp/liboamlib.so.1

Process 376852 (ls) exited status=0.

# dbs

load_object: attempt load of liboamutilities.so.1

load_elf32: loaded lib at addr fe378000(text) fe38ac90(data)

load_object: attempt load of libcommonSlSwLogLib.so.1

load_elf32: loaded lib at addr fe38c000(text) fe39b500(data)

load_object: attempt load of libutilities.so.1

load_elf32: loaded lib at addr fe39d000(text) fe3b4740(data)

load_object: attempt load of liboamlib.so.1

load_elf32: loaded lib at addr fe3b6000(text) fe41dca0(data)

load_object: attempt load of liboamwaveready.so.1

load_elf32: loaded lib at addr fe424000(text) fe4dac30(data)

load_object: attempt load of libacilib.so.1

load_elf32: loaded lib at addr fe4e3000(text) fe4f0660(data)

load_object: attempt load of libcommonSlAppBaseLib.so.1

load_elf32: loaded lib at addr fe4f2000(text) fe509d40(data)

load_object: attempt load of libcommonRblPulseTimerLib.so.1

load_elf32: loaded lib at addr fe50b000(text) fe514690(data)

load_object: attempt load of libcommonRblUtilitiesLib.so.1

load_elf32: loaded lib at addr fe515000(text) fe523c30(data)

load_object: attempt load of libsocket.so.2

load_elf32: loaded lib at addr fe525000(text) fe545a60(data)

load_object: attempt load of libm.so.2

load_elf32: loaded lib at addr fe550000(text) fe56edb0(data)

load_object: attempt load of libham.so.2

load_elf32: loaded lib at addr fe573000(text) fe57ce80(data)

load_object: attempt load of libecpp-ne.so.4

load_elf32: loaded lib at addr fe57e000(text) fe59b780(data)

As you can see, the file in /tmp works much better than the one in /proc/boot.

I am cross compiling from x86 linux to ppc QNX 6.3.2.  Our build environment is not trivial to further complicate the issue.

Why are the libraries different sizes?

Could whatever changed the size of the lib cause this issue?

Is there anything else that could cause the issue?

Thanks,

Liam

post37484: Windows hosted build problems

2009-09-08T07:42:47Z

Windows XP hosted (SP1), Momentics 6.4.1.

I had to fix the lib/crypto/common.mk and lib/ssl/common.mk files get the trunk networking source build done. Any idea why?

...

BLDROOT=$(CURDIR)/../../../..

#BLDROOT:=$(call abspath, $(CURDIR)/../../../..)

...

The error (BLDROOT:=$(call abspath, $(CURDIR)/../../../..)):

F:\networking_src\trunk\lib\crypto>make install

make -j 1 -Carm -fMakefile install

make[1]: Entering directory `F:/networking_src/trunk/lib/crypto/arm'

make -j 1 -Ca.le -fMakefile install

make[2]: Entering directory `F:/networking_src/trunk/lib/crypto/arm/a.le'

../../common.mk:49: F:/networking_src/trunk/lib/crypto/arm/a.le/F:/networking_sr

c/trunk/crypto/Makefile.openssl: Invalid argument

make[2]: *** No rule to make target `F:/networking_src/trunk/lib/crypto/arm/a.le

/F:/networking_src/trunk/crypto/Makefile.openssl'. Stop.

make[2]: Leaving directory `F:/networking_src/trunk/lib/crypto/arm/a.le'

make[1]: *** [install] Error 2

make[1]: Leaving directory `F:/networking_src/trunk/lib/crypto/arm'

make: *** [install] Error 2

qconf-override.mk:

USE_INSTALL_ROOT=1

INSTALL_ROOT_nto=f:/networking_src/stage

VERSION_REL=6.4.1

set:

...

QCONF_OVERRIDE=F:/networking_src/qconf-override.mk

QNX_CONFIGURATION=F:\Programme\QNX Software Systems

QNX_HOST=g:/QNX641/host/win32/x86

QNX_JAVAHOME=g:\QNX641\_jvm

QNX_TARGET=g:/QNX641/target/qnx6

SESSIONNAME=Console

SystemDrive=F:

SystemRoot=F:\WINDOWS

TEMP=F:\DOKUME~1\training\LOKALE~1\Temp

TMP=F:\DOKUME~1\training\LOKALE~1\Temp

post36991: how is QCONF_OVERRIDE used? can you not use it for building nicinfo?

2009-08-31T19:52:12Z

Greetings all,

This is a bit of a loaded question, but I've been trying to do the following: Build nicinfo by itself without using the QCONF_OVERRIDE env variable. A fellow co-worker added some extra stats to nicinfo and we've been able to build it for months now. I'm trying to simplify our build process, so if I could remove the dependency on the env variable, it would be better.

How does QCONF_OVERRIDE actually work? There doesnt look like there's anything in common.mk. If I could add something like: EXTRA_INCVPATH+=v:\core_networking\stage\usr\include in common.mk that would be perfect, but it isnt working for me.

Thanks.

post36501: Re: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-24T13:08:11Z

On Thu, Aug 20, 2009 at 05:48:14PM -0400, Liam Howlett wrote:

> So in ifconfig, the struct that's used is an in6_ifreq.  How do I get from an ifnet to an in6_ifreq?  Or how do I get from the sockaddr returned from the getifaddrs to an in6_ifreq?

>

> Basically I have to match up an ifnet to a prefix, but I don't know how to get the information from an ifnet or from a sockaddr directly or indirectly.

prefixes are associated with addresses which in turn are

associated with interfaces (struct ifnet).  An interface

may have more than one address and therefore more than

one prefix.  As per the ifconfig example:

memset(&ifr6, 0, sizeof(ifr6));

strlcpy(ifr6.ifr_name, name, sizeof(ifr6.ifr_name));

ifr6.ifr_addr = creq->ifr_addr;

if (ioctl(s, SIOCGIFNETMASK_IN6, &ifr6) == -1) {

...

...

}

You put the interface name in ifr6.ifr_name and the

address you want the prefix for in ifr6.ifr_addr.

The SIOCGIFNETMASK_IN6 ioctl will return out the

prefix for that address on that particular interface.

-seanb

post36392: Re: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-20T21:48:14Z

So in ifconfig, the struct that's used is an in6_ifreq. How do I get from an ifnet to an in6_ifreq? Or how do I get from the sockaddr returned from the getifaddrs to an in6_ifreq?

Basically I have to match up an ifnet to a prefix, but I don't know how to get the information from an ifnet or from a sockaddr directly or indirectly.

post36264: Re: QNX 6.4.1 Compilation error

2009-08-19T14:24:25Z

Hi Sean,

Thanks a lot.

if i will go to indujuval directory, give make.

then i came back to root directory giv make CPULIST=x86 arm install

then its getting compiled.

I dont know the reason.

Thanks and Regards

K.Senthil

post36250: Re: QNX 6.4.1 Compilation error

2009-08-19T12:31:59Z

On Wed, Aug 19, 2009 at 03:34:26AM -0400, Senthil K wrote:

> Hi,

>

> Another error i m facing .

>

> please find the below log

>

>   /home/senthil/QNX_6.4.1/dist/bind/bin/check/check-tool.c

> /usr/qnx641/host/qnx6/x86/usr/bin/qcc -Vgcc_ntoarm -c -O -Wc,-Wall -Wc,-Wno-parentheses -Wc,-fno-builtin -DNS_LOCALSTATEDIR=\"/var\" -DNS_SYSCONFDIR=\"/etc\" -DVERSION=\"9.5.0-P2\" -DWANT_IPV6 -DOPENSSL -DISC_PLATFORM_USETHREADS -DNAMED_CONFFILE=\"/etc/named.conf\" -DNDEBUG   -I. -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm/o.le -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf -I/home/senthil/QNX_6.4.1/dist/bind/bin/check -I/home/senthil/QNX_6.4.1/services/bind/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/bind9/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isccfg/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isccc/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/lwres/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/lwres/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/sec/dst/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/pthreads/include -I/usr/qnx641/target/qnx6/usr/include    -EL    -DVARIANT_le -DBUILDENV_qss  /home/senthil/QNX_6.4.1/dist/bind/bin/check/named-checkconf.c

> make[6]: *** No rule to make target `libbind9.a', needed by `/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm/o.le/named-checkconf'.  Stop.

You need to build libbind9 for arm and install it to

your stage.  IIRC you were building for x86 yesterday.

The easiest way is to do a 'make CPULIST=x86 arm" install'

from the root of the networking repo as documented here:

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

-seanb

post36240: Re: QNX 6.4.1 Compilation error

2009-08-19T07:34:25Z

Hi,

Another error i m facing .

please find the below log

  /home/senthil/QNX_6.4.1/dist/bind/bin/check/check-tool.c

/usr/qnx641/host/qnx6/x86/usr/bin/qcc -Vgcc_ntoarm -c -O -Wc,-Wall -Wc,-Wno-parentheses -Wc,-fno-builtin -DNS_LOCALSTATEDIR=\"/var\" -DNS_SYSCONFDIR=\"/etc\" -DVERSION=\"9.5.0-P2\" -DWANT_IPV6 -DOPENSSL -DISC_PLATFORM_USETHREADS -DNAMED_CONFFILE=\"/etc/named.conf\" -DNDEBUG   -I. -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm/o.le -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm -I/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf -I/home/senthil/QNX_6.4.1/dist/bind/bin/check -I/home/senthil/QNX_6.4.1/services/bind/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/bind9/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isccfg/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isccc/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/lwres/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/lwres/unix/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/dns/sec/dst/include -I/home/senthil/QNX_6.4.1/dist/bind/lib/isc/pthreads/include -I/usr/qnx641/target/qnx6/usr/include    -EL    -DVARIANT_le -DBUILDENV_qss  /home/senthil/QNX_6.4.1/dist/bind/bin/check/named-checkconf.c

make[6]: *** No rule to make target `libbind9.a', needed by `/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm/o.le/named-checkconf'.  Stop.

make[6]: Leaving directory `/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm/o.le'

make[5]: *** [all] Error 2

make[5]: Leaving directory `/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf/arm'

make[4]: *** [all] Error 2

make[4]: Leaving directory `/home/senthil/QNX_6.4.1/services/bind/check/named-checkconf'

make[3]: *** [all] Error 2

make[3]: Leaving directory `/home/senthil/QNX_6.4.1/services/bind/check'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/home/senthil/QNX_6.4.1/services/bind'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/senthil/QNX_6.4.1/services'

make: *** [all] Error 2

# cd /home/senthil/QNX_6.4.1/dist/bind/bin/check/

Thanks

K.Senthil

post36232: Re: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-18T22:21:33Z

On Tue, Aug 18, 2009 at 05:06:02PM -0400, Liam Howlett wrote:

> The addrs don't have enough information to replace the structure we are missing.

>

> How can I rebuild the information in this struct with the current stack?

>

> struct ifprefix {

>         struct  sockaddr *ifpr_prefix;  /* prefix of interface */

>         struct  ifnet *ifpr_ifp;        /* back-pointer to interface */

>         struct ifprefix *ifpr_next;

>         unsigned char   ifpr_plen;              /* prefix length in bits */

>         unsigned char   ifpr_type;              /* protocol dependent prefix type */

> };

>

The list of interfaces and addrs can be obtained with

getifaddrs().  A particular IPv6 addr's prefixlen can be

obtained with the SIOCGIFNETMASK_IN6 ioctl.  Check out the

ifconfig utility for an example.

Regards,

-seanb

post36230: Re: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-18T21:05:59Z

The addrs don't have enough information to replace the structure we are missing.

How can I rebuild the information in this struct with the current stack?

struct ifprefix {

        struct  sockaddr *ifpr_prefix;  /* prefix of interface */

        struct  ifnet *ifpr_ifp;        /* back-pointer to interface */

        struct ifprefix *ifpr_next;

        unsigned char   ifpr_plen;              /* prefix length in bits */

        unsigned char   ifpr_type;              /* protocol dependent prefix type */

};

post36208: Re: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-18T18:39:15Z

On Tue, Aug 18, 2009 at 10:08:02AM -0400, Liam Howlett wrote:

> Hello,

>

> I have a piece of software that used to cycle through the interface list in the ifnet struct in if.h when compiled against the older 6.3.2 release of QNX. Where has this functionality been moved in 6.4.1 or has it been removed all together? How can one iterate through the list of interfaces in io-pkt?

The suggested way is to use getifaddrs() / freeifaddrs().

Regards,

-seanb

post36191: Re: QNX 6.4.1 Compilation error

2009-08-18T14:55:09Z

Hi Sean,

Thanks a lot.

Now its a workaround But is there any solution that help will help to me.

Thanks and Regards

K.Senthil

post36188: Re: QNX 6.4.1 Compilation error

2009-08-18T14:45:31Z

On Tue, Aug 18, 2009 at 10:09:46AM -0400, Senthil K wrote:

> Hi Sean,

>

> I have tried same,still error.

Try a 'make clean' first.

-seanb

post36178: Re: QNX 6.4.1 Compilation error

2009-08-18T14:09:43Z

Hi Sean,

I have tried same,still error.

please help me.

# cd lib/edit/x86/a/

# ls

.             ..            Makefile      editline.o    history.o

# make ISWIN=yes install

/usr/qnx641/host/qnx6/x86/usr/bin/qcc -Vgcc_ntox86 -c -Wc,-Wall -Wc,-Wno-parentheses  -O -DNDEBUG   -I. -I/home/senthil/QNX_6.4.1/lib/edit/premade -I/home/senthil/QNX_6.4.1/lib/edit -I/usr/qnx641/target/qnx6/usr/include        -DVARIANT_a -DBUILDENV_qss  /home/senthil/QNX_6.4.1/lib/edit/readline.c

In file included from /home/senthil/QNX_6.4.1/lib/edit/el.h:105,

                 from /home/senthil/QNX_6.4.1/lib/edit/readline.c:60:

/home/senthil/QNX_6.4.1/lib/edit/map.h:59: error: expected specifier-qualifier-list before 'el_func_t'

/home/senthil/QNX_6.4.1/lib/edit/map.h:73: error: expected declaration specifiers or '...' before 'el_func_t'

/home/senthil/QNX_6.4.1/lib/edit/readline.c: In function 'rl_bind_key':

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: 'ED_INSERT' undeclared (first use in this function)

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: (Each undeclared identifier is reported only once

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: for each function it appears in.)

cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.3.3/cc1 error 1

make: *** [readline.o] Error 1

#

Thanks

K.senthil

post36177: usr/include/net/if.h ifprefix changes from 6.3.2 to 6.4.1

2009-08-18T14:08:01Z

Hello,

I have a piece of software that used to cycle through the interface list in the ifnet struct in if.h when compiled against the older 6.3.2 release of QNX. Where has this functionality been moved in 6.4.1 or has it been removed all together? How can one iterate through the list of interfaces in io-pkt?

Thanks,

Liam

post36175: Re: QNX 6.4.1 Compilation error

2009-08-18T13:54:32Z

On Tue, Aug 18, 2009 at 08:41:16AM -0400, Senthil K wrote:

> Hi,

>

> I have download QNX 6.4.1 and tried to compile but i face erros.

>

> just i gave make form source directory.

>

> I compiled for x86

>

> Please find below log.

> ------------------------

>

> In file included from /home/senthil/QNX_6.4.1/lib/edit/el.h:105,

> from /home/senthil/QNX_6.4.1/lib/edit/readline.c:60:

> /home/senthil/QNX_6.4.1/lib/edit/map.h:59: error: expected specifier-qualifier-list before 'el_func_t'

> /home/senthil/QNX_6.4.1/lib/edit/map.h:73: error: expected declaration specifiers or '...' before 'el_func_t'

> /home/senthil/QNX_6.4.1/lib/edit/readline.c: In function 'rl_bind_key':

> /home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: 'ED_INSERT' undeclared (first use in this function)

> /home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: (Each undeclared identifier is reported only once

> /home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: for each function it appears in.)

> cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/arm-unknown-nto-qnx6.4.0/4.3.3/cc1 error 1

It looks like your lib/edit/fcns.h isn't being

built correctly (though not sure why). Try

this as a workaround:

# (cd lib/edit/x86/a && make ISWIN=yes install)

-seanb

post36152: QNX 6.4.1 Compilation error

2009-08-18T12:41:15Z

Hi,

I have download QNX 6.4.1 and tried to compile but i face erros.

just i gave make form source directory.

I compiled for x86

Please find below log.

------------------------

In file included from /home/senthil/QNX_6.4.1/lib/edit/el.h:105,

from /home/senthil/QNX_6.4.1/lib/edit/readline.c:60:

/home/senthil/QNX_6.4.1/lib/edit/map.h:59: error: expected specifier-qualifier-list before 'el_func_t'

/home/senthil/QNX_6.4.1/lib/edit/map.h:73: error: expected declaration specifiers or '...' before 'el_func_t'

/home/senthil/QNX_6.4.1/lib/edit/readline.c: In function 'rl_bind_key':

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: 'ED_INSERT' undeclared (first use in this function)

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: (Each undeclared identifier is reported only once

/home/senthil/QNX_6.4.1/lib/edit/readline.c:1568: error: for each function it appears in.)

cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/arm-unknown-nto-qnx6.4.0/4.3.3/cc1 error 1

Please help me on this.

Thanks and Regards

K.Senthil

post35993: Re: Build error Exception: STATUS_ACCESS_VIOLATION

2009-08-14T13:17:00Z

On Fri, Aug 14, 2009 at 07:35:33AM -0400, Ashwin Patwekar wrote:

> Hi ,

>

> I am trying to build the core_networking stuff using  "QNX Software Development Platform 6.4.1"

>

> When I try make CPULIST=ppc hinstall

> I am getting following errors

>

> make[4]: Entering directory `D:/Ashwin/svn/qnx/core_networking/lib/socket/ppc/a.be'

>       0 [main] sh 5884 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION

>    5323 [main] sh 5884 open_stackdumpfile: Dumping stack trace to sh.exe.stackdu

> mp

>

> I tried uninstalling and reinstalling the deelopment platform but that does not help.

>

> Any ideas what might be wrong.

>

> Ashwin

This sounds like a tools issue.  Try posting in the

tools project.

Regards,

-seanb

post35976: Build error Exception: STATUS_ACCESS_VIOLATION

2009-08-14T11:35:32Z

Hi ,

I am trying to build the core_networking stuff using  "QNX Software Development Platform 6.4.1"

When I try make CPULIST=ppc hinstall

I am getting following errors

make[4]: Entering directory `D:/Ashwin/svn/qnx/core_networking/lib/socket/ppc/a.be'

      0 [main] sh 5884 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION

   5323 [main] sh 5884 open_stackdumpfile: Dumping stack trace to sh.exe.stackdu

mp

I tried uninstalling and reinstalling the deelopment platform but that does not help.

Any ideas what might be wrong.

Ashwin

post35450: Re: Core Networking Final Milestone build - tar: This does not look like a tar archive

2009-08-07T13:34:55Z

Got it!

Look like I have to rebuild it from source anyway since lsm-nraw.so is not included.

Thanks!

post35448: Re: Core Networking Final Milestone build - tar: This does not look like a tar archive

2009-08-07T13:28:13Z

Hi Martin:

   It's a gzip-ped tar file.  Did you "gzip -d" it first?

As a side note, this is from the 6.4.0 code base.  A version for 6.3.2 based on the 6.4.1 code base hasn't been built (but you can always build one for yourself if you'd like it).

   R.

post35437: Core Networking Final Milestone build - tar: This does not look like a tar archive

2009-08-07T11:16:35Z

Hi,

I downloaded the Final Milestone build but could not extract it.

Is any other place available where I can get the binaries?

Thanks!

post35388: Re: Reg - Compiling io-pkt for ppc.

2009-08-06T14:45:23Z

On Thu, Aug 06, 2009 at 01:15:37AM -0400, Senthil K wrote:

> Hi,

>

> I had downloaded the sam.c and compliled successfully in X86 PC.

> Can you please tell me how to compile the sample io-pkt driver for PPC.

>

> What are all the changes i have to do in make file?

>

> please tell me the procedure.

I added the variants. You can either:

- update your tree

or

- (cd sys/dev_qnx/sample && addvariant ppc dll.be)

Then build as usual as per the oft quoted wiki page:

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

Regards,

-seanb

post35336: Reg - Compiling io-pkt for ppc.

2009-08-06T05:15:37Z

Hi,

I had downloaded the sam.c and compliled successfully in X86 PC.

Can you please tell me how to compile the sample io-pkt driver for PPC.

What are all the changes i have to do in make file?

please tell me the procedure.

Thanks and Regards

K.Senthil

post35237: Re: Reg - QNX Stack code compilation

2009-08-05T12:01:27Z

On Wed, Aug 05, 2009 at 02:04:07AM -0400, Senthil K wrote:

> Hi,

>

> i want to compile the QNX io-pkt stack code and load the new io-pkt-v4-hc in QNX.

> Please guide how to compile the QNX stack code,is there any makefile available and how to load new io-pkt-v4-hc.

As mentioned before, the build procedure is documented here:

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

If you're having problems please post specific questions.

Regards,

-seanb

post35220: Reg - QNX Stack code compilation

2009-08-05T06:04:06Z

Hi,

i want to compile the QNX io-pkt stack code and load the new io-pkt-v4-hc in QNX.

Please guide how to compile the QNX stack code,is there any makefile available and how to load new io-pkt-v4-hc.

Thanks and Regards

K.Senthil

post34540: No source available for "pcap_loop() "

2009-07-24T17:40:54Z

I am using pcap_loop to capture packets. The project

compiles and builds but during debugging when I run pcap_loop function the program stops and shows

>

> No source available for "pcap_loop() "

>

Regards,

Mohammad

>

> my code

>

>

> #include <stdlib.h>

> #include <stdio.h>

> #include "pcap.h"

>

> /* prototype of the packet handler */

> void packet_handler(u_char *param, const struct pcap_pkthdr *header, const u_char *pkt_data);

>

> int main(int argc, char *argv[]) {

> pcap_if_t *alldevs;

> pcap_if_t *d;

> int inum;

> int i=0;

> pcap_t *adhandle;

> char errbuf[PCAP_ERRBUF_SIZE];

>

>     /* Retrieve the device list on the local machine */

>     if (pcap_findalldevs(&alldevs, errbuf) == -1)

>     {

>         fprintf(stderr,"Error in pcap_findalldevs: %s\n", errbuf);

>         exit(1);

>     }

>

>     /* Print the list */

>     for(d=alldevs; d; d=d->next)

>     {

>         printf("%d. %s", ++i, d->name);

>         if (d->description)

>             printf(" (%s)\n", d->description);

>         else

>             printf(" (No description available)\n");

>     }

>

>     if(i==0)

>     {

>         printf("\nNo interfaces found! Make sure WinPcap is installed.\n");

>         return -1;

>     }

>

>     printf("Enter the interface number (1-%d):",i);

>     //scanf("%d", &inum);

>     inum=1;

>

>     if(inum < 1 || inum > i)

>     {

>         printf("\nInterface number out of range.\n");

>         /* Free the device list */

>         pcap_freealldevs(alldevs);

>         return -1;

>     }

>

>     /* Jump to the selected adapter */

>     for(d=alldevs, i=0; i< inum-1 ;d=d->next, i++);

>

>     /* Open the device */

>

>     adhandle=pcap_open_live(d->name, 65536, 1, 20, errbuf);

>

>     if (adhandle=NULL)

>     {

>         fprintf(stderr,"\nUnable to open the adapter. %s is not supported by WinPcap\n", d->name);

>         /* Free the device list */

>         pcap_freealldevs(alldevs);

>         return -1;

>     }

>

>     //printf("\nlistening on %s...\n", d->description);

>

>     /* At this point, we don't need any more the device list. Free it */

>     pcap_freealldevs(alldevs);

>

>     /* start the capture */

>     pcap_loop(adhandle, 0, packet_handler, NULL);

>

> return EXIT_SUCCESS;

> }

>

> /* Callback function invoked by libpcap for every incoming packet */

> void packet_handler(u_char *param, const struct pcap_pkthdr *header, const u_char *pkt_data)

> {

>     struct tm *ltime;

>     char timestr[16];

>     time_t local_tv_sec;

>

>     /* convert the timestamp to readable format */

>     local_tv_sec = header->ts.tv_sec;

>     ltime=localtime(&local_tv_sec);

>     strftime( timestr, sizeof timestr, "%H:%M:%S", ltime);

>

>     printf("%s,%.6d len:%d\n", timestr, header->ts.tv_usec, header->len);

>

> }

>

>

>

>

> _______________________________________________

>

> io-net migration

> http://community.qnx.com/sf/go/post34529

>

post31056: Re: io-pkt build error

2009-06-08T03:31:37Z

The issue is solved, when compiled using GA 6.4.0 release. I was making use of the trunk in my previous compilation

post31055: io-pkt build error

2009-06-08T01:42:05Z

Hello all.

I'm on the way to write an customized packet filter, for example, under QNX 6.4.0 specific to ARM.

I've downloaded the core_networking with SVN.

I tried to build the core networking lib doing a make CPULIST=arm install

Do I miss something. Do I proceed wrong ?

Please advice me on a simple ways to compile and make use of Packet filter.

Thanks

Hansen

post27771: Re: RE: Trouble configuring network

2009-04-22T16:28:50Z

The file /etc/resolv.conf had the vendors domain and nameaddress. Removing that solved the issue.

Thanks for the inputs!

post27747: RE: Trouble configuring network

2009-04-22T14:31:40Z

> -----Original Message-----

> From: Lakshminarayanan R [mailto:community-noreply@qnx.com]

> Sent: April-22-09 3:45 AM

> To: builds-networking

> Subject: Trouble configuring network

>

> Hello,

>

> I'm having trouble configuring network through DHCP in my target which

> uses 6.4.0.

> I execute the following in the target:

>

> io-pkt-v4-hc -ptcpip &

> waitfor /dev/socket

> inetd &

> dhcp.client -i en0 -m -u -T 10

There doesn't seems to be any network driver loaded.

>

> After this when I check up with ifconfig I find that the system is not

> configured to any IP. Is there something I'm missing here or is there

> any other dependency which I should have?

>

> Thanks,

> Lakshminarayanan.R

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post27689

>

post27734: Re: RE: RE: RE: Trouble configuring network

2009-04-22T13:54:44Z

On Wed, Apr 22, 2009 at 09:49:35AM -0400, Robert Craig wrote:

> You're on to the next thing. Check the documentation (or the web) on

> how you set up the name resolver (DNS).

In particular the documentation on /etc/resolv.conf, /etc/hosts

and /etc/nsswitch.conf in the utilities reference.

-seanb

post27731: RE: RE: RE: RE: Trouble configuring network

2009-04-22T13:49:32Z

You're on to the next thing. Check the documentation (or the web) on

how you set up the name resolver (DNS).

R.

-----Original Message-----

From: Lakshminarayanan R [mailto:community-noreply@qnx.com]

Sent: Wednesday, April 22, 2009 9:49 AM

To: builds-networking

Subject: Re: RE: RE: RE: Trouble configuring network

Yes, it is trying to look up the name links and with ping -n the delay

is aborted. But, how to avoid this without -n?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post27730

post27730: Re: RE: RE: RE: Trouble configuring network

2009-04-22T13:48:39Z

Yes, it is trying to look up the name links and with ping -n the delay is aborted. But, how to avoid this without -n?

post27725: RE: RE: RE: Trouble configuring network

2009-04-22T13:15:44Z

This is probably a name server problem. Your apps are attempting to

convert an IP address into a name and this is failing.

You can test this with the ping application by adding the -n option

(don't look up names).

R.

-----Original Message-----

From: Lakshminarayanan R [mailto:community-noreply@qnx.com]

Sent: Wednesday, April 22, 2009 9:14 AM

To: builds-networking

Subject: Re: RE: RE: Trouble configuring network

Now, I'm able to hop the packets through the gateway. Route gateway

wasn't configured and I did it with this command:

route add default .......

Still I'm facing an issue. If I give a route show (or) a telnet to

another sys (or) a ping to another sys it is taking time, although it

works.

But this is not observed with DHCP! Any suggestions on this?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post27724

post27724: Re: RE: RE: Trouble configuring network

2009-04-22T13:13:52Z

Now, I'm able to hop the packets through the gateway. Route gateway wasn't configured and I did it with this command:

route add default .......

Still I'm facing an issue. If I give a route show (or) a telnet to another sys (or) a ping to another sys it is taking time, although it works.

But this is not observed with DHCP! Any suggestions on this?

post27711: RE: RE: Trouble configuring network

2009-04-22T12:16:26Z

DHCP also configures such things as default routes and name servers. If

you're trying to connect to your target from a host on a different

subnet, setting a default route is the first thing you're going to have

to do.

I'd recommend reading up on the documentation for networking (or simply

go to the web) for basic information on how networking is configured.

R.

-----Original Message-----

From: Lakshminarayanan R [mailto:community-noreply@qnx.com]

Sent: Wednesday, April 22, 2009 6:46 AM

To: builds-networking

Subject: Re: RE: Trouble configuring network

You are right. en0 wasn't mounted. I managed to configure it in DHCP.

But, now I'm trying manual configuration. Just replacing dhcp.client

with ifconfig ifconfig en0 192.168.12.11/24

This configures the network. But when I try to ping it from outside, the

request times out.

What could be the possible reason? Anything else to be done for this?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post27702

post27702: Re: RE: Trouble configuring network

2009-04-22T10:46:27Z

You are right. en0 wasn't mounted. I managed to configure it in DHCP.

But, now I'm trying manual configuration. Just replacing dhcp.client with ifconfig

ifconfig en0 192.168.12.11/24

This configures the network. But when I try to ping it from outside, the request times out.

What could be the possible reason? Anything else to be done for this?

post27701: RE: Trouble configuring network

2009-04-22T10:40:59Z

Hi:

If there's no typo, then you haven't specified any hardware driver for io-pkt to load (the "-d" option).

R.

-----Original Message-----

From: Lakshminarayanan R [mailto:community-noreply@qnx.com]

Sent: Wed 4/22/2009 3:45 AM

To: builds-networking

Subject: Trouble configuring network

Hello,

I'm having trouble configuring network through DHCP in my target which uses 6.4.0.

I execute the following in the target:

io-pkt-v4-hc -ptcpip &

waitfor /dev/socket

inetd &

dhcp.client -i en0 -m -u -T 10

After this when I check up with ifconfig I find that the system is not configured to any IP. Is there something I'm missing here or is there any other dependency which I should have?

Thanks,

Lakshminarayanan.R

_______________________________________________

Builds

http://community.qnx.com/sf/go/post27689

post27689: Trouble configuring network

2009-04-22T07:44:58Z

Hello,

I'm having trouble configuring network through DHCP in my target which uses 6.4.0.

I execute the following in the target:

io-pkt-v4-hc -ptcpip &

waitfor /dev/socket

inetd &

dhcp.client -i en0 -m -u -T 10

After this when I check up with ifconfig I find that the system is not configured to any IP. Is there something I'm missing here or is there any other dependency which I should have?

Thanks,

Lakshminarayanan.R

post27271: RE: Missing header files in QNX640

2009-04-16T18:27:07Z

We don't support sctp on io-pkt at this moment.

Thanks

Weijie

-----Original Message-----

From: Stefan Nguyen [mailto:community-noreply@qnx.com]

Sent: April 16, 2009 2:13 PM

To: builds-networking

Subject: Missing header files in QNX640

In QNX632, there were sctp header files under

target/qnx6/usr/include/netinet. These header files particularly sctp.h

are missing in QNX640/target/qnx6/usr/include/netinet.

If this is a bug, please file this bug for the next release.

Is there a workaround? or tell us how to get these headers. We need

them.

Thanks,

S. Nguyen

_______________________________________________

Builds

http://community.qnx.com/sf/go/post27270

post27270: Missing header files in QNX640

2009-04-16T18:13:00Z

In QNX632, there were sctp header files under target/qnx6/usr/include/netinet. These header files particularly sctp.h are missing in QNX640/target/qnx6/usr/include/netinet.

If this is a bug, please file this bug for the next release.

Is there a workaround? or tell us how to get these headers. We need

them.

Thanks,

S. Nguyen

post24025: Building ntp package on qnx6.4

2009-03-10T15:16:45Z

Hi

I downloaded NTP package (ntp-4.2.4p6 from ntp.org) and attached to this query. I tried to port it to QNX 6.4 but I got lot of errors while doing make. I have seen current version of ntpq in QNX6.4 is 4.2.2p4@1.1585-o

If anyone has package which is ported to QNX 6.4 please provide me (No need of sntp). I want to get the notification from ntpd when it’s unable to reach server or it uses settimeofday to set the time. So I am going to use pulse in ntpd and get the notification. Is it possible to do?

Thanks in advance.

Thanks,

-Rahul

post23561: RE: RE: RE: make errors

2009-03-04T22:23:34Z

Hi Santosh:

If you aren't using extensive floating point operations in your

application, then you won't need it. The SPE variant was needed to

provide ABI compatibility with the floating point hardware

implementation on the PQ-III processors.

The software emulated floating point works just fine on these processors

when not using SPE, it's just a slower implementation.

R.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Wednesday, March 04, 2009 5:21 PM

To: builds-networking

Subject: Re: RE: RE: make errors

We are using MPC8572E processor. Do we need spe??

thanks

_______________________________________________

Builds

http://community.qnx.com/sf/go/post23558

post23558: Re: RE: RE: make errors

2009-03-04T22:21:00Z

We are using MPC8572E processor. Do we need spe??

thanks

post23511: RE: RE: make errors

2009-03-04T18:40:31Z

Sometime around the May/June time frame, I believe. Is there specific

functionality that you're looking for?

Robert.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Wednesday, March 04, 2009 1:01 PM

To: builds-networking

Subject: Re: RE: make errors

Any idea when 6.4.1 release available?

Thanks

_______________________________________________

Builds

http://community.qnx.com/sf/go/post23501

post23501: Re: RE: make errors

2009-03-04T18:01:20Z

Any idea when 6.4.1 release available?

Thanks

post23454: Re: make errors

2009-03-04T13:56:20Z

On Tue, Mar 03, 2009 at 09:34:03PM -0500, Santosh Kumar wrote:

> I tried to compile io-pkt GA in QNX 6.4 environment we got this make error:

>

> make[4]: *** No rule to make target `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/io-pkt-spe-v4.use', needed by `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4/io-pkt-spe-v4'.  Stop.

> make[4]: Leaving directory `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4'

> make[3]: *** [install] Error 2

>

> I found that io-pkt-spe-v4.use is missing from the source.

>

> I then made a copy of

> io-pkt-v4.use to io-pkt-spe-v4.use,

> io-pkt-v4-hc.use to io-pkt-spe-v4-hc.use

> io-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

> iio-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

>

> recompiled, and the make errors went away. Subsequently, the make succeeded.

>

> Is the copy the right way to resolve the errors? If not what would be the appropriate way?

Is your io-pkt/sys/target/common.mk up to date?  I think the last

update to it should address this:

io-pkt/sys/target >svn diff -c 805 common.mk

Index: common.mk

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

--- common.mk   (revision 804)

+++ common.mk   (revision 805)

@@ -35,7 +35,7 @@

NAME=io-pkt

empty:=

space:=$(empty) $(empty)

-USEFILE= $(PRODUCT_ROOT)/$(NAME)-$(subst $(space),-,$(filter-out be le, $(VARIANT_LIST))).use

+USEFILE= $(PRODUCT_ROOT)/$(NAME)-$(subst $(space),-,$(filter-out be le spe, $(VARIANT_LIST))).use

ISMIPS:= $(filter mips,$(subst /,$(space),$(patsubst $(IOPKT_ROOT)%,%, $(CURDIR))))

ISSH:= $(filter sh,$(subst /,$(space),$(patsubst $(IOPKT_ROOT)%,%, $(CURDIR))))

post23428: RE: make errors

2009-03-04T03:17:52Z

Hi Santosh:

SPE isn't related to SMP. SPE is an ABI variant for the Freescale PowerQUICC-III processors. The tool chain to build this variant is only available with the upcoming 6.4.1 release.

Robert.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Tue 3/3/2009 10:06 PM

To: builds-networking

Subject: Re: make errors

Colin,

We're using multi-core processor, so we need spe.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post23427

post23427: Re: make errors

2009-03-04T03:06:35Z

Colin,

We're using multi-core processor, so we need spe.

post23426: Re: make errors

2009-03-04T02:39:45Z

Without an updated set of mkfiles in $QNX_TARGET/usr/include/mk, you will have to add

EXCLUDE_VARIANTLIST=spe to your build.

Colin

Santosh Kumar wrote:

> I tried to compile io-pkt GA in QNX 6.4 environment we got this make error:

>

> make[4]: *** No rule to make target `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/io-pkt-spe-v4.use', needed by `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4/io-pkt-spe-v4'. Stop.

> make[4]: Leaving directory `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4'

> make[3]: *** [install] Error 2

>

> I found that io-pkt-spe-v4.use is missing from the source.

>

> I then made a copy of

> io-pkt-v4.use to io-pkt-spe-v4.use,

> io-pkt-v4-hc.use to io-pkt-spe-v4-hc.use

> io-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

> iio-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

>

> recompiled, and the make errors went away. Subsequently, the make succeeded.

>

> Is the copy the right way to resolve the errors? If not what would be the appropriate way?

>

> Thanks,

>

>

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post23424

>

--

cburgess@qnx.com

post23424: make errors

2009-03-04T02:33:58Z

I tried to compile io-pkt GA in QNX 6.4 environment we got this make error:

make[4]: *** No rule to make target `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/io-pkt-spe-v4.use', needed by `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4/io-pkt-spe-v4'. Stop.

make[4]: Leaving directory `/home/snguyen/workspace/ne_main/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4'

make[3]: *** [install] Error 2

I found that io-pkt-spe-v4.use is missing from the source.

I then made a copy of

io-pkt-v4.use to io-pkt-spe-v4.use,

io-pkt-v4-hc.use to io-pkt-spe-v4-hc.use

io-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

iio-pkt-v6-hc.use to io-pkt-spe-v6-hc.use

recompiled, and the make errors went away. Subsequently, the make succeeded.

Is the copy the right way to resolve the errors? If not what would be the appropriate way?

Thanks,

post22289: Re: RE: RE: Linker errors

2009-02-14T14:25:03Z

On Fri, Feb 13, 2009 at 10:52:37PM -0500, Santosh Kumar wrote:

> That worked!!

>

BTW sys/target/common.mk looks to have the fix for this

already so the EXCLUDE_VARIANTLIST shouldn't be needed:

io-pkt/sys/target >svn diff -c805 common.mk

Index: common.mk

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

--- common.mk (revision 804)

+++ common.mk (revision 805)

@@ -35,7 +35,7 @@

NAME=io-pkt

empty:=

space:=$(empty) $(empty)

-USEFILE= $(PRODUCT_ROOT)/$(NAME)-$(subst $(space),-,$(filter-out be le, $(VARIANT_LIST))).use

+USEFILE= $(PRODUCT_ROOT)/$(NAME)-$(subst $(space),-,$(filter-out be le spe, $(VARIANT_LIST))).use

ISMIPS:= $(filter mips,$(subst /,$(space),$(patsubst $(IOPKT_ROOT)%,%, $(CURDIR))))

ISSH:= $(filter sh,$(subst /,$(space),$(patsubst $(IOPKT_ROOT)%,%, $(CURDIR))))

post22282: Re: RE: RE: Linker errors

2009-02-14T03:52:33Z

That worked!!

Thanks,

Santosh

>

> Try:

>

> # make EXCLUDE_VARIANTLIST=spe VARIANTLIST="ppc x86"

>

> -seanb

>

> On Fri, Feb 13, 2009 at 10:03:37PM -0500, Robert Craig wrote:

> > Hi Santosh:

> >

> > I've asked the developer who's working on it to let me know...

> > It may take a little while to sort out, but hopefully he'll just say "do

> > this".

> >

post22281: Re: RE: RE: Linker errors

2009-02-14T03:43:12Z

Try:

# make EXCLUDE_VARIANTLIST=spe VARIANTLIST="ppc x86"

-seanb

On Fri, Feb 13, 2009 at 10:03:37PM -0500, Robert Craig wrote:

> Hi Santosh:

>

> I've asked the developer who's working on it to let me know...

> It may take a little while to sort out, but hopefully he'll just say "do

> this".

>

> Robert.

>

> -----Original Message-----

> From: Santosh Kumar [mailto:community-noreply@qnx.com]

> Sent: Friday, February 13, 2009 10:00 PM

> To: builds-networking

> Subject: Re: RE: RE: Linker errors

>

> Hi Robert,

>

> I tried that but I see the same result. I am compiling for ppc. How does

> it distinguish between PQII vs PQIII both of which are ppc?

>

> Thanks,

> Santosh

> > Hi Santosh:

> >

> > That's a new CPU variant that's being added in for

> PowerQUICC-III

> > processors. The compiler chain will be introduced in 6.4.1, so it

> > won't build in 6.4.0 (or 6.3.2).

> >

> > Ti build in 6.3.2 / 6.4.0, specify the cpu variants that you want to

> > build for (variants are arm, sh, ppc, x86) E.g.

> >

> > make CPULIST="x86 ppc" install

> >

> > R.

> >

>

>

>

>

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post22279

>

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post22280

>

post22280: RE: RE: RE: Linker errors

2009-02-14T03:03:31Z

Hi Santosh:

I've asked the developer who's working on it to let me know...

It may take a little while to sort out, but hopefully he'll just say "do

this".

Robert.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Friday, February 13, 2009 10:00 PM

To: builds-networking

Subject: Re: RE: RE: Linker errors

Hi Robert,

I tried that but I see the same result. I am compiling for ppc. How does

it distinguish between PQII vs PQIII both of which are ppc?

Thanks,

Santosh

> Hi Santosh:

>

> That's a new CPU variant that's being added in for

PowerQUICC-III

> processors. The compiler chain will be introduced in 6.4.1, so it

> won't build in 6.4.0 (or 6.3.2).

>

> Ti build in 6.3.2 / 6.4.0, specify the cpu variants that you want to

> build for (variants are arm, sh, ppc, x86) E.g.

>

> make CPULIST="x86 ppc" install

>

> R.

>

_______________________________________________

Builds

http://community.qnx.com/sf/go/post22279

post22279: Re: RE: RE: Linker errors

2009-02-14T02:59:33Z

Hi Robert,

I tried that but I see the same result. I am compiling for ppc. How does it distinguish between PQII vs PQIII both of which are ppc?

Thanks,

Santosh

> Hi Santosh:

>

> That's a new CPU variant that's being added in for

> PowerQUICC-III processors. The compiler chain will be introduced in

> 6.4.1, so it won't build in 6.4.0 (or 6.3.2).

>

> Ti build in 6.3.2 / 6.4.0, specify the cpu variants that you want to

> build for (variants are arm, sh, ppc, x86)

> E.g.

>

> make CPULIST="x86 ppc" install

>

> R.

>

post22278: RE: RE: Linker errors

2009-02-14T02:19:17Z

Hi Santosh:

That's a new CPU variant that's being added in for

PowerQUICC-III processors. The compiler chain will be introduced in

6.4.1, so it won't build in 6.4.0 (or 6.3.2).

Ti build in 6.3.2 / 6.4.0, specify the cpu variants that you want to

build for (variants are arm, sh, ppc, x86)

E.g.

make CPULIST="x86 ppc" install

R.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Friday, February 13, 2009 9:00 PM

To: builds-networking

Subject: Re: RE: Linker errors

Hi Robert,

I changed the common.mk inside trunk/sys/target directory to add in a

additional compiler flag. After that I see this:

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/host

apd/hostapd_cli.c: In function `wpa_request':

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/host

apd/hostapd_cli.c:398: warning: implicit declaration of function

`strncasecmp'

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/host

apd/hostapd_cli.c: In function `wpa_request':

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/host

apd/hostapd_cli.c:398: warning: implicit declaration of function

`strncasecmp'

make[4]: *** No rule to make target

`/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/sys/io-pkt-s

pe-v4.use', needed by

`/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/sys/target/p

pc/o.be.spe.v4/io-pkt-spe-v4'. Stop.

make[3]: *** [install] Error 2

make[2]: *** [install] Error 2

make[1]: *** [install] Error 2

make: *** [install] Error 2

What is io-pkt-spe-v4? Any idea how to resolve this? The common.mk is

attached.

Thanks,

Santosh

> Hi Robert,

>

> Seems like one of our group members had made some change in libc that

> we use on 6.3.2. This could be as a a result of that. We are

investigating it.

>

> Thanks,

> Santosh

> > Have you modified the 6.3.2 installation at all? I just tried a

> > fresh build on 6.3.2 and lib/edit built as expected for ppc.

> >

> > R.

> >

> > -----Original Message-----

> > From: Santosh Kumar [mailto:community-noreply@qnx.com]

> > Sent: Thursday, February 12, 2009 4:23 PM

> > To: builds-networking

> > Subject: Re: Linker errors

> >

> > Performing an nm on libc.a (ntoppc-nm libc.a |grep openpty) we have

> > in

> > 6.3.2 tool chain returns nothing. What version of libc is required?

> >

> > Santosh

>

>

>

_______________________________________________

Builds

http://community.qnx.com/sf/go/post22277

post22277: Re: RE: Linker errors

2009-02-14T01:59:28Z

Hi Robert,

I changed the common.mk inside trunk/sys/target directory to add in a additional compiler flag. After that I see this:

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/hostapd/hostapd_cli.c: In function `wpa_request':

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/hostapd/hostapd_cli.c:398: warning: implicit declaration of function `strncasecmp'

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/hostapd/hostapd_cli.c: In function `wpa_request':

/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/dist/wpa/hostapd/hostapd_cli.c:398: warning: implicit declaration of function `strncasecmp'

make[4]: *** No rule to make target `/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/sys/io-pkt-spe-v4.use', needed by `/home/skumar/workspace/scm1/ne/thirdparty/Networking/trunk/sys/target/ppc/o.be.spe.v4/io-pkt-spe-v4'. Stop.

make[3]: *** [install] Error 2

make[2]: *** [install] Error 2

make[1]: *** [install] Error 2

make: *** [install] Error 2

What is io-pkt-spe-v4? Any idea how to resolve this? The common.mk is attached.

Thanks,

Santosh

> Hi Robert,

>

> Seems like one of our group members had made some change in libc that we use

> on 6.3.2. This could be as a a result of that. We are investigating it.

>

> Thanks,

> Santosh

> > Have you modified the 6.3.2 installation at all? I just tried a fresh

> > build on 6.3.2 and lib/edit built as expected for ppc.

> >

> > R.

> >

> > -----Original Message-----

> > From: Santosh Kumar [mailto:community-noreply@qnx.com]

> > Sent: Thursday, February 12, 2009 4:23 PM

> > To: builds-networking

> > Subject: Re: Linker errors

> >

> > Performing an nm on libc.a (ntoppc-nm libc.a |grep openpty) we have in

> > 6.3.2 tool chain returns nothing. What version of libc is required?

> >

> > Santosh

>

>

>

post22163: Re: RE: Linker errors

2009-02-12T22:31:37Z

Hi Robert,

Seems like one of our group members had made some change in libc that we use on 6.3.2. This could be as a a result of that. We are investigating it.

Thanks,

Santosh

> Have you modified the 6.3.2 installation at all? I just tried a fresh

> build on 6.3.2 and lib/edit built as expected for ppc.

>

> R.

>

> -----Original Message-----

> From: Santosh Kumar [mailto:community-noreply@qnx.com]

> Sent: Thursday, February 12, 2009 4:23 PM

> To: builds-networking

> Subject: Re: Linker errors

>

> Performing an nm on libc.a (ntoppc-nm libc.a |grep openpty) we have in

> 6.3.2 tool chain returns nothing. What version of libc is required?

>

> Santosh

post22160: RE: Linker errors

2009-02-12T22:18:49Z

Have you modified the 6.3.2 installation at all? I just tried a fresh

build on 6.3.2 and lib/edit built as expected for ppc.

R.

-----Original Message-----

From: Santosh Kumar [mailto:community-noreply@qnx.com]

Sent: Thursday, February 12, 2009 4:23 PM

To: builds-networking

Subject: Re: Linker errors

Performing an nm on libc.a (ntoppc-nm libc.a |grep openpty) we have in

6.3.2 tool chain returns nothing. What version of libc is required?

Santosh

> Hi Sean,

>

> Yes libc.a is present with 766 permissions on it. BTW, Im trying to

> comilple it with 6.3.2 tool chain. So, the libc is probably version 2.

Is that OK?

>

> Thanks,

> Santosh

_______________________________________________

Builds

http://community.qnx.com/sf/go/post22155

post22155: Re: Linker errors

2009-02-12T21:22:55Z

Performing an nm on libc.a (ntoppc-nm libc.a |grep openpty) we have in 6.3.2 tool chain returns nothing. What version of libc is required?

Santosh

> Hi Sean,

>

> Yes libc.a is present with 766 permissions on it. BTW, Im trying to comilple

> it with 6.3.2 tool chain. So, the libc is probably version 2. Is that OK?

>

> Thanks,

> Santosh

post22144: Re: Linker errors

2009-02-12T20:14:11Z

Hi Sean,

Yes libc.a is present with 766 permissions on it. BTW, Im trying to comilple it with 6.3.2 tool chain. So, the libc is probably version 2. Is that OK?

Thanks,

Santosh

> On Wed, Feb 11, 2009 at 07:09:00PM -0500, Santosh Kumar wrote:

> > Hi,

> >

> > I am getting linker error while compiling the latest trunk. How do I fix it?

>

> >

> > Thanks,

> > Santosh

> > [skumar@ts4 trunk]$ make CPULIST="ppc" install>build.out

> > In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:9:

> > /home/skumar/io-pkt/trunk/lib/edit/filecomplete.c: In function `

> _fn_qsort_string_compare':

> > /home/skumar/io-pkt/trunk/lib/edit/filecomplete.c:337: warning: implicit

> declaration of function `strcasecmp'

> > In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:21:

> > /home/skumar/io-pkt/trunk/lib/edit/tty.c: In function `tty_stty':

> > /home/skumar/io-pkt/trunk/lib/edit/tty.c:1290: warning: implicit declaration

>  of function `ffs'

> > sys-nto.o: In function `get_pty':

> > /home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: undefined

> reference to `openpty'

> > /home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: relocation

> truncated to fit: R_PPC_REL24 openpty

> > cc: /opt/qnx632/host/linux/x86/usr/bin/powerpc-unknown-nto-qnx6.3.0-ld error

>  1

> > make[5]: *** [/home/skumar/io-pkt/trunk/services/pppd/nto/ppc/be/pppd] Error

>  1

> > make[4]: *** [install] Error 2

> > make[3]: *** [install] Error 2

> > make[2]: *** [install] Error 2

> > make[1]: *** [install] Error 2

> > make: *** [install] Error 2

> >

>

> openpty is in the static libc (libc.a).  Do you have a

> /opt/qnx632/target/qnx6/ppcbe/lib/libc.a ?

>

> -seanb

post22093: Re: Linker errors

2009-02-12T14:57:44Z

On Wed, Feb 11, 2009 at 07:09:00PM -0500, Santosh Kumar wrote:

> Hi,

>

> I am getting linker error while compiling the latest trunk. How do I fix it?

>

> Thanks,

> Santosh

> [skumar@ts4 trunk]$ make CPULIST="ppc" install>build.out

> In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:9:

> /home/skumar/io-pkt/trunk/lib/edit/filecomplete.c: In function `_fn_qsort_string_compare':

> /home/skumar/io-pkt/trunk/lib/edit/filecomplete.c:337: warning: implicit declaration of function `strcasecmp'

> In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:21:

> /home/skumar/io-pkt/trunk/lib/edit/tty.c: In function `tty_stty':

> /home/skumar/io-pkt/trunk/lib/edit/tty.c:1290: warning: implicit declaration of function `ffs'

> sys-nto.o: In function `get_pty':

> /home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: undefined reference to `openpty'

> /home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: relocation truncated to fit: R_PPC_REL24 openpty

> cc: /opt/qnx632/host/linux/x86/usr/bin/powerpc-unknown-nto-qnx6.3.0-ld error 1

> make[5]: *** [/home/skumar/io-pkt/trunk/services/pppd/nto/ppc/be/pppd] Error 1

> make[4]: *** [install] Error 2

> make[3]: *** [install] Error 2

> make[2]: *** [install] Error 2

> make[1]: *** [install] Error 2

> make: *** [install] Error 2

>

openpty is in the static libc (libc.a). Do you have a

/opt/qnx632/target/qnx6/ppcbe/lib/libc.a ?

-seanb

post22056: Linker errors

2009-02-12T00:08:56Z

Hi,

I am getting linker error while compiling the latest trunk. How do I fix it?

Thanks,

Santosh

[skumar@ts4 trunk]$ make CPULIST="ppc" install>build.out

In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:9:

/home/skumar/io-pkt/trunk/lib/edit/filecomplete.c: In function `_fn_qsort_string_compare':

/home/skumar/io-pkt/trunk/lib/edit/filecomplete.c:337: warning: implicit declaration of function `strcasecmp'

In file included from /home/skumar/io-pkt/trunk/lib/edit/editline.c:21:

/home/skumar/io-pkt/trunk/lib/edit/tty.c: In function `tty_stty':

/home/skumar/io-pkt/trunk/lib/edit/tty.c:1290: warning: implicit declaration of function `ffs'

sys-nto.o: In function `get_pty':

/home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: undefined reference to `openpty'

/home/skumar/io-pkt/trunk/services/pppd/nto/sys-nto.c:1923: relocation truncated to fit: R_PPC_REL24 openpty

cc: /opt/qnx632/host/linux/x86/usr/bin/powerpc-unknown-nto-qnx6.3.0-ld error 1

make[5]: *** [/home/skumar/io-pkt/trunk/services/pppd/nto/ppc/be/pppd] Error 1

make[4]: *** [install] Error 2

make[3]: *** [install] Error 2

make[2]: *** [install] Error 2

make[1]: *** [install] Error 2

make: *** [install] Error 2

post19507: RE: build problem with cat
2009-01-07T12:16:37Z
The creation of a qconf-override file / staging area is required in order to prevent you from overwriting your OS installation with the binaries that you're building.

The ^D (Ctrl-D) should be the thing that completes the "cat" command.  Alternatively, you can use an editor to create the qconf-override file.  I use the following contents

USE_INSTALL_ROOT=1

INSTALL_ROOT_nto=$(HOME)/stage

which stores the build products under a stage directory in my home directory

   Robert.

-----Original Message-----

From: thanos tzois [mailto:community-noreply@qnx.com]

Sent: Wed 1/7/2009 4:27 AM

To: builds-networking

Subject: build problem with cat <qconf ...instruction

hello,

iam new to qnx

i try to build qnx 6.4.0

i've downloaded the source and i try to follow the instructions

i try to configure  the override makefile stub step

but when i put the instruction

cat >qconf-override.mk  the execution of the instruction never ends...

i tried not to use step 2 and 3 but i get error in the building process...

any ideas???

are steps 2 and 3 important and why??

_______________________________________________

Builds

http://community.qnx.com/sf/go/post19501

post19501: build problem with cat
2009-01-07T09:27:23Z
hello,

iam new to qnx

i try to build qnx 6.4.0

i've downloaded the source and i try to follow the instructions

i try to configure the override makefile stub step

but when i put the instruction

cat >qconf-override.mk the execution of the instruction never ends...

i tried not to use step 2 and 3 but i get error in the building process...

any ideas???

are steps 2 and 3 important and why??

post19423: None

2009-01-06T10:01:48Z

_____________________________

Lasse Skov

Development engineer

kk-electronic a/s

Bøgildvej 3

DK-7430 Ikast

+45 96 92 45 17 (Direct)

+45 97 21 14 31 (Fax)

http://www.kk-electronic.com <http://www.kk-electronic.com/>

CONFIDENTIAL AND PROPRIETARY INFORMATION NOTICE:

The information contained in and/or attached to this e-mail is Confidential and Proprietary Information of kk-electronic a/s, and its operating companies and subsidiaries. This information is intended only for the confidential use of the person(s) designated above. If this message has reached a person or persons not designated above, you are hereby notified that you have received this document in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you are not a designated recipient, please notify the sender immediately by reply e-mail and delete the original message together with any and all attachments.

post19073: New header installation

2008-12-19T20:22:41Z

Changes have just been checked in that create and install all headers required to build drivers without having to check out the entire io-pkt source tree. You'll find an "io-pkt/..." directory in your stage/usr/include area after a new install. The build files under sys/dev_qnx have been updated to look in this directory for header files instead of trying to find them in the embedded source tree. Note that the shim driver won't build outside of the source tree because it pulls in numerous additional header that aren't required for other drivers. All NetBSD drivers (under sys/dev) still require the full source tree to build since they rely heavily on having the complete NetBSD header infrastructure in place.

Robert.

post18156: Change in build infrastructure

2008-12-08T19:03:01Z

We're changing the build a bit in order to allow drivers to be built without having to check out the entire networking source tree.  As a first step, an intermediary build directory (sys/buildenv) has been removed and some files (nw_tls.h and nw_sync.h) have been added into the build.  These files would change depending upon whether you were building on 6.4.0 or 6.3.2.  We now determine the OS version from a system include file so a smoke build for these files isn't required any more.  What this means, is that, if you are building drivers, you have to remove the inclusion of the "sys/buildenv/buildenv.mk" file in your driver common.mk file.

  Hopefully this won't cause too much inconvenience.

   Robert.

post18078: Re: etype_list_remove

2008-12-06T20:56:37Z

On Fri, Dec 05, 2008 at 05:30:50PM -0500, Michael Li wrote:

> Hello,

>

> I have a bug report in the file "trunk/sys/net/if_ethersubr.c", function "etype_list_remove". So the only place in the networking code that uses the "etype_list_insert" function is in the qnet src. This is only done at initialization and never has to call "etype_list_remove".

Fixed. Thanks,

-seanb

post18062: etype_list_remove

2008-12-05T22:30:49Z

Hello,

I have a bug report in the file "trunk/sys/net/if_ethersubr.c", function "etype_list_remove".  So the only place in the networking code that uses the "etype_list_insert" function is in the qnet src.  This is only done at initialization and never has to call "etype_list_remove".

In a port of TIPC as a loadable shared module, there is functionality that allows binding and unbinding the TIPC protocol on specific ethernet interfaces so I'm using both functions for registering and deregistering ethernet driver callbacks.

etype_list_remove doesn't take the callback function off the list.  Here's the snippet:

/* if same etype already in list, refuse it. */

for (lpp = &etype_list_head, lp = *lpp; lp ; lpp = &lp->next, lp = *lpp) {

if (lp->etype == etype) {

*lpp = lp;

break;

}

}

"*lpp = lp;"  should be this: "*lpp = lp->next;"

Otherwise, a double free occurs and io-pkt crashes.

Cheers,

Mike

post16503: Re: Building io-pkt on xp using 6.4.0 tool chain

2008-11-13T05:50:38Z

Working fine now.I think the problem is with qconf_override.mk.changed the case of nto in INSTALL_ROOT_NTO.

post16472: Re: RE: Building native drivers on Momentics 6.4

2008-11-12T15:36:35Z

Ok craig,I will try to import the mpc85xx folder as a standard make c project.Will post if it does not build.

post16471: Re: Building io-pkt on xp using 6.4.0 tool chain

2008-11-12T15:34:05Z

QCONF_OVERRIDE=d:/rtos/6.4/network/qconf-override.mk

Contents of qconf-override.mk:

USE_INSTALL_ROOT=1

INSTALL_ROOT_NTO=d:/rtos/6.4/network/stage

VERSION_REL=6.4.0

post16470: RE: Building native drivers on Momentics 6.4

2008-11-12T15:19:47Z

Given that you currently need all of the io-pkt source checked out, we

don't recommend it. If you like, you should be able to point the IDE at

the mpc85xx directory as a standard make C project.

-----Original Message-----

From: Vijayanandham Kamalasekaran [mailto:community-noreply@qnx.com]

Sent: Wednesday, November 12, 2008 2:40 AM

To: builds-networking

Subject: Building native drivers on Momentics 6.4

I have the core networking source with me.i want to build the 85xx tsec

driver alone and i was able to build the 85xx tsec driver from command

line.Is it possible to import the driver source to momentics ide 6.4? If

it is possible how can i do it?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post16439

post16463: Re: Building io-pkt on xp using 6.4.0 tool chain

2008-11-12T14:24:18Z

On Wed, Nov 12, 2008 at 09:18:28AM -0500, Vijayanandham Kamalasekaran wrote:

> Iam trying to build io-pkt on xp using 6.4.0 tool chain as a user with restrictive privilages.I followed the steps on build guide but iam getting some errors.Check the attachment for the error capture.Can someone help me out?

It doesn't look like a staging area is set up correctly.

What's in the file QCONF_OVERRIDE points to?

-seanb

post16461: Building io-pkt on xp using 6.4.0 tool chain

2008-11-12T14:18:19Z

Iam trying to build io-pkt on xp using 6.4.0 tool chain as a user with restrictive privilages.I followed the steps on build guide but iam getting some errors.Check the attachment for the error capture.Can someone help me out?

post16439: Building native drivers on Momentics 6.4

2008-11-12T07:39:30Z

I have the core networking source with me.i want to build the 85xx tsec driver alone and i was able to build the 85xx tsec driver from command line.Is it possible to import the driver source to momentics ide 6.4? If it is possible how can i do it?

post15505: Re: _res is not supported for multi-threaded programs

2008-10-24T13:53:20Z

On Fri, Oct 24, 2008 at 09:37:15AM -0400, William Smith wrote:

> We encountered a bug when running io-pkt with j9. We get the message "_res is not supported for multi-threaded programs" when we try and start one of our java apps. I did a search on the string of our binaries and found that the message is in libsocket.so. However, when I searched the foundry repository in socket, I couldn't find the message. We do not get this message when we run with io-net. Anybody have any insight as to what the message means or what function is generating it?

It's from __res_state() in lib/socket/resolve/res_state.c.

This was part of the work to make the resolving funcs

thread safe. In a multi threaded app there's no longer

a global struct __res_state.

-seanb

post15504: _res is not supported for multi-threaded programs

2008-10-24T13:37:12Z

We encountered a bug when running io-pkt with j9. We get the message "_res is not supported for multi-threaded programs" when we try and start one of our java apps. I did a search on the string of our binaries and found that the message is in libsocket.so. However, when I searched the foundry repository in socket, I couldn't find the message. We do not get this message when we run with io-net. Anybody have any insight as to what the message means or what function is generating it?

Thx,

Bill

post14854: RE: Build

2008-10-10T15:36:30Z

Hey!  You mean everyone ISN'T running self-hosted (Laugh!)

Robert.

-----Original Message-----

From: Mario Charest [mailto:community-noreply@qnx.com]

Sent: Friday, October 10, 2008 11:33 AM

To: builds-networking

Subject: Re: Build

> On Tue, Oct 07, 2008 at 09:15:08AM -0400, Mario Charest wrote:

> > If I  build net_source with JLEVEL=-j3 I get a bunch of errors that

will go

> away at the next launch of a build.  End up having to start make about

10

> times to get everything to build. With JLEVEL=-j1 no such problem.

>

> Which platform are you on?  On self hosted I saw one weird

> issue once but make consistently faults in sys/lib/libnbdrvr.

> Guess I need to be able to semi consistently reproduce it...

Lol!. Self-Hosted

>

> -seanb

_______________________________________________

Builds

http://community.qnx.com/sf/go/post14853

post14853: Re: Build

2008-10-10T15:33:18Z

> On Tue, Oct 07, 2008 at 09:15:08AM -0400, Mario Charest wrote:

> > If I  build net_source with JLEVEL=-j3 I get a bunch of errors that will go

> away at the next launch of a build.  End up having to start make about 10

> times to get everything to build. With JLEVEL=-j1 no such problem.

>

> Which platform are you on?  On self hosted I saw one weird

> issue once but make consistently faults in sys/lib/libnbdrvr.

> Guess I need to be able to semi consistently reproduce it...

Lol!. Self-Hosted

>

> -seanb

post14729: Re: Build

2008-10-08T22:35:14Z

On Tue, Oct 07, 2008 at 09:15:08AM -0400, Mario Charest wrote:

> If I build net_source with JLEVEL=-j3 I get a bunch of errors that will go away at the next launch of a build. End up having to start make about 10 times to get everything to build. With JLEVEL=-j1 no such problem.

Which platform are you on? On self hosted I saw one weird

issue once but make consistently faults in sys/lib/libnbdrvr.

Guess I need to be able to semi consistently reproduce it...

-seanb

post14586: Build

2008-10-07T13:15:06Z

If I build net_source with JLEVEL=-j3 I get a bunch of errors that will go away at the next launch of a build. End up having to start make about 10 times to get everything to build. With JLEVEL=-j1 no such problem.

post12715: RE: RE: Upgrading core_networking from Rev 151 to the latest

2008-09-02T22:42:30Z

Hi Shannon:

That branch should be OK (and the trunk should also work for

you), but you still have to do a make install to put all the headers in

the right place to get picked up by your application.

I've just put in a build request for a Milestone 4, so if you want to

hold off a bit, you can get the latest and greatest. Should be posted

in a couple of days.

Robert.

-----Original Message-----

From: Shannon Gu [mailto:community-noreply@qnx.com]

Sent: Tuesday, September 02, 2008 1:52 PM

To: builds-networking

Subject: Re: RE: Upgrading core_networking from Rev 151 to the latest

Hi Robert,

Now I got a complete M3 image on the board, with core_networking shows

the version number 470 -- is this OK? Can I use headers from source code

that checked out from tunk/branches/BX640_23212_M6 with reivision 470

to compile my program?

Thanks,

Shannon

_______________________________________________

Builds

http://community.qnx.com/sf/go/post12705

post12705: Re: RE: Upgrading core_networking from Rev 151 to the latest

2008-09-02T17:51:41Z

Hi Robert,

Now I got a complete M3 image on the board, with core_networking shows the version number 470 -- is this OK? Can I use headers from source code that checked out from tunk/branches/BX640_23212_M6 with reivision 470 to compile my program?

Thanks,

Shannon

post11883: Re: RE: Upgrading core_networking from Rev 151 to the latest

2008-08-15T17:31:27Z

Hi Robert.

Thank you so much for your prompt and thorough reply, it is very help and exactly what we need to know.

My best regards,

Shannon

post11826: RE: Upgrading core_networking from Rev 151 to the latest

2008-08-15T03:08:01Z

Hi Shannon:

1. Is Milestone 3 the latest stable release? what about M5 and M6?

The builds for the last three months have pretty much all been stable.  Milestone 3 is being provided as a convenience so that people don't have to do a complete build themselves.  I don't know what you mean by M5 and M6 with respect to networking.  I know that we have core OS milestone builds that are M5 and M6, but these aren't relevant to networking.

2. What is the revision number for M3? is it Rev.468?

M3 is slightly before Rev468 (I'll have to check the build times to let you know the exact revision.  We normally create a tag with each milestone build, but that was unfortunately skipped with this build.  We'll correct it for the next build in September).  The changes that have gone in since M3 should be minor though so Rev 468 is fine to use.

3. I have downloaded M3 and trunk #468; and have compiled my code with minor modification, the compilation went through; I also loaded all the libs and executable onto the target and have then correctly pointed; here is the running result while my program trying to call l2_packet_init() :

.....

pcap_open_live: BIOCSETIF: ath0: Invalid argument

ifname='ath0'

.....

it seems like interface ath0 has not been attached; but I dont know why and how;

could anyone lend a hand?

You also *MUST* recompile your Atheros driver within the new source bsdr.  Many structures have had additional members / padding added which would mean that a driver built with an earlier rev of source will not work.

If you've already done this and it still doesn't work, "ifconfig" will tell you if the interface exists or not and "sloginfo" might provide additional information as to what has failed.

4. I did not rebuild the network stack as I dont have debug port on my board so I have to ship it back to our customer for re-flashing, pls. let me know if re-build and re-flashing is necessary; ?

I'm not sure I understand this.  Are you using the networking stack that's in milestone 3?  If not, why would you link your application against it? If you want to upgrade appropriately, then ALL networking binaries (the stack, libraries and applications) need to be upgraded to Milestone 3.  You can take the binaries from milestone 3 without re-building.

5. I'd also like to know if there are big changes regarding interface and/or architecture from Rev151 to Rev468 that will effect the old code;

The architecture hasn't changed so if you're dealing strictly with the application layer, then you're likely OK.  However, ANYTHING that requires direct interaction with the stack (drivers, etc.) must be re-built with the new source code in place in order to pick up the newer headers.

If you want to get an idea about what's changed, you can browse all of the changes that have gone in since 151 through the SVN web interface.  There are quite a few...

6. And your suggestion to pursuit this upgrading; (my code includes wpa_supplicant and a manager program running on top of it)

Make sure that you use the complete set of binaries from Milestone 3 in your image.  This will ensure full compatibility between the binaries

    Hope this helps,

       Robert.

-----Original Message-----

From: Shannon Gu [mailto:community-noreply@qnx.com]

Sent: Thu 8/14/2008 8:20 PM

To: builds-networking

Subject: Upgrading core_networking from Rev 151 to the latest

Hello,

We have been using io-pkt for a while, and now it is time to look for an integration with the latest release build; I have also tried and encounter some problems, here are my questions:

1. Is Milestone 3 the latest stable release? what about M5 and M6?

2. What is the revision number for M3? is it Rev.468?

3. I have downloaded M3 and trunk #468; and have compiled my code with minor modification, the compilation went through; I also loaded all the libs and executable onto the target and have then correctly pointed; here is the running result while my program trying to call l2_packet_init() :

.....

pcap_open_live: BIOCSETIF: ath0: Invalid argument

ifname='ath0'

.....

it seems like interface ath0 has not been attached; but I dont know why and how;

could anyone lend a hand?

4. I did not rebuild the network stack as I dont have debug port on my board so I have to ship it back to our customer for re-flashing, pls. let me know if re-build and re-flashing is necessary; ?

5. I'd also like to know if there are big changes regarding interface and/or architecture from Rev151 to Rev468 that will effect the old code;

6. And your suggestion to pursuit this upgrading; (my code includes wpa_supplicant and a manager program running on top of it)

I'd appreciate any input/help;

Regards,

Shannon

_______________________________________________

Builds

http://community.qnx.com/sf/go/post11825

post11825: Upgrading core_networking from Rev 151 to the latest

2008-08-15T00:20:19Z

Hello,

We have been using io-pkt for a while, and now it is time to look for an integration with the latest release build; I have also tried and encounter some problems, here are my questions:

1. Is Milestone 3 the latest stable release? what about M5 and M6?

2. What is the revision number for M3? is it Rev.468?

3. I have downloaded M3 and trunk #468; and have compiled my code with minor modification, the compilation went through; I also loaded all the libs and executable onto the target and have then correctly pointed; here is the running result while my program trying to call l2_packet_init() :

.....

pcap_open_live: BIOCSETIF: ath0: Invalid argument

ifname='ath0'

.....

it seems like interface ath0 has not been attached; but I dont know why and how;

could anyone lend a hand?

4. I did not rebuild the network stack as I dont have debug port on my board so I have to ship it back to our customer for re-flashing, pls. let me know if re-build and re-flashing is necessary; ?

5. I'd also like to know if there are big changes regarding interface and/or architecture from Rev151 to Rev468 that will effect the old code;

6. And your suggestion to pursuit this upgrading; (my code includes wpa_supplicant and a manager program running on top of it)

I'd appreciate any input/help;

Regards,

Shannon

post10439: Re: IDE

2008-07-12T18:19:51Z

On 7/11/08, Mario Charest <mcharest@zinformatic.com> wrote:

>

>

> SVN repository contains no files related to Eclipse ( .cproject, .project

> etc).

>

> Does that mean that nobody in the network group uses it?  Or the people

> that do create their own project each time?

I do it from scratch each time, checking out the whole tree (or parts of it,

but in the same directory structure) into a single root project and then

creating additional projects that point within this root project on source

code as required.

I do this for a for a couple of reasons:

0) Project creation is relatively fast and can be tuned to be flexible to

the particular situation you are encountering.  Different development

activities need different project scopes.

1) I don't actually do clean checkouts very often, so the root project

creation isn't a frequent activity.  I do often flip around parts of the

source tree fairly regularly, so I like to have several small more focused

projects while maintaining access to all of the source that _may_ be

referenced.

2) The QNX source tree, being a hiearchichal build, really wants to have a

single rooted project to work with for things like SVN operations

(update/compare etc), world global builds and stage directories.  However,

not every module needs the whole tree to build (depending on your stage

configuration etc) so if you know what you are working with you can tailor

your checkouts/project creation as appropriate.

Thomas ... IDE lover.

post10427: RE: IDE

2008-07-11T17:40:00Z

Hi Mario:

That is correct.  Given the extent of the networking source,

it's all command line driven.  I often pull things into my own project

in the IDE, but most people work outside of Eclipse.

Robert.

-----Original Message-----

From: Mario Charest [mailto:mcharest@zinformatic.com]

Sent: Friday, July 11, 2008 1:39 PM

To: builds-networking

Subject: IDE

SVN repository contains no files related to Eclipse ( .cproject,

.project etc).

Does that mean that nobody in the network group uses it?  Or the people

that do create their own project each time?

- Mario

_______________________________________________

Builds

http://community.qnx.com/sf/go/post10426

post10426: IDE

2008-07-11T17:38:35Z

SVN repository contains no files related to Eclipse ( .cproject, .project etc).

Does that mean that nobody in the network group uses it? Or the people that do create their own project each time?

- Mario

post10050: Re: RE: recvfrom() could not return back even with TimerTimeout

2008-07-04T12:38:22Z

thx, for the "bad file descriptor", io-net didnot work anymore and all the network cards have stopped working, i traced the initial errors when i ran the program, like this is the real problem:

"tcpip: blown stack handling 0x102. See "stacksize" option. " then after this came out the bad file descriptor for server and client thread.

my boot script for the network setup:

/proc/boot/devp-pccard ss -m

waitfor /dev/pccard 59

io-net -d ns83815 -p tcpip -p qnet bind=en0

waitfor /dev/io-net/en0

waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

display_msg "configuring adhoc network mode"

mount -o channel=11,network=mywork,mode=adhoc -T io-net devn-orinoco.so

waitfor /dev/io-net/en1

ifconfig en1 192.168.1.1 netmask 255.255.255.0

thx

Eric

post10033: Re: RE: recvfrom() could not return back even with TimerTimeout

2008-07-03T16:19:15Z

On Thu, Jul 03, 2008 at 10:51:39AM -0400, Eric Dong wrote:

> thx, i added your snippet, but when no pkts received, recvfrom() still blocks and the timertimeout still does not make any effects.

The following works for me.

#include <sys/neutrino.h>

#include <sys/socket.h>

#include <netinet/in.h>

#include <err.h>

#include <stdio.h>

int

main(void)

{

        int             s;

        uint64_t        timeo;

        struct sockaddr sin;

        socklen_t       slen;

        char            c;

        if ((s = socket(AF_INET, SOCK_RAW, 0)) == -1)

                err(1, "socket");

        timeo = 1 * 1000000000;

        TimerTimeout(CLOCK_REALTIME, _NTO_TIMEOUT_SEND | _NTO_TIMEOUT_REPLY,

            NULL, &timeo, NULL);

        slen = sizeof(sin);

        if (recvfrom(s, &c, 1, 0, (struct sockaddr *)&sin, &slen) == -1)

                err(1, "recvfrom");

        return 0;

}

>

> now i came across another problem, as in my previous post, i have server and client thread, now when i just started the client thread(only sending out packets) , the machine on the other side could receive it. but when i started the server thread, then both two threads gave me the error during execution:

>     sendto: Bad file descriptor

>     recvfrom: Bad file descriptor

>

> and if i just only started the server thread, still the same error. seems sth wrong with the server thread. but the server and client threads on two machines are the same. so what might cause the above errors? thank u.

Is io-pkt still running?

post10025: RE: RE: recvfrom() could not return back even with TimerTimeout

2008-07-03T14:54:50Z

Just as a side point, topics such as these which deal with application

issues as opposed to building io-pkt from the repository really belong

in the "general" networking forum rather than here.  We can keep this

one here, but this group is intended for discussions related

specifically to building code from the repository.

Thanks!

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Thursday, July 03, 2008 10:52 AM

To: builds-networking

Subject: Re: RE: recvfrom() could not return back even with TimerTimeout

thx, i added your snippet, but when no pkts received, recvfrom() still

blocks and the timertimeout still does not make any effects.

now i came across another problem, as in my previous post, i have server

and client thread, now when i just started the client thread(only

sending out packets) , the machine on the other side could receive it.

but when i started the server thread, then both two threads gave me the

error during execution:

    sendto: Bad file descriptor

    recvfrom: Bad file descriptor

and if i just only started the server thread, still the same error.

seems sth wrong with the server thread. but the server and client

threads on two machines are the same. so what might cause the above

errors? thank u.

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post10024

post10024: Re: RE: recvfrom() could not return back even with TimerTimeout

2008-07-03T14:51:36Z

thx, i added your snippet, but when no pkts received, recvfrom() still blocks and the timertimeout still does not make any effects.

now i came across another problem, as in my previous post, i have server and client thread, now when i just started the client thread(only sending out packets) , the machine on the other side could receive it. but when i started the server thread, then both two threads gave me the error during execution:

sendto: Bad file descriptor

recvfrom: Bad file descriptor

and if i just only started the server thread, still the same error. seems sth wrong with the server thread. but the server and client threads on two machines are the same. so what might cause the above errors? thank u.

Eric

post10017: RE: recvfrom() could not return back even with TimerTimeout

2008-07-03T14:06:31Z

You need to setup "fromSockaddr" properly before you can use them.

memset(&fromSockaddr, 0, sizeof(fromSockaddr));

fromSockaddr.sa_len = sizeof(fromSockaddr);

fromSockaddr.sa_family = AF_INET;

...

> -----Original Message-----

> From: Eric Dong [mailto:eric.dongxx@gmail.com]

> Sent: Thursday, July 03, 2008 9:18 AM

> To: builds-networking

> Subject: Re: recvfrom() could not return back even with TimerTimeout

>

> thank you. basically i have two concurrent threads in my

> program, one server thread for receiving only and one client

> thread for sending only. and each one binds a different

> socket descriptor to itself.

>

> code snippet for the server thread:

>

> struct sockaddr_in fromSockaddr;

> socklen_t fromSockaddrLen;

> int recvBytes = 0;

>         fromSockaddrLen = sizeof(fromSockaddr);

>         recvBytes = recvfrom( serverSockID, (void *)recvBuf,

> RECV_BUF_LEN, 0, (struct sockaddr

> *)&fromSockaddr, &fromSockaddrLen );

>         .....

>

> and i just wanna the recvfrom() blocked thx Eric

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post10011

>

>

post10011: Re: recvfrom() could not return back even with TimerTimeout

2008-07-03T13:18:08Z

thank you. basically i have two concurrent threads in my program, one server thread for receiving only and one client thread for sending only. and each one binds a different socket descriptor to itself.

code snippet for the server thread:

struct sockaddr_in fromSockaddr;

socklen_t fromSockaddrLen;

int recvBytes = 0;

        fromSockaddrLen = sizeof(fromSockaddr);

        recvBytes = recvfrom( serverSockID, (void *)recvBuf, RECV_BUF_LEN, 0, (struct sockaddr *)&fromSockaddr, &fromSockaddrLen );

        .....

and i just wanna the recvfrom() blocked

thx

Eric

post10007: Re: recvfrom() could not return back even with TimerTimeout

2008-07-03T12:43:17Z

On Thu, Jul 03, 2008 at 03:28:57AM -0400, Eric Dong wrote:

> I am doing peer to peer wireless communication with two QNX6.3.2 machines using UDP. sending is okay, but on the recvfrom() thread, the program stuck just in the recvfrom() call, and the TimerTimeout(CLOCK_REALTIME, _NTO_TIMEOUT_CONDVAR | _NTO_TIMEOUT_MUTEX | _NTO_TIMEOUT_RECEIVE, NULL, &nWait, NULL); could not timeout after 2ms of blocking in recvfrom(). Look for your help.

Use _NTO_TIMEOUT_SEND | _NTO_TIMEOUT_RECEIVE; or set the socket

to non blocking, receive in a loop until -1 and block in poll().

-seanb

post9984: recvfrom() could not return back even with TimerTimeout

2008-07-03T07:28:55Z

I am doing peer to peer wireless communication with two QNX6.3.2 machines using UDP. sending is okay, but on the recvfrom() thread, the program stuck just in the recvfrom() call, and the TimerTimeout(CLOCK_REALTIME, _NTO_TIMEOUT_CONDVAR | _NTO_TIMEOUT_MUTEX | _NTO_TIMEOUT_RECEIVE, NULL, &nWait, NULL); could not timeout after 2ms of blocking in recvfrom(). Look for your help.

Eric

post9858: RE: RE: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-30T14:07:17Z

Qnet-compat is an old style version of qnet that provides backwards

compatibility with QNX6.2.1. It isn't recommended for new projects.

If qnet-compat works, there's no reason why regular qnet wouldn't work,

though...

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Monday, June 30, 2008 9:26 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

i made it thru via mounting "npm-qnet-compat.so" instead of

"npm-qnet.so", it worked fine now. thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9854

post9854: Re: RE: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-30T13:25:59Z

i made it thru via mounting "npm-qnet-compat.so" instead of "npm-qnet.so", it worked fine now. thx

Eric

post9776: RE: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-27T13:52:52Z

Hi Eric:

I'm not sure that I understand the question...  If you're using

io-net, you need npm-qnet.so as well as the usual networking libraries

and that all seems to be there already.  Would it be worthwhile doing a

fresh install of the software on the machine that doesn't work to see if

there's some sort of corruption issue?  I suspect not since this would

have shown up as a failure of some sort in the logs.

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Friday, June 27, 2008 9:18 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

thx, Robert, i have changed the hardware configuration. the problem

definitely lies in the wrong machine, but one question: what kind of

library is needed when calling qnet? seems it is unable to resolve the

network name?

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9772

post9772: Re: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-27T13:18:24Z

thx, Robert, i have changed the hardware configuration. the problem definitely lies in the wrong machine, but one question: what kind of library is needed when calling qnet? seems it is unable to resolve the network name?

Eric

post9670: RE: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-25T14:19:25Z

Certainly shouldn't be a problem with the Ethernet switch and you did

say that you can ping the other machines via IP, correct?

The "no route" simply means that it couldn't find anything on the

network. I was hoping that by forcing it to attempt a resolution that

things would work, but apparently not.

I'm grasping at straws here, but can you try changing the switch port

for the machine that doesn't work to one that does?

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Wednesday, June 25, 2008 5:41 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: qnet problem under qnx6.3.2

you are right.

the output of "ls /net/target.intra.net" is as follows:

ls: No route to host (/net/target.intra.net)

there should be no route problem in the hub connection, right?

thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9644

post9644: Re: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-25T09:41:23Z

you are right.

the output of "ls /net/target.intra.net" is as follows:

ls: No route to host (/net/target.intra.net)

there should be no route problem in the hub connection, right?

thx

Eric

post9598: RE: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-24T15:27:27Z

Hi Eric:

This is a driver problem so you need to post the information in

the drivers forum.  (Which I believe that you've already done with the

"WLAN among qnx" thread).

Robert

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 24, 2008 9:30 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network

cards

> well, seems not fully solved:

> the adhoc network could not work now, i tried "nicinfo"

> only the wired ethernet network card showed its message, without the

wireless

> orinoco.  since when i only "io-net -d orinoco -p tcpip", "nicinfo"

would show

>  the orinoco's info.

> so, the orinoco card still could not work, i.e. "mount -o

channel=11,......-p

> tcpip" didnot fully start the orinoco card.

>

> Eric

some updates, the problem now is that qnx machines in the wlan could not

ping thru one another in the adhoc mode.

when i tried "nicinfo -r en1" it would display the nicinfo of the

orinoco card like follows:

ORiNOCO 802.11 Wireless Ethernet Controller

  Physical Node ID ........................... 00022D 01B57F

  Current Physical Node ID ................... 00022D 01B57F

  Current Operation Rate ..................... 11.00 Mb/s half-duplex

  Active Interface Type ...................... Unknown

  Maximum Transmittable data Unit ............ 1514

  Maximum Receivable data Unit ............... 1514

  Hardware Interrupt ......................... 0x3

  I/O Aperture ............................... 0x300 - 0x33f

  Promiscuous Mode ........................... Off

  Multicast Support .......................... Enabled

  Station Name ...............................

  Network Name (SSID) ........................

  Channel: ................................... 4294967295

  BSS Type ................................... Unknown

  Packets Transmitted OK ..................... 0

  Bytes Transmitted OK ....................... 300

  Packets Received OK ........................ 3

  Bytes Received OK .......................... 0

so, what are the possible reasons here? thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9565

post9595: RE: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-24T15:24:22Z

I'm a bit confused myself...  Just to re-cap.  You have three x86 boxes,

all connected together on the same Ethernet switch: a target T, A and B.

A and T can see each other through qnet.  B can not see either A or T. B

can ping A and T though (so IP works OK).

If T is named target and you do ls /net/target from B, does anything

appear.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 24, 2008 11:19 AM

To: builds-networking

Subject: Re: RE: RE: RE: qnet problem under qnx6.3.2

thx, one target, machine A and machine B all with qnx 6.3.2 connected

via a hub. on the target and A, both can see each other under /net

directory. while B could only see itself. that's confusing...

ps: could you please provide me with your explanation to my another

thread "script for two network cards?" got stuck quite a lot on my

current project. and do appreciate all of your responses so far.

> And you were right that nicinfo looks as it should :) (but at least I

> know now that it's an Intel driver and that auto-negotiation is good

and

> there are no errors on the interface).

>

> If you know the name of one of the other machines on the network, can

> you try an ls /net/name_of_other_computer and see if that works?

>

> One other point is that QNET is a layer 2 protocol that isn't routed.

> Are all of these hosts connected to the same layer 2 switch domain?

>

>

>

> -----Original Message-----

> From: Eric Dong [mailto:eric.dongxx@gmail.com]

> Sent: Tuesday, June 24, 2008 11:03 AM

> To: builds-networking

> Subject: Re: RE: RE: qnet problem under qnx6.3.2

>

> yes, u guess is right. since the other hosts would be available under

> /net on the target, here is the output of nicinfo of the "wrong"

> machine:

>

> INTEL 82558 Ethernet Controller

>

>   Physical Node ID ........................... 000D60 106287

>   Current Physical Node ID ................... 000D60 106287

>   Current Operation Rate ..................... 100.00 Mb/s full-duplex

>   Active Interface Type ...................... MII

>     Active PHY address ....................... 1

>   Maximum Transmittable data Unit ............ 1514

>   Maximum Receivable data Unit ............... 1514

>   Hardware Interrupt ......................... 0xb

>   I/O Aperture ............................... 0x8000 - 0x803f

>   Memory Aperture ............................ 0xc0201000 - 0xc0201fff

>   Promiscuous Mode ........................... Off

>   Multicast Support .......................... Enabled

>

>   Packets Transmitted OK ..................... 251

>   Bytes Transmitted OK ....................... 39582

>   Broadcast Packets Transmitted OK ........... 251

>   Multicast Packets Transmitted OK ........... 0

>   Memory Allocation Failures on Transmit ..... 0

>

>   Packets Received OK ........................ 5285

>   Bytes Received OK .......................... 471963

>   Broadcast Packets Received OK .............. 5285

>   Multicast Packets Received OK .............. 0

>   Memory Allocation Failures on Receive ...... 0

>

>   Single Collisions on Transmit .............. 0

>   Multiple Collisions on Transmit ............ 0

>   Deferred Transmits ......................... 0

>   Late Collision on Transmit errors .......... 0

>   Transmits aborted (excessive collisions) ... 0

>   Transmit Underruns ......................... 0

>   No Carrier on Transmit ..................... 0

>   Receive Alignment errors ................... 0

>   Received packets with CRC errors ........... 0

>   Packets Dropped on receive ................. 0

>   Short packets .............................. 0

>   Total Frames experiencing Collison(s) ...... 0

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post9588

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9591

post9591: Re: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-24T15:19:06Z

thx, one target, machine A and machine B all with qnx 6.3.2 connected via a hub. on the target and A, both can see each other under /net directory. while B could only see itself. that's confusing...

ps: could you please provide me with your explanation to my another thread "script for two network cards?" got stuck quite a lot on my current project. and do appreciate all of your responses so far.

> And you were right that nicinfo looks as it should :) (but at least I

> know now that it's an Intel driver and that auto-negotiation is good and

> there are no errors on the interface).

>

> If you know the name of one of the other machines on the network, can

> you try an ls /net/name_of_other_computer and see if that works?

>

> One other point is that QNET is a layer 2 protocol that isn't routed.

> Are all of these hosts connected to the same layer 2 switch domain?

>

>

>

> -----Original Message-----

> From: Eric Dong [mailto:eric.dongxx@gmail.com]

> Sent: Tuesday, June 24, 2008 11:03 AM

> To: builds-networking

> Subject: Re: RE: RE: qnet problem under qnx6.3.2

>

> yes, u guess is right. since the other hosts would be available under

> /net on the target, here is the output of nicinfo of the "wrong"

> machine:

>

> INTEL 82558 Ethernet Controller

>

>   Physical Node ID ........................... 000D60 106287

>   Current Physical Node ID ................... 000D60 106287

>   Current Operation Rate ..................... 100.00 Mb/s full-duplex

>   Active Interface Type ...................... MII

>     Active PHY address ....................... 1

>   Maximum Transmittable data Unit ............ 1514

>   Maximum Receivable data Unit ............... 1514

>   Hardware Interrupt ......................... 0xb

>   I/O Aperture ............................... 0x8000 - 0x803f

>   Memory Aperture ............................ 0xc0201000 - 0xc0201fff

>   Promiscuous Mode ........................... Off

>   Multicast Support .......................... Enabled

>

>   Packets Transmitted OK ..................... 251

>   Bytes Transmitted OK ....................... 39582

>   Broadcast Packets Transmitted OK ........... 251

>   Multicast Packets Transmitted OK ........... 0

>   Memory Allocation Failures on Transmit ..... 0

>

>   Packets Received OK ........................ 5285

>   Bytes Received OK .......................... 471963

>   Broadcast Packets Received OK .............. 5285

>   Multicast Packets Received OK .............. 0

>   Memory Allocation Failures on Receive ...... 0

>

>   Single Collisions on Transmit .............. 0

>   Multiple Collisions on Transmit ............ 0

>   Deferred Transmits ......................... 0

>   Late Collision on Transmit errors .......... 0

>   Transmits aborted (excessive collisions) ... 0

>   Transmit Underruns ......................... 0

>   No Carrier on Transmit ..................... 0

>   Receive Alignment errors ................... 0

>   Received packets with CRC errors ........... 0

>   Packets Dropped on receive ................. 0

>   Short packets .............................. 0

>   Total Frames experiencing Collison(s) ...... 0

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post9588

post9589: RE: RE: RE: qnet problem under qnx6.3.2

2008-06-24T15:06:23Z

And you were right that nicinfo looks as it should :) (but at least I

know now that it's an Intel driver and that auto-negotiation is good and

there are no errors on the interface).

If you know the name of one of the other machines on the network, can

you try an ls /net/name_of_other_computer and see if that works?

One other point is that QNET is a layer 2 protocol that isn't routed.

Are all of these hosts connected to the same layer 2 switch domain?

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 24, 2008 11:03 AM

To: builds-networking

Subject: Re: RE: RE: qnet problem under qnx6.3.2

yes, u guess is right. since the other hosts would be available under

/net on the target, here is the output of nicinfo of the "wrong"

machine:

INTEL 82558 Ethernet Controller

  Physical Node ID ........................... 000D60 106287

  Current Physical Node ID ................... 000D60 106287

  Current Operation Rate ..................... 100.00 Mb/s full-duplex

  Active Interface Type ...................... MII

    Active PHY address ....................... 1

  Maximum Transmittable data Unit ............ 1514

  Maximum Receivable data Unit ............... 1514

  Hardware Interrupt ......................... 0xb

  I/O Aperture ............................... 0x8000 - 0x803f

  Memory Aperture ............................ 0xc0201000 - 0xc0201fff

  Promiscuous Mode ........................... Off

  Multicast Support .......................... Enabled

  Packets Transmitted OK ..................... 251

  Bytes Transmitted OK ....................... 39582

  Broadcast Packets Transmitted OK ........... 251

  Multicast Packets Transmitted OK ........... 0

  Memory Allocation Failures on Transmit ..... 0

  Packets Received OK ........................ 5285

  Bytes Received OK .......................... 471963

  Broadcast Packets Received OK .............. 5285

  Multicast Packets Received OK .............. 0

  Memory Allocation Failures on Receive ...... 0

  Single Collisions on Transmit .............. 0

  Multiple Collisions on Transmit ............ 0

  Deferred Transmits ......................... 0

  Late Collision on Transmit errors .......... 0

  Transmits aborted (excessive collisions) ... 0

  Transmit Underruns ......................... 0

  No Carrier on Transmit ..................... 0

  Receive Alignment errors ................... 0

  Received packets with CRC errors ........... 0

  Packets Dropped on receive ................. 0

  Short packets .............................. 0

  Total Frames experiencing Collison(s) ...... 0

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9588

post9588: Re: RE: RE: qnet problem under qnx6.3.2

2008-06-24T15:02:54Z

yes, u guess is right. since the other hosts would be available under /net on the target, here is the output of nicinfo of the "wrong" machine:

INTEL 82558 Ethernet Controller

  Physical Node ID ........................... 000D60 106287

  Current Physical Node ID ................... 000D60 106287

  Current Operation Rate ..................... 100.00 Mb/s full-duplex

  Active Interface Type ...................... MII

    Active PHY address ....................... 1

  Maximum Transmittable data Unit ............ 1514

  Maximum Receivable data Unit ............... 1514

  Hardware Interrupt ......................... 0xb

  I/O Aperture ............................... 0x8000 - 0x803f

  Memory Aperture ............................ 0xc0201000 - 0xc0201fff

  Promiscuous Mode ........................... Off

  Multicast Support .......................... Enabled

  Packets Transmitted OK ..................... 251

  Bytes Transmitted OK ....................... 39582

  Broadcast Packets Transmitted OK ........... 251

  Multicast Packets Transmitted OK ........... 0

  Memory Allocation Failures on Transmit ..... 0

  Packets Received OK ........................ 5285

  Bytes Received OK .......................... 471963

  Broadcast Packets Received OK .............. 5285

  Multicast Packets Received OK .............. 0

  Memory Allocation Failures on Receive ...... 0

  Single Collisions on Transmit .............. 0

  Multiple Collisions on Transmit ............ 0

  Deferred Transmits ......................... 0

  Late Collision on Transmit errors .......... 0

  Transmits aborted (excessive collisions) ... 0

  Transmit Underruns ......................... 0

  No Carrier on Transmit ..................... 0

  Receive Alignment errors ................... 0

  Received packets with CRC errors ........... 0

  Packets Dropped on receive ................. 0

  Short packets .............................. 0

  Total Frames experiencing Collison(s) ...... 0

post9586: RE: RE: qnet problem under qnx6.3.2

2008-06-24T14:56:32Z

It would still be useful to see the nicinfo to see what the driver is

doing.  I take it that other machines on the same network are working ok

with the mount command, so this seems to point to something being wrong

with this particular box.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 24, 2008 10:49 AM

To: builds-networking

Subject: Re: RE: qnet problem under qnx6.3.2

relevant sloginfo as follows:

Jun 24 09:52:39    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init()

- calling

Jun 24 09:52:39    7    15     0 npm-qnet(L4): en_ionet_rx_ctrl(): new

interface: en0: index 0 cell 1 endpt 0 iface 0 mac addr

00:0D:60:10:62:87

Jun 24 09:52:39    7    15     0 npm-qnet(QOS): nd_change_notify(): Node

Up:   nd 0 xx.edu

Jun 24 09:52:39    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init()

- complete: 0

Jun 24 09:52:39    7    15     0 npm-qnet(L4):

lr_verify_my_name_and_domain(): starting resolution of our hostname

xx.edu to ensure unique

Jun 24 09:52:40    7    15     0 npm-qnet(L4):

lr_verify_my_name_and_domain(): qnet going online

seemed okay, i started the qnet thru "mount -T io-net

/lib/dll/npm-qnet.so", this scipt could work well on other machines. and

the nicinfo should be no problem.

thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9585

post9585: Re: RE: qnet problem under qnx6.3.2

2008-06-24T14:49:05Z

relevant sloginfo as follows:

Jun 24 09:52:39    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init() - calling

Jun 24 09:52:39    7    15     0 npm-qnet(L4): en_ionet_rx_ctrl(): new interface: en0: index 0 cell 1 endpt 0 iface 0 mac addr 00:0D:60:10:62:87

Jun 24 09:52:39    7    15     0 npm-qnet(QOS): nd_change_notify(): Node Up:   nd 0 xx.edu

Jun 24 09:52:39    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init() - complete: 0

Jun 24 09:52:39    7    15     0 npm-qnet(L4): lr_verify_my_name_and_domain(): starting resolution of our hostname xx.edu to ensure unique

Jun 24 09:52:40    7    15     0 npm-qnet(L4): lr_verify_my_name_and_domain(): qnet going online

seemed okay, i started the qnet thru "mount -T io-net /lib/dll/npm-qnet.so", this scipt could work well on other machines. and the nicinfo should be no problem.

thx

Eric

post9576: RE: qnet problem under qnx6.3.2

2008-06-24T14:08:57Z

If you can provide information from nicinfo, sloginfo to start that

might help to diagnose the problem.

The corrupted file system could be a problem, but that seems unlikely.

You can use "chkfsys" to fix the file system corruption if it isn't too

severe.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 24, 2008 5:00 AM

To: builds-networking

Subject: qnet problem under qnx6.3.2

I have a qnx 6.3.2 machine and qnx6.3.2 target, i wanna the two to

transfer data via qnet.

i was able to start them via "mount -T io-net /lib/dll/npm-qnet.so" and

the two could ping thru each other, but under /net of the target, there

was no qnx host there. when i changed another host machine, then /net

had the host name.

And another problem is that when the qnx host started, it popped up:

"Unable to mount a qnx4 file systems as fs/hd0-qnx4 on /dev/hd0779

(Corrupted file system detected), may the qnet problem be the result of

this?

thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9547

post9565: Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-24T13:30:17Z

> well, seems not fully solved:

> the adhoc network could not work now, i tried "nicinfo"

> only the wired ethernet network card showed its message, without the wireless

> orinoco.  since when i only "io-net -d orinoco -p tcpip", "nicinfo" would show

>  the orinoco's info.

> so, the orinoco card still could not work, i.e. "mount -o channel=11,......-p

> tcpip" didnot fully start the orinoco card.

>

> Eric

some updates, the problem now is that qnx machines in the wlan could not ping thru one another in the adhoc mode.

when i tried "nicinfo -r en1" it would display the nicinfo of the orinoco card like follows:

ORiNOCO 802.11 Wireless Ethernet Controller

  Physical Node ID ........................... 00022D 01B57F

  Current Physical Node ID ................... 00022D 01B57F

  Current Operation Rate ..................... 11.00 Mb/s half-duplex

  Active Interface Type ...................... Unknown

  Maximum Transmittable data Unit ............ 1514

  Maximum Receivable data Unit ............... 1514

  Hardware Interrupt ......................... 0x3

  I/O Aperture ............................... 0x300 - 0x33f

  Promiscuous Mode ........................... Off

  Multicast Support .......................... Enabled

  Station Name ...............................

  Network Name (SSID) ........................

  Channel: ................................... 4294967295

  BSS Type ................................... Unknown

  Packets Transmitted OK ..................... 0

  Bytes Transmitted OK ....................... 300

  Packets Received OK ........................ 3

  Bytes Received OK .......................... 0

so, what are the possible reasons here? thx

Eric

post9564: RE: qnet problem under qnx6.3.2

2008-06-24T13:26:05Z

If you have more than 1 interface, you have to specify which one is

bound to qnet. (use option bind=nic in your mount command).

Thanks.

Weijie

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: June 24, 2008 5:00 AM

To: builds-networking

Subject: qnet problem under qnx6.3.2

I have a qnx 6.3.2 machine and qnx6.3.2 target, i wanna the two to

transfer data via qnet.

i was able to start them via "mount -T io-net /lib/dll/npm-qnet.so" and

the two could ping thru each other, but under /net of the target, there

was no qnx host there. when i changed another host machine, then /net

had the host name.

And another problem is that when the qnx host started, it popped up:

"Unable to mount a qnx4 file systems as fs/hd0-qnx4 on /dev/hd0779

(Corrupted file system detected), may the qnet problem be the result of

this?

thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9547

post9547: qnet problem under qnx6.3.2

2008-06-24T09:00:25Z

I have a qnx 6.3.2 machine and qnx6.3.2 target, i wanna the two to transfer data via qnet.

i was able to start them via "mount -T io-net /lib/dll/npm-qnet.so" and the two could ping thru each other, but under /net of the target, there was no qnx host there. when i changed another host machine, then /net had the host name.

And another problem is that when the qnx host started, it popped up:

"Unable to mount a qnx4 file systems as fs/hd0-qnx4 on /dev/hd0779 (Corrupted file system detected), may the qnet problem be the result of this?

thx

Eric

post9544: Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-24T03:36:17Z

well, seems not fully solved:

the adhoc network could not work now, i tried "nicinfo"

only the wired ethernet network card showed its message, without the wireless orinoco. since when i only "io-net -d orinoco -p tcpip", "nicinfo" would show the orinoco's info.

so, the orinoco card still could not work, i.e. "mount -o channel=11,......-p tcpip" didnot fully start the orinoco card.

Eric

post9521: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-23T14:25:05Z

Hi Eric:

Only thing I can think of again is timing. The time it takes to

set up and configure the first interface is what's needed for the pccard

server to settle so that it's ready when the Orinoco is mounted...

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Monday, June 23, 2008 8:49 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: RE: Start script for two network cards

thx, i tried like this from another guy's idea, and it worked fine now.

sloginfo -c

/proc/boot/devp-pccard -vvvv &

waitfor /dev/pccard 59

# sloginfo > sloginfo.txt

io-net -d ns83815 -p tcpip -p qnet bind=en0

waitfor /dev/io-net/en0

waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

mount -o channel=11,network=mywork,mode=adhoc -Tio-net devn-orinoco.so

waitfor /dev/io-net/en1

ifconfig en1 *.*.*.* netmask 255.255.255.0

seemed changed the io-net with mount would make effects?

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9512

post9512: Re: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-23T12:49:05Z

thx, i tried like this from another guy's idea, and it worked fine now.

sloginfo -c

/proc/boot/devp-pccard -vvvv &

waitfor /dev/pccard 59

# sloginfo > sloginfo.txt

io-net -d ns83815 -p tcpip -p qnet bind=en0

waitfor /dev/io-net/en0

waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

mount -o channel=11,network=mywork,mode=adhoc -Tio-net devn-orinoco.so

waitfor /dev/io-net/en1

ifconfig en1 *.*.*.* netmask 255.255.255.0

seemed changed the io-net with mount would make effects?

Eric

post9499: RE: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-21T04:43:09Z

Just a thought.

Maybe put "pin" in your image, and try run it after "waitfor /dev/pccard

59", see if "pin" can detect any device. If it can't, put "sleep 5"

before "pin".

Like this.

/proc/boot/devp-pccard -vvvv &

waitfor /dev/pccard 59

/proc/boot/sleep 5

/proc/boot/pin

# sloginfo > sloginfo.txt

io-net -d ns83815 -d orinoco

channel=11,network=mywork,mode=adhoc -p tcpip -p qnet bind=en0

-xtang

> -----Original Message-----

> From: Eric Dong [mailto:eric.dongxx@gmail.com]

> Sent: June 21, 2008 12:18 AM

> To: builds-networking

> Subject: Re: RE: RE: RE: RE: RE: Start script for two network cards

>

> Hi, Robert, My whole script is belows:

>

> # Start up some consoles

> devc-con -n1 &

> reopen /dev/con1

> devc

>     display_msg Welcome

> # Start the pci server

> display_msg "start sedres pci-bios "

> seedres

> pci-bios &

> waitfor /dev/pci

>

> # Start up the CompactFlash Disk drivers

> display_msg "auto mount CF card hd0t77...."

>     devb-eide blk automount=hd0t77:/ eide nobmstr &

>

> # Wait for th uav/bin for the rest of the commands (up to 200 secs)

> display_msg "waitfor /x86/bin....."

> waitfor /x86/bin 10

>

> #Start up TCP/IP and QNET

> slogger

> sleep 5

>

> sloginfo -c

> /proc/boot/devp-pccard -vvvv &

> waitfor /dev/pccard 59

> # sloginfo > sloginfo.txt

> io-net -d ns83815 -d orinoco

channel=11,network=mywork,mode=adhoc -p

> tcpip -p qnet bind=en0

> waitfor /dev/io-net/en0

> waitfor /dev/io-net/en1

> waitfor /dev/socket

>

> ifconfig en0 *.*.*.* netmask 255.255.0.0

> ifconfig en1 *.*.*.* netmask 255.255.255.0

>

> # Start some common servers

>     display_msg "some drivers , especially devc-ser8250, starts...."

> qconn &

> pipe &

> mqueue &

> devc-pty &

>

>     devc-ser8250 -u 1 -b 57600 3f8,4&

>     devc-ser8250 -u 2 -b 115200 2f8,3&

>     devc-ser8250 -u 3 -b 115200 3e8,9&

> # devc-ser8250 -u 4 -b 115200 2e8,3&

>

>    .........

>

>

>

> _______________________________________________

> Builds

> http://community.qnx.com/sf/go/post9498

post9498: Re: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-21T04:17:57Z

Hi, Robert, My whole script is belows:

# Start up some consoles

devc-con -n1 &

reopen /dev/con1

devc

    display_msg Welcome

# Start the pci server

display_msg "start sedres pci-bios "

seedres

pci-bios &

waitfor /dev/pci

# Start up the CompactFlash Disk drivers

display_msg "auto mount CF card hd0t77...."

    devb-eide blk automount=hd0t77:/ eide nobmstr &



# Wait for th uav/bin for the rest of the commands (up to 200 secs)

display_msg "waitfor /x86/bin....."

waitfor /x86/bin 10

#Start up TCP/IP and QNET

slogger

sleep 5

sloginfo -c

/proc/boot/devp-pccard -vvvv &

waitfor /dev/pccard 59

# sloginfo > sloginfo.txt

io-net -d ns83815 -d orinoco channel=11,network=mywork,mode=adhoc -p tcpip -p qnet bind=en0

waitfor /dev/io-net/en0

waitfor /dev/io-net/en1

waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

ifconfig en1 *.*.*.* netmask 255.255.255.0



# Start some common servers

    display_msg "some drivers , especially devc-ser8250, starts...."

qconn &

pipe &

mqueue &

devc-pty &

    devc-ser8250 -u 1 -b 57600 3f8,4&

    devc-ser8250 -u 2 -b 115200 2f8,3&

    devc-ser8250 -u 3 -b 115200 3e8,9&

# devc-ser8250 -u 4 -b 115200 2e8,3&



   .........

post9488: RE: RE: RE: RE: RE: Start script for two network cards

2008-06-20T18:21:44Z

Hi Eric:

I've asked around and it looks like the network driver is trying

to access the card before it's been enumerated....

Make sure that you have

waitfor /dev/pccard

and add

sleep(3)

after it in the script before you start io-net.

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Friday, June 20, 2008 3:17 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: Start script for two network cards

Hi, Robert, here is the output of my sloginfo.txt:

Time             Sev Major Minor Args

Feb 17 21:30:41    5    18     0 devp-pccard: Found Vendor 104c - Device

ac51

Feb 17 21:30:42    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 GetStatus Socket 1 returned CardState

80 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 GetSocket Socket 1 returned SCIntMask 0

- Vcontrol 10 - VppLevels 0 -

VccLevel 0 - CtlInd 0 - State 80 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 Socket state 80

Feb 17 21:30:42    5    18     0 Card Inserted

Feb 17 21:30:42    5    18     0 5.0V Card

Feb 17 21:30:42    5    18     0 io_open for id = 30007

Feb 17 21:30:42    2    18     0 io_close_ocb

Feb 17 21:30:42    5    18     0 io_open for id = 7

Feb 17 21:30:43    2    18     0 Timer expired 2

Feb 17 21:30:43    5    18     0 Powered up 2

Feb 17 21:30:43    5    14     0 tcpip starting

Feb 17 21:30:43    3    14     0 Using pseudo random generator.  See

"random" option

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0

- Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 devp-pccard: Memory window req. 0

Feb 17 21:30:43    5    18     0 devp-pccard: Memory window act.

1e001000

Feb 17 21:30:43    2    18     0 LAN Node ID 00 02 2d 07 22 5e

Feb 17 21:30:43    5    18     0 Config Base 3e0

Feb 17 21:30:43    5    18     0 Rmask 1

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 IRQ1 = 7f - IRQ2 = ffff

Feb 17 21:30:43    5    18     0 I/O 0 - Len 64 - ip 8071ff0

Feb 17 21:30:43    5    18     0 IRQ 7

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0

- Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0

- Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 I/O port 300

Feb 17 21:30:43    5    18     0 Config base 3e0 - Index 1 - Window 0 -

Page 0

Feb 17 21:30:43    5    18     0 Base - 40105000 - p = 401053e0

Feb 17 21:30:44    2    18     0 Timer expired 3

Feb 17 21:30:44    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 GetSocket Socket 1 returned SCIntMask 0

- Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 Socket state c0

Feb 17 21:30:44    5    18     0 Card Inserted

Feb 17 21:30:45    2    18     0 Timer expired 3

Feb 17 21:30:45    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:45    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:46    2    18     0 Timer expired 3

Feb 17 21:30:47    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:47    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:48    2    18     0 Timer expired 3

Feb 17 21:30:48    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:48    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:49    2    18     0 Timer expired 3

Feb 17 21:30:49    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:50    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:51    2    18     0 Timer expired 3

Feb 17 21:30:51    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:51    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:52    2    18     0 Timer expired 3

Feb 17 21:30:52    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:52    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:53    2    18     0 Timer expired 3

Feb 17 21:30:54    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:54    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:55    2    18     0 Timer expired 3

Feb 17 21:30:55    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:55    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:56    2    18     0 Timer expired 3

Feb 17 21:30:56    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:57    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:58    2    18     0 Timer expired 3

Feb 17 21:30:58    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:58    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:59    2    18     0 Timer expired 3

Feb 17 21:30:59    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:59    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:00    2    18     0 Timer expired 3

Feb 17 21:31:01    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:01    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:02    2    18     0 Timer expired 3

Feb 17 21:31:02    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:02    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:03    2    18     0 Timer expired 3

Feb 17 21:31:03    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:04    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:05    2    18     0 Timer expired 3

Feb 17 21:31:05    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:05    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:06    2    18     0 Timer expired 3

Feb 17 21:31:06    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:06    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:07    2    18     0 Timer expired 3

Feb 17 21:31:08    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:08    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:09    2    18     0 Timer expired 3

Feb 17 21:31:09    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:09    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:10    2    18     0 Timer expired 3

Feb 17 21:31:10    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:11    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:12    2    18     0 Timer expired 3

Feb 17 21:31:12    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:12    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:13    2    18     0 Timer expired 3

Feb 17 21:31:13    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:13    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:14    2    18     0 Timer expired 3

Feb 17 21:31:15    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:15    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:16    2    18     0 Timer expired 3

Feb 17 21:31:16    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:16    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:17    2    18     0 Timer expired 3

Feb 17 21:31:17    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:18    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:19    2    18     0 Timer expired 3

Feb 17 21:31:19    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:19    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:20    2    18     0 Timer expired 3

Feb 17 21:31:20    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:20    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:21    2    18     0 Timer expired 3

Feb 17 21:31:22    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:22    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:23    2    18     0 Timer expired 3

Feb 17 21:31:23    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:23    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:24    2    18     0 Timer expired 3

Feb 17 21:31:24    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:25    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:26    2    18     0 Timer expired 3

Feb 17 21:31:26    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:26    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:27    2    18     0 Timer expired 3

Feb 17 21:31:27    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:27    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:28    2    18     0 Timer expired 3

Feb 17 21:31:29    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:29    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:30    2    18     0 Timer expired 3

Feb 17 21:31:30    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:30    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:31    2    18     0 Timer expired 3

Feb 17 21:31:32    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:32    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:33    2    18     0 Timer expired 3

Feb 17 21:31:33    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:33    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:34    2    18     0 Timer expired 3

Feb 17 21:31:34    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:35    5    18     0 GetStatus Socket 1 returned CardState

c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:36    2    18     0 Timer expired 3

Feb 17 21:31:36    5    18     0 GetStatus Socket 0 returned CardState 0

- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9450

post9450: Re: RE: RE: RE: RE: Start script for two network cards

2008-06-20T07:17:10Z

Hi, Robert, here is the output of my sloginfo.txt:

Time             Sev Major Minor Args

Feb 17 21:30:41    5    18     0 devp-pccard: Found Vendor 104c - Device ac51

Feb 17 21:30:42    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 GetStatus Socket 1 returned CardState 80 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 0 -

VccLevel 0 - CtlInd 0 - State 80 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 Socket state 80

Feb 17 21:30:42    5    18     0 Card Inserted

Feb 17 21:30:42    5    18     0 5.0V Card

Feb 17 21:30:42    5    18     0 io_open for id = 30007

Feb 17 21:30:42    2    18     0 io_close_ocb

Feb 17 21:30:42    5    18     0 io_open for id = 7

Feb 17 21:30:43    2    18     0 Timer expired 2

Feb 17 21:30:43    5    18     0 Powered up 2

Feb 17 21:30:43    5    14     0 tcpip starting

Feb 17 21:30:43    3    14     0 Using pseudo random generator.  See "random" option

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 devp-pccard: Memory window req. 0

Feb 17 21:30:43    5    18     0 devp-pccard: Memory window act. 1e001000

Feb 17 21:30:43    2    18     0 LAN Node ID 00 02 2d 07 22 5e

Feb 17 21:30:43    5    18     0 Config Base 3e0

Feb 17 21:30:43    5    18     0 Rmask 1

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 Rmask 0

Feb 17 21:30:43    5    18     0 IRQ1 = 7f - IRQ2 = ffff

Feb 17 21:30:43    5    18     0 I/O 0 - Len 64 - ip 8071ff0

Feb 17 21:30:43    5    18     0 IRQ 7

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:43    5    18     0 I/O port 300

Feb 17 21:30:43    5    18     0 Config base 3e0 - Index 1 - Window 0 - Page 0

Feb 17 21:30:43    5    18     0 Base - 40105000 - p = 401053e0

Feb 17 21:30:44    2    18     0 Timer expired 3

Feb 17 21:30:44    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -

VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 Socket state c0

Feb 17 21:30:44    5    18     0 Card Inserted

Feb 17 21:30:45    2    18     0 Timer expired 3

Feb 17 21:30:45    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:45    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:46    2    18     0 Timer expired 3

Feb 17 21:30:47    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:47    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:48    2    18     0 Timer expired 3

Feb 17 21:30:48    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:48    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:49    2    18     0 Timer expired 3

Feb 17 21:30:49    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:50    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:51    2    18     0 Timer expired 3

Feb 17 21:30:51    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:51    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:52    2    18     0 Timer expired 3

Feb 17 21:30:52    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:52    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:53    2    18     0 Timer expired 3

Feb 17 21:30:54    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:54    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:55    2    18     0 Timer expired 3

Feb 17 21:30:55    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:55    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:56    2    18     0 Timer expired 3

Feb 17 21:30:56    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:57    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:58    2    18     0 Timer expired 3

Feb 17 21:30:58    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:58    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:30:59    2    18     0 Timer expired 3

Feb 17 21:30:59    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:59    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:00    2    18     0 Timer expired 3

Feb 17 21:31:01    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:01    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:02    2    18     0 Timer expired 3

Feb 17 21:31:02    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:02    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:03    2    18     0 Timer expired 3

Feb 17 21:31:03    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:04    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:05    2    18     0 Timer expired 3

Feb 17 21:31:05    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:05    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:06    2    18     0 Timer expired 3

Feb 17 21:31:06    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:06    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:07    2    18     0 Timer expired 3

Feb 17 21:31:08    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:08    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:09    2    18     0 Timer expired 3

Feb 17 21:31:09    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:09    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:10    2    18     0 Timer expired 3

Feb 17 21:31:10    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:11    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:12    2    18     0 Timer expired 3

Feb 17 21:31:12    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:12    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:13    2    18     0 Timer expired 3

Feb 17 21:31:13    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:13    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:14    2    18     0 Timer expired 3

Feb 17 21:31:15    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:15    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:16    2    18     0 Timer expired 3

Feb 17 21:31:16    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:16    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:17    2    18     0 Timer expired 3

Feb 17 21:31:17    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:18    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:19    2    18     0 Timer expired 3

Feb 17 21:31:19    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:19    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:20    2    18     0 Timer expired 3

Feb 17 21:31:20    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:20    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:21    2    18     0 Timer expired 3

Feb 17 21:31:22    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:22    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:23    2    18     0 Timer expired 3

Feb 17 21:31:23    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:23    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:24    2    18     0 Timer expired 3

Feb 17 21:31:24    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:25    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:26    2    18     0 Timer expired 3

Feb 17 21:31:26    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:26    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:27    2    18     0 Timer expired 3

Feb 17 21:31:27    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:27    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:28    2    18     0 Timer expired 3

Feb 17 21:31:29    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:29    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:30    2    18     0 Timer expired 3

Feb 17 21:31:30    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:30    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:31    2    18     0 Timer expired 3

Feb 17 21:31:32    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:32    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:33    2    18     0 Timer expired 3

Feb 17 21:31:33    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:33    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:34    2    18     0 Timer expired 3

Feb 17 21:31:34    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:31:35    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1

Feb 17 21:31:36    2    18     0 Timer expired 3

Feb 17 21:31:36    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

post9437: RE: RE: RE: RE: Start script for two network cards

2008-06-19T15:36:06Z

Hi Eric:

You need to run "slogger" before you start io-net to get

sloginfo to work.

I take it from the follow on e-mail that the orinoco driver

wasn't in the correct directory?

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Thursday, June 19, 2008 11:10 AM

To: builds-networking

Subject: Re: RE: RE: RE: Start script for two network cards

thx again, Robert.

I put devn-orinoco.so in the same directory as devn-ns83815--/x86/dll

but still the same error:

   unable to load dll /x86/dll/orinoco: Library cannot be found

   unable to access "/dev/io-net/en1"

and when i tried "sloginfo":

   Unable to open /dev/slog: No such file or directory.

however, when the target finished booting, i typed "io-net -d orinoco -p

tcpip" without specifying its directory, the orinoco card worked.

Appreciate your help.

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9434

post9436: Re: RE: RE: RE: Start script for two network cards

2008-06-19T15:17:59Z

> however, when the target finished booting, i typed "io-net -d orinoco -p tcpip

> " without specifying its directory, the orinoco card worked.

sorry, plz ignore this. i still kept the previous one under /proc/boot.

post9434: Re: RE: RE: RE: Start script for two network cards

2008-06-19T15:10:27Z

thx again, Robert.

I put devn-orinoco.so in the same directory as devn-ns83815--/x86/dll

but still the same error:

   unable to load dll /x86/dll/orinoco: Library cannot be found

   unable to access "/dev/io-net/en1"

and when i tried "sloginfo":

   Unable to open /dev/slog: No such file or directory.

however, when the target finished booting, i typed "io-net -d orinoco -p tcpip" without specifying its directory, the orinoco card worked.

Appreciate your help.

Eric

post9425: RE: RE: RE: Start script for two network cards

2008-06-19T13:42:45Z

Hi Eric:

If you want to restrict the usage of qnet to a single interface

(the ns83815), you can use the following line

io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p

tcpip -p qnet bind=en0

And yes, devn-orinoco.so needs to be in the same place as you're ns83815

binary.

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Thursday, June 19, 2008 8:06 AM

To: builds-networking

Subject: Re: RE: RE: Start script for two network cards

thx, Robert.

The script "io-net -d ns83815 -d orinoco

channel=11,network=nusuav,mode=adhoc -p tcpip -p qnet &"

is going to assign two interfaces to the two network cards, right? a

little confused is that the -p option, here can ns83815 work with tcpip

and qnet while orinoco only work with tcpip or also with qnet?

Another problem about the orinoco, would it be that i need to put the

devn-orinoco.so into some particular directory?

thx

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9421

post9421: Re: RE: RE: Start script for two network cards

2008-06-19T12:06:10Z

thx, Robert.

The script "io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip -p qnet &"

is going to assign two interfaces to the two network cards, right? a little confused is that the -p option, here can ns83815 work with tcpip and qnet while orinoco only work with tcpip or also with qnet?

Another problem about the orinoco, would it be that i need to put the devn-orinoco.so into some particular directory?

thx

Eric

post9379: RE: RE: Start script for two network cards

2008-06-18T14:18:53Z

Hi Eric:

There are a couple of problems here...

The

waitfor /dev/pccard

must be as typed.  What this does is wait for the devp-pccard binary to

start up and register /dev/pccard (as opposed to looking for the

binary).  The /dev/pccard entry is what the libs look for in order to

get access to the pccard information.

The second problem is that you're starting up two version of io-net and

this isn't going to give you the expected behaviour.

Give this a try:

/proc/boot/devp-pccard

waitfor /dev/pccard

io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p

tcpip -p qnet &

waitfor /dev/io-net/en0

wauitfor /dev/io-net/en1

waitfor /dev/socket



ifconfig en0 *.*.*.* netmask 255.255.0.0

ifconfig en1 *.*.*.* netmask 255.255.0.0

I suspect that this isn't going to fix the Orinoco problem since you're

sleep 2 should have been adequate. Is there any information in sloginfo?

(Is slogger up and running before you're script starts)?  You can also

add -vvv options to each of the drivers to get additional output for

debugging.  If the command works at the command line after the system is

booted, then there's another dependency that's being missed out on.

Hope that helps,

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Wednesday, June 18, 2008 3:31 AM

To: builds-networking

Subject: Re: RE: Start script for two network cards

thx, Robet. now my scripts are like this:

    io-net -d ns83815 -p tcpip -p qnet &

    waitfor /dev/io-net/en0

    waitfor /dev/socket/2



    ifconfig en0 *.*.*.*

    netmask 255.255.0.0

devp-pccard

waitfor /proc/boot/devp-pccard (i put this binary here on the

target)

io-net -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip

sleep 2

ifconfig en1 192.168.1.10 netmask 255.255.255.0

still the same error. thx for ur suggestions.

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9371

post9371: Re: RE: Start script for two network cards

2008-06-18T07:30:57Z

thx, Robet. now my scripts are like this:

    io-net -d ns83815 -p tcpip -p qnet &

    waitfor /dev/io-net/en0

    waitfor /dev/socket/2



    ifconfig en0 *.*.*.*

    netmask 255.255.0.0

devp-pccard

waitfor /proc/boot/devp-pccard (i put this binary here on the target)

io-net -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip

sleep 2

ifconfig en1 192.168.1.10 netmask 255.255.255.0

still the same error. thx for ur suggestions.

Eric

post9333: RE: Start script for two network cards

2008-06-17T15:57:23Z

1) I wonder if you're starting things too early...  Is it possible that

you're trying to launch the Orinoco driver before devp-pccard has

completed?  If you add in a "waitfor /dev/pccard" after devp-pccard,

does that make any difference?

Also, just to make sure...  You aren't running two versions of the stack

on startup are you?  If you want to have two separate interfaces, you

have to either specify both on the command line (with separate -d

options) or "mount" the interfaces after io-net has started.

2)  Interfaces in io-net are numbered sequentially from 0 as they're

loaded in.  You can either use dhcp.client or manually assign the

interface an IP address.  Make sure that the two interfaces are on

separate subnets though.  If you assign addresses on the same subnet to

different interfaces, you'll get peculiar results.

Robert.

-----Original Message-----

From: Eric Dong [mailto:eric.dongxx@gmail.com]

Sent: Tuesday, June 17, 2008 7:25 AM

To: builds-networking

Subject: Start script for two network cards

I have a qnx6.3.2 PC104 computer stack with two network cards, one is

the onboard ethernet card, the other the orinoco wifi network card.

Basically, i wanna use the wifi card for msg passing with other qnx

machines, while the wired card for debugging usage. I have two problems:

1. I use the following boot scripts to start the wired network qnet:

    io-net -d ns83815 -p tcpip -p qnet &

    waitfor /dev/io-net/en0

    waitfor /dev/socket/2

    ifconfig en0 *.*.*.*

and it works fine. but i used

    devp-pccard

    io-net -d orinoco -p tcpip

the machine gave the error during its boot:

    unable to init dll devn-orinoco: No such device.

But when the machine finishes starting, i typed the above two commands

again, the orinoco wifi card starts to work. i have no ideas about this.

2. There are two network interfaces, so i should assign two different ip

address for each interface? for the wired network case, the above

scripts are okay. how about when coming the assign the ip to the wifi

network card? use en1? or ??

Thank you

Eric

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9277

post9277: Start script for two network cards

2008-06-17T11:24:53Z

I have a qnx6.3.2 PC104 computer stack with two network cards, one is the onboard ethernet card, the other the orinoco wifi network card. Basically, i wanna use the wifi card for msg passing with other qnx machines, while the wired card for debugging usage. I have two problems:

1. I use the following boot scripts to start the wired network qnet:

    io-net -d ns83815 -p tcpip -p qnet &

    waitfor /dev/io-net/en0

    waitfor /dev/socket/2

    ifconfig en0 *.*.*.*

and it works fine. but i used

    devp-pccard

    io-net -d orinoco -p tcpip

the machine gave the error during its boot:

    unable to init dll devn-orinoco: No such device.

But when the machine finishes starting, i typed the above two commands again, the orinoco wifi card starts to work. i have no ideas about this.

2. There are two network interfaces, so i should assign two different ip address for each interface? for the wired network case, the above scripts are okay. how about when coming the assign the ip to the wifi network card? use en1? or ??

Thank you

Eric

post9233: RE: source availability

2008-06-16T18:17:30Z

Hi Mario:

Everything not covered by NDA is going to get moved into the

foundry. We're in the process of running the other code through some

source analyzers before we post it. It should be there in a few weeks.

Robert.

-----Original Message-----

From: Mario Charest [mailto:mcharest@zinformatic.com]

Sent: Monday, June 16, 2008 2:16 PM

To: builds-networking

Subject: source availability

Will the source available from svn contain everything and not just stuff

that is specific to io-pkt?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post9231

post9231: source availability

2008-06-16T18:16:09Z

Will the source available from svn contain everything and not just stuff that is specific to io-pkt?

post7283: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-24T20:40:29Z

Hi Hayder:

Can you do me a favour and start up a new thread in the Technology

forum instead of this one? This thread is a bit misleading now and those

who would be able to answer this question are probably not monitoring this

forum.

Thanks!

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Thursday, April 24, 2008 11:58 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

Greetings,

I was wondering how you setup the encryption with 8548 and Windows XP? I

have this on my ppc:

spdadd 10.4.255.254 10.4.0.2 any -P out ipsec esp/transport//require;

spdadd 10.4.0.2 10.4.255.254 any -P in ipsec esp/transport//require;

add 10.4.255.254 10.4.0.2 ah 1235 -A hmac-md5 "1234567890123456";

add 10.4.255.254 10.4.0.2 esp 1234 -m any -E 3des-cbc

"KeyIsTwentyFourBytesLong";

add 10.4.0.2 10.4.255.254 ah 1236 -A hmac-md5 "1234567890123456";

add 10.4.0.2 10.4.255.254 esp 1234 -m any -E 3des-cbc

"KeyIsTwentyFourBytesLong";

Windows makes you have authentication, but when I set it up between the 2

machines, I dont see any place to provide the md5 hash key. Is the hash key

sent in the message somehow?

Also, is there a way to test that the encryption is working? I have the 8548

talking to an 8260, which should be using software encryption.

Many thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7252

post7252: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-24T15:58:06Z

Greetings,

I was wondering how you setup the encryption with 8548 and Windows XP? I have this on my ppc:

spdadd 10.4.255.254 10.4.0.2 any -P out ipsec esp/transport//require;

spdadd 10.4.0.2 10.4.255.254 any -P in ipsec esp/transport//require;

add 10.4.255.254 10.4.0.2 ah 1235 -A hmac-md5 "1234567890123456";

add 10.4.255.254 10.4.0.2 esp 1234 -m any -E 3des-cbc "KeyIsTwentyFourBytesLong";

add 10.4.0.2 10.4.255.254 ah 1236 -A hmac-md5 "1234567890123456";

add 10.4.0.2 10.4.255.254 esp 1234 -m any -E 3des-cbc "KeyIsTwentyFourBytesLong";

Windows makes you have authentication, but when I set it up between the 2 machines, I dont see any place to provide the md5 hash key. Is the hash key sent in the message somehow?

Also, is there a way to test that the encryption is working? I have the 8548 talking to an 8260, which should be using software encryption.

Many thanks.

post7156: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-22T11:29:11Z

Andrew,

Attached is an output of the log from the sec engine test. My goal for this morning is to get the hardware encryption running and talking to another machine using software encryption. Thanks for your help.

--H

post7131: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T16:59:47Z

Forgot the last question. The SVN repository that you see today is exactly

the same as the one that we work in, so everything there is the latest and

greatest.

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Monday, April 21, 2008 12:51 PM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using

XP

R,

I think a solution has been found! The bootcmd environment variable had a

different length than what the new image with io-pkt had. It was not loading

the entire image into ram, and I guess io-pkt was in the middle. Changed it

to make it bigger, and it all works fine now.

With that out of the way. Can you use io-pkt without hc to talk to a machine

with hc? Does the hc encrypt/decrypt everything on the stack? Are the files

in the svn the lastest for mpcsec?

Many thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7128

post7130: RE: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics usin g XP

2008-04-21T16:58:27Z

I'm a bit surprised that anything worked at all for you in that case :)).

Glad that's cleared up!

The io-pkt-v4-hc variant of the stack has a number of extra features some of

which include:

1) WiFi

2) Support for IPSec

3) Allows the default software crypto routines to be replaced with hardware

accelerated crypto.

The v4 variant of the stack can talk to the v4-hc variant of the stack as

long as you aren't using IPSec. The encryption in the stack isn't turned on

unless you create an IPSec session (see

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

wiki_page

)

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Monday, April 21, 2008 12:51 PM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using

XP

R,

I think a solution has been found! The bootcmd environment variable had a

different length than what the new image with io-pkt had. It was not loading

the entire image into ram, and I guess io-pkt was in the middle. Changed it

to make it bigger, and it all works fine now.

With that out of the way. Can you use io-pkt without hc to talk to a machine

with hc? Does the hc encrypt/decrypt everything on the stack? Are the files

in the svn the lastest for mpcsec?

Many thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7128

post7129: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T16:51:51Z

> the encryption results in the log do not

> match what is in the readme for mpcsec.

Argh, I had to make a change to the test

encryptions after another bug fix for multi-iov

input and output, and I didn't update the

readme :-(

If you start it with the verbose cranked up,

what info does it output to the console?

If you configure one machine with hardware

encryption (eg mpcsec) and the other side

with software encryption, can they talk?

post7128: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T16:50:57Z

R,

I think a solution has been found! The bootcmd environment variable had a different length than what the new image with io-pkt had. It was not loading the entire image into ram, and I guess io-pkt was in the middle. Changed it to make it bigger, and it all works fine now.

With that out of the way. Can you use io-pkt without hc to talk to a machine with hc? Does the hc encrypt/decrypt everything on the stack? Are the files in the svn the lastest for mpcsec?

Many thanks.

post7124: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T15:40:15Z

Hi Hayder:

By "log" I meant capture the output from your uboot terminal session

(running on the PC) so that we can see what you see when uboot is running.

In terms of what uboot does with the boot command, this depends upon how

you've set up uboot so we wouldn't be able to tell what it's actually doing.

I do know for sure that you can't download the image into RAM, "go 100000",

reset the board and "go 100000" again. When the OS starts up it will

overwrite all of the startup code that was originally at 100000...

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Monday, April 21, 2008 11:30 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using

XP

R,

I dont know if this helps or makes things more confusing, but this is a new

scenario I tried. I tftp'd the image, copied it into flash, and instead of

doing a go 100000, I did a boot. Am I correct in thinking this boots the

image from flash? If so, it works from there, but once I reset the target it

I get the io-pkt seg fault.

I did not see any log options in the uboot help, where can I find this log

information? Thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7122

post7122: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T15:30:05Z

R,

I dont know if this helps or makes things more confusing, but this is a new scenario I tried. I tftp'd the image, copied it into flash, and instead of doing a go 100000, I did a boot. Am I correct in thinking this boots the image from flash? If so, it works from there, but once I reset the target it I get the io-pkt seg fault.

I did not see any log options in the uboot help, where can I find this log information? Thanks.

post7118: RE: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics usin g XP

2008-04-21T14:48:19Z

Hi Hayder:

It looks like you're previous problem was due to a corrupt

installation which you fixed by moving to a new machine.  This output looks

to me like you've got something far more serious wrong with the image than

running io-pkt since none of your drivers or other processes are starting.

The only thing that comes to mind right away is that io-pkt is significantly

bigger than io-net. Have you checked the image size to make sure that you

haven't overrun some boundary?

It sounds like the tftp'd image ran without any problem, so the issue would

appear to be the transfer into and back out of flash.  Maybe you can post

the log output from your uboot session where you download the image, copy it

into FLASH and then reset the board to run the flash image.

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Monday, April 21, 2008 8:42 AM

To: builds-networking

Subject: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using

XP

R,

I jumped the gun too quickly. It was running because after I copied the

image into flash, I did a go 100000. This was running it out of ram, instead

of having the bootloader copy it into ram!! When I reset the target and want

it to run from flash I get:

System page at phys:0000c000 user:0000c000 kern:0000c000

Starting next program at v0013b5d4

Welcome to QNX Neutrino 6.3 on the PowerPC 8548CDS board

Unable to start "devc-ser8250-mpc8540" (84)

Unable to access "/dev/ser1" (2)

Unable to access "/dev/ser1" (2)

Unable to start "slogger" (84)

Unable to start "pipe" (84)

Unable to start "io-pkt-v4-hc" (84)

Unable to access "/dev/socket" (2)

Unable to start "ifconfig" (8)

Unable to start "devc-pty" (8)

Unable to access "/dev/ptyp0" (2)

Unable to access "/dev/socket" (2)

Unable to start "qconn" (8)

Unable to start "ksh" (84)

Steps:

tftp 100000 bsp-mpc8548ads.ifs

erase ff800000 ffdfffff

cp.b 100000 ff800000 <size>

So, now more interesting questions arise!!! Why can we run io-net with the

bootloader, but not io-pkt? We know io-pkt runs by itself, we know the whole

image runs, before we reset to have the bootloader load it into ram?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7107

post7107: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T12:41:49Z

R,

I jumped the gun too quickly. It was running because after I copied the image into flash, I did a go 100000. This was running it out of ram, instead of having the bootloader copy it into ram!! When I reset the target and want it to run from flash I get:

System page at phys:0000c000 user:0000c000 kern:0000c000

Starting next program at v0013b5d4

Welcome to QNX Neutrino 6.3 on the PowerPC 8548CDS board

Unable to start "devc-ser8250-mpc8540" (84)

Unable to access "/dev/ser1" (2)

Unable to access "/dev/ser1" (2)

Unable to start "slogger" (84)

Unable to start "pipe" (84)

Unable to start "io-pkt-v4-hc" (84)

Unable to access "/dev/socket" (2)

Unable to start "ifconfig" (8)

Unable to start "devc-pty" (8)

Unable to access "/dev/ptyp0" (2)

Unable to access "/dev/socket" (2)

Unable to start "qconn" (8)

Unable to start "ksh" (84)

Steps:

tftp 100000 bsp-mpc8548ads.ifs

erase ff800000 ffdfffff

cp.b 100000 ff800000 <size>

So, now more interesting questions arise!!! Why can we run io-net with the bootloader, but not io-pkt? We know io-pkt runs by itself, we know the whole image runs, before we reset to have the bootloader load it into ram?

post7103: Re: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-21T11:34:15Z

R,

More interesting finds!! I had another machine setup with momentics, so I built the 8548 bsp on it, and everything worked!! I don't know what would cause the difference in the images, they both have the same thing, but I still need to look into the differences with more detail.

I attached the output of the log. The key's and input are the same, but the iv, encryption, decryption are not right. I compared the readme I have to what's currently in svn, and at least for the test that were in the log the input and keys appear to be the same.

Thanks!

post7086: RE: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T21:02:40Z

Hi Hayder:

Well that's (sort of) a relief!  At least we know that the

networking build is all set up and working, although why the build file

isn't working for you confuses me...

The XML file generated by the tools is a bit difficult to interpret... I

couldn't see anything obviously wrong... Maybe we can work the other way

around.  If you send the image to me, I'll try and figure out why io-pkt

wasn't running from the image for you.

What parts of the log don't match the readme?  I know that we recently did

some tweaks to the driver to fix a problem that we found on the 8548, and

maybe those aren't reflected in the readme.  What command line do you use to

start io-pkt-v4-hc?

It is possible that there's a bug in the driver for multicast, so

I'll try and get someone else to look into that.  Are the multicast packet

counts incrementing as expected?

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Friday, April 18, 2008 4:48 PM

To: builds-networking

Subject: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

R,

An interesting find!! Momentics and the debugging was taking a hit! So, I

copied the executable and drivers to /tmp and ran it from there ... they

worked! I took the same files and built them into the image using momentics,

and they segfaulted. I think there must be something wrong with how it is

building the image or generating the build file. I attached my build file.

With io-pkt-v4 working, I went ahead and tried the -hc. Two things I've

noticed. First, the encryption results in the log do not match what is in

the readme for mpcsec. Second, when I do an ifconfig it says the driver is

configured for multicasting, but my multicast receiver program does not

receive messages; it is still receiving messages on the ppc8260 targets.

Thanks again for all your help! I appreciate it.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7085

post7085: Re: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T20:47:49Z

R,

An interesting find!! Momentics and the debugging was taking a hit! So, I copied the executable and drivers to /tmp and ran it from there ... they worked! I took the same files and built them into the image using momentics, and they segfaulted. I think there must be something wrong with how it is building the image or generating the build file. I attached my build file.

With io-pkt-v4 working, I went ahead and tried the -hc. Two things I've noticed. First, the encryption results in the log do not match what is in the readme for mpcsec. Second, when I do an ifconfig it says the driver is configured for multicasting, but my multicast receiver program does not receive messages; it is still receiving messages on the ppc8260 targets.

Thanks again for all your help! I appreciate it.

post7050: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T14:48:45Z

Hmmm... My current build has a bunch of custom stuff in it so I'd have to

re-work it to get it to you.

Let's take a quick shot at the debugging first since that should locate the

problem immediately.

R.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Friday, April 18, 2008 10:09 AM

To: builds-networking

Subject: Re: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

R,

I double checked and we are using the same system. Would it be possible for

you to send us your image, so see if it works?

Many thanks,

--H

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7045

post7049: RE: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T14:43:50Z

Ahhhhh!  Ok.  I think I now know what your problem is. Given that you're

connecting into the 8548 with the tools, you must already be running a

stack.  As soon as io-pkt starts running, it "takes over" from the old stack

and you lose your connection to the host so, from the host point of view,

things look ok, but you're debug session stops working.

Luckily, multiple stacks aren't an issue for Neutrino.  The way to get

around this is to start you initial stack with an alternate prefix.  Given

that you're using the io-net version of the stack, do the following:

# io-net -dmpc85xx syspage -ptcpip prefix=/alt

# SOCK=/alt ifconfig en0 xxx.xxx.xxx.xxx

# SOCK=/alt qconn

Adding the "SOCK=" setting before the command gets the socket library to

look for /alt/dev/socket instead of the usual /dev/socket so that when

io-pkt is started by the debugger, it won't conflict.

(See the last section of

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

ki_page

)

If you're starting io-pkt with a driver specified on the command line

through your launch configuration, you also have to make sure that you don't

specify the same device.  You can specify the device using the "pci=" option

to the driver

(e.g. io-net -dmpc85xx syspage,pci=0 -ptcpip prefix=/alt

io-pkt-v4 -dmpc85xx syspage,pci=1 )

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Friday, April 18, 2008 9:10 AM

To: builds-networking

Subject: Re: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

R,

I'm not sure if something got corrupted somewhere, but these are the steps I

follow for creating the staging area and results:

results of interest for set:

QCONF_OVERRIDE=c:/community/qconf-override.mk

QNX_CONFIGURATION=C:\Program Files\QNX Software Systems

QNX_HOST=C:/QNX632/host/win32/x86

QNX_TARGET=C:/QNX632/target/qnx6

contents of qconf-override.mk

USE_INSTALL_ROOT=1

INSTALL_ROOT_nto=C:/community/stage

VERSION=6.3.2

run hide-gnu script:

C:\community>c:\QNX632\host\win32\x86\usr\bin\ksh.exe hide-gnu.sh

c:/community

Locating GNUmakefile's in c:/community

Touching c:/community/trunk/utils/t/tcpdump/win32/prj/Makefile.dnm

mkdir stage

cd trunk

make OSLIST=nto hinstall

result of make:

c:/community/trunk/lib/socket/public/arpa/tftp.h ->

c:/community/stage/usr/include/arpa/tftp.h

cp: c:/community/stage/usr/include/arpa/tftp.h: Invalid argument

..............

C:/community/trunk/crypto/dist2/openssl/crypto/store/store.h ->

c:/community/stage/usr/include/openssl/store.h

cp: c:/community/stage/usr/include/openssl/store.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/txt_db/txt_db.h ->

c:/community/stage/usr/include/openssl/txt_db.h

cp: c:/community/stage/usr/include/openssl/txt_db.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/ui/ui.h ->

c:/community/stage/usr/include/openssl/ui.h

cp: c:/community/stage/usr/include/openssl/ui.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/ui/ui_compat.h ->

c:/community/stage/usr/include/openssl/ui_compat.h

cp: c:/community/stage/usr/include/openssl/ui_compat.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509/x509.h ->

c:/community/stage/usr/include/openssl/x509.h

cp: c:/community/stage/usr/include/openssl/x509.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509/x509_vfy.h ->

c:/community/stage/usr/include/openssl/x509_vfy.h

cp: c:/community/stage/usr/include/openssl/x509_vfy.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509v3/x509v3.h ->

c:/community/stage/usr/include/openssl/x509v3.h

cp: c:/community/stage/usr/include/openssl/x509v3.h: Invalid argument

make[4]: [hinstall] Error 1 (ignored)

C:/community/trunk/lib/crypto/openssl/opensslconf.h ->

c:/community/stage/usr/include/openssl/opensslconf.h

cp: c:/community/stage/usr/include/openssl/opensslconf.h: Invalid argument

make[4]: *** [hinstall] Error 1

make[4]: Leaving directory `C:/community/trunk/lib/crypto/arm/a.be'

make[3]: *** [hinstall] Error 2

make[3]: Leaving directory `C:/community/trunk/lib/crypto/arm'

make[2]: *** [hinstall] Error 2

make[2]: Leaving directory `C:/community/trunk/lib/crypto'

make[1]: *** [hinstall] Error 2

make[1]: Leaving directory `C:/community/trunk/lib'

make: *** [hinstall] Error 2

It says invalid arguments but the files are copied into stage until it

errors in the openssl.

Now these steps were working yesterday morning, but starting in the

afternoon it stopped working.

So, I shifted gears to the qnx workstation. I can build release/debug using

make <OPTIONS> install. The binary I'm left with for io-pkt-v4 is 3.2 meg,

which is bigger than the release of 700kb, so I'm assuming it built a proper

debug binary. In momentics I create a standard make c project, make the

default directory /root/trunk. It refreshes everything. I go to

sys/target/ppc/o.be.v4, the io-pkt-v4 binary is there, right click and do a

debug as debug, select my ppc8260 target, tell it to debug. It says attached

to process XXXXX, msgnak received - resending, then it says target has timed

out. I have a serial connection to the target as well, and if I do a pidin,

the process gets started up, and goes into the stopped state. Other projects

I can debug just fine.

I tried using command line ntoppc-gdb. When it starts up I enter:

target qnx 10.4.0.7:8000 (I have pdebug 8000 running on target)

connects to remote target

sym io-pkt-v4, says symbols load ok.

I set some break points at:

main and pre_main_init, I'm sure it has to hit those 2 functions??

run io-pkt-v4, then it says it starts running and nothing happens. I try

using next, step and it says cannot find bounds of current function.

I'm wanting to figure out what's happening on the ppc8260, since it works,

then apply it to the 8548. Have any ideas on what I could do to get the

debugging going from the qnx wkst? or Why the windows environment got messed

up? Thanks!

--H

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7041

post7045: Re: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T14:08:57Z

R,

I double checked and we are using the same system. Would it be possible for you to send us your image, so see if it works?

Many thanks,

--H

post7041: Re: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-18T13:10:10Z

R,

I'm not sure if something got corrupted somewhere, but these are the steps I follow for creating the staging area and results:

results of interest for set:

QCONF_OVERRIDE=c:/community/qconf-override.mk

QNX_CONFIGURATION=C:\Program Files\QNX Software Systems

QNX_HOST=C:/QNX632/host/win32/x86

QNX_TARGET=C:/QNX632/target/qnx6

contents of qconf-override.mk

USE_INSTALL_ROOT=1

INSTALL_ROOT_nto=C:/community/stage

VERSION=6.3.2

run hide-gnu script:

C:\community>c:\QNX632\host\win32\x86\usr\bin\ksh.exe hide-gnu.sh c:/community

Locating GNUmakefile's in c:/community

Touching c:/community/trunk/utils/t/tcpdump/win32/prj/Makefile.dnm

mkdir stage

cd trunk

make OSLIST=nto hinstall

result of make:

c:/community/trunk/lib/socket/public/arpa/tftp.h -> c:/community/stage/usr/include/arpa/tftp.h

cp: c:/community/stage/usr/include/arpa/tftp.h: Invalid argument

..............

C:/community/trunk/crypto/dist2/openssl/crypto/store/store.h -> c:/community/stage/usr/include/openssl/store.h

cp: c:/community/stage/usr/include/openssl/store.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/txt_db/txt_db.h -> c:/community/stage/usr/include/openssl/txt_db.h

cp: c:/community/stage/usr/include/openssl/txt_db.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/ui/ui.h -> c:/community/stage/usr/include/openssl/ui.h

cp: c:/community/stage/usr/include/openssl/ui.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/ui/ui_compat.h -> c:/community/stage/usr/include/openssl/ui_compat.h

cp: c:/community/stage/usr/include/openssl/ui_compat.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509/x509.h -> c:/community/stage/usr/include/openssl/x509.h

cp: c:/community/stage/usr/include/openssl/x509.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509/x509_vfy.h -> c:/community/stage/usr/include/openssl/x509_vfy.h

cp: c:/community/stage/usr/include/openssl/x509_vfy.h: Invalid argument

C:/community/trunk/crypto/dist2/openssl/crypto/x509v3/x509v3.h -> c:/community/stage/usr/include/openssl/x509v3.h

cp: c:/community/stage/usr/include/openssl/x509v3.h: Invalid argument

make[4]: [hinstall] Error 1 (ignored)

C:/community/trunk/lib/crypto/openssl/opensslconf.h -> c:/community/stage/usr/include/openssl/opensslconf.h

cp: c:/community/stage/usr/include/openssl/opensslconf.h: Invalid argument

make[4]: *** [hinstall] Error 1

make[4]: Leaving directory `C:/community/trunk/lib/crypto/arm/a.be'

make[3]: *** [hinstall] Error 2

make[3]: Leaving directory `C:/community/trunk/lib/crypto/arm'

make[2]: *** [hinstall] Error 2

make[2]: Leaving directory `C:/community/trunk/lib/crypto'

make[1]: *** [hinstall] Error 2

make[1]: Leaving directory `C:/community/trunk/lib'

make: *** [hinstall] Error 2

It says invalid arguments but the files are copied into stage until it errors in the openssl.

Now these steps were working yesterday morning, but starting in the afternoon it stopped working.

So, I shifted gears to the qnx workstation. I can build release/debug using make <OPTIONS> install. The binary I'm left with for io-pkt-v4 is 3.2 meg, which is bigger than the release of 700kb, so I'm assuming it built a proper debug binary. In momentics I create a standard make c project, make the default directory /root/trunk. It refreshes everything. I go to sys/target/ppc/o.be.v4, the io-pkt-v4 binary is there, right click and do a debug as debug, select my ppc8260 target, tell it to debug. It says attached to process XXXXX, msgnak received - resending, then it says target has timed out. I have a serial connection to the target as well, and if I do a pidin, the process gets started up, and goes into the stopped state. Other projects I can debug just fine.

I tried using command line ntoppc-gdb. When it starts up I enter:

target qnx 10.4.0.7:8000 (I have pdebug 8000 running on target)

connects to remote target

sym io-pkt-v4, says symbols load ok.

I set some break points at:

main and pre_main_init, I'm sure it has to hit those 2 functions??

run io-pkt-v4, then it says it starts running and nothing happens. I try using next, step and it says cannot find bounds of current function.

I'm wanting to figure out what's happening on the ppc8260, since it works, then apply it to the 8548. Have any ideas on what I could do to get the debugging going from the qnx wkst? or Why the windows environment got messed up? Thanks!

--H

post7024: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T21:28:02Z

I'm wondering if you might have inadvertently "broken" the build directories

by changing the build targets in the IDE.  You might want to try deleting

sys/target and use svn to pull in new copies.  Don't use the IDE to change

any build properties....

When I do a "make clean" from the appropriate directory, I get:

C:\Community\networking\trunk\sys\target\ppc\o.be.v4>make clean

make -C ../libkern clean

make[1]: Entering directory

`C:/Community/networking/trunk/sys/target/ppc/libker

n'

make -j 1 -Ca.be -fMakefile clean

make[2]: Entering directory

`C:/Community/networking/trunk/sys/target/ppc/libker

n/a.be'

C:/QNX632/host/win32/x86/usr/bin/rm -f  libkern.a  *.pinfo *.o *.err *.map

mapfi

le *.sym *.i

make[2]: Leaving directory

`C:/Community/networking/trunk/sys/target/ppc/libkern

/a.be'

make[1]: Leaving directory

`C:/Community/networking/trunk/sys/target/ppc/libkern

'

C:/QNX632/host/win32/x86/usr/bin/rm -f  io-pkt-v4  *.pinfo *.o *.err *.map

mapfi

le *.sym *.i asmoff.def C:/Community/networking/trunk/sys/static_drvrs.h

libkern

C:/Community/networking/trunk/sys/target/ppc/o.be.v4/bridge.h

C:/Community/netw

orking/trunk/sys/target/ppc/o.be.v4/gre.h

C:/Community/networking/trunk/sys/targ

et/ppc/o.be.v4/gif.h

C:/Community/networking/trunk/sys/target/ppc/o.be.v4/pppoe.

h C:/Community/networking/trunk/sys/target/ppc/o.be.v4/opt_pppoe.h

C:/Community/

networking/trunk/sys/target/ppc/o.be.v4/opt_ipsec.h

C:/Community/networking/trun

k/sys/target/ppc/o.be.v4/opt_inet.h

C:/Community/networking/trunk/sys/target/ppc

/o.be.v4/opt_mrouting.h

C:/Community/networking/trunk/sys/target/ppc/o.be.v4/opt

_gateway.h C:/Community/networking/trunk/sys/target/ppc/o.be.v4/ppp.h

C:/Communi

ty/networking/trunk/sys/target/ppc/o.be.v4/opt_ppp.h

C:/Community/networking/tru

nk/sys/nw_tls.h C:/Community/networking/trunk/sys/nw_sync.h

C:/Community/network

ing/trunk/sys/buildenv/tls_tst.o

C:/Community/networking/trunk/sys/buildenv/tls_

tst.c C:/Community/networking/trunk/sys/nw_tls.h

C:/Community/networking/trunk/s

ys/buildenv/sync_tst.o C:/Community/networking/trunk/sys/buildenv/sync_tst.c

C:/

Community/networking/trunk/sys/nw_sync.h

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Thursday, April 17, 2008 4:08 PM

To: builds-networking

Subject: Re: RE: RE: Building io-pkt for ppc in Momentics using XP

Thanks for the info. When I was able to get addvariant to work, the folders

were made, but make clean resulted in make clean is up to date, and make

install, was make install is up to date. I tried doing the whole make

CCOPTS=..... debug method, and it built, but not a debug build. I am now

trying to build it again, and the results are erratic. Sometimes creating

the stage part works, sometimes it doesnt, I'm yet to get consistent

results. I am trying to create a debug build on my qnx workstation, because

I think that is a better way to go.

Now, the exact line I use to start io-pkt on the 8548 is::

io-pkt-v4 -d mpc85xx mac=110011001100 -ptcpip

then I wait for /dev/socket

and ifconfig en0 address

(the mac argument is put in there, I dont know if the driver required one or

not, but io-net picks up the real mac address)

then I tried just using:

io-pkt-v4

this seg faulted as well.

We are using the 8548ads bsp, which one are using? Thanks for your help.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7013

post7015: RE: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T20:32:28Z

Hmmm....  The fact that the results are erratic points to a build

configuration problem of some sort.  I regularly use windows to build on, so

it should build fine.

Are you sure that your staging area and QCONF_OVERRIDE var is setup properly

(as in

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

_Guide

)?

What does the output from "set" return? (Of specific interest are (e.g.

here are mine...)

QCONF_OVERRIDE=c:/community/qconf-override.mk

QNX_CONFIGURATION=C:\Program Files\QNX Software Systems

QNX_HOST=C:/QNX632/host/win32/x86

QNX_TARGET=C:/QNX632/target/qnx6

What does the contents of your qconf-override.mk file look like?

(Here's mine)

USE_INSTALL_ROOT=1

INSTALL_ROOT_nto=c:/community/stage

As a side note, you wouldn't get an en0 device if you are using the devnp

drive.  You'd get a tsec0 device.

Just to triple check:

Are you sure that you have the PPC variant of the executable in your

image?

Do you also have the io-pkt versions of ifconfig and libsocket.so

included?

Do you have fpemu.so included in your image (This shouldn't

matter... Just a wild guess)?

Can you show me what your build file looks like?

I'm just using the standard 8548cds BSP on an MPC8548CDS platform.

As a side note, I think that the bit set in the first byte for the MAC is

the multicast bit and you really don't want to have that set as your MAC

address :).  Use something like 0011223344 or something similar.

R.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Thursday, April 17, 2008 4:08 PM

To: builds-networking

Subject: Re: RE: RE: Building io-pkt for ppc in Momentics using XP

Thanks for the info. When I was able to get addvariant to work, the folders

were made, but make clean resulted in make clean is up to date, and make

install, was make install is up to date. I tried doing the whole make

CCOPTS=..... debug method, and it built, but not a debug build. I am now

trying to build it again, and the results are erratic. Sometimes creating

the stage part works, sometimes it doesnt, I'm yet to get consistent

results. I am trying to create a debug build on my qnx workstation, because

I think that is a better way to go.

Now, the exact line I use to start io-pkt on the 8548 is::

io-pkt-v4 -d mpc85xx mac=110011001100 -ptcpip

then I wait for /dev/socket

and ifconfig en0 address

(the mac argument is put in there, I dont know if the driver required one or

not, but io-net picks up the real mac address)

then I tried just using:

io-pkt-v4

this seg faulted as well.

We are using the 8548ads bsp, which one are using? Thanks for your help.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post7013

post7013: Re: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T20:08:27Z

Thanks for the info. When I was able to get addvariant to work, the folders were made, but make clean resulted in make clean is up to date, and make install, was make install is up to date. I tried doing the whole make CCOPTS=..... debug method, and it built, but not a debug build. I am now trying to build it again, and the results are erratic. Sometimes creating the stage part works, sometimes it doesnt, I'm yet to get consistent results. I am trying to create a debug build on my qnx workstation, because I think that is a better way to go.

Now, the exact line I use to start io-pkt on the 8548 is::

io-pkt-v4 -d mpc85xx mac=110011001100 -ptcpip

then I wait for /dev/socket

and ifconfig en0 address

(the mac argument is put in there, I dont know if the driver required one or not, but io-net picks up the real mac address)

then I tried just using:

io-pkt-v4

this seg faulted as well.

We are using the 8548ads bsp, which one are using? Thanks for your help.

post7004: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T17:38:57Z

Hi Hayder:

Just to provide feedback on the xargs error... You're quite right

that addvariant doesn't work on windows. This has been fixed internally.

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Thursday, April 17, 2008 11:57 AM

To: builds-networking

Subject: Re: RE: Building io-pkt for ppc in Momentics using XP

Rob,

I got through the xargs error. Needed to install cygwin!!! Now when I go to

do the make install, it says make install is up to date.

Note: instead of using o.v4 mine was o.be.v4, I think they are the same.

What else do I have to do in order to get the debug build going? I tried

doing a make CCOPTS=-O0 DEBUG=-g CPULIST=ppc install from the main /trunk,

but it creates nondebug executables. Thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post6997

post6998: RE: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T16:08:24Z

Cool!

I'm very surprised that you had to install cygwin though. All of those

dependencies should have been resolved with the installation of the 6.3.2

development environment.

Did you do a "make clean" before the "make CCOPTS..." etc?  If not then the

make wouldn't have re-built things and you'd be left with your original

non-debug binaries.  Execute the make commands in the trunk/sys/target/ppc

directory so you don't have to end up re-building the world.

The instructions on the wiki are for an x86 platform so you would indeed be

creating an o.be.v4.g directory for a specific debug binary.  This creates

and io-pkt-v4_g binary independently from io-pkt-v4 whereas the "make

CCOPTS..." makes io-pkt-v4 a debug version.

If you're using the IDE, I wouldn't use the IDE to change the make

infrastructure.  Also, with a standard make, options for "debug" and

"release" don't exist since the IDE didn't create and shouldn't modify the

make files.

I'm a bit puzzled about your reference to npm-*.  From the io-net migration

Wiki:

"The IP stack is an integral part of io-pkt. io-pkt can not be started

without it. This means that it isn't necessary to specify the "-ptcpip"

option to the stack unless there are additional parameters (e.g. prefix=...)

that need to be passed in. If the "-ptcpip" option is passed, it will be

accepted with no effect."

So while specifying the library shouldn't matter, it does add some confusion

to the mix.

Exactly what command line are you using to start io-pkt?

Robert.

P.S. Just to let you know, I can guarantee that the 8548 binary works since

I've actually got one running on my desk as we speak, so we've either got a

build or configuration issue here.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Thursday, April 17, 2008 11:57 AM

To: builds-networking

Subject: Re: RE: Building io-pkt for ppc in Momentics using XP

Rob,

I got through the xargs error. Needed to install cygwin!!! Now when I go to

do the make install, it says make install is up to date.

Note: instead of using o.v4 mine was o.be.v4, I think they are the same.

What else do I have to do in order to get the debug build going? I tried

doing a make CCOPTS=-O0 DEBUG=-g CPULIST=ppc install from the main /trunk,

but it creates nondebug executables. Thanks.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post6997

post6997: Re: RE: Building io-pkt for ppc in Momentics using XP

2008-04-17T15:56:51Z

Rob,

I got through the xargs error. Needed to install cygwin!!! Now when I go to do the make install, it says make install is up to date.

Note: instead of using o.v4 mine was o.be.v4, I think they are the same.

What else do I have to do in order to get the debug build going? I tried doing a make CCOPTS=-O0 DEBUG=-g CPULIST=ppc install from the main /trunk, but it creates nondebug executables. Thanks.

post6942: Re: RE: Building io-pkt for ppc in Momentics using XP

2008-04-16T23:09:42Z

Rob,

Thanks for the reply! I downloaded the source and created the stage directory and did a "make CPULIST=ppc install". I was able to take the binary for io-pkt and successfully run it on the ppc8260. However, the same binary seg faults on the ppc8548. We are using the devnp-mp85xx driver that was built with the core_networking, and when io-pkt is ran by itself without loading any drivers it seg faults. We tried to follow the wiki on creating a debug build, but the addvariant did not work. I am running it in the following way

c:\qnx632\host\win32\x86\usr\bin\ksh.exe (path to)\addvariant o.v4.g,

this said xargs not found

I tried using as: addvariant nto ppc o.v4.g, addvariant -i OS ppc o.v4.g, these did not work either. What is the proper way to run the command? Also, when you create a standard make c project in Momentics, I found the way you can select what architecture you want, but I could not find the choice for debug or release, is there one?

Do you have any ideas what would cause io-pkt-v4 to seg fault on the 8548? We have tcpip.so as a symbolic link to npm-tcpip-4, libsocket, ifconfig, and from my understanding devnp-mpc85xx is already a pkt driver, so we don't need the shim.

Thanks.

--H

post6823: RE: Building io-pkt for ppc in Momentics using XP

2008-04-15T20:25:13Z

Hi Hayder:

One of the first things to find out is where the crash is occurring.

Let's start with the initial crash.   The fact that the binaries work on an

8260 and not on an 8548 seems to point to a driver problem or something

missing in your image.

What drivers are you running in each case? What is your command line? If you

start io-pkt-v4 with no driver specified, does it run as expected?

Can you then mount the drivers in question using the mount command instead

of specifying them on the io-pkt command line?

Can you start the drivers with the verbose option and see if additional

information is printed out?

As a side note, devnp-shim.so must be located in a path that is included in

the LD_LIBRARY_PATH. "\bin" is not the usual location for this (but this

seems to work for you, so maybe it's OK).

If you want to use pre-built binaries I would recommend using the load

marked Custom Engineering (and not the milestone 0 build) since it's a more

up to date version.   I'll look at getting a recent milestone build posted

shortly.

With regards to your build, what include files were missing?  Did the build

from the command line run without problems and is it only the integration

with Momentics that caused the failure?  This sounds like a problem with

either your staging area set up or your installation.

What I would recommend for Momentics is to create a project for the stack

that uses a subset of the overall io-pkt project.

First off, download the source as described in the wiki (make sure that you

have your staging area and environment variables properly set up) and do a

"make install" from the top level so that all of the source is built and the

staging area is properly filled.

To pull just the stack into Momentics, create a new Standard Make C project,

add in a suitable project name and unset "Use default location".

For the Location, fill in the path to (path to)/trunk/sys/target.

This will let you build all of the stack variants (which can take a bit of

time).  If you wanted to work with just the PPC stack builds, you would go

down one level and change the path to .../target/ppc which will shorten your

build times.

If you want to be able to build the binaries and have them automatically

installed to your staging area, you need to right click on the project click

on "Build make target...", click on "Add", "Target Name:" install  "Make

target:" install "Create".

Now you can do a make install which will copy the new stack into the staging

area.

You can also add in a debug variant so that you can step through the source.

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

ge

Note the section on "Debugging".

NOTE:  You MUST have your staging area AND your environment variables set up

correctly.  This might be why the include files weren't showing up.

From

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

_Guide

"Just a couple of notes on the QCONF_OVERRIDE environment variable. On

windows, in a DOS shell, use the SET command (there is no export). You can

make the env var "stick" by right clicking on "My Computer" (select

Properties). Select the "Advanced" tab and click on the "Environment

Variables" button (bottom left in XP). Click on the "New" button and add in

QCONF_OVERRIDE and the value and "OK" your way out and, the next time you

start a DOS shell, QCONF_OVERRIDE will already be set up for you. If you're

running self-hosted (or under Linux), you can add the export command to your

.profile script and it will also automatically get set when you start a new

terminal session."

Robert.

-----Original Message-----

From: Hayder Mouhammed [mailto:hayder.mouhammed@emerson.com]

Sent: Tuesday, April 15, 2008 2:51 PM

To: builds-networking

Subject: Building io-pkt for ppc in Momentics using XP

Greetings,

I have ran into an interesting issue and I was wondering if anyone has any

suggestions. I have two ppc targets: ppc8260 and ppc8548. I was able to take

the prebuilt binaries in Milestone0 and run them on the ppc8260 without

problems, but these same binaries cause a SIGSEGV error on the ppc8548. I

have tried fetching the source, but building has been quite troublesome. I

would like to use Momentics to build and debug io-pkt. I create a standard

make project, set the build environment for ppc, using gcc 3.3.5. When I

build I end up with numerous errors of variables not being defined. I

noticed that several include files were missing, and that they were in the

Milestone0, so I copied the ones I needed into my qnx632/usr/include. I am

still left with several variables not being defined. I have a self hosted

x86 QNX workstation, which I was able to do a "make CPULIST=ppc install" and

it completed without errors, and I copy them to the ppc targets, and they

BOTH segfault! That surpr!

ised me, because the prebuilts worked on the 8260. Below is the result of

the SIGSEGV error and the all the information in the log. I am using an

io-net driver, so I have devnp-shim in my /bin directory. If anyone has any

ideas on what I can do to get this built in momentics I'd greatly appreciate

it. Many thanks.

----INFORMATION----

Process 12295 (io-pkt-v4) terminated SIGSEGV code=1 fltno=11 ip=fe37aae0

mapaddr=00002ae0. ref=00000000

ifconfig: socket: Address family not supported by protocol family

# sloginfo

Time             Sev Major Minor Args

Jan 01 00:00:00    5    14     0 tcpip starting

Jan 01 00:00:00    3    14     0 Unable to attach to pci server: No such

file or                              directory

Jan 01 00:00:00    3    14     0 Using pseudo random generator.  See

"random" op                             tion

Jan 01 00:00:01    3    25     0 Couldn't initialize listen service: tcp

(Addres                             s family not supported by protocol

family)

_______________________________________________

Builds

http://community.qnx.com/sf/go/post6819

post6819: Building io-pkt for ppc in Momentics using XP

2008-04-15T18:51:08Z

Greetings,

I have ran into an interesting issue and I was wondering if anyone has any suggestions. I have two ppc targets: ppc8260 and ppc8548. I was able to take the prebuilt binaries in Milestone0 and run them on the ppc8260 without problems, but these same binaries cause a SIGSEGV error on the ppc8548. I have tried fetching the source, but building has been quite troublesome. I would like to use Momentics to build and debug io-pkt. I create a standard make project, set the build environment for ppc, using gcc 3.3.5. When I build I end up with numerous errors of variables not being defined. I noticed that several include files were missing, and that they were in the Milestone0, so I copied the ones I needed into my qnx632/usr/include. I am still left with several variables not being defined. I have a self hosted x86 QNX workstation, which I was able to do a "make CPULIST=ppc install" and it completed without errors, and I copy them to the ppc targets, and they BOTH segfault! That surprised me, because the prebuilts worked on the 8260. Below is the result of the SIGSEGV error and the all the information in the log. I am using an io-net driver, so I have devnp-shim in my /bin directory. If anyone has any ideas on what I can do to get this built in momentics I'd greatly appreciate it. Many thanks.

----INFORMATION----

Process 12295 (io-pkt-v4) terminated SIGSEGV code=1 fltno=11 ip=fe37aae0 mapaddr=00002ae0. ref=00000000

ifconfig: socket: Address family not supported by protocol family

# sloginfo

Time             Sev Major Minor Args

Jan 01 00:00:00    5    14     0 tcpip starting

Jan 01 00:00:00    3    14     0 Unable to attach to pci server: No such file or                              directory

Jan 01 00:00:00    3    14     0 Using pseudo random generator.  See "random" op                             tion

Jan 01 00:00:01    3    25     0 Couldn't initialize listen service: tcp (Addres                             s family not supported by protocol family)

post6491: Re: possible bug in kern_sync.c

2008-04-07T15:18:59Z

On Mon, Mar 10, 2008 at 02:15:25PM -0400, Gary Faulkner wrote:

> Thanks Sean! I had thought about that solution; but wasn't sure of all of the ramifications (I did not thoroughly understand all of the intricacies of the thread sleeping models being used at this point in the code).

>

> FWIW, I am willing to try other fixes if it will help (as I'm still relatively early in product development at this point).

>

> Thanks!!

>

> -garyf

Should be fixed now.

-seanb

post6331: Re: RE: RE: RE: RE: io-pkt build problems.

2008-04-01T13:09:14Z

On Tue, Apr 01, 2008 at 08:39:46AM -0400, j v wrote:

> 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 ,

>

strlcpy.h is shipped with 6.3.2 but it's not

needed in this case as nbutil.h defines strl*().

I removed the reference to strlcpy.h.

-seanb

post6329: Re: RE: RE: RE: RE: io-pkt build problems.

2008-04-01T12:39:44Z

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 ,

post6299: RE: RE: RE: RE: io-pkt build problems.

2008-03-31T14:24:29Z

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

post6287: Re: RE: RE: RE: io-pkt build problems.

2008-03-31T08:33:56Z

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 ?

post6256: Re: RE: RE: RE: io-pkt build problems.

2008-03-28T16:54:46Z

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?

post6254: Re: RE: RE: RE: io-pkt build problems.

2008-03-28T16:11:14Z

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?

post6206: RE: RE: RE: io-pkt build problems.

2008-03-27T14:42:03Z

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

post6202: Re: RE: RE: io-pkt build problems.

2008-03-27T14:32:31Z

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.

post6200: RE: RE: io-pkt build problems.

2008-03-27T14:26:47Z

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             libsocket.so

_______________________________________________

Builds

http://community.qnx.com/sf/go/post6191

_______________________________________________

Builds

http://community.qnx.com/sf/go/post6199

post6199: RE: RE: io-pkt build problems.

2008-03-27T14:06:57Z

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

post6191: Re: RE: io-pkt build problems.

2008-03-27T13:10:59Z

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

post6185: Re: RE: io-pkt build problems.

2008-03-27T09:15:16Z

Thanks a lot. I'll try that and let you know the results

post6158: Re: RE: io-pkt build problems.

2008-03-26T17:08:09Z

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

post6157: RE: RE: io-pkt build problems.

2008-03-26T17:07:17Z

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

post6153: Re: RE: io-pkt build problems.

2008-03-26T16:53:04Z

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

post5947: RE: io-pkt build problems.

2008-03-19T13:48:06Z

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

post5940: Re: io-pkt build problems.

2008-03-19T13:18:49Z

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

post5938: Re: io-pkt build problems.

2008-03-19T12:32:43Z

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.

post5936: Re: io-pkt build problems.

2008-03-19T11:09:37Z

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

post5931: Re: io-pkt build problems.

2008-03-19T09:02:47Z

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

post5894: Re: error while building core_networking (trunk)

2008-03-18T13:26:33Z

On Tue, Mar 18, 2008 at 12:36:02AM -0400, ravi holal wrote:

> hi ,

>

> I am building the core-networking for QNX 6.3.2, but is failling to build.It is giving the error message "cant find the lndrvrS",

> I seareched for the lndrvrS in my QNX kernel directory but it has libdrvrS.a

> and I used that path while building , but it is giving the same error.

> Can you help me to resolve this problem?

>

This should be fixed in commits 260, 261 from yesterday.

A 'make install' from the root should work as before.

-seanb

post5888: error while building core_networking (trunk)

2008-03-18T04:36:00Z

hi ,

I am building the core-networking for QNX 6.3.2, but is failling to build.It is giving the error message "cant find the lndrvrS",

I seareched for the lndrvrS in my QNX kernel directory but it has libdrvrS.a

and I used that path while building , but it is giving the same error.

Can you help me to resolve this problem?

regards

ravi holal

post5869: Re: io-pkt build problems.

2008-03-17T16:26:07Z

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

post5867: Re: io-pkt build problems.

2008-03-17T16:06:04Z

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)?

post5866: Re: io-pkt build problems.

2008-03-17T15:45:33Z

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?

post5863: io-pkt build problems.

2008-03-17T14:55:44Z

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

post5862: io-pkt build problems

2008-03-17T14:54:54Z

post5852: F... io-pkt!!!!

2008-03-17T10:45:25Z

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.

post5735: RE: RE: RE: setup io-pkt without disabling io-net

2008-03-12T16:18:58Z

Hi:

Feedback is always welcome.  If you're having problems, then it

likely means that the information that you're getting isn't quite where it

needs to be :>.

The CLI that you get on boot is indeed what you should be working with to

get io-pkt running.

Robert.

-----Original Message-----

From: j v [mailto:jeanmarieverret@gmail.com]

Sent: Wednesday, March 12, 2008 11:44 AM

To: builds-networking

Subject: Re: RE: RE: setup io-pkt without disabling io-net

First, Thanks a lot for your detailed answers and your patience.

I have one more question though (last one I promess).

       When qnx is launched I log in and then I have access to a command

line interface (CLI). (#login: root then #...)

Is  it ok for me to work in that CLI, or is it what you meant by "startup "?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post5734

post5734: Re: RE: RE: setup io-pkt without disabling io-net

2008-03-12T15:44:13Z

First, Thanks a lot for your detailed answers and your patience.

I have one more question though (last one I promess).

When qnx is launched I log in and then I have access to a command line interface (CLI). (#login: root then #...)

Is it ok for me to work in that CLI, or is it what you meant by "startup "?

post5729: RE: RE: setup io-pkt without disabling io-net

2008-03-12T14:20:31Z

I think you're probably misinterpreting the wikis...

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

_Guide

At the bottom "How do I use what I built".  Note the comment "don't forget

to slay io-net before starting io-pkt"

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

ki_page

The section "How do I run io-pkt?" covers how you start the stack with an

"alternate" socket interface (which utilizes the SOCK var).

"Can I run io-net and io-pkt at the same time on one machine?" mentions the

need for having two network cards.

The FAQ is indeed confusing from this respect.  I've removed the SOCK=

option from the general script and beefed up the description of io-net /

io-pkt in particular.

Essentially, you need to both install and run the io-pkt executables.  Given

that you're trying to replace the networking stack, doing this through a

protocol (telnet) that requires networking won't work unless you have more

than one interface for the stacks to use (i.e. one interface for io-net and

one for io-pkt).  From what I can see with the pidin, io-pkt isn't running

and io-net has probably been started using the enumerators (which means it

probably has "taken over" all networking hardware).

My recommendation:

Make sure that you have the appropriate executables installed on your system

and that you know which driver is required by your hardware.

From a command line interface (NOT telnet)

export LD_LIBRARY_PATH=/home/pc236/io-pkt:$LD_LIBRARY_PATH

export PATH=/home/pc236/io-pkt:$PATH

io-pkt-v4 -d (whatever your driver is)

dhcp.client

and this replaces io-net with io-pkt.  Because you're doing this in a

command line (and not as part of the startup), when you re-boot the box

it will revert back to io-net.  If you want to telnet into the box, you

should also install the new inetd that comes with io-pkt and run it as well.

Robert.

-----Original Message-----

From: j v [mailto:jeanmarieverret@gmail.com]

Sent: Wednesday, March 12, 2008 4:32 AM

To: builds-networking

Subject: Re: RE: setup io-pkt without disabling io-net

First thing, It seems I have not damaged qnx installation. Again, I am able

to connect to the target qnx. (may be explained because we're several on the

same target)

To answer your questions,

- "SOCK=/alt": I just did a copy/paste operation of the wiki changing the

directory. I don't really know what it does, from what you said it seems it

specifies an option for libsocket

- the export commands were executed in the telnet shell and I don't have a

command line on the target

- pidin ar give the following result:

# pidin ar

     pid Arguments

       1 procnto

       2 /sbin/tinit

    4099 pci-bios

    4100 slogger -s32

    4101 io-usb -duhci -dohci -dehci

    4102 io-hid -d ps2ser kbd:kbddev:ps2mouse:mousedev -d usb

/dev/io-usb/io-usb

    4103 devc-con-hid -n4

    8200 devb-eide blk auto=partition dos exe=all cam quiet

    8201 umass-enum -h hd -d /dev -m /fs/hd -f /proc/boot/umass-enum.cfg

   16394 pipe

   20491 mqueue

   77838 devc-ser8250 -u1 3f8,4 -u2 2f8,3

   77841 devc-par -p0x378

   77843 io-net -ptcpip

  110614 spooler -d/dev/par1

  135183 devc-pty -n 32

  139280 random -t

  151572 dumper -d /var/dumps

  188437 inetd

  196632 syslogd

  213015 login

  213017 login

  213018 login

  213019 login

  225292 in.telnetd

  229389 -sh

  274450 pidin ar

But anyway, now that I can connect to the target I just need to install

io-pkt in a staging directory if I read the wiki correctly.

How can I do that???

Hmmm... Why have  exported?  This assumes that you're running a

version of the stack with the "prefix=/alt" option provided.  If not, then

libsocket is going to be trying to connect into a non-existent stack.

Where were the export commands executed (in the telnet shell or as part of

the boot up process)?

Do you have a command line that you can get into on your target?  What does

"pidin ar" say?

How are you invoking the stack (what are your command line arguments)?

Robert.

_______________________________________________

Builds

http://community.qnx.com/sf/go/post5723

post5723: Re: RE: setup io-pkt without disabling io-net

2008-03-12T08:32:18Z

First thing, It seems I have not damaged qnx installation. Again, I am able to connect to the target qnx. (may be explained because we're several on the same target)

To answer your questions,

- "SOCK=/alt": I just did a copy/paste operation of the wiki changing the directory. I don't really know what it does, from what you said it seems it specifies an option for libsocket

- the export commands were executed in the telnet shell and I don't have a command line on the target

- pidin ar give the following result:

# pidin ar

     pid Arguments

       1 procnto

       2 /sbin/tinit

    4099 pci-bios

    4100 slogger -s32

    4101 io-usb -duhci -dohci -dehci

    4102 io-hid -d ps2ser kbd:kbddev:ps2mouse:mousedev -d usb /dev/io-usb/io-usb

    4103 devc-con-hid -n4

    8200 devb-eide blk auto=partition dos exe=all cam quiet

    8201 umass-enum -h hd -d /dev -m /fs/hd -f /proc/boot/umass-enum.cfg

   16394 pipe

   20491 mqueue

   77838 devc-ser8250 -u1 3f8,4 -u2 2f8,3

   77841 devc-par -p0x378

   77843 io-net -ptcpip

  110614 spooler -d/dev/par1

  135183 devc-pty -n 32

  139280 random -t

  151572 dumper -d /var/dumps

  188437 inetd

  196632 syslogd

  213015 login

  213017 login

  213018 login

  213019 login

  225292 in.telnetd

  229389 -sh

  274450 pidin ar

But anyway, now that I can connect to the target I just need to install io-pkt in a staging directory if I read the wiki correctly.

How can I do that???

Hmmm... Why have  exported?  This assumes that you're running a

version of the stack with the "prefix=/alt" option provided.  If not, then

libsocket is going to be trying to connect into a non-existent stack.

Where were the export commands executed (in the telnet shell or as part of

the boot up process)?

Do you have a command line that you can get into on your target?  What does

"pidin ar" say?

How are you invoking the stack (what are your command line arguments)?

Robert.

post5697: RE: setup io-pkt without disabling io-net

2008-03-11T16:17:10Z

Hmmm... Why have "SOCK=/alt" exported?  This assumes that you're running a

version of the stack with the "prefix=/alt" option provided.  If not, then

libsocket is going to be trying to connect into a non-existent stack.

Where were the export commands executed (in the telnet shell or as part of

the boot up process)?

Do you have a command line that you can get into on your target?  What does

"pidin ar" say?

How are you invoking the stack (what are your command line arguments)?

Robert.

-----Original Message-----

From: j v [mailto:jeanmarieverret@gmail.com]

Sent: Tuesday, March 11, 2008 12:10 PM

To: builds-networking

Subject: setup io-pkt without disabling io-net

I have an application which uses Libpcap, more specifically I need to be

able to read and write on an ethernet adapter.

Read operation can be achieved with io-net and nfm-bpf.so but write

operation is not possible (unless paying for nfm-nraw.so)

To be able to write I have been advised to use io-pkt instead of io-net

because it seems to be directly compatible with LIbpcap.

So I looked at the wiki and put these files in a io-pkt directory:

io-pkt-v4-hc, io-pkt-v6-hc, libsocket.so, devnp-shim.so, devnp-i82544.so

ifconfig, netstat,nicinfo =>there are prebuilt binaries I have dowloaded

from the site.

After that I typed

export LD_LIBRARY_PATH=/home/pc236/io-pkt:$LD_LIBRARY_PATH

export PATH=/home/pc236/io-pkt:$PATH

export SOCK=/alt

and then lost the connexion with the target qnx (Because I run qnx from

telnet on a windows computer)

When I tried to ping the target qnx I got no answer so I am afraid I deleted

or disabled io-net.

So how do I fix it up (without reinstall qnx if possible).

And then, how can I install io-pkt correctly (I read about staging directory

but don't know how to install io-pkt in it)?

_______________________________________________

Builds

http://community.qnx.com/sf/go/post5696