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 b
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 platf
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
>
> 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
> "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'
> 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.
That is kind of weird,
> "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>
I was unable to get Apple's mod_perl to do anything at all, it just kept
crashing.
Also, I am confused as to exactly what Apache::Request is, and where it
is found, because all these work (and I've never installed a specific
Apache::Request):
[localhost:~] kyle% perl -MApache::Request -e '1'
On Tuesday, February 19, 2002, at 08:49 PM, Kyle Moffett wrote:
> 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
I wouldn't say so. I've had mod_perl working for a very long time, but
Apache::Reques
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 'PerlR
>> 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 th
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 out
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 out
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::
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 on
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 getti
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 succeed
Sure, will do as soon as I get everything done.
Kyle Moffett
On Thursday, January 24, 2002, at 09:29 , David R. Morrison wrote:
> 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
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 PRO
On 25/1/02 1:26 PM, "Kyle Moffett" <[EMAIL PROTECTED]> wrote:
> On Thursday, January 24, 2002, at 09:20 , Jeremy Higgs wrote:
>
>> On 25/1/02 1:15 PM, "Kyle Moffett" <[EMAIL PROTECTED]> wrote:
>>
>>> I am attempting to create a slew of packages for Apache::ASP and all
>>> its
>>> dependancies,
On Thursday, January 24, 2002, at 09:20 , Jeremy Higgs wrote:
> On 25/1/02 1:15 PM, "Kyle Moffett" <[EMAIL PROTECTED]> wrote:
>
>> 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? O
shit I didn't know that, I did diff -ru and ran
Patch: %f.patch
PatchScript: touch blah
[EMAIL PROTECTED] writes:
>I usually extract the source tarball twice, and move one to
>SOURCE-patched,
>modify everything in then, and then run 'diff -ru SOURCE SOURCE-patch >
>PACKAGE-VERSION-REVISION.patch
On 25/1/02 1:15 PM, "Kyle Moffett" <[EMAIL PROTECTED]> wrote:
> 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)?
Not sure
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
24 matches
Mail list logo
