<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I always build with:<br><br> --with-libz=internal \<br> --with-png=internal \<br> --with-libtiff=internal \<br> --with-geotiff=internal \<br><b> --with-jpeg=internal \<br></b> --with-gif=internal \<br><br> If that helps...<br><br><div>> Date: Fri, 10 Jan 2014 17:33:52 +0100<br>> From: even.rouault@mines-paris.org<br>> To: jlaura@asu.edu<br>> CC: gdal-dev@lists.osgeo.org<br>> Subject: Re: [gdal-dev] Standard Dev. Environment?<br>> <br>> Jay,<br>> <br>> hum it is well possible that the build with --without-jpeg doesn't work and that<br>> some drivers will try to use it. I haven't tried it for ages. GDAL has an<br>> internal version of libjpeg, so when you've no external libjpeg, that one will<br>> be picked up. I imagine that very few people test --without-jpeg.<br>> <br>> Frank suggested you to just use plain "./configure". I'd recommend strongly that<br>> you just to try it. This must work well and autodetect which libs are available<br>> or not. The BuildingOnUnixWithMinimizedDrivers page you quote represents a<br>> non-standard configuration of GDAL, so you may hit rough corners.<br>> <br>> To answer your question concerning the value for --with-jpeg, it is the<br>> installation prefix of libjpeg. Typically /usr for system jpeg (but that one<br>> would be picked up implicitely) or /usr/local (if you've installed your own<br>> libjpeg).<br>> <br>> > Evan,<br>> ><br>> > Thanks for the info. One more question for you - make clean worked, but I<br>> > have hit another issue:<br>> ><br>> > After running `./configure --without-jpeg ...`, `make clean`, `sudo make<br>> > install`:<br>> > ...<br>> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to<br>> > `jpeg_write_scanlines'<br>> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to<br>> > `jpeg_CreateCompress'<br>> > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to<br>> > `jpeg_read_scanlines'<br>> ><br>> > So lib-jpeg is seen. This doesn't make sense since I have --without-jpeg<br>> > specified in the config. I looked in the config and must have missed it -<br>> > does a flag to specify the full PATH to libjpeg exist?<br>> ><br>> > Thanks,<br>> > Jay<br>> ><br>> ><br>> > On Fri, Jan 10, 2014 at 7:24 AM, Even Rouault<br>> > <even.rouault@mines-paris.org>wrote:<br>> ><br>> > > Selon "Jay L." <jlaura@asu.edu>:<br>> > ><br>> > > > Frank,<br>> > > ><br>> > > > Thanks for the heads up. I am using the --without-jasper flag as part of<br>> > > > the ./configure call. Here is the error that I am seeing - that led to<br>> > > me<br>> > > > to believe that the issue is jasper related:<br>> > > ><br>> > > > make[1]: Entering directory `/home/vagrant/gdal-1.10.1/apps'<br>> > > > g++ gdalinfo.o commonutils.o -L/home/vagrant/gdal-1.10.1 -lgdal<br>> > > > -lpthread -lm -lrt -ldl -o gdalinfo<br>> > > > /home/vagrant/gdal-1.10.1/libgdal.so: undefined reference to<br>> > > `dec_jpeg2000'<br>> > > > collect2: ld returned 1 exit status<br>> > > > make[1]: *** [gdalinfo] Error 1<br>> > > > make[1]: Leaving directory `/home/vagrant/gdal-1.10.1/apps'<br>> > > > make: *** [apps-target] Error 2<br>> > > ><br>> > > > I did install libjpeg-dev and libjasper-dev in hopes that this would<br>> > > > alleviate the issue.<br>> > > ><br>> > > > Perhaps I am pursuing the issue in the wrong direction?<br>> > ><br>> > > When you run ./configure several times, make sure to run "make clean"<br>> > > between<br>> > > the attempts. I'm not clear why you've had this error with the<br>> > > "dec_jpeg2000"<br>> > > symbol that is defined and used in the GRIB driver (it has a definition<br>> > > even if<br>> > > you don't have Jasper). Anway the "make clean" will probably solve it.<br>> > > Generally, "./configure" without any particular argument should work on<br>> > > most<br>> > > platforms.<br>> > ><br>> > > ><br>> > > > Thanks,<br>> > > > Jay<br>> > > ><br>> > > ><br>> > > > On Thu, Jan 9, 2014 at 9:33 PM, Frank Warmerdam <warmerdam@pobox.com><br>> > > wrote:<br>> > > ><br>> > > > > Jay,<br>> > > > ><br>> > > > > Are you needing Jasper? Normally a default build ("./configure")<br>> > > should<br>> > > > > work pretty well on a precise system. I'm guessing you have enabled<br>> > > jasper<br>> > > > > because it is key to what you want to do? If not --without-jasper<br>> > > should<br>> > > > > be straight forward.<br>> > > > ><br>> > > > > Best regards,<br>> > > > > Frank<br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > > On Thu, Jan 9, 2014 at 8:00 PM, Jay L. <jlaura@asu.edu> wrote:<br>> > > > ><br>> > > > >> List,<br>> > > > >><br>> > > > >> I wonder if a standard dev. environment exists? I am working to<br>> > > extend a<br>> > > > >> driver and am having trouble getting an environment working that will<br>> > > > >> compile. Current setup is a VagrantVM, Ubuntu 12.04 32-bit with<br>> > > source<br>> > > > >> downloaded from SVN. Attempting to build with minimized<br>> > > > drivers<<br>> > > http://trac.osgeo.org/gdal/wiki/BuildingOnUnixWithMinimizedDrivers>as<br>> > > > per the build documentation and am having build errors due to<br>> > > > >> dec_jpeg2000 (jasper I believe).<br>> > > > >><br>> > > > >> Q: Are devs using a standard environment (or a different flavor of<br>> > > *nix?)?<br>> > > > >><br>> > > > >><br>> > > > >><br>> > > > >><br>> > > > >><br>> > > > >> _______________________________________________<br>> > > > >> gdal-dev mailing list<br>> > > > >> gdal-dev@lists.osgeo.org<br>> > > > >> http://lists.osgeo.org/mailman/listinfo/gdal-dev<br>> > > > >><br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > > --<br>> > > > ><br>> > > > ><br>> > > ><br>> > ><br>> > ---------------------------------------+--------------------------------------<br>> > > > > I set the clouds in motion - turn up | Frank Warmerdam,<br>> > > > > warmerdam@pobox.com<br>> > > > > light and sound - activate the windows | http://pobox.com/~warmerdam<br>> > > > > and watch the world go round - Rush | Geospatial Software Developer<br>> > > > ><br>> > > ><br>> > ><br>> > ><br>> ><br>> _______________________________________________<br>> gdal-dev mailing list<br>> gdal-dev@lists.osgeo.org<br>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<br></div> </div></body>
</html>