message unavailable
Sam, here’s how patching works:
The fs-pkg works on a top-down basis in the packages file,
/etc/system/package/packages
If you put a package higher in the list than another package,
its files will be seen and any duplicate files in the lower
package will be hidden.
In this way, you can ensure that a package which is meant
to patch an older package is seen, just ensure that it is
installed higher in the list than the package to which it is
an update.
This can be done with an Order Dependency in the manifest:
QPM:ProductInstallationProcedure
QPM:OrderDependency
QPM:OrderInstallOver</QPM:Order>
QPM:Productold_product_identifier</QPM:Product>
</QPM:OrderDependency>
</QPM:ProductInstallationProcedure>
Packager also allows you to use a QPP (QNX Package
Patching) file to tell packager what old packages are being
updated. It will then make patches which include only those
files which are new, or have changed since the previous
package was built.
Let me know if you need to know how to use QPP files
for your project.
Jerry Chappell
CC setting stuff
- that the src/helper/GuessOS was wrong. The default was
for QNX4(Watcom C) not for Neutrino cc.- the use of crypt() (search for QNX or qnx in the src files)
- the use of -lunix.
Doesn’t using qcc (vs gcc) for CC fix the last one?
Plus what else?
libtoolize might help #1 and 2 ?
n2kra@orn.com wrote:
:>
:>
:>
:>- that the src/helper/GuessOS was wrong. The default was
:> for QNX4(Watcom C) not for Neutrino cc.
:>- the use of crypt() (search for QNX or qnx in the src files)
:>- the use of -lunix.
: Doesn’t using qcc (vs gcc) for CC fix the last one?
Not really, IIRC, it was hardcoded in the src/Configure
: Plus what else?
That’s all I could remember. If you have any other problems
post the log here, it will probably refresh my memory.
: libtoolize might help #1 and 2 ?
I recently ported apache to QNX, here is what I did:
download the latest tgz from www.apache.org (1.3.20)
(note all of the following is to override apaches desire to compile & link for QNX 4.x)
edit src/helpers/GuessOS & comment out QNX section
export LDFLAGS=-lsocket
edit src/support/htdigest.c so that it uses <signal.h> not <sys/signal.h>
…/configure
make
make install
Alain Magloire wrote:
n2kra@orn.com > wrote:
:
:> - that the src/helper/GuessOS was wrong. The default was
:> for QNX4(Watcom C) not for Neutrino cc.
:>- the use of crypt() (search for QNX or qnx in the src files)
:>- the use of -lunix.: Doesn’t using qcc (vs gcc) for CC fix the last one?
Not really, IIRC, it was hardcoded in the src/Configure
: Plus what else?
That’s all I could remember. If you have any other problems
post the log here, it will probably refresh my memory.: libtoolize might help #1 and 2 ?
Thanks, I downloaded and compiled version 1.3.29 using the info you posted
and I got an executable with no errors…however when I try to start it
using:
…/apachectl start
it says “httpd started”, but I can’t see the process running using PIDIN and
I don’t get a process ID reported back to the shell. When I use:
…/apachectl stop
it says “http: (no pid file) not running”
Any ideas ?
Thank you!
Simon Platten
“Chris Goebel” <cgoebel@tridium.com> wrote in message
news:3BCB436B.36502E9A@tridium.com…
I recently ported apache to QNX, here is what I did:
download the latest tgz from > www.apache.org > (1.3.20)
(note all of the following is to override apaches desire to compile & link
for QNX 4.x)edit src/helpers/GuessOS & comment out QNX section
export LDFLAGS=-lsocket
edit src/support/htdigest.c so that it uses <signal.h> not <sys/signal.h./configure
make
make install
Alain Magloire wrote:n2kra@orn.com > wrote:
:
:> - that the src/helper/GuessOS was wrong. The default was
:> for QNX4(Watcom C) not for Neutrino cc.
:>- the use of crypt() (search for QNX or qnx in the src files)
:>- the use of -lunix.: Doesn’t using qcc (vs gcc) for CC fix the last one?
Not really, IIRC, it was hardcoded in the src/Configure
: Plus what else?
That’s all I could remember. If you have any other problems
post the log here, it will probably refresh my memory.: libtoolize might help #1 and 2 ?
simon.platten@vtcontrols.co.uk sed in <atkm0e$aep$1@inn.qnx.com>:
./apachectl start
it says “httpd started”, but I can’t see the process running using PIDIN and
What does error_log say?
(not particular to QNX BTW)
kabe
sounds like you were not running “apachectl” as root?
frank
Simon A. Platten <simon.platten@vtcontrols.co.uk> wrote:
Thanks, I downloaded and compiled version 1.3.29 using the info you posted
and I got an executable with no errors…however when I try to start it
using:./apachectl start
it says “httpd started”, but I can’t see the process running using PIDIN and
I don’t get a process ID reported back to the shell. When I use:./apachectl stop
it says “http: (no pid file) not running”
Any ideas ?
Thank you!
Simon Platten
“Chris Goebel” <> cgoebel@tridium.com> > wrote in message
news:> 3BCB436B.36502E9A@tridium.com> …
I recently ported apache to QNX, here is what I did:download the latest tgz from > www.apache.org > (1.3.20)
(note all of the following is to override apaches desire to compile & link
for QNX 4.x)edit src/helpers/GuessOS & comment out QNX section
export LDFLAGS=-lsocket
edit src/support/htdigest.c so that it uses <signal.h> not <sys/signal.h./configure
make
make install
Alain Magloire wrote:n2kra@orn.com > wrote:
:
:> - that the src/helper/GuessOS was wrong. The default was
:> for QNX4(Watcom C) not for Neutrino cc.
:>- the use of crypt() (search for QNX or qnx in the src files)
:>- the use of -lunix.: Doesn’t using qcc (vs gcc) for CC fix the last one?
Not really, IIRC, it was hardcoded in the src/Configure
: Plus what else?
That’s all I could remember. If you have any other problems
post the log here, it will probably refresh my memory.: libtoolize might help #1 and 2 ?