Thursday, December 05, 2019

Re: Fails to build textproc/mupdf on mips64el/loongson

On 2019-12-05 6:00 PM, Brian Callahan wrote:
>
>
> On 2019-12-05 5:55 PM, Stuart Henderson wrote:
>> On 2019/12/04 16:35, Xiyue Deng wrote:
>>>>     # https://marc.info/?l=openbsd-ports&m=156448467232400&w=2
>>>>   # possible alignment issue?
>>>> -MODULES +=    gcc4
>>>> +MODULES +=    gcc4 lang/clang
>>>>   MODGCC4_ARCHS =    armv7
>>>>   MODGCC4_LANGS =    c
>>>> +MODCLANG_ARCHS = mips64 mips64el
>>>> +MODCLANG_LANGS = c
>>> Thanks for the updated patch.  It's definitely clearner this way.
>>>
>>> As it's now using clang from ports, it needs to build lang/clang first
>>> which may take a few days on this loongson box.  Will report back as
>>> soon as it's finished.
>> hmm, actually can you skip the MODULES/MODCLANG_* change above and see
>> if it works with base-gcc? I doubt it needs to build with a different
>> compiler, just use the different linker..
>
> base-gcc doesn't support the -fuse-ld= option. What you're suggesting
> was already tried and unfortunately didn't work.
>

That is to say, it will link the font files with lld but link the code
and font files together with bfd; the combination didn't work :(

~Brian

> ~Brian
>
>>> Just curious: Is it OK to just whitelist /usr/bin/clang?
>> I think that would really be a last resort, we try to avoid it in ports.
>>
>>> Also is there
>>> a plan to add mips64* to base-clang archs?
>> "when it's ready" :)
>>
>

No comments:

Post a Comment