harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5871) Cannot build 32bit C libraries on X86_64 Linux host
Date Sat, 14 Jun 2008 14:51:45 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605078#action_12605078

Mark Hindess commented on HARMONY-5871:

Ah fixing depends.xml would work for you but I think you only actually get to that bit of
the ant file if is.x86_64 is true.  It wouldn't work for everyone even if we fixed that[0].
 Debian really doesn't support multi-arch stuff in the same way so /usr/lib64 is just a symlink
to /usr/lib and only has a 32-bit liblcms.so in /emul/ia32-linux/usr/lib/liblcms.so.

[0] Im not really sure how we ended up using static liblcms on x86 and dynamic on x86_64 -
there was an issue with x86_64 using static but I think we should have changed both to use
liblcms dynamically rather than make it more complicated especially given that the interface
for lcms is fairly stable.  I'll try to get this fixed but it will involve some discussion
on the mailing list.

> Cannot build 32bit C libraries on X86_64 Linux host
> ---------------------------------------------------
>                 Key: HARMONY-5871
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5871
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>    Affects Versions: 5.0M6
>         Environment: x86_64 GNU/Linux
>            Reporter: Ian Rogers
>            Assignee: Mark Hindess
>         Attachments: build.out, build.out2
> I would like to build a 32bit version of Harmony on a x86_64 linux system for a VM with
incomplete x86_64 support. Setting the CFLAGS and CXXFLAGS to define -m32 causes a failure
during linking the C libraries (not all the components have picked up the CFLAGS). Running
the build under linux32 is also unsuccessful.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message