on vacation. will test later. however, I have looked at the svn sources and consider it a weakness to assume that the expected target exists. never getting that message, at the least, has made understanding what I need to correct very difficult. I do not know either libtool or apr well enough to know if the root cause is in instdso.sh. imho the root cause is elsewhere (question: why is the target not installed?). Without having studied the content of the .la file I suspect a real structural solution comes from correcting what is wrong or missing there.
peeked at .la file, says dlname=libphp5.so If that is then intended target then that may be pointing more at apr as root cause. however that may be a misunderstanding on my part. in short, while I feel a warning about a missing target is what instdso.sh really needs - other changes constitute correcting errors from other/previous instructions and that it would be better to correct errors earlier in the build/install process. On Jun 22, 2014 6:58 AM, "Victor J. Orlikowski" < victor.j.orlikow...@alumni.duke.edu> wrote: > On Jun 20, 2014, at 12:34 PM, Michael Felt <mamf...@gmail.com> wrote: > > Here is the patch - as text, and a file (not sure what normal is, but > since it is small doing both). > > > So - I looked at what you did here, and then compared it both against > what’s in httpd-2.4.x and httpd-trunk. > > What happens when you use the instdso.sh from httpd-trunk, rather than > what you have in your patch? > You can get it from here: > https://svn.apache.org/repos/asf/httpd/httpd/trunk/build/instdso.sh > > Looks to me that the instdso.sh from trunk performs the same function, > except for multiple DSO names, and has some accomodations for AIX. > > If that works - it makes sense to me to pull the instdso.sh from trunk > back to 2.4.x and 2.2.x. > > Best, > Victor > -- > Victor J. Orlikowski <> victor.j.orlikow...@alumni.duke.edu > >
