[Bug gprofng/29113] Build error for x86_64-w64-mingw32 host since CLOCK_MONOTONIC does not exist

2022-05-03 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29113

--- Comment #3 from cqwrteur  ---
(In reply to Vladimir Mezentsev from comment #2)
>  How do you configure your build ?
> 
> gprofng should not be built for x86_64-w64-mingw32.
> Only these platforms are supported:
> 
> % cat gprofng/configure.ac
> ...
>   case "${target}" in
> x86_64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
> i?86-*-linux*)
>   build_collector=true
>   build_collector=true
>   ;;
> aarch64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
>   esac

I do Canadian compilation for building cross back compiler. (Aka, the compiler
is built on linux, hosted on windows, and targeting windows)

Here the bug is that if target is linux but host is windows, your configure
script would still build collector.

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


[Bug gprofng/29113] Build error for x86_64-w64-mingw32 host since CLOCK_MONOTONIC does not exist

2022-05-03 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29113

--- Comment #4 from cqwrteur  ---
(In reply to Vladimir Mezentsev from comment #2)
>  How do you configure your build ?
> 
> gprofng should not be built for x86_64-w64-mingw32.
> Only these platforms are supported:
> 
> % cat gprofng/configure.ac
> ...
>   case "${target}" in
> x86_64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
> i?86-*-linux*)
>   build_collector=true
>   build_collector=true
>   ;;
> aarch64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
>   esac

the compiler runs on WINDOWS. but the compiled program runs on linux.

The build process is again on linux. It is a crossback Canadian toolchain.

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


[Bug gprofng/29113] Build error for x86_64-w64-mingw32 host since CLOCK_MONOTONIC does not exist

2022-05-03 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29113

--- Comment #5 from cqwrteur  ---
(In reply to Vladimir Mezentsev from comment #2)
>  How do you configure your build ?
> 
> gprofng should not be built for x86_64-w64-mingw32.
> Only these platforms are supported:
> 
> % cat gprofng/configure.ac
> ...
>   case "${target}" in
> x86_64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
> i?86-*-linux*)
>   build_collector=true
>   build_collector=true
>   ;;
> aarch64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
>   esac

case "${target}" in
is clearly wrong. It should be ${host}, not ${target}

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


[Bug ld/29101] [Bug] User input is not sanitized in libdep_plugin.c and cause trouble on 32bit machine

2022-05-03 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=29101

--- Comment #1 from cvs-commit at gcc dot gnu.org  ---
The master branch has been updated by Nick Clifton :

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=46465574a925062ba7dfa72f49ba5199d7a39fc3

commit 46465574a925062ba7dfa72f49ba5199d7a39fc3
Author: Nick Clifton 
Date:   Tue May 3 11:40:41 2022 +0100

Fix potential arithmetic overflow in the linker's plugin handling code.

PR 29101
* libdep_plugin.c (get_libdeps): Check for overflow when computing
amount of memory to allocate.

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


[Bug ld/29101] [Bug] User input is not sanitized in libdep_plugin.c and cause trouble on 32bit machine

2022-05-03 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29101

Nick Clifton  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Nick Clifton  ---
I have applied a small patch to fix this problem.

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #7 from H.J. Lu  ---
Were you building x86-64 binutils on i686 Linux?

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


[Bug gprofng/29116] New: gprofng fails to build on i686-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

Bug ID: 29116
   Summary: gprofng fails to build on i686-linux-gnu
   Product: binutils
   Version: 2.39 (HEAD)
Status: NEW
  Severity: normal
  Priority: P2
 Component: gprofng
  Assignee: vladimir.mezentsev at oracle dot com
  Reporter: doko at debian dot org
  Target Milestone: ---

gprofng fails to build on i686-linux-gnu, trunk 20220503:

libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/synctrace.o   
-Wl,--version-script -W
l,../../../gprofng/libcollector/mapfile.intel-Linux -Wl,--no-as-needed -Wl,-lrt
-Wl,-ldl -Wl,-z -Wl,re
lro   -Wl,-soname -Wl,libgp-sync.so -o .libs/libgp-sync.so
/usr/bin/ld: .libs/libgp-sync.so: version node not found for symbol
pthread_cond_wait@GLIBC_2.2.5
/usr/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status
make[6]: *** [Makefile:580: libgp-sync.la] Error 1

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

Matthias Klose  changed:

   What|Removed |Added

 Target|i686-inux-gnu   |i686-inux-gnu
   ||aarch64-linux-gnu
Summary|gprofng fails to build on   |gprofng fails to build on
   |i686-linux-gnu  |i686-linux-gnu,
   ||aarch64-linux-gnu

--- Comment #5 from Matthias Klose  ---
also aarch64-linux-gnu:

libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/synctrace.o   
-Wl,--version-script -W
l,../../../gprofng/libcollector/mapfile.aarch64-Linux -Wl,--no-as-needed
-Wl,-lrt -Wl,-ldl -Wl,-z -Wl,
relro   -Wl,-soname -Wl,libgp-sync.so -o .libs/libgp-sync.so
/usr/bin/ld: .libs/libgp-sync.so: version node not found for symbol
pthread_cond_wait@@GLIBC_2.3.2
/usr/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status
make[6]: *** [Makefile:580: libgp-sync.la] Error 1

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #9 from H.J. Lu  ---
gprofng/libcollector/synctrace.c is written for target.  But synctrace.o
is linked against the host library.  It failed to link when host != target.

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

Matthias Klose  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|WAITING |UNCONFIRMED

--- Comment #3 from Matthias Klose  ---
glibc 2.35

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu

2022-05-03 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #4 from H.J. Lu  ---
It looks like WSIZE(64) is 1 for i686-linux-gnu.  Please show the output of

# echo __x86_64 | x86_64-linux-gnu-gcc -E -
# echo __x86_64 | x86_64-linux-gnu-gcc -m32 -E -

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #6 from Matthias Klose  ---
sorry, this is glibc 2.33, not 2.35.

$ echo __x86_64 | x86_64-linux-gnu-gcc -E -
# 0 ""
# 0 ""
# 0 ""
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 0 "" 2
# 1 ""
1
$ echo __x86_64 | x86_64-linux-gnu-gcc -m32 -E -
# 0 ""
# 0 ""
# 0 ""
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 0 "" 2
# 1 ""
__x86_64

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

Matthias Klose  changed:

   What|Removed |Added

 Target||i686-inux-gnu
 CC||hjl.tools at gmail dot com

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu

2022-05-03 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

H.J. Lu  changed:

   What|Removed |Added

 Status|NEW |WAITING

--- Comment #1 from H.J. Lu  ---
Which version of glibc was used?

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu

2022-05-03 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #2 from H.J. Lu  ---
i686 glibc should reference pthread_cond_wait@@GLIBC_2.3.2, not
pthread_cond_wait@GLIBC_2.2.5.

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #8 from Matthias Klose  ---
no, everything on x86_64-linux-gnu so far, the i686 and aarch64 builds are
configured for these targets.

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


[Bug gprofng/29113] Build error for x86_64-w64-mingw32 host since CLOCK_MONOTONIC does not exist

2022-05-03 Thread hp at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29113

--- Comment #6 from Hans-Peter Nilsson  ---
(In reply to Vladimir Mezentsev from comment #2)
>  How do you configure your build ?
> 
> gprofng should not be built for x86_64-w64-mingw32.
> Only these platforms are supported:
> 
> % cat gprofng/configure.ac
> ...
>   case "${target}" in
> x86_64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
> i?86-*-linux*)
>   build_collector=true
>   build_collector=true
>   ;;
> aarch64-*-linux*)
>   build_src=true
>   build_collector=true
>   ;;
>   esac

Surely unrelated, but what's the effect of the apparent typo in the
"i?86-*-linux*)" case?

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


[Bug gprofng/29116] gprofng fails to build on i686-linux-gnu, aarch64-linux-gnu

2022-05-03 Thread vladimir.mezentsev at oracle dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29116

--- Comment #10 from Vladimir Mezentsev  
---
How do you configure your build ?

It looks like there are two bugs here:
1. libgp-sync.so may not link with libc.
 In run time, libgp-sync.so has to dlopen libc and use dlsym to find
pthread_cond_wait.

2. it is probably a bug 29113 - Build error for x86_64-w64-mingw32 host since
CLOCK_MONOTONIC does not exist

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