[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Make command failing

From: Kaz Kylheku
Subject: Re: Make command failing
Date: Thu, 31 Mar 2022 14:41:14 -0700
User-agent: Roundcube Webmail/1.4.13

On 2022-03-31 09:05, Justin White wrote:
Good Morning Everyone.

I am trying to follow this page

This repo has 29 commits, the most recent being almost a year old.
Maybe it's just broken. One of the commits is about fixing errors for GCC 7.5. Maybe there are more errors under newer GCC, not yet fixed.

In general if you're trying someone's public git repository, try to
see if it has a release process: has the project tagged any base
line as a release? If so, build that. Otherwise you could be trying
to build this morning's breakaage.

Not all projects have a good process for catching build breakages
before they are committed.

Not all build instructions tell you how to look for a stable
baseline, if you're a newcomer to the project who just wants
something that works.

[  2%] Building CXX object
In static member function ‘*static gr::lora_sdr::add_crc::sptr
*error: *could not convert ‘*gnuradio::get_initial_sptr(T*) [with T =
[ ... ]

I tried to search the archive first, but did not come across this. I
apologize ahead of time if I missed it.

Unfortunately, a C++ conversion error /per se/ is not really in
the scope of the GNU Make mailing list, unless it's the result
of Make doing something wrong in the way it dispatches the
compiler command.

E.g. suppose that the Makefile contained a command like

   $(CXX) $(CXXFLAGS) -Dimportant_macro=foo  ...

and somehow Make was accidentally eating the
-Dimportant_macro=foo definition before invoking the
compiler command. If that were the root
cause of the C++ compilation problem; then that would be a Make
issue. Not the specific C++ error itself, but the fact of not
invoking the compiler right.

Your best bet here is to contact the repo owner and report that their
build instructions don't work for their latest commit, on Ubuntu 20.
(And are they still interested in maintaining that code in working order, if not with new development.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]