public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug build/28742] New: how to use the x86_64-linux-gnu compiler ?
@ 2022-01-03 14:28 zimmerma+gcc at loria dot fr
  2022-01-03 14:49 ` [Bug build/28742] " schwab@linux-m68k.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: zimmerma+gcc at loria dot fr @ 2022-01-03 14:28 UTC (permalink / raw)
  To: glibc-bugs

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

            Bug ID: 28742
           Summary: how to use the x86_64-linux-gnu compiler ?
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: zimmerma+gcc at loria dot fr
                CC: carlos at redhat dot com
  Target Milestone: ---

thanks to the help of H.J., I was able to build a x86_64-linux-gnu compiler
with build-many-glibcs.py.

Now I want to use that compiler to check the accuracy of the recent libmvec
patches. For this I need to link with MPFR, GMP and libmvec. How to proceed?

So far with the following compilation line:

/localdisk/zimmerma/glibc-many/install/compilers/x86_64-linux-gnu/bin/x86_64-gl\
ibc-linux-gnu-gcc
-I/localdisk/zimmerma/glibc-many/install/host-libraries/inclu\
de -L/localdisk/zimmerma/glibc-many/install/host-libraries/lib -DWITHOUT_OMP
-D\
LIBMVEC -Ofast -DSTR=$f check_exhaustive.c -mavx2 -lm -lmpfr -lgmp -o
/tmp/chec\
k_${f}f

I get:

/tmp/check_acosf: /lib/x86_64-linux-gnu/libmvec.so.1: version `GLIBC_2.35' not
\
found (required by /tmp/check_acosf)
/tmp/check_acosf: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not
fou\
nd (required by /tmp/check_acosf)

When builing glibc there is a testrun.sh wrapper script to use it, is there a
similar wrapper script when using a compiler build from build-many-glibcs.py,
and how to use it?

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug build/28742] how to use the x86_64-linux-gnu compiler ?
  2022-01-03 14:28 [Bug build/28742] New: how to use the x86_64-linux-gnu compiler ? zimmerma+gcc at loria dot fr
@ 2022-01-03 14:49 ` schwab@linux-m68k.org
  2022-01-03 15:55 ` hjl.tools at gmail dot com
  2022-01-03 15:59 ` zimmerma+gcc at loria dot fr
  2 siblings, 0 replies; 4+ messages in thread
From: schwab@linux-m68k.org @ 2022-01-03 14:49 UTC (permalink / raw)
  To: glibc-bugs

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

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
You need to run /tmp/check_acosf with the testrun.sh wrapper.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug build/28742] how to use the x86_64-linux-gnu compiler ?
  2022-01-03 14:28 [Bug build/28742] New: how to use the x86_64-linux-gnu compiler ? zimmerma+gcc at loria dot fr
  2022-01-03 14:49 ` [Bug build/28742] " schwab@linux-m68k.org
@ 2022-01-03 15:55 ` hjl.tools at gmail dot com
  2022-01-03 15:59 ` zimmerma+gcc at loria dot fr
  2 siblings, 0 replies; 4+ messages in thread
From: hjl.tools at gmail dot com @ 2022-01-03 15:55 UTC (permalink / raw)
  To: glibc-bugs

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unspecified                 |2.35
           Assignee|unassigned at sourceware dot org   |skpgkp2 at gmail dot com
                 CC|                            |hjl.tools at gmail dot com

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Sunil, can create a script which generates a script for
a native compiler built by build-many-glibcs.py to run
binaries with glibc from the native compiler?  The native
compiler is under:

$ ls install/compilers/x86_64-linux-gnu/bin/
x86_64-glibc-linux-gnu-addr2line   x86_64-glibc-linux-gnu-gcov-dump
x86_64-glibc-linux-gnu-ar          x86_64-glibc-linux-gnu-gcov-tool
x86_64-glibc-linux-gnu-as          x86_64-glibc-linux-gnu-gprof
x86_64-glibc-linux-gnu-c++         x86_64-glibc-linux-gnu-ld
x86_64-glibc-linux-gnu-c++filt     x86_64-glibc-linux-gnu-ld.bfd
x86_64-glibc-linux-gnu-cpp         x86_64-glibc-linux-gnu-lto-dump
x86_64-glibc-linux-gnu-elfedit     x86_64-glibc-linux-gnu-nm
x86_64-glibc-linux-gnu-g++         x86_64-glibc-linux-gnu-objcopy
x86_64-glibc-linux-gnu-gcc         x86_64-glibc-linux-gnu-objdump
x86_64-glibc-linux-gnu-gcc-11.2.1  x86_64-glibc-linux-gnu-ranlib
x86_64-glibc-linux-gnu-gcc-ar      x86_64-glibc-linux-gnu-readelf
x86_64-glibc-linux-gnu-gcc-nm      x86_64-glibc-linux-gnu-size
x86_64-glibc-linux-gnu-gcc-ranlib  x86_64-glibc-linux-gnu-strings
x86_64-glibc-linux-gnu-gcov        x86_64-glibc-linux-gnu-strip

Its glibc is under:

$ ls install/compilers/x86_64-linux-gnu/sysroot/
etc  lib  lib64  libx32  sbin  usr  var
$

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug build/28742] how to use the x86_64-linux-gnu compiler ?
  2022-01-03 14:28 [Bug build/28742] New: how to use the x86_64-linux-gnu compiler ? zimmerma+gcc at loria dot fr
  2022-01-03 14:49 ` [Bug build/28742] " schwab@linux-m68k.org
  2022-01-03 15:55 ` hjl.tools at gmail dot com
@ 2022-01-03 15:59 ` zimmerma+gcc at loria dot fr
  2 siblings, 0 replies; 4+ messages in thread
From: zimmerma+gcc at loria dot fr @ 2022-01-03 15:59 UTC (permalink / raw)
  To: glibc-bugs

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

Paul Zimmermann <zimmerma+gcc at loria dot fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #3 from Paul Zimmermann <zimmerma+gcc at loria dot fr> ---
thank you, Andreas' solution works (taking the testrun.sh script after doing
"make" in the GLIBC master branch). We can thus close the bug.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-01-03 15:59 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-03 14:28 [Bug build/28742] New: how to use the x86_64-linux-gnu compiler ? zimmerma+gcc at loria dot fr
2022-01-03 14:49 ` [Bug build/28742] " schwab@linux-m68k.org
2022-01-03 15:55 ` hjl.tools at gmail dot com
2022-01-03 15:59 ` zimmerma+gcc at loria dot fr

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).