public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: overseers@sourceware.org
Subject: Spurious bz "inappropriate content" rejection and now my bz account is locked
Date: Tue, 02 Feb 2021 16:14:53 +0000	[thread overview]
Message-ID: <87sg6eigzm.fsf@esperi.org.uk> (raw)

So I just tried to submit a bug report with this content against
gdbserver:

> Subject: gdbserver fails to build with --with-included-gettext

> (Caveat: not currently reproducible on platforms with Bison 3.0+
> because missing patches in binutils intl/ cause the build to fail
> earlier: will be submitting patches to fix that later today.)
> 
> Building gdbserver with --with-included-libintl fails. Log below,
> trimmed down drastically because including the whole log gets rejected
> as "inappropriate content":
> 
> g++  -shared -fPIC -Wl,--soname=libinproctrace.so \
> 	-Wl,--no-undefined    -I. -I../../gdbserver -I../../gdbserver/../gdb/regformats -I../../gdbserver/.. -I../../gdbserver/../include -I../../gdbserver/../gdb -I../../gdbserver/../gnulib/import -I../gnulib/import -I../../gdbserver/.. -I.. -I./../intl  -pthread -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-variable -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-error=maybe-uninitialized -Wno-mismatched-tags -Wsuggest-override -Wimplicit-fallthrough=3 -Wduplicated-cond -Wshadow=local -Wdeprecated-copy -Wdeprecated-copy-dtor -Wredundant-move -Wmissing-declarations -Wstrict-null-sentinel -Wformat -Wformat-nonliteral -Werror -DGDBSERVER  -Wl,--dynamic-list=../../gdbserver/proc-service.list \
> 	 -g -O2     \
> 	-o libinproctrace.so alloc-ipa.o ax-ipa.o gdbsupport/common-utils-ipa.o gdbsupport/errors-ipa.o gdbsupport/format-ipa.o gdbsupport/print-utils-ipa.o gdbsupport/rsp-low-ipa.o gdbsupport/safe-strerror-ipa.o gdbsupport/tdesc-ipa.o regcache-ipa.o remote-utils-ipa.o tdesc-ipa.o tracepoint-ipa.o utils-ipa.o linux-amd64-ipa.o linux-x86-tdesc-ipa.o arch/amd64-ipa.o   ../libiberty/libiberty.a -ldl -pthread
> /usr/local/lib/gcc/x86_64-pc-linux-gnu/11.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ax-ipa.o: in function `ax_printf(unsigned long, unsigned long, char const*, int, unsigned long*) [clone .constprop.0]':
> /home/oranix/oracle/private/binutils-gdb/x86_64-loom/gdbserver/../../gdbserver/ax.cc:928: undefined reference to `libintl_gettext'
> [...]
> make[2]: *** [Makefile:404: libinproctrace.so] Error 1
> make[2]: Leaving directory '/home/oranix/oracle/private/binutils-gdb/x86_64-loom/gdbserver'
> make[1]: *** [Makefile:11345: all-gdbserver] Error 2
> make[1]: Leaving directory '/home/oranix/oracle/private/binutils-gdb/x86_64-loom'
> 
> The cause is that libinproctrace.so calls gettext, but does not pull
> in $(LIBINTL). The tricky part is that it *cannot*, because intl/
> isn't built with PIC, so presumably intl/ would need adjusting to
> generate a PIC version of itself, like libiberty, before this could be
> fixed. (And probably the change would need trickling down from
> gettext, via GCC, to binutils.)

A longer (untrimmed) version was rejected due to "inappropriate
content". Trying to add this version instead asked me to log into bz
(even though I was already logged in), then auto-locked my account "due
to spam".

Please can you unlock it, and if possible figure out what is causing
this false positive rejection and fix it?

Thanks!

(I'm no longer surprised this bug hasn't been fixed in a while: nobody
can report it :P of course that bug text is already incorrect because
I've now *done* the stuff I said was too hard to do. I still need to
report it, though, because it's user-visible, which is hard if reporting
it locks my account...)

             reply	other threads:[~2021-02-02 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 16:14 Nick Alcock [this message]
2021-02-19 16:59 ` Nick Alcock
2021-02-19 17:04   ` Frank Ch. Eigler

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=87sg6eigzm.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=overseers@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).