On Sat, 14 Feb 2004, Riccardo wrote:
Hello,
I posted the buildlog I got on AIX... did someone had a look at it to see if there are some warnings or errors that could explain the brokeness of dillo on aix?
Yes I did. The only thing capable of producing an illegal instruction I can think of by reading the gcc compile log is: <q> main.c:298: warning: passing arg 3 of `naccept' from incompatible pointer type bookmarks.c:1824: warning: passing arg 3 of `naccept' from incompatible pointer type downloads.c:176: warning: passing arg 3 of `naccept' from incompatible pointer type </q> The third argument of accept() is of socklen_t * type. If the size of the pointed-to value is smaller than the actual type, memory corruption can happen. If AIX doesn't provide socklen_t, dillo blithely defines it as: <q> IO/http.c: #define socklen_t guint32 ../dpi/downloads.c: #define socklen_t guint32 ../dpid/dpi.h: #define socklen_t guint32 </q> Please try changing these to int. This is: #define socklen_t int The other warnings worth of considering at this point are: <q> ld: 0711-224 WARNING: Duplicate symbol: .strcmp ld: 0711-224 WARNING: Duplicate symbol: strcmp ld: 0711-224 WARNING: Duplicate symbol: .pow ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. </q> Hope this helps Jorge.-