It’s time to say Merry Christmas and a Happy New Year to all. I’m
off to Kiwiland for my Christmas vacation.
Happy hacking, and see you in January!!!
Colin
Wait!
Patch A hasn’t been out yet, how come you are already going to leave
for vacation 
On 13 Dec 2000 cburgess@qnx.com wrote:
It’s time to say Merry Christmas and a Happy New Year to all. I’m
off to Kiwiland for my Christmas vacation.Happy hacking, and see you in January!!!
Colin
You deserve it Colin, as an Aussie would say “avagoodollie”
<cburgess@qnx.com> wrote in message news:918uo2$1q0$2@nntp.qnx.com…
It’s time to say Merry Christmas and a Happy New Year to all. I’m
off to Kiwiland for my Christmas vacation.Happy hacking, and see you in January!!!
Colin
Frank Liu <liug@mama.indstate.edu> wrote:
Wait!
Patch A hasn’t been out yet, how come you are already going to leave
for vacation >
Hmmmm, and I just got back to find that it hasn’t gone out yet. 
Great holiday though…
On 13 Dec 2000 > cburgess@qnx.com > wrote:
It’s time to say Merry Christmas and a Happy New Year to all. I’m
off to Kiwiland for my Christmas vacation.Happy hacking, and see you in January!!!
Colin
Just joking. Been with qnx for so many years, I know it won’t be this quick.
tcpip5 beta (aka tcp bsd4.4, once a big deal) has been in beta for more
than two years.
Anyway, now that we are already late, is it possible for you to
introduce a system config file (like /etc/ld.so.conf) for shared libs?
I know you have set env variable on per application basis, but there
are many cases we’d prefer a system config file. I am sure you know
what I mean.
frank
On 12 Jan 2001 cburgess@qnx.com wrote:
Frank Liu <> liug@mama.indstate.edu> > wrote:
Wait!
Patch A hasn’t been out yet, how come you are already going to leave
for vacation >Hmmmm, and I just got back to find that it hasn’t gone out yet. >
Great holiday though…
On 13 Dec 2000 > cburgess@qnx.com > wrote:
It’s time to say Merry Christmas and a Happy New Year to all. I’m
off to Kiwiland for my Christmas vacation.Happy hacking, and see you in January!!!
Colin
–
cburgess@qnx.com
\
Anyway, now that we are already late, is it possible for you to
introduce a system config file (like /etc/ld.so.conf) for shared libs?
I know you have set env variable on per application basis, but there
are many cases we’d prefer a system config file. I am sure you know
what I mean.
frank
That would mean a change to the runtime linker, which isn’t really
my baby, but I’ll ask…
Previously, Frank Liu wrote in qdn.public.qnxrtp.devtools:
[…]
Anyway, now that we are already late, is it possible for you to
introduce a system config file (like /etc/ld.so.conf) for shared libs?
I know you have set env variable on per application basis, but there
are many cases we’d prefer a system config file. I am sure you know
what I mean.
I did a little experiment, and it looks like you have to set the env
variable before you start the program. If you use setenv() in C
code then it does not take effect. So there is a reasonably good
technical reason for wanting the ld.so.conf file as well.
Andrew
Andrew Thomas <Andrew@cogent.ca> wrote:
Previously, Frank Liu wrote in qdn.public.qnxrtp.devtools:
[…]
Anyway, now that we are already late, is it possible for you to
introduce a system config file (like /etc/ld.so.conf) for shared libs?
I know you have set env variable on per application basis, but there
are many cases we’d prefer a system config file. I am sure you know
what I mean.I did a little experiment, and it looks like you have to set the env
variable before you start the program. If you use setenv() in C
code then it does not take effect. So there is a reasonably good
technical reason for wanting the ld.so.conf file as well.
This is true for shared libraries, since the runtime linker runs before
main.
However, setting the LD_LIBRARY_PATH variable does have effect on dlopen().