Hi David, Jay,

David Bertoni <[EMAIL PROTECTED]> writes:

> Note that in the AMD64 case, the output file is
> xercesc_messages_3_0_dat.o, while for s390, it's
> xercesc_messages_3_0_dat.ao. That would explain why the object file
> wasn't found.
>
> Can you look at the makefiles the ICU generated on these two platforms
> to see if there are any differences?

It appears that ICU can generate two types of makefiles: one that goes
through assembler (which uses .o for non-PIC object files) and one that
goes through C (which uses .ao). Since we are trying to guess which file
it is going to generate (we are not using the resulting library, only the
object file) and I didn't know about the second type of makefiles until
now, things broke. I've committed the fix which should account for this
variance.

Jay, will you be able to pull the source code from SVN or do you want
me to make a snapshot?

Thanks,
Boris

--
Boris Kolpackov, Code Synthesis Tools
Open source XML data binding for C++:   http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to