Re: "expected to be defined in a dynamic image"
[EMAIL PROTECTED] (Chris Nandor) writes: > But ... libapreq is what I am building/testing. I can't link libapreq to > itself ... so I have no idea what to do here. Here's the complete error: > > dyld: /usr/local/apache/bin/httpd Undefined symbols: > /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b > undle undefined reference to _ApacheRequest > _post_params expected to be defined in a dynamic image > /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b > undle undefined reference to _ApacheRequest > _query_params expected to be defined in a dynamic image Please give Stas' patch a try: http://marc.theaimsgroup.com/?l=apreq-dev&m=105965131008577&w=2 The only reason it wasn't included in 1.3 was that we didn't know what would happen on OSX. We've seen enough bugreports from RedHat 9 users to believe that this patch should go in anyways. -- Joe Schaefer
Re: "expected to be defined in a dynamic image"
i would have said that the errors were coming from a failure to link Apache::Request to libapreq. in a diffident, mumbled sort of a way. But Apache::Request is a part of libapreq. ah. i dimly grasp the wrongness of this end of the stick and let go of it as if burnt. i assumed that libapreq was the name of the C library - what the apache site refers to as a 'Generic Apache Request Library for manipulating request data via the apache api', and that Apache::Request was a wrapper around that to expose those functions in perl. from what you're saying i glean that actually libapreq is just the name of the whole thing? oops. No it's not, libapreq is a C library, and then there are Perl (XS) interfaces to libapqreq: Apache::Request, Apache::Cookie and Apache::Upload. Granted it's a tad confusing since the whole thing is packaged under the name libapreq as a CPAN distro. -- Eric Cholet
Re: "expected to be defined in a dynamic image"
On 21 Nov 2003, at 22:15, Chris Nandor wrote: At 22:01 + 2003.11.21, william ross wrote: On 21 Nov 2003, at 20:54, Chris Nandor wrote: In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (William Ross) wrote: In your case it looks like a broken link to libapreq. i had similar errors with libapreq built through CPAN.pm, but I vaguely recall that rebuilding it by hand seemed to work. It wasn't a new apache, though: just the standard one, and i was so beset with error messages at the time that it's hard to remember what worked. But ... libapreq is what I am building/testing. I can't link libapreq to itself ... so I have no idea what to do here. Here's the complete error: i would have said that the errors were coming from a failure to link Apache::Request to libapreq. in a diffident, mumbled sort of a way. But Apache::Request is a part of libapreq. ah. i dimly grasp the wrongness of this end of the stick and let go of it as if burnt. i assumed that libapreq was the name of the C library - what the apache site refers to as a 'Generic Apache Request Library for manipulating request data via the apache api', and that Apache::Request was a wrapper around that to expose those functions in perl. from what you're saying i glean that actually libapreq is just the name of the whole thing? oops. beg your pardon. will
Re: "expected to be defined in a dynamic image"
At 22:01 + 2003.11.21, william ross wrote: >On 21 Nov 2003, at 20:54, Chris Nandor wrote: > >> In article <[EMAIL PROTECTED]>, >> [EMAIL PROTECTED] (William Ross) wrote: >> >>> > >>> In your case it looks like a broken link to libapreq. i had similar >>> errors with libapreq built through CPAN.pm, but I vaguely recall that >>> rebuilding it by hand seemed to work. It wasn't a new apache, though: >>> just the standard one, and i was so beset with error messages at the >>> time that it's hard to remember what worked. >> >> But ... libapreq is what I am building/testing. I can't link libapreq >> to >> itself ... so I have no idea what to do here. Here's the complete >> error: > >i would have said that the errors were coming from a failure to link >Apache::Request to libapreq. in a diffident, mumbled sort of a way. But Apache::Request is a part of libapreq. -- Chris Nandor [EMAIL PROTECTED]http://pudge.net/ Open Source Development Network[EMAIL PROTECTED] http://osdn.com/
Re: "expected to be defined in a dynamic image"
On 21 Nov 2003, at 20:54, Chris Nandor wrote: In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (William Ross) wrote: In your case it looks like a broken link to libapreq. i had similar errors with libapreq built through CPAN.pm, but I vaguely recall that rebuilding it by hand seemed to work. It wasn't a new apache, though: just the standard one, and i was so beset with error messages at the time that it's hard to remember what worked. But ... libapreq is what I am building/testing. I can't link libapreq to itself ... so I have no idea what to do here. Here's the complete error: i would have said that the errors were coming from a failure to link Apache::Request to libapreq. in a diffident, mumbled sort of a way. I had similar trouble when in CPAN.pm but it all eventually worked for me when i downloaded libapreq from http://httpd.apache.org/apreq/ and approached it that way round. ? best will
Re: "expected to be defined in a dynamic image"
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Chris Nandor) wrote:
> dyld: /usr/local/apache/bin/httpd Undefined symbols:
> /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b
> undle undefined reference to _ApacheRequest
> _post_params expected to be defined in a dynamic image
> /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b
> undle undefined reference to _ApacheRequest
> _query_params expected to be defined in a dynamic image
> [Fri Nov 21 12:48:52 2003] [notice] child pid 1858 exit signal Trace/BPT
> trap (5)
For kicks, I decided to rebuild this one extension with the old LDDLFLAGS
("-flat_namespace -undefined suppress"). The errors are now:
dyld: /usr/local/apache/bin/httpd Undefined symbols:
_ApacheRequest_post_params
_ApacheRequest_query_params
I don't know if this is instructive in any way.
--
Chris Nandor [EMAIL PROTECTED]http://pudge.net/
Open Source Development Network[EMAIL PROTECTED] http://osdn.com/
Re: "expected to be defined in a dynamic image"
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (William Ross) wrote: > I've run into these. The answer has been to specify explicitly > libraries that are normally left implicit. I found the failures odd, > too. if a libdir is incorrect, make fails. if the directory is correct > but the library is unspecified, make appears to work but all tests > fail. > > (eg. to build Image::Magick properly you have to specify -lpng -lxml2 > -ljpeg and so on in the LIBS, and to build DBD::Pg you have to specify > -lssl -lcrypto, though it both normally work without the extra nudges.) > > In your case it looks like a broken link to libapreq. i had similar > errors with libapreq built through CPAN.pm, but I vaguely recall that > rebuilding it by hand seemed to work. It wasn't a new apache, though: > just the standard one, and i was so beset with error messages at the > time that it's hard to remember what worked. But ... libapreq is what I am building/testing. I can't link libapreq to itself ... so I have no idea what to do here. Here's the complete error: dyld: /usr/local/apache/bin/httpd Undefined symbols: /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b undle undefined reference to _ApacheRequest _post_params expected to be defined in a dynamic image /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/Request.b undle undefined reference to _ApacheRequest _query_params expected to be defined in a dynamic image [Fri Nov 21 12:48:52 2003] [notice] child pid 1858 exit signal Trace/BPT trap (5) > but most things still just work, for me, including other XSive modules > and heavy linkers like DBD::mysql. I've only had trouble linking to > fink- and cpan-built libraries, now that i think of it. Perhaps there > is a subtle mismatch of compilers or configurations somewhere? Nope. Everything built fresh with same compilers, same perl version. I really hope I don't need to back out of this two-level namespace thing and rebuild everything again. -- Chris Nandor [EMAIL PROTECTED]http://pudge.net/ Open Source Development Network[EMAIL PROTECTED] http://osdn.com/
Re: "expected to be defined in a dynamic image"
I've run into these. The answer has been to specify explicitly libraries that are normally left implicit. I found the failures odd, too. if a libdir is incorrect, make fails. if the directory is correct but the library is unspecified, make appears to work but all tests fail. (eg. to build Image::Magick properly you have to specify -lpng -lxml2 -ljpeg and so on in the LIBS, and to build DBD::Pg you have to specify -lssl -lcrypto, though it both normally work without the extra nudges.) In your case it looks like a broken link to libapreq. i had similar errors with libapreq built through CPAN.pm, but I vaguely recall that rebuilding it by hand seemed to work. It wasn't a new apache, though: just the standard one, and i was so beset with error messages at the time that it's hard to remember what worked. but most things still just work, for me, including other XSive modules and heavy linkers like DBD::mysql. I've only had trouble linking to fink- and cpan-built libraries, now that i think of it. Perhaps there is a subtle mismatch of compilers or configurations somewhere? best will On 21 Nov 2003, at 15:47, Chris Nandor wrote: [Fri Nov 21 07:27:55 2003] [notice] child pid 22666 exit signal Trace/BPT trap (5) dyld: /usr/local/apache/bin/httpd Undefined symbols: /Users/pudge/.cpan/build/libapreq-1.3/blib/arch/auto/Apache/Request/ Request.bundle undefined reference to _ApacheRequest _post_params expected to be defined in a dynamic image I am seeing quite a lot of errors in Apache, preventing me from starting it up, regarding undefined references with "expected to be defined in a dynamic image". This is perl 5.8.2, darwin-2level. I am tempted to try to disable two-level namespaces in perl ... anyone? Thanks, -- Chris Nandor [EMAIL PROTECTED]http://pudge.net/ Open Source Development Network[EMAIL PROTECTED] http://osdn.com/
