Marcus you did not man. It's all good your always here for all of us all
the time, when we need stuff.

On Sun, Jul 21, 2019, 12:32 PM Müller, Marcus (CEL) <muel...@kit.edu> wrote:

> Hello Andi,
>
> I didn't mean to offend you!
> I just read
>
> > While intrin.h header file is founded in clang also downloadable from
> GitHub.
>
> as instruction to look for it in an out-of-distribution source; I
> would've interpreted it that way, and presumed a lesser experienced
> reader would've done the same. And so, I felt compelled to clarify
> that's not the way to go.
>
> Again, these files are unrelated to the CMake failure! VOLK's CMake
> checks for their existence, and them missing is an expected thing, and
> handled appropriately.
> So, these "errors" are none, the files are not there, but they're not
> "missing", which is why Michael asked for the plain CMake output
> instead of the (slightly misleading) CMakeOutput.log.
>
> Hope you understand why I wanted to avoid derailing the discussion!
>
> Best regards,
> Marcus
>
> On Sun, 2019-07-21 at 09:29 -0400, Andi Kita wrote:
> > Hello Marcus,
> >
> > With all due respect. I mentioned to him that those two header files
> > which are missing are part of gcc and clang. I mentioned for
> > compiling those sources to have the files on. Also suggested getting
> > the files separately.
> >
> > I was not sure what the problem was but I see that CMake cannot find
> > the proper header files. Neither did I State in my email that header
> > files compile. Where did you come up with that?
> >
> > On Sun, Jul 21, 2019, 5:39 AM Müller, Marcus (CEL) <muel...@kit.edu>
> > wrote:
> > > Hi Andi,
> > >
> > > not quite sure where you're taking this.
> > > Neither cpuid.h not intrin.h are reasons for failure here.
> > > Also, it's almost certain you wouldn't want to download a compiler-
> > > specific include file from gihtub and put it somewhere! Please
> > > don't
> > > recommend something like that: We've (and I personally) had way too
> > > many people just plastering their system with wildly incompatible
> > > versions of fragments of software, and it made none of them happy.
> > >
> > > Also, header files can't be compiled.
> > >
> > > Best regards,
> > > Marcus
> > >
> > > On Sun, 2019-07-21 at 00:32 -0400, Andi Kita wrote:
> > > > Hello,
> > > >
> > > > cpuid.h is part of gcc. You should have gcc installed already!
> > > While
> > > > intrin.h header file is founded in clang also downloadable from
> > > > GitHub.
> > > >
> > > > CMake is looking for both files. Once you compile each one you
> > > will
> > > > be able to resolve this issue. You can always copy and paste the
> > > > header files but if you install them from source it will place
> > > the
> > > > files where they belong. I think in this case in the "include"
> > > > directory.
> > > >
> > > > Let me know if you have any questions.
> > > >
> > > >
> > > > On Sat, Jul 20, 2019, 7:27 PM Michael Dickens <
> > > > michael.dick...@ettus.com> wrote:
> > > > > Here are the (current) key issues:
> > > > > {{{
> > > > > -- Python checking for click - found
> > > > > -- Python checking for click-plugins - not found
> > > > > }}}
> > > > >
> > > > > These are Python packages. If you get them installed hopefully
> > > the
> > > > > "cmake" command will finish & you can get on with building from
> > > > > source! - MLD
> > > > >
> > > > > On Sat, Jul 20, 2019, at 6:56 PM, Barry Duggan wrote:
> > > > > > I used """cmake -DENABLE_GR_UHD=OFF
> > > > > -DCMAKE_INSTALL_PREFIX="/usr/local"
> > > > > > -DCMAKE_BUILD_TYPE=Release
> > > -DPYTHON_EXECUTABLE=/usr/bin/python3
> > > > > ../ >
> > > > > > cmake_out.txt 2>&1""". The file is attached.
> > > > > >
> > > > > > There are several 'missing' packages, but I don't know which
> > > ones
> > > > > are
> > > > > > important.
> > > > > > ---
> > > > > > Barry Duggan
> > > > > >
> > > > > > Attachments:
> > > > > > * cmake_out.txt
> > > > >
> > > > > _______________________________________________
> > > > > Discuss-gnuradio mailing list
> > > > > Discuss-gnuradio@gnu.org
> > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > > >
> > > > _______________________________________________
> > > > Discuss-gnuradio mailing list
> > > > Discuss-gnuradio@gnu.org
> > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to