Re: [Fink-devel] Perl Packages Diff usage

2002-02-24 Thread Jeff Whitaker


 the .so for A::R and A::C both statically link to libapreq, which
 should internally bind the entry points between the A::R/A::C and
 libapreq libs, and it does on every platform including Apple.

 However, on Apple, the entry points are also *published*, so when both
 .so's are pulled in, you get a duplicate on the libapreq entry points!
 I'm not smart enough to know how to turn that off.


Randall:  I think setting the environment variable
DYLD_FORCE_FLAT_NAMESPACE may fix this.  At least it has for me in similar
situations with the python interpreter.

-Jeff

 --
Jeffrey S. Whitaker Phone  : (303)497-6313
Meteorologist   FAX: (303)497-6449
NOAA/OAR/CDC  R/CDC1Email  : [EMAIL PROTECTED]
325 BroadwayWeb: www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-24 Thread David R. Morrison

Kyle Moffett [EMAIL PROTECTED] wrote:

 On Sunday, February 24, 2002, at 07:25 , Jeff Whitaker wrote:
 
  the .so for A::R and A::C both statically link to libapreq, which
  should internally bind the entry points between the A::R/A::C and
  libapreq libs, and it does on every platform including Apple.
 
  However, on Apple, the entry points are also *published*, so when both
  .so's are pulled in, you get a duplicate on the libapreq entry points!
  I'm not smart enough to know how to turn that off.
 
 
  Randall:  I think setting the environment variable
  DYLD_FORCE_FLAT_NAMESPACE may fix this.  At least it has for me in 
  similar
  situations with the python interpreter.
 
 Unfortunately, this tends to break other packages that need the two 
 level namespace (Grrr.)

How about linking with the -force_flat_namespace option?  Does that help?




___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-24 Thread Kyle Moffett

On Sunday, February 24, 2002, at 08:20 , David R. Morrison wrote:

 Kyle Moffett [EMAIL PROTECTED] wrote:

 On Sunday, February 24, 2002, at 07:25 , Jeff Whitaker wrote:

 the .so for A::R and A::C both statically link to libapreq, which
 should internally bind the entry points between the A::R/A::C and
 libapreq libs, and it does on every platform including Apple.

 However, on Apple, the entry points are also *published*, so when 
 both
 .so's are pulled in, you get a duplicate on the libapreq entry 
 points!
 I'm not smart enough to know how to turn that off.


 Randall:  I think setting the environment variable
 DYLD_FORCE_FLAT_NAMESPACE may fix this.  At least it has for me in
 similar
 situations with the python interpreter.

 Unfortunately, this tends to break other packages that need the two
 level namespace (Grrr.)

 How about linking with the -force_flat_namespace option?  Does that 
 help?

Will try, that goes in LDFLAGS, right?

Thanks, Kyle Moffett


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-21 Thread Randal L. Schwartz

 Kyle == Kyle Moffett [EMAIL PROTECTED] writes:

Kyle Also, I am confused as to exactly what Apache::Request is, and where
Kyle it is found, because all these work (and I've never installed a
Kyle specific Apache::Request):

Kyle [localhost:~] kyle% perl -MApache::Request -e '1'
Kyle [localhost:~] kyle% perl -e 'use Apache::Request ()'
Kyle [localhost:~] kyle% perldoc Apache::Request

The problem is that both Apache::Request and Apache::Cookie link in
libapreq (statically).  You can use one *or* the other in a given
mod_perl-enabled process, but if you try to use both, they both
publish the same libapreq's symbols, and you get a symbol clash.

One hacky solution is to have libapreq linked statically in with the
binary, then let the dynamic Apache/Request.so satisfy the libapreq
from there.  That's the approach taken by this proffered solution.  To
me... it seems an odd hack to have to make the core binary provide
callbacks needed by second-tier shared libs. :(

Of course, the only way I could get mod_perl to pull in .so's is to
link it statically, which also seems odd.  How could Apple have
screwed up the linker and dynloader so much?

Kyle I don't know about custom-built dynamic ones, I just rebuilt my
Kyle mod_perl static and this worked well.

Until you use both Apache::Request and Apache::Cookie, then Booom!

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-21 Thread Randal L. Schwartz

 Kyle == Kyle Moffett [EMAIL PROTECTED] writes:

 The problem is that both Apache::Request and Apache::Cookie link in
 libapreq (statically).  You can use one *or* the other in a given
 mod_perl-enabled process, but if you try to use both, they both
 publish the same libapreq's symbols, and you get a symbol clash.

Kyle That is kind of weird, why isn't this the case on other platforms?

Not sure.

the .so for A::R and A::C both statically link to libapreq, which
should internally bind the entry points between the A::R/A::C and
libapreq libs, and it does on every platform including Apple.

However, on Apple, the entry points are also *published*, so when both
.so's are pulled in, you get a duplicate on the libapreq entry points!
I'm not smart enough to know how to turn that off.

That is, how do you tell Apple's linker that when making a .so that is
linking to a .a that the entry points that pull the .a in are
satisfied and now private?  Works on standard GNU ld, and every other
ld on the planet.  Not on Apple.  It makes those .a externs to be
also published by the .so.  Boom.  Bug?  Or feature?

Another workaround would be to make libapreq a separate .so, and then
pulling it in both ways from both A::C and A::R would still be OK.
Perhaps. :)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-19 Thread Ken Williams


On Sunday, January 27, 2002, at 03:55 PM, Kyle Moffett wrote:
 In using Apache::ASP, I need to use Apache::Request, I think, and I 
 think that is the cause for this error:

 parse_file_count check failed at T.pm line 33. -- , 
 blib/lib/Apache/ASP.pm line 1556
 FAILED before any test output arrived

 What a HEADACHE!!!   *:-(

Have you had any more luck with Apache::Request?  On the [EMAIL PROTECTED] 
list there have been some recent successes:

   http://archive.develooper.com/macosx%40perl.org/msg01539.html


  -Ken


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-19 Thread Kyle Moffett

 parse_file_count check failed at T.pm line 33. -- , 
 blib/lib/Apache/ASP.pm line 1556
 FAILED before any test output arrived

I figured out this stupid error, the test script makes a silly logical 
error, I made a patch to fix it, can somebody please add the three 
packages to CVS (on the tracker)

Thanks,
Kyle Moffett


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-02-19 Thread Kyle Moffett

I have figured out the problem.  The apple provided mod_perl is a shared 
lib.  I was looking to rebuild mod_perl with the latest version, and 
here's what I found:

The mod_perl readme says that the shared lib support is new and very 
unstable
I have encountered similar problems just using 'PerlRequire startup.pl' 
(startup.pl just '#!/usr/bin/perl' )in the httpd.conf file (a.k.a. 
malloc double free() error)
I downloaded and rebuilt apache with mod_perl statically linked, and 
everything has been going fine (I installed over Apple's, will reinstall 
after upgrades)
I even got some complex perl stuff to work.

Therefore:  The instability in Apache::Request (A part of mod_perl) may 
be due to the fact that mod_perl was unstable itself in the .so lib

Unfortunately, Apache::ASP does not work yet

On Tuesday, February 19, 2002, at 08:56 , Ken Williams wrote:


 On Sunday, January 27, 2002, at 03:55 PM, Kyle Moffett wrote:
 In using Apache::ASP, I need to use Apache::Request, I think, and I 
 think that is the cause for this error:

 parse_file_count check failed at T.pm line 33. -- , 
 blib/lib/Apache/ASP.pm line 1556
 FAILED before any test output arrived

 What a HEADACHE!!!   *:-(

 Have you had any more luck with Apache::Request?  On the 
 [EMAIL PROTECTED] list there have been some recent successes:

   http://archive.develooper.com/macosx%40perl.org/msg01539.html


  -Ken



___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-27 Thread Kyle Moffett

Sorry, I went skiing this weekend, so I was unable to answer until now

On Friday, January 25, 2002, at 11:28 , Ken Williams wrote:

 Hi Kyle, I have a couple of questions about this:

 1) Is Apache::Request one of the modules you've ported?  AFAIK nobody 
 else has succeeded in actually getting that (libapr) to work on OS X.  
 It builds and installs fine, but segfaults when you try to run, for 
 instance, the mod_perl test suite.

I'm not sure what you mean, all I have done so far is package some of 
the dependencies that Apache::Request uses to run, I haven't compiled 
its package at all yet, other than to have it tell me what it needs.  I 
will do that now.  I am not trying to compile mod_perl, since the 
modules can be used with either Apple's preinstalled mod_perl or a Fink 
installed one, or both!

 2) Was there any actual porting work, or just packaging so that you can 
 have the benefits of the package management system?

As above, so far all I have done is package stuff for Fink.

  -Ken

Kyle Moffett


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-27 Thread Ken Williams


On Sunday, January 27, 2002, at 01:03 PM, Kyle Moffett wrote:
 Sorry, I went skiing this weekend, so I was unable to answer until now

No problem. =)

 On Friday, January 25, 2002, at 11:28 , Ken Williams wrote:
 Hi Kyle, I have a couple of questions about this:

 1) Is Apache::Request one of the modules you've ported?  AFAIK nobody 
 else has succeeded in actually getting that (libapr) to work on OS X.  
 It builds and installs fine, but segfaults when you try to run, for 
 instance, the mod_perl test suite.

 I'm not sure what you mean, all I have done so far is package some of 
 the dependencies that Apache::Request uses to run, I haven't compiled 
 its package at all yet, other than to have it tell me what it needs.  I 
 will do that now.  I am not trying to compile mod_perl, since the 
 modules can be used with either Apple's preinstalled mod_perl or a Fink 
 installed one, or both!

Right - however, when you start compiling Apache::Request you'll find 
some difficulties.  The following threads from [EMAIL PROTECTED] have 
tried to deal with these questions:

   http:[EMAIL PROTECTED]/msg00800.html
   http:[EMAIL PROTECTED]/msg00625.html
   http:[EMAIL PROTECTED]/msg01121.html

(I wish there were a better archive for that list, that one's pretty 
hard to navigate, and not searchable.)

  -Ken


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-27 Thread Kyle Moffett

OK, I see what you mean

 1) Is Apache::Request one of the modules you've ported?  AFAIK nobody 
 else has succeeded in actually getting that (libapr) to work on OS X.  
 It builds and installs fine, but segfaults when you try to run, for 
 instance, the mod_perl test suite.

In using Apache::ASP, I need to use Apache::Request, I think, and I 
think that is the cause for this error:

parse_file_count check failed at T.pm line 33. -- , 
blib/lib/Apache/ASP.pm line 1556
FAILED before any test output arrived

What a HEADACHE!!!   *:-(

Thanx,
Kyle Moffett


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-27 Thread Ken Williams


On Sunday, January 27, 2002, at 03:55 PM, Kyle Moffett wrote:
 In using Apache::ASP, I need to use Apache::Request, I think, and I 
 think that is the cause for this error:

 parse_file_count check failed at T.pm line 33. -- , 
 blib/lib/Apache/ASP.pm line 1556
 FAILED before any test output arrived

 What a HEADACHE!!!   *:-(

Yeah, agreed.  Figuring this out is probably going to take some insight 
into how shared libraries work, insight I unfortunately don't have.  But 
I know lots of people that would be quite happy indeed to have this 
problem figured out!

  -Ken


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-25 Thread Ken Williams


On Thursday, January 24, 2002, at 08:15 PM, Kyle Moffett wrote:
 I am attempting to create a slew of packages for Apache::ASP and all 
 its dependancies...

Hi Kyle, I have a couple of questions about this:

1) Is Apache::Request one of the modules you've ported?  AFAIK nobody 
else has succeeded in actually getting that (libapr) to work on OS X.  
It builds and installs fine, but segfaults when you try to run, for 
instance, the mod_perl test suite.

2) Was there any actual porting work, or just packaging so that you can 
have the benefits of the package management system?

  -Ken


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



[Fink-devel] Perl Packages Diff usage

2002-01-24 Thread Kyle Moffett

I am attempting to create a slew of packages for Apache::ASP and all its 
dependancies, should I create them all, then post to a single package 
submission? Or should I post individually (like 15 different 
submissions)?

Also, can somebody give the procedure for using diff to make a patch, I 
did it once successfully, but I have been having problems repeating the 
thing.

Thanks,
Kyle Moffett


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] Perl Packages Diff usage

2002-01-24 Thread David R. Morrison

At the very least, you could create all 15 .info files, wrap them up into
a single .tar file, and put the .tar file onto the package submission
tracker.  Don't make me download 15 separate things!

  Thanks,
  Dave

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel