-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"brix11 make" does not set the exit code after build errors #155
Comments
ClausKlein
changed the title
"brirx11 make" does not set the exit code after build errors
"brix11 make" does not set the exit code after build errors
Oct 12, 2023
We fixed #43 years ago, maybe there is another issue in that area |
bash-5.2$ /usr/local/Cellar/ruby/3.2.2_1/bin/ruby bin/brix11 make
# ...
ERROR: (g++) file: ../../../tao/x11/ifr_client/IFR_BasicC.h line: 2155 - non-constexpr declaration of 'make_reference' follows constexpr declaration
friend TAOX11_CORBA::object_reference<_Tp1> TAOX11_CORBA::make_reference(Args&& ...args);
^
INFO: (g++) file: ../../../tao/x11/object_traits_t.h line: 242 - previous declaration is here
ERROR: (make) - [.shobj/IFR_ExtendedS.o] Error 1
ERROR: (make) - Waiting for unfinished jobs....
ERROR: (make) - [.shobj/IFR_BasicS.o] Error 1
ERROR: (make) - [.shobj/IFR_ComponentsS.o] Error 1
ERROR: (make) - [.shobj/IFR_BaseS.o] Error 1
bash-5.2$ echo $?
0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Product
TAOX11
Version
Your TAOX11 version
master
Describe the bug
After an error,
brix11 make
should NOT continue and set an exit error codeTo Reproduce
Parts of my
makefile.mk
Expected behavior
Like make, stop and set exit code != 0
Output
Any output (shell/compiler) that is given. When it is a runtime bug please set
X11_LOG_MASK=all
and attach the runtime output as attachmentEnvironment:
Output of
ruby -v && bin/brix11 env && bin/brix11 -- configure --print-config
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: