pointed out that I needed the GCC files installed!!! I put on the following RPMs: binutils, cpp,
kernel-headers, glibc-devel, gcc, openssl-devel - and it then built the connector perfectly!
Final question: Having built this connector, can I use it on another machine with identical
configuration but without the additional GCC files installed? I appreciate that if/when Apache
and/or CFMX is next upgraded I will need to build another connector but it would mean that the
deployed servers can run with a connector built on a test machine (of identical spec) here in the
office.
Thanks, M
On 9/10/03, Matthew Smith <[EMAIL PROTECTED]> wrote:
>Sorry to be a pain but how do I actually find out which command failed? Is it a question of issuing
>the 'Macromedia command statements' one by one or something? Sorry but I need some v. basic
>instructions!
>
>Incidentally, I have spoken to Red Hat here in the UK about this issue this morning but it goes
>beyond the normal level of their support. The engineer did say that he was 'surprised' that the
>command for apxs didn't include a '-o' flag?! Don't know why that would be relevant but thought I
>would pass it on!!
>
>(I have tried several Google searches but am amazed that nobody else is having this problem? I am
>happy to deploy the server using the standard connector - and trust Steven's experience of never
>seeing a case of Apache crashing - but would feel much better if it was the proper connector!).
>
>Many thanks, M
>
>On 8/10/03, Steven Erat <[EMAIL PROTECTED]> wrote:
>
>>Well, you're right that its better to recompile the connector for EAPI, although I've never seen an
>actual case of Apache crashing due to this. I recommend finding the command that failed while
>running apxs, then running that command from the same location by itself. Then you'd get an error
>from the compiler instead of an apxs error code.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
