However there is a libglu1-mesa-dev package for armel. So why isn't it used so its the same across the architectures?
The two options for this but are: * shrug about qt5base-dev not depending libglu1-mesa-dev and include it explicitly; or * not have mudlet in armel because the glu support is really not there - Craig On Sun, 5 Jun 2016 2:47 am Scott Kitterman <deb...@kitterman.com> wrote: > On Saturday, June 04, 2016 03:59:49 PM Emilio Pozuelo Monfort wrote: > > On 26/05/16 14:49, Craig Small wrote: > > > On Thu, May 26, 2016 at 8:57 PM Emilio Pozuelo Monfort < > po...@debian.org > > > > > > <mailto:po...@debian.org>> wrote: > > > Project ERROR: glu development package not found > > > > > > That library is part of libglu1-mesa-dev which is a dependency for > > > qtbase5-dev. > > > > > > Except for armel which, for some reason, qtbase5-dev does not include > it. > > > > > > Architecture: amd64 > > > Depends: libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev, > > > > > > Architecture: armel > > > Depends: libgles2-mesa-dev | libgles2-dev, > > > > > > I think it should be just a matter of adding libglu1-mesa-dev to the > build > > > dependencies and we're done. > > > > Maybe this ought to get reassigned to qtbase5-dev? > > Qt (both Qt4 and Qt5) only support GLES on armel. The absence is > intentional. > Packages that need Qt and GL either need to adapt to using GLES or be > removed. > Please don't reassign. > > Scott K > -- Craig Small (@smallsees) http://enc.com.au/ csmall at : dropbear.xyz Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
