>Number:         3862
>Category:       os-aix
>Synopsis:       DSO-capable Compile error on AIX -- complains of missing file 
>(src/libhttpd.exp)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Feb  8 21:50:01 PST 1999
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.3 and 1.3.4
>Environment:
AIX 4.2
CC=gcc
./configure enable-rule=SHARED_CORE enable-module=so prefix=/home/sweet/home
and
./configure enable-rule=SHARED_CORE prefix=/home/sweet/home
>Description:
cf pr 3748

ld -H512 -T512 -bhalt:4 -bM:SRE -bnoentry -bI:./support/httpd.exp  -bE:`echo 
libhttpd.so|sed -e 's:\.so$:.exp:'` -lc -o libhttpd.so buildmark.o modules.o 
modules/standard/libstandard.a main/libmain.a ./os/unix/libos.a ap/libap.a 
regex/libregex.a
ld: 0706-004 Cannot find or read export file: libhttpd.exp
        ld:accessx(): A file or directory in the path name does not exist.
make[2]: *** [libhttpd.so] Error 255

So far as I can make out, the linker is expecting both the list of
symbols to be imported (-bI:) and the list of symbols to be exported
(-bE:) to already exist.  Unfortunately, the latter--which should
hold, I believe, all the symbols in all the .o files listed (?)--does
not exist.  If I create it by hand (a simple column of ar -w output, minus 
the .o containers),  I see spew of warnings about duplicate symbols, then
compile trips at next target (libhttpd.ep).

Works fine without DSO support.  Works fine with DSO support on solaris 26 
(fwiw)

>How-To-Repeat:

>Fix:
I've tried.  Failed.  Hoping your aix maven can shed a little light on this.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to