Feed for discussion QFC Installation and build in project QNX Foundation Classes.
http://community.qnx.com/sf/discussion/do/listTopics/projects.qfc/discussion.general
Posts for QFC Installation and buildpost117145: Unable to Install QNX Neutrino on Dell Precision Tower 3620
http://community.qnx.com/sf/go/post117145
Hello,
I am a student and I am working on QNX for performing HIL and SIL Simnulations.
I ordered new system to install QNX as RTOS. My system is Dell Precision Tower 3620 with following configurations:
i7 Quad Core Processor
16GB RAM
1 TB HDD
When I tried to install QNX with installation CD from boot menu, it asked me to apply driver update disk?
F1 = Apply and F2 = Abort.
The process stops here.
When I tried to install it on other system (Dell Vostro), I was able to install QNX from installation CD successfully.
Can I know what is the problem to install on Dell Precision Tower? And what is the proper solution for it?
I am attaching screenshot of the problem I am facing while installing QNX on Precision Tower 3620.
Thank You,
Waiting for your response ASAP.
Hitesh UkaniHitesh Ukani(deleted)2016-11-18T17:19:10Zpost114597: Building a program using SDP 6.6 for the target version 6.4.1
http://community.qnx.com/sf/go/post114597
Is it possible to build a program using qcc from SDP 6.6 for 6.4.1?
I have already tried several ways and still have a problem with libcpp.so.5. I can build successfully on my window host computer but when I executed the program on qnx target, it printed:
"Could not load library libcpp.so.5".
I think I should change the target version using -v in qcc command. I have tried some combinations but they don't work. Could anyone give me any suggestions?
Thank you in advance.Piyapat Saranrittichai(deleted)2015-10-07T10:29:36Zpost85555: QFC on 6.5 ?
http://community.qnx.com/sf/go/post85555
Is it possible to use QFC on 6.5 ?
thanks,
Ranran wainstein2011-05-10T16:20:31Zpost19312: Unable to build QFC under 6.4.0 and IDE 4.5
http://community.qnx.com/sf/go/post19312
Have the following 'warning' message for the following projects:
'No active build configurations defined. All existing configurations will be built.'
Cli, Guardian, Ramdisk, SatTest, Serv, TPool, Thrs, testAP
Under right-click of Cli project, Build Configurations/Set Active, the active configuration is ntox86-gcc-3.3.5-debug, with ntox86-gcc-3.3.5-release and ntox86-gcc-4.2.3-release.
Folders ntox86-gcc-3.3.5-debug and notx86-gcc-3.3.5-release are created for Cli project.
Here's the output of the build.
**** Clean-only build of configuration ntox86-gcc-3.3.5-debug for project Cli ****
make clean
rm -rf ./Cli.o ./main.o ./Cli.d ./main.d Cli_g
**** Build of configuration ntox86-gcc-3.3.5-debug for project Cli ****
make all
Building file: ../Cli.cpp
Invoking: QCC Compiler
qcc -o Cli.o ../Cli.cpp -V3.3.5,gcc_ntox86_cpp -w1 -I"C:\QNX_QFC\sigc++\public" -I"C:\QNX_QFC\QFC\public" -I"C:\QNX_QFC\Serv" -c -g -Wc,-Wno-parentheses -Wp,-MMD,Cli.d -Wp,-MT,Cli.o
cc: unknown target 'gcc_ntox86_cpp+debug'
cc: no targets defined in /3.3.5!
make: *** [Cli.o] Error 1Keith Smith2009-01-02T16:19:33Zpost16947: build qfc fail,please help
http://community.qnx.com/sf/go/post16947
I'v successfuly install subversion and checked out QFC into my workspace.
But I can't build the whole project.
I found there is no '.cdtbuild ' file in sigc++ dirctory and QFC dirctory.
please help!
Thanksshen xifeng2008-11-20T03:33:29Zpost13352: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13352
Yes, thanks. I have only developed servers with this library, and as such priority manipulation has not been required (servers always inherit priority). I have committed your patch with a minor name change (nice thing about C++ namespaces, is that there is no need to create mangled names for types).Rennie Allen2008-09-12T16:28:40Zpost13319: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13319
Thanks.
A timertree is indeed sufficient for now.
I have another question. As far as I can see it is not possible to create a Thread and let it run on a specific priority? I've included a patch which should add that to PosixAPI::Thread. Haven't tested it yet, but I will test it soon.
It also fixes the docgen.Doxyfile for the QFC project.Bart Veldhuijzen2008-09-12T12:33:58Zpost13260: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13260
SETIOV is defined in unistd.h (which is included in the example Serv.h).
I have added unistd.h to ipc; thanks for pointing this out.
Are you sure you want a timerbank as opposed to a timertree? A timerbank is a priority vector of timertrees (i.e. 255 timertrees, with callbacks from each tree executing at the associated priority).
If you are just trying out the interface, a timertree may be sufficient.Rennie Allen2008-09-11T16:58:02Zpost13236: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13236
Thanks, Serv does compile now.
When I try to instantiate the TimerBank myself, I get the following error:
/home/veldhuijzen/workspace/QFC/public/qfc/ipc:697: error: 'SETIOV' was not declared in this scope
I guess I'm missing something here. I just want a timerbank and add some timed callbacks to it.
Can you give some hints on how to proceed?Bart Veldhuijzen2008-09-11T09:54:32Zpost13220: Re: Building under Neutrino
http://community.qnx.com/sf/go/post13220
Norton,
Sorry for the delayed response, I have been traveling a lot through July and August.
Doxygen does build for nto (as Mario mentions), and the plug-ins should work. If the "find & install" is not working for you, then you can just download eclox and unzip in the plugins directory. I haven't tried it, but it is java, and should just work...
RennieRennie Allen2008-09-10T21:39:30Zpost13214: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13214
Actually, I tried switching the compiler on Serv to 4.2.3, and I see exactly the same problem. There is a bug in the Cancel() method of TimerBank which I have fixed and committed. If you update QFC from the repository it should work now.Rennie Allen2008-09-10T20:49:27Zpost13211: Re: Build errors (and warnings)
http://community.qnx.com/sf/go/post13211
Hmmm,
It works fine for me (IDE 4.5 gcc 4.2.3 & gcc 3.3.5).
Do you have gcc 3.3.5 available on your system (as this is the compiler defined in the project for Serv by default)?
Could you post the entire output from the console window when you try to build.Rennie Allen2008-09-10T20:20:43Zpost13199: Re: Building under Neutrino
http://community.qnx.com/sf/go/post13199
> I'm just trying out QFC. I'm an educational user, and I was forced to choose
> either Neutrino or Windows for my development environment and went with
> Neutrino. This may be an IDE question, but is it possible to install the
> Doxygen plugins under Neutrino? At the moment the "Find and Install..." option
> does not even give me a dialog, so that approach doesn't appear to work for
> anything. I did my svn checkout from the command line for lack of a subversion
> plugin. I'm wondering if I'll have to do builds under Neutrino and generate
> documentation under a generic Eclipse install on Windows.
You can build doxygen for Neutrino (I'm using 1.5.1). However it's not a plug-in. It will have to be added to the makefile or manually invoked.
The IDE under Neutrino is *really* slow. Until QNX find a way to speed it up I personnaly feel that for any serious project it's unusable.Mario Charest2008-09-10T19:28:33Zpost13137: Build errors (and warnings)
http://community.qnx.com/sf/go/post13137
Hi,
I can't get my projects to compile properly when I try to include part of the QFC. For example, just including <qfc/timerbank> generates compiler errors:
/home/veldhuijzen/ide-4.5-workspace/QFC/public/qfc/timerbank: In member function 'void QNXAPI::TimerBank<T, V, R>::Cancel(QNXAPI::TimerTree::TimerNode*, sigc::slot<bool, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>)':
/home/veldhuijzen/ide-4.5-workspace/QFC/public/qfc/timerbank:127: error: 'priority' was not declared in this scope
/home/veldhuijzen/ide-4.5-workspace/QFC/public/qfc/timerbank:131: error: request for member 'Cancel' in 'iter->second', which is of non-class type 'QNXAPI::TimerTree*'
This also happens when I try to compile the Serv example. I am using QDE 4.5, and QNX 6.4.0 with gcc 4.2.4.
Any hints on how to solve these problems?
Further there are some warnings about deprecated conversions from string constant to 'char*'.Bart Veldhuijzen2008-09-10T09:51:56Zpost9781: Building under Neutrino
http://community.qnx.com/sf/go/post9781
I'm just trying out QFC. I'm an educational user, and I was forced to choose either Neutrino or Windows for my development environment and went with Neutrino. This may be an IDE question, but is it possible to install the Doxygen plugins under Neutrino? At the moment the "Find and Install..." option does not even give me a dialog, so that approach doesn't appear to work for anything. I did my svn checkout from the command line for lack of a subversion plugin. I'm wondering if I'll have to do builds under Neutrino and generate documentation under a generic Eclipse install on Windows.Norton Allen2008-06-27T14:37:28Zpost9633: Re: QFC and Doxygen
http://community.qnx.com/sf/go/post9633
Hmmm,
I got the Hot Eclox as well, but it worked for me. I am running the latest Momentics (ver 4.5 available here on F27) but AFAIK, it is still based on eclipse 3.2. Anyway, glad it is working for you.
Have you installed dot as well?Rennie Allen2008-06-24T21:52:41Zpost9632: Re: QFC and Doxygen
http://community.qnx.com/sf/go/post9632
I found the problem.
I had gotten the Hot Eclox plug-in. This plug-in is only for 3.3 and higher.
Momentics is 3.2. Disabled Hot Eclox and now I can properly click on .doxyfiles.Keith Smith2008-06-24T21:16:00Zpost9608: Re: QFC and Doxygen
http://community.qnx.com/sf/go/post9608
BTW: I am preparing a major upgrade to QFC, that includes:
1. A dynamic plug-in class (i.e. a factory container that allows you to simply invoke a class constructor; under the covers this class will load the appropriate DLL, using a user supplied method to turn class name into a file name).
2. An adaptive partitioning class, that provides a basic framework for programmatic control/monitoring of temporal partitions.
3. A SAT class that takes care of a lot of the trickiness of dynamic tracing.
Look for an announcement on the project page around the middle of July...Rennie Allen2008-06-24T16:49:21Zpost9603: Re: QFC and Doxygen
http://community.qnx.com/sf/go/post9603
Keith,
I just tried installing Eclox from the link in your post, and it worked fine for me. After installation, I double-clicked on docgen.Doxyfile in the project "Ramdisk", and it opened the correct Eclox editor.
Did you restart eclipse after installing?Rennie Allen2008-06-24T16:17:10Zpost9558: QFC and Doxygen
http://community.qnx.com/sf/go/post9558
After obtaining the QFC files from the repository following the directions at:
http://community.qnx.com/sf/projects/qfc
and obtaining my plug-in of Eclox from http://download.gna.org/eclox/update
I get the following message when I click on a Doxyfile.
"Unable to create this part due to an internal error. Reason for the failure: The editor class could not be instantiated. This usually indicates that the editor's class name was mistyped in plugin.xml."
What do I do next to correct this problem?
KeithKeith Smith2008-06-24T12:32:29Zpost5037: RE: RE: RE: Build failure
http://community.qnx.com/sf/go/post5037
Rennie,
I overwrote the existing copies of those libraries in /lib on the target
(just to make sure), and got the same behavior.
I do not recall putting copies of those libraries anywhere else on the
target.
Gordon
-----Original Message-----
From: Rennie Allen [mailto:rallen@qnx.com]
Sent: Thursday, February 14, 2008 10:13 AM
To: install-qfc
Subject: Re: RE: RE: Build failure
Gordon,
Did you copy libsigc++ and libqfc to /lib? Are there any other copies
of these libraries potentially on the path?
_______________________________________________
QFC Installation and build
http://community.qnx.com/sf/go/post5033
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.Gordon Molek2008-02-14T18:39:00Zpost5033: Re: RE: RE: Build failure
http://community.qnx.com/sf/go/post5033
Gordon,
Did you copy libsigc++ and libqfc to /lib? Are there any other copies of these libraries potentially on the path?Rennie Allen2008-02-14T16:13:19Zpost4845: RE: RE: Build failure
http://community.qnx.com/sf/go/post4845
Rennie,
I downloaded Ramdisk_g to /sbin and ran it with the same results.
Here's the result of my "set" command.
ABLANG=en_US
ABLPATH=/usr/photon/translations
DISPLAY=127.1:0
FONTSLEUTH=/dev/fontsleuthctrl
HOME=/root
HOSTNAME=localhost
IFS='
'
KSH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2'
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll:/opt/lib:/Zebra/lib:/u
sr/photon/lib:/usr/photon/dll:/usr/local/lib:/opt/X11R6/lib:/usr/X11R6/l
ib:/Zebra/lib
LOGNAME=root
MAILCHECK=600
MAKEFLAGS=-I/usr/qnx632/target/qnx6/usr/include
OLDPWD=/Parser
OPTIND=1
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/photon/bin:/usr/photon/appbuilde
r:/opt/X11R6/bin:/usr/X11R6/bin:/usr/local/bin:/opt/bin:/opt/sbin:/usr/q
nx632/host/qnx6/x86/usr/bin:/usr/qnx632/host/qnx6/x86/usr/sbin:/usr/qnx6
32/host/qnx6/x86/sbin:/usr/qnx632/host/qnx6/x86/bin:/usr/qnx632/host/qnx
6/x86/usr/photon/appbuilder
PHFONT=/dev/phfont
PHINSTANCE=1
PHOTON=/dev/photon
PHOTON2_PATH=/usr/photon
PHOTON_PATH=/usr/photon
PHSTART=1
PHTK_PATH=/usr/photon
PHWM=pwm
PPID=561191
PROCESSOR=x86
PS1='# '
PS2='> '
PS3='#? '
PS4='+ '
PWD=/
QNX_CONFIGURATION=/etc/qnx
QNX_HELP_HOME_PAGE=/usr/qnx632/target/qnx6/usr/help/product/momentics/bo
okset.html
QNX_HELP_PATH=/usr/qnx632/target/qnx6/usr/help/product
QNX_HOST=/usr/qnx632/host/qnx6/x86
QNX_TARGET=/usr/qnx632/target/qnx6
RANDOM=15580
SECONDS=15488
SHELL=/bin/sh
SYSNAME=nto
TERM=qansi-m
TMOUT=0
TMPDIR=/tmp
USER_NAME=/dev/photon
_=set
-----Original Message-----
From: Rennie Allen [mailto:rallen@qnx.com]
Sent: Wednesday, February 06, 2008 11:59 AM
To: install-qfc
Subject: Re: RE: Build failure
> Rennie,
> Thanks for the response. I did a fresh check-out, fixed the libsigc++
> include file reference problem, downloaded libsigc-2.0_g.so and
> libqfc_g.so to /lib on the target and ran Ramdisk_g from within
> Momentics, setting its argument to the mount point "/ramdisk". It
> seems to run and I can do an "ls -l /ramdisk" which returns an empty
> directory, but when I attempt to copy a file into the /ramdisk
> directory I get the error message "Can't open destination file.
(/ramdisk/foo):
> Resource temporarily unavailable"
Could you try running Ramdisk by copying it to the target and launching
from the command line? The IDE may have a different path, and might be
picking up an old library.
Also, from the shell could you execute:
# set
and post the results?
Thanks,
> Thanks,
>
> Gordon Molek
>
> -----Original Message-----
> From: Rennie Allen [mailto:rallen@qnx.com]
> Sent: Monday, February 04, 2008 1:04 PM
> To: install-qfc
> Subject: Re: Build failure
>
> I Gordon,
>
> Sorry, I thought I had responded. The fact that you have list
> corruption implies a build error.
>
> Could you clean the library, re-build and download to target, and then
> rebuild Ramdisk and try again?
>
> I have tried it here (from the repository) and it works fine for me.
>
> Thanks,
>
> Rennie
>
>
> _______________________________________________
> QFC Installation and build
> http://community.qnx.com/sf/go/post4781
>
> - CONFIDENTIAL-
> This email and any files transmitted with it are confidential, and may
> also be legally privileged. If you are not the intended recipient,
> you may not review, use, copy, or distribute this message. If you
> receive this email in error, please notify the sender immediately by
> reply email and then delete this email.
_______________________________________________
QFC Installation and build
http://community.qnx.com/sf/go/post4842
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.Gordon Molek2008-02-06T19:31:43Zpost4844: Re: Build -> deploy
http://community.qnx.com/sf/go/post4844
When I do a run-as->qconn c/c++ the debugger can not find the libraries and symbols. If I copy the executable, and run it on the targer (Vmware) it works fine.
Might I need to copy the header files to the vmware target as well in order to get debugging working? The library is build with debugging symbols on btw.Jeffry Molanus2008-02-06T18:43:42Zpost4843: Re: Build -> deploy
http://community.qnx.com/sf/go/post4843
Jeffry, what are the symptoms? (debug works fine for me).
What version of the IDE/tools are you using? For C++ I definitely recommend getting the TAU build of the IDE, and the gcc 4.2 preview. The C++ support in gcc 4.2 is much better than earlier compilers...Rennie Allen2008-02-06T18:02:02Zpost4842: Re: RE: Build failure
http://community.qnx.com/sf/go/post4842
> Rennie,
> Thanks for the response. I did a fresh check-out, fixed the libsigc++
> include file reference problem, downloaded libsigc-2.0_g.so and
> libqfc_g.so to /lib on the target and ran Ramdisk_g from within
> Momentics, setting its argument to the mount point "/ramdisk". It seems
> to run and I can do an "ls -l /ramdisk" which returns an empty
> directory, but when I attempt to copy a file into the /ramdisk directory
> I get the error message "Can't open destination file. (/ramdisk/foo):
> Resource temporarily unavailable"
Could you try running Ramdisk by copying it to the target and launching from the command line? The IDE may have a different path, and might be picking up an old library.
Also, from the shell could you execute:
# set
and post the results?
Thanks,
> Thanks,
>
> Gordon Molek
>
> -----Original Message-----
> From: Rennie Allen [mailto:rallen@qnx.com]
> Sent: Monday, February 04, 2008 1:04 PM
> To: install-qfc
> Subject: Re: Build failure
>
> I Gordon,
>
> Sorry, I thought I had responded. The fact that you have list
> corruption implies a build error.
>
> Could you clean the library, re-build and download to target, and then
> rebuild Ramdisk and try again?
>
> I have tried it here (from the repository) and it works fine for me.
>
> Thanks,
>
> Rennie
>
>
> _______________________________________________
> QFC Installation and build
> http://community.qnx.com/sf/go/post4781
>
> - CONFIDENTIAL-
> This email and any files transmitted with it are confidential, and may also be
> legally privileged. If you are not the intended recipient, you may not
> review, use, copy, or distribute this message. If you receive this email in
> error, please notify the sender immediately by reply email and then delete
> this email.Rennie Allen2008-02-06T17:58:29Zpost4841: Re: Build -> deploy
http://community.qnx.com/sf/go/post4841
Doing a remote debug with qconn etc, still doesnt work... any fix for that?Jeffry Molanus2008-02-06T17:56:39Zpost4839: Re: Build -> deploy
http://community.qnx.com/sf/go/post4839
Thanks for the quick reply. I'm looking forward to use QFC for codegeneration of CSP based control models.
JeffryJeffry Molanus2008-02-06T17:20:28Zpost4838: Re: Build -> deploy
http://community.qnx.com/sf/go/post4838
> Hi,
>
> Once I have build the libqfc, how do I 'deploy' it to the target? I've got a
> vmware machine running, but it cant find the libqfc_g.so.
Hi Jeffry,
To "deploy" qfc, onto VMWare, you simply need to use the IDE's "Target File System Navigator" to drag&drop both libqfc[_g].so and libsigc-2.0.so into either the "/lib" or "/usr/lib" (whatever your personal preference is) directories.
That should do it...Rennie Allen2008-02-06T17:00:19Zpost4837: RE: Build failure
http://community.qnx.com/sf/go/post4837
Rennie,
Thanks for the response. I did a fresh check-out, fixed the libsigc++
include file reference problem, downloaded libsigc-2.0_g.so and
libqfc_g.so to /lib on the target and ran Ramdisk_g from within
Momentics, setting its argument to the mount point "/ramdisk". It seems
to run and I can do an "ls -l /ramdisk" which returns an empty
directory, but when I attempt to copy a file into the /ramdisk directory
I get the error message "Can't open destination file. (/ramdisk/foo):
Resource temporarily unavailable"
Thanks,
Gordon Molek
-----Original Message-----
From: Rennie Allen [mailto:rallen@qnx.com]
Sent: Monday, February 04, 2008 1:04 PM
To: install-qfc
Subject: Re: Build failure
I Gordon,
Sorry, I thought I had responded. The fact that you have list
corruption implies a build error.
Could you clean the library, re-build and download to target, and then
rebuild Ramdisk and try again?
I have tried it here (from the repository) and it works fine for me.
Thanks,
Rennie
_______________________________________________
QFC Installation and build
http://community.qnx.com/sf/go/post4781
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.Gordon Molek2008-02-06T16:58:23Zpost4836: Build -> deploy
http://community.qnx.com/sf/go/post4836
Hi,
Once I have build the libqfc, how do I 'deploy' it to the target? I've got a vmware machine running, but it cant find the libqfc_g.so.Jeffry Molanus2008-02-06T16:55:38Zpost4781: Re: Build failure
http://community.qnx.com/sf/go/post4781
I Gordon,
Sorry, I thought I had responded. The fact that you have list corruption implies a build error.
Could you clean the library, re-build and download to target, and then rebuild Ramdisk and try again?
I have tried it here (from the repository) and it works fine for me.
Thanks,
RennieRennie Allen2008-02-04T19:04:08Zpost4104: Re: Build failure
http://community.qnx.com/sf/go/post4104
Ok, I figured it out (I think). Here you go.
#0 0xb0320668 in _list_release ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#1 0xb0320f41 in __prelocked_free ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#2 0xb0320ff0 in __free () from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#3 0xb031ea4e in free () from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#4 0xb82fd351 in operator delete(void*) ()
from /usr/qnx632/target/qnx6/x86/lib/libcpp.so.4
#5 0xb82911e9 in ~Node (this=0x80476cc) at node.cpp:519
#6 0xb8293651 in ~Ocb (this=0x80596a0) at ocb.cpp:122
#7 0xb82661f8 in QNXAPI::Resmgr::DispatchCloseOcb(_resmgr_context*, void*, ocb*
) (this=0x80477c4, ctp=0x8059738, reserved=0x0, ocb=0x80596f8)
at resmgr.cpp:801
#8 0xb8263180 in QNXAPI::CloseRedir(_resmgr_context*, void*, ocb*) (
ctp=0x8059738, msg=0x0, ocb=0x80596f8) at resmgr.cpp:155
#9 0xb033785c in _resmgr_close_handler ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#10 0xb0337aa8 in _resmgr_connect_handler ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#11 0xb0338db5 in _resmgr_handler ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#12 0xb032a432 in resmgr_handler ()
from /usr/qnx632/target/qnx6/x86/lib/libc.so.2
#13 0xb826854c in QNXAPI::Resmgr::ResmgrIoSelector::BlockContext(_resmgr_context
*) (this=0x8047a10, context=0x8059738) at resmgr.cpp:1251
#14 0xb82829d7 in sigc::bound_mem_functor1<void, QNXAPI::Resmgr::ResmgrIoSelecto
r, _resmgr_context*>::operator()(_resmgr_context* const&) const (
this=0x804d29c, _A_a1=@0x80475bc) at functors/mem_fun.h:1851
#15 0xb828295f in operator()<resmgr_context_t* const&> (this=0x804d298,
_A_arg1=@0x80475bc) at adaptor_trait.h:84
#16 0xb8282931 in sigc::internal::slot_call1<sigc::bound_mem_functor1<void, QNXA
PI::Resmgr::ResmgrIoSelector, _resmgr_context*>, void, _resmgr_context*>::call_i
t(sigc::internal::slot_rep*, _resmgr_context* const&) (rep=0x804d280,
a_1=@0x80475bc) at functors/slot.h:136
#17 0xb8282df5 in sigc::internal::signal_emit1<void, _resmgr_context*, sigc::nil
>::emit(sigc::internal::signal_impl*, _resmgr_context* const&) (
impl=0x804b398, _A_a1=@0x80475bc) at signal.h:686
#18 0xb826ba3a in sigc::signal1<void, _resmgr_context*, sigc::nil>::emit(_resmgr
_context* const&) const (this=0x8047a2c, _A_a1=@0x80475bc) at signal.h:1812
#19 0xb826b5c5 in QNXAPI::IoSelector<_resmgr_context>::Block() (this=0x8047a10)
at ioselector:447
#20 0xb8268827 in QNXAPI::Resmgr::Run(sigc::slot<bool, int, sigc::nil, sigc::nil
, sigc::nil, sigc::nil, sigc::nil, sigc::nil>) (this=0x80477c4, loopControl=
{<slot1<bool,int>> = {<slot_base> = {<functor_base> = {<No data fields
>}, rep_ = 0x804d4b0, blocked_ = false}, <No data fields>}, <No data fields>})
at resmgr.cpp:1288
#21 0xb82685e4 in QNXAPI::Resmgr::Run() (this=0x80477c4) at resmgr.cpp:1267
#22 0x0804911d in main (argc=2, argv=0x8047a6c) at main.cpp:38Gordon Molek2008-01-07T19:40:12Zpost4102: Re: Build failure
http://community.qnx.com/sf/go/post4102
Rennie,
I would be happy to provide a backtrace if you can provide me with instructions on how to do so (I am new to QNX).
Thanks regarding the "Monitor" button. I wasn't looking for it at that level of the forums.
GordonGordon Molek2008-01-07T19:23:31Zpost4092: Re: Build failure
http://community.qnx.com/sf/go/post4092
Gordon,
Are saying you started Ramdisk like so:
# Ramdisk /ramdisk ?
If so then this should work. Can you get a back-trace from gdb?
You can certainly get notification of posts, by clicking on the "monitor" button for the forum.
Thanks,
RennieRennie Allen2008-01-07T17:16:13Zpost4079: Re: Build failure
http://community.qnx.com/sf/go/post4079
> Hi Gordon,
>
> What is your command line invocation for Ramdisk?
>
> It requires a single argument (which is the mountpoint of the ramdisk). Since
> it is intended as example code, the error handling of detecting a NULL argv[0
> ] is omitted...
>
> Thanks,
>
> Rennie
Rennie,
In the "Arguments" tab of the "Open Launch Config" pane reached via "Run As->C/C++ QNX Conn" menu I simply but "/ramdisk". Did you mean to say "argv[1]" as isn't argv[0] the programe's name, supplied by the fork/exec?
Also, is there any way to set up my account to receive e-mail notification when a post in made to the forum?
Thanks,
GordonGordon Molek2008-01-07T12:57:30Zpost4025: Re: Build failure
http://community.qnx.com/sf/go/post4025
Hi Gordon,
What is your command line invocation for Ramdisk?
It requires a single argument (which is the mountpoint of the ramdisk). Since it is intended as example code, the error handling of detecting a NULL argv[0] is omitted...
Thanks,
RennieRennie Allen2008-01-03T02:45:55Zpost3991: Re: Build failure
http://community.qnx.com/sf/go/post3991
Rennie,
Thanks, now we can build.
I've attempted to run the RAM disk example. I've copied the libsigc-2.0_g.so and libqfc_g.so libraries to the target and placed them in /lib. The RAM disk application runs and is receive blocked until I attempt to do anything signficant to it, e.g., ls -l /mount-point, cd /mount-point, etc., at which point it terminates. Running in the debugger doesn't help much as I don't know how to set it up yet to see all the necessary source (I only see the main() source for the ram disk application.
Thanks,
Gordon MolekGordon Molek2007-12-27T13:23:25Zpost3917: Re: Build failure
http://community.qnx.com/sf/go/post3917
> Hello,
> I'm attempting to build QFC for the first time and when I attempt to build
> sigc++ I get errors in signal.h
>
> 33: typedef size_t size_type; - ISO C++ forbids declaration
> 34: typedef ptrdiff_t difference_type - ISO C++ forbids declaration
>
> and similarly in signal_base.h
>
> 45: typedef size_t size_type; - ISO C++ fobids declaration
>
> I am running Momemtics Version: 4.0.1 Build id: I20070321
>
> Thanks in advance,
>
> Gordon Molek
> Zebra Technologies Corporation
Hi Gordon,
This is an error on my part (sorry). Momentics base directory used to be QNX630, but it is now QNX632.
Here is how to fix this.
1. right-click on the "sigc++" project and then select "properties".
2. on the properties dialog select "C/C++ build"
3. on the "configuration" drop-down, select the build target (unfortunately, the following steps need to be performed for each build target)
4. once you have the desired build target selected, then under "QCC Compiler", select the "General" item
5. you should now see a text field titled "Other Options"; in this field change all references to QNX630 to QNX632
That should do it. I'll update this in the next few days. Thanks for pointing this out!Rennie Allen2007-12-19T15:49:35Zpost3901: Build failure
http://community.qnx.com/sf/go/post3901
Hello,
I'm attempting to build QFC for the first time and when I attempt to build sigc++ I get errors in signal.h
33: typedef size_t size_type; - ISO C++ forbids declaration
34: typedef ptrdiff_t difference_type - ISO C++ forbids declaration
and similarly in signal_base.h
45: typedef size_t size_type; - ISO C++ fobids declaration
I am running Momemtics Version: 4.0.1 Build id: I20070321
Thanks in advance,
Gordon Molek
Zebra Technologies CorporationGordon Molek2007-12-19T14:10:59Z