Hi List,
I finally have a first alpha release of BIA. There are still lots of
little things that need to be added or improved. I am still trying to
figure out how to get out of the whole RPATH mess. Any tips on how to
build Tcl and AOLserver without any embedded RPATHs (and without
patching the
At Wednesday 07:16 PM 8/24/2005, Andrew Piskorski
wrote:
John Caruso wrote:
Basically, AOLserver 4 is hostile to being built (or having its
modules built) in anything other than its final installation
directory.
Frankly, I'm not sure what you're talking about.
I explained one facet of it in
On 2005.08.24, John Caruso [EMAIL PROTECTED] wrote:
But AOLserver 4 doesn't let you do this, and in fact makes it very
difficult to achieve at all (much more so that it was under AOLserver
3.4.2, as I showed in my posting).
Maybe I'm misunderstanding this, but ... at least for the tip of the
Dynamic link is best -- there was a lot of effort recently to get all
that working right recently, with modules as small stubs that call
into the dll's located in the lib/ directory and such.
-Jim
On Aug 25, 2005, at 10:00 AM, Olaf Mersmann wrote:
Another issue I am undecided on is
Nate's working on some config stuff as well -- would be good to
coordinate the efforts and get it into the core distribution.
-jim
On Aug 25, 2005, at 9:52 AM, Olaf Mersmann wrote:
* Jim Davidson [EMAIL PROTECTED] [050825 15:24]:
*snip*
7. would also be good if something in the
On 2005.08.25, Olaf Mersmann [EMAIL PROTECTED] wrote:
Ok, I plan on setting the -rpaths to the default install directory
(/opt/aolserver/ - any objections?) [...]
This is exactly the danger of using -R/-rpath. On Solaris, /opt is a
popular place to install packages. On Linux, /usr/local is
* Jim Davidson [EMAIL PROTECTED] [050825 15:24]:
*snip*
7. would also be good if something in the install helped build up the
server nsd.tcl config as well
I'm working on a simple nsd.tcl generation TCL script for the
Batteries Included AOLserver distribution. Maybe parts of this can be
On 2005.08.25, Jim Davidson [EMAIL PROTECTED] wrote:
Dynamic link is best -- there was a lot of effort recently to get all
that working right recently, with modules as small stubs that call
into the dll's located in the lib/ directory and such.
On Aug 25, 2005, at 10:00 AM, Olaf Mersmann
I am indeed. :-)
Basically I've started creating a series of small config examples
which can be concatenated together based on which features you would
like to enable. See: $AOLSERVER/examples/config.
Example: cat base.tcl nscp.tcl nsd.tcl (would create base AOLserver
config with a
Folks,
OK -- so it sounds like we have the following goals:
1. sources need to be configurable and buildable in the source directory
2. final install location needs to be part of the config for all the -
rpath junk
3. install/copy step needs to bypass the final install location and
copy to
On 2005.08.25, Nathan Folkman [EMAIL PROTECTED] wrote:
$ bin/tclsh84 ./nsconfig.tcl -debug -modules nscp
or maybe this is better...
A thin ADP application that stores config settings in a AGF file which
is then used to forward-generate a nsd.tcl.
Web-based config. It was all the rage in the
On Aug 25, 2005, at 11:12 AM, Dossy Shiobara wrote:
On 2005.08.25, Nathan Folkman [EMAIL PROTECTED] wrote:
$ bin/tclsh84 ./nsconfig.tcl -debug -modules nscp
or maybe this is better...
A thin ADP application that stores config settings in a AGF file which
is then used to forward-generate a
Ugh -- that thing was a mess and hard to maintain. Better to start
over.
-Jim
On Aug 25, 2005, at 11:22 AM, Nathan Folkman wrote:
On Aug 25, 2005, at 11:12 AM, Dossy Shiobara wrote:
On 2005.08.25, Nathan Folkman [EMAIL PROTECTED] wrote:
$ bin/tclsh84 ./nsconfig.tcl -debug -modules
Yup -- that's what I understood the question to be and agree, link
against the dynamic libraries.
-Jim
On Aug 25, 2005, at 10:53 AM, Dossy Shiobara wrote:
On 2005.08.25, Jim Davidson [EMAIL PROTECTED] wrote:
Dynamic link is best -- there was a lot of effort recently to get all
that
On Thursday 25 August 2005 07:29, Dossy Shiobara wrote:
On 2005.08.25, Olaf Mersmann [EMAIL PROTECTED] wrote:
Ok, I plan on setting the -rpaths to the default install directory
(/opt/aolserver/ - any objections?) [...]
This is exactly the danger of using -R/-rpath. On Solaris, /opt is a
* Dossy Shiobara [EMAIL PROTECTED] [050825 17:18]:
On 2005.08.25, Nathan Folkman [EMAIL PROTECTED] wrote:
*snip*
A thin ADP application that stores config settings in a AGF file which
is then used to forward-generate a nsd.tcl.
My current setup is pretty frontend neutral. The current system
* Dossy Shiobara [EMAIL PROTECTED] [050825 17:00]:
On 2005.08.25, Jim Davidson [EMAIL PROTECTED] wrote:
Dynamic link is best -- there was a lot of effort recently to get all
that working right recently, with modules as small stubs that call
into the dll's located in the lib/ directory
* Dossy Shiobara [EMAIL PROTECTED] [050824 07:21]:
On 2005.08.24, Olaf Mersmann [EMAIL PROTECTED] wrote:
Another point I'm still unsure about is weather to ship stripped
libs and binaries
No ... please don't. It makes debugging other people's problems much
harder if they're running
On Wed, Aug 24, 2005 at 01:14:53AM -0400, Dossy Shiobara wrote:
A simple kludge would be to provide a wrapper script to start nsd that
sets LD_LIBRARY_PATH accordingly, but this seems like a big kludge.
It's absolutely not a kludge: matter of fact, I think Debian Linux
requires that paths
Turns out I spent a lot of time getting those -rpaths and -
install_name things to work :) Oh well.
Anyway, seems like three cases:
- Mac OS/X -- without -install_name, it burns in the current build
directory -- I think install_name_tool can be used at install time to
reset.
- On
At Wednesday 02:55 PM 8/24/2005, Jim Davidson wrote:
- On all other Unix, I could
purge all the -rpath stuff from the
build so folks are required to do the right thing with
LD_LIBRARY_PATH, ld.config, whatever on their
system.
I'd cast a very strong NO vote for this. Forcing people to always
On Wed, Aug 24, 2005 at 03:45:47PM -0700, John Caruso wrote:
I discussed some of the thorny issues facing package developers for
AOLserver 4 (which included some of these very issues) in this posting
about two years ago...:
http://article.gmane.org/gmane.comp.web.aolserver/9468
In
Hi list,
I've been hacking on a simple script to download, unpack and build
TCL, AOLserver and all needed modules + dependencies. The ultimate
goal of this is to create a simple way to build installable shars of
AOLserver for different plaforms os people can test out AOLserver
easily without the
23 matches
Mail list logo
