[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: [RFC] dietlibc port to ppc64el


(could you please remember to Cc me? I'm reading your emails via
the list archive web interface ;-))

> On 04/04/2016 07:57 PM, Christian Seiler wrote:
>> Yeah, so CC='klcc' means that this mksh was built against klibc instead
>> of dietlibc. CC='diet gcc' or CC='diet cc' would indicate dietlibc...
>> So you just verified that mksh with klibc works. :-)
> Silly me.  When I tried to but using diet, I got the following error:
> diet cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -Wno-deprecated-declarations -fno-asynchronous-unwind-tables -fno-strict-aliasing -fstack-protector-strong -fwrapv -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o mksh  lalloc.o eval.o exec.o expr.o funcs.o histrap.o jobs.o lex.o main.o misc.o shf.o syn.o tree.o var.o edit.o  || for _f in ${tcfn}*; do case $_f in Build.sh|check.pl|check.t|dot.mkshrc|*.1|*.c|*.h|*.ico|*.opt) ;; *) rm -f "$_f" ;; esac; done
> /usr/lib/diet/lib-ppc64le/libc.a(setjmp.o): In function `__sigsetjmp':
> (.text+0xa8): undefined reference to `.__sigjmp_save'
> collect2: error: ld returned 1 exit status
> Do you know this problem? Is it related to something like:
> https://github.com/ensc/dietlibc/blob/87a59f2e6dc11d9f5b82c9d6eff09aae2daa1bbb/ppc64/setjmp.S#L3-L7

I believe I have fixed that recently independently of your report (not
tested though), just do a git pull and try again, see the other email
I just sent.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: