[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #64590] Wrong behavior of mkoctfile when optio
From: |
Rafael Laboissière |
Subject: |
[Octave-bug-tracker] [bug #64590] Wrong behavior of mkoctfile when option -fdebug-prefix-map is present |
Date: |
Thu, 24 Aug 2023 09:36:57 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?64590>
Summary: Wrong behavior of mkoctfile when option
-fdebug-prefix-map is present
Group: GNU Octave
Submitter: rlaboiss
Submitted: Thu 24 Aug 2023 01:36:55 PM UTC
Category: Other
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Unexpected Error or Warning
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Release: 8.3.0
Discussion Lock: Any
Operating System: GNU/Linux
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Thu 24 Aug 2023 01:36:55 PM UTC By: Rafael Laboissière <rlaboiss>
I came across an issue with mkoctfile, which can be exercised with the
Makefile attached to this message. When copying it to an empty directory and
running "make", it produces the output below.
touch b.cc
touch a.cc
mkoctfile --verbose -c a.cc
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/octave-8.3.0/octave/.. -I/usr/include/octave-8.3.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-8.3.0=. -flto=aut
o -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
a.cc -o a.o
===== FINE
mkoctfile --verbose b.cc a.o
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/octave-8.3.0/octave/.. -I/usr/include/octave-8.3.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-8.3.0=. -flto=aut
o -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
b.cc -o /var/tmp/oct-8sYg58.o
g++ -I/usr/include/octave-8.3.0/octave/.. -I/usr/include/octave-8.3.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-8.3.0=. -flto=auto
-ffat-lto-objects -fstack-protector-str
ong -Wformat -Werror=format-security -o b.oct a.o /var/tmp/oct-8sYg58.o
-shared -Wl,-Bsymbolic -L/usr/lib/x86_64-linux-gnu -shared -Wl,-Bsymbolic
-L/usr/lib/x86_64-linux-gnu -shared -Wl,-Bsymbolic -flto=a
uto -ffat-lto-objects -Wl,-z,relro
===== FAIL
mkoctfile --verbose -fdebug-prefix-map=.=. b.cc a.o
g++ -I/usr/include/octave-8.3.0/octave/.. -I/usr/include/octave-8.3.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-8.3.0=. -flto=auto
-ffat-lto-objects -fstack-protector-str
ong -Wformat -Werror=format-security -fdebug-prefix-map=.=. b.cc -o a.oct
a.o -shared -Wl,-Bsymbolic -L/usr/lib/x86_64-linux-gnu -shared
-Wl,-Bsymbolic -L/usr/lib/x86_64-linux-gnu -shared -Wl,-Bsymbolic -
flto=auto -ffat-lto-objects -Wl,-z,relro
rm a.cc
This Makefile has two targets "fine" and "fail", whose difference is only the
presence (or absence) of option -fdebug-prefix-map when invoking mkoctfile. In
both cases, the output file produced by mkoctfile should be b.oct. This is
indeed the case for the "fine" target. However, for the "fail" target, file
a.oct is built.
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Thu 24 Aug 2023 01:36:55 PM UTC Name: Makefile Size: 293B By:
rlaboiss
<http://savannah.gnu.org/bugs/download.php?file_id=55072>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64590>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #64590] Wrong behavior of mkoctfile when option -fdebug-prefix-map is present,
Rafael Laboissière <=