[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #64725] Inconsistent behavior of mkoctifile wh
From: |
Rafael Laboissière |
Subject: |
[Octave-bug-tracker] [bug #64725] Inconsistent behavior of mkoctifile when a compiler -f* option is used |
Date: |
Thu, 28 Sep 2023 10:11:31 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?64725>
Summary: Inconsistent behavior of mkoctifile when a compiler
-f* option is used
Group: GNU Octave
Submitter: rlaboiss
Submitted: Thu 28 Sep 2023 02:11:29 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 28 Sep 2023 02:11:29 PM UTC By: Rafael Laboissière <rlaboiss>
If mkoctifile is called like this:
mkoctfile a.cc b.o
then file a.oct is created, as expected.
However, when adding a compiler option like this:
mkoctfile -fcf-protection a.cc b.o
file b.oct is created, unexpectedly.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64725>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #64725] Inconsistent behavior of mkoctifile when a compiler -f* option is used,
Rafael Laboissière <=