From: sotrdg sotrdg <euloanty@live.com>
To: DJ Delorie <dj@redhat.com>,
sotrdg sotrdg via Libc-alpha <libc-alpha@sourceware.org>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: RE: FW: several glibc build bugs on MinGW-w64
Date: Sat, 17 Oct 2020 10:46:27 +0000 [thread overview]
Message-ID: <CH2PR02MB6522C4E2C4AF19DD40018159B2000@CH2PR02MB6522.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CH2PR02MB65223773124B1A8FCDBF920DB2000@CH2PR02MB6522.namprd02.prod.outlook.com>
I have found out the issue by replacing all D:/msys64/ to just /
The issue is that D:/msys64 generated from the map files are incorrect that does not match regex. It requires some patches
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: sotrdg sotrdg<mailto:euloanty@live.com>
Sent: Saturday, October 17, 2020 06:31
To: DJ Delorie<mailto:dj@redhat.com>; sotrdg sotrdg via Libc-alpha<mailto:libc-alpha@sourceware.org>; libc-help@sourceware.org<mailto:libc-help@sourceware.org>
Subject: RE: FW: several glibc build bugs on MinGW-w64
$ LC_ALL=C \
> sed -n 's@^[0-9a-f ]*/build-glibc/\([^(]*\)(\([^)]*\.os\)) *.*$@\1 \2@p' \
> /build-glibc/elf/librtld.map | \
> while read lib file; do \
> case $lib in \
> libc_pic.a) \
> LC_ALL=C fgrep -l /$file \
> /build-glibc/stamp.os /build-glibc/*/stamp.os | \
> LC_ALL=C \
> sed 's@^/build-glibc/\([^/]*\)/stamp\.os$@rtld-\1'" +=$file@"\
> ;; \
> */*.a) \
> echo rtld-${lib%%/*} += $file ;; \
> *) echo "Wasn't expecting $lib($file)" >&2; exit 1 ;; \
> esac; \
> done > /build-glibc/elf/librtld.mkT
It looks like the problem here is because the script generates null file from this librtld.map. Anyone knows how to deal with the issue here?
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: DJ Delorie<mailto:dj@redhat.com>
Sent: Friday, October 16, 2020 21:40
To: sotrdg sotrdg<mailto:euloanty@live.com>
Subject: Re: FW: several glibc build bugs on MinGW-w64
Sorry, I have no idea.
next prev parent reply other threads:[~2020-10-17 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH2PR02MB652261928A76F3257DE01D20B2000@CH2PR02MB6522.namprd02.prod.outlook.com>
[not found] ` <xnmu0l1vg8.fsf@greed.delorie.com>
2020-10-17 10:31 ` sotrdg sotrdg
2020-10-17 10:46 ` sotrdg sotrdg [this message]
2020-10-17 10:50 ` sotrdg sotrdg
2020-10-13 16:32 sotrdg sotrdg
2020-10-13 16:43 ` FW: " sotrdg sotrdg
2020-10-13 20:53 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CH2PR02MB6522C4E2C4AF19DD40018159B2000@CH2PR02MB6522.namprd02.prod.outlook.com \
--to=euloanty@live.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).