sc6502 has joined #Speedsaver
peterm6881 has joined #Speedsaver
<peterm6881> hi roomies
<peterm6881> wb sc6502
<peterm6881> hi Xogium
<peterm6881> I tried a build of that MangoPi-MQ external buildroot tree. I got this error, but hopefully its fixed:
<peterm6881> configure: error: no C99 compiler found, eudev requires a C99 compiler
<peterm6881> Google search reckoned it was rogue files in the /usr/local/include directory, in my case curtail.h and shapefil.h
<peterm6881> just running the build again
<peterm6881> nop.....
<peterm6881> grrr
<peterm6881> my gcc is fine
<peterm6881> gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
<peterm6881> maybe it needs a later version
<Xogium> peterm6881: not sure. For me the build fails like this instead
<Xogium> ln: failed to create symbolic link '/home/xogium/buildroot/output/mq/host/riscv64-buildroot-linux-gnu/sysroot/lib64xthead/lp64d': No such file or directory
<Xogium> ln: failed to create symbolic link '/home/xogium/buildroot/output/mq/host/riscv64-buildroot-linux-gnu/sysroot/usr/lib64xthead/lp64d': No such file or directory
<Xogium> make[1]: *** [package/pkg-generic.mk:290: /home/xogium/buildroot/output/mq/build/toolchain-external-custom/.stamp_staging_installed] Error 1
<peterm6881> those toolchain libraries you mentioned
<Xogium> yep
<peterm6881> this is bizarre, I have GCC, what compiler are you using?
<Xogium> gcc 11
<Xogium> but this has nothing to do with the compiler in my case
<peterm6881> i know
<Xogium> what package is it trying to configure when you hit this error ?
<peterm6881> checking for gawk... (cached) gawk
<peterm6881> configure: error: no C99 compiler found, eudev requires a C99 compiler.
<peterm6881> checking for /home/peter/buildroot/output/host/bin/riscv64-unknown-linux-gnu-gcc option to accept ISO C99... unsupported
<peterm6881> make[1]: *** [package/pkg-generic.mk:240: /home/peter/buildroot/output/build/eudev-3.2.9/.stamp_configured] Error 1
<peterm6881> make: *** [Makefile:84: _all] Error 2
<Xogium> lol this is crazy you manage to go further in the build than I do
<peterm6881> lol why am I not compforted by this :)
<peterm6881> sigh....
<peterm6881> i think it must be my middle aged version of gcc
<peterm6881> compiling from source looks umm ........ hard
<Xogium> well hard to say… I can't get past the stage of installing the toolchain while you somehow do
<peterm6881> how can you tell its past that stage?
<Xogium> because it is trying to build eudev for the target
<Xogium> and logically, you can't build packages for the target until the toolchain has been installed properly
<peterm6881> ohh
<Xogium> I have no idea how you did that
<peterm6881> just following the repo
<Xogium> but I can tell you for certain it has nothing to do with your host's gcc, the gcc toolchain they offer doesn't support c99 standard, and eudev requires it
<peterm6881> would it help if i emailed you some of the toolchain stuff?
<Xogium> heh, probably not, I mean I've downloaded litterally the same archive
<peterm6881> yeah but didnt some new stuff get copied over in the build process?
<peterm6881> what the heck, any idea how I fix that?
<peterm6881> how is that possible? im assuming it worked for them at some point
<Xogium> I honestly don't know
<Xogium> hard to know since all the stuff is in chinese
<peterm6881> try this
<peterm6881> let me know if you can read it
<peterm6881> but tbh, there is literally nothing strange or startling there. It has to be my Lubuntu
<peterm6881> its disheartening, nothing is ever simple, or just works
<Xogium> wow, google translate chinese to english surprisingly good
<Xogium> hmm ok so I might understand how it is you managed
<Xogium> I just saw they recommend you once again use their fork
<Xogium> I used mainline buildroot with their external tree, thinking it would just work
<Xogium> now of course even the stupid commit messages for their git repo are in chinese. Sigh
<peterm6881> I opened a new issue about my problem
<peterm6881> Xogium, im glad at least we can get a kinda translation
<Xogium> and yeah it looks like they want you to use their fork and using mainline buildroot with their external tree won't work
<peterm6881> sigh
<peterm6881> lol
<peterm6881> to be fair, their readme does say they're following LTS, but you weren't to know
<peterm6881> since it was in Chinese :)
<Xogium> peterm6881: they follow lts of buildroot yes
<Xogium> but to me that meant their external tree could be used with upstream lts. I guess not
<Xogium> as for u-boot, well, it's a custom version they picked too, and which is at the very least nearly 4 years old by now
<Xogium> a more recent u-boot, say like the one we could get away with using on the orange pi, wouldn't have the problem with building with a more recent gcc
peterm6881 has quit [Quit: Leaving]