public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] elf: Use a temporary file to generate Makefile fragments [BZ #28550]
Date: Wed, 17 Nov 2021 14:49:45 +0100	[thread overview]
Message-ID: <87zgq26gee.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20211116131418.2070092-1-hjl.tools@gmail.com> (H. J. Lu via Libc-alpha's message of "Tue, 16 Nov 2021 05:14:18 -0800")

I still see

  /builddir/build/BUILD/glibc-2.34.9000-294-ga43c0b5483/build-x86_64-redhat-linux/elf/dso-sort-tests-2.def.generated-makefile:1067: warning: overriding recipe for target '/builddir/build/BUILD/glibc-2.34.9000-294-ga43c0b5483/build-x86_64-redhat-linux/elf/tst-redhat-1162810-dir/tst-redhat-1162810-M22X17.os'

and eventually a build failure:

  make[2]: Leaving directory '/builddir/build/BUILD/glibc-2.34.9000-294-ga43c0b5483/elf'
  make[1]: *** [Makefile:483: elf/tests] Error 2
  make: *** [Makefile:9: check] Error 2

There's no error before that, or other message indicating which make
target is failing.

The full build log is here:

  <https://koji.fedoraproject.org/koji/taskinfo?taskID=78987342>
  <https://kojipkgs.fedoraproject.org//work/tasks/7342/78987342/build.log>

The make error messages are not very helpful to me though.

Thanks,
Florian


  parent reply	other threads:[~2021-11-17 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 13:14 H.J. Lu
2021-11-16 13:16 ` Adhemerval Zanella
2021-11-17 13:49 ` Florian Weimer [this message]
2021-11-17 13:56   ` H.J. Lu
2021-11-17 15:29     ` Florian Weimer
2021-11-17 15:39       ` H.J. Lu
2021-11-17 15:52         ` Florian Weimer
2021-11-17 16:02           ` H.J. Lu
2021-11-17 16:41             ` Florian Weimer

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=87zgq26gee.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@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).