public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xer8686 at mail dot ru" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27997] New: I get an error when building glibc 2.33.
Date: Sat, 19 Jun 2021 20:56:02 +0000	[thread overview]
Message-ID: <bug-27997-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27997

            Bug ID: 27997
           Summary: I get an error when building glibc 2.33.
           Product: glibc
           Version: 2.33
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: xer8686 at mail dot ru
                CC: carlos at redhat dot com
  Target Milestone: ---

Created attachment 13504
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13504&action=edit
build logs

I.. -I../libio -I. -nostdinc -isystem
/usr/lib64/gcc/x86_64-openmandriva-linux-gnu/11.1.0/include -isystem
/usr/include -D_LIBC_REENTRANT -include
/builddir/build/BUILD/glibc-2.33/build-i686-linux/libc-modules.h
-DMODULE_NAME=libc -include ../include/libc-symbols.h      
-DTOP_NAMESPACE=glibc -o
/builddir/build/BUILD/glibc-2.33/build-i686-linux/misc/select.o -MD -MP -MF
/builddir/build/BUILD/glibc-2.33/build-i686-linux/misc/select.o.dt -MT
/builddir/build/BUILD/glibc-2.33/build-i686-linux/misc/select.o
../sysdeps/unix/sysv/linux/select.c: In function '__select64':
../sysdeps/unix/sysv/linux/select.c:92:1: error: bp cannot be used in 'asm'
here
   92 | }
      | ^
make[2]: *** [/builddir/build/BUILD/glibc-2.33/build-i686-linux/sysd-rules:213:
/builddir/build/BUILD/glibc-2.33/build-i686-linux/misc/select.o] Error 1
make[2]: Leaving directory '/builddir/build/BUILD/glibc-2.33/misc'
make[1]: *** [Makefile:479: misc/subdir_lib] Error 2
make[1]: Leaving directory '/builddir/build/BUILD/glibc-2.33'
make: *** [Makefile:9: all] Error 2

gcc version 11.1.0

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-06-19 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 20:56 xer8686 at mail dot ru [this message]
2021-06-19 21:04 ` [Bug build/27997] " xer8686 at mail dot ru
2021-06-22  4:08 ` adhemerval.zanella at linaro dot org
2021-06-22 10:30 ` fweimer at redhat dot com
2021-06-22 12:19 ` adhemerval.zanella at linaro dot org
2021-06-22 13:51 ` adhemerval.zanella at linaro dot org
2021-06-22 14:32 ` xer8686 at mail dot ru
2021-06-22 14:34 ` fweimer at redhat dot com
2021-06-22 14:44 ` xer8686 at mail dot ru
2021-06-22 14:59 ` adhemerval.zanella at linaro dot org
2021-06-22 15:07 ` xer8686 at mail dot ru
2021-08-15 20:50 ` xer8686 at mail dot ru
2021-08-19 12:17 ` adhemerval.zanella at linaro dot org
2022-01-10 16:23 ` [Bug libc/27997] i386: CAN_USE_REGISTER_ASM_EBP is unreliable fweimer at redhat dot com
2022-01-10 16:25 ` fweimer at redhat dot com
2022-01-13 14:23 ` fweimer at redhat dot com

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=bug-27997-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).