<div dir="ltr"><div><div><div>When I check-out the libgdal package and I run the osc build command, isn't this building locally and not trying to <i>upload </i>any binaries? I thought this chroot was in my local machine and only making changes there?<br>
<br></div>I was trying to keep this all a local build by following the instructions at: <a href="https://en.opensuse.org/openSUSE:Build_Service_Tutorial">https://en.opensuse.org/openSUSE:Build_Service_Tutorial</a> maybe I misunderstood what "local" really means. Should I not be using osc to build this and instead use the rpmbuild commands directly?<br>
<br></div>I'll explore those two options you've suggested, I was trying to do option 2, but kept running into permission issues when the source tarball for the API was being extracted to the chroot environment at /usr/lib64 with permission denied.<br>
<br></div><div>I'll read more on this stuff, thanks again.<br></div><div><br><br></div>I think I just need to read more on how to handle user permissions in the spec file, so I'll take some time to read some more docs on bundling RPMs from spec files.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 25, 2013 at 3:57 PM, Angelos Tzotsos <span dir="ltr"><<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Donovan,<br>
<br>
This approach will not work. <br>
<br>
OpenBuildService (OBS) is a system to automate builds and create
packages, and we are using it to <br>
<a href="http://openbuildservice.org/" target="_blank">http://openbuildservice.org/</a><br>
<br>
openSUSE Build Service is a deployment of OBS that we are using to
produce openSUSE distribution<br>
<a href="https://build.opensuse.org/" target="_blank">https://build.opensuse.org/</a><br>
<br>
The root of your problem:<br>
<br>
OBS builds packages in an isolated environment (chroot or kvm
virtual machines where network is not accessible). <br>
In order to satisfy dependencies, those have to be already
packaged and get pre-installed on the chroot environment (or vm)
as specified by the "Requires:" and "BuildRequires:" sections of
the spec file.<br>
This is made in order to CONFIRM that everything that is needed to
build the new rpm package is already included in the distribution
and that the source code is available for it. <br>
On the openSUSE Build Service (including Application:Geo
repository) it is FORBIDDEN to upload binaries, only source code
is permitted. This is done to confirm that our distribution can be
built completely from source code.<br>
OBS is Open Source and if you want to build non open source stuff
you can deploy it on your own server, no problem there. <br>
<br>
The specifics of your problem:<br>
<br>
It is correct to use ./configure
--with-fgdb=/usr/lib64/FIleGDB_API but the problem is that these
files have to be installed inside the chroot environment.<br>
You have 2 options:<br>
1. Create an RPM for the GDB_API and make a "BuildRequires"
statement in the spec file to pull it in the build environment<br>
2. Include the original tar.gz files on your spec file and move
around files in correct places before the configure command<br>
<br>
I hope this helps.<br>
<br>
Best,<br>
Angelos<div><div class="h5"><br>
<br>
<br>
On 01/25/2013 11:34 PM, Donovan Cameron wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<pre>My buildlog from "osc build openSUSE_12.2 x86_64 libgdal.spec --clean" if
it helps.
<a href="http://paste.opensuse.org/view/raw/e119c82d" target="_blank">http://paste.opensuse.org/view/raw/e119c82d</a>
On Fri, Jan 25, 2013 at 1:54 PM, Donovan Cameron <a href="mailto:sault.don@gmail.com" target="_blank"><sault.don@gmail.com></a>wrote:
</pre>
<blockquote type="cite">
<pre>I've tested compiling the 64bit gdal-1.9.2 from the tar.gz source file:
./configure --with-fgdb=/usr/lib64/FileGDB_API
And it completes successfully where I can see the FileGDB driver
read/write format in the output of ogrinfo --formats.
There must be something in this SPEC file that is causing a conflict
so that that the .so for the FileGDB driver can't be found, even after
it's registered with ldconfig.
On Fri, Jan 25, 2013 at 11:05 AM, Donovan Cameron <a href="mailto:sault.don@gmail.com" target="_blank"><sault.don@gmail.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre>Thanks for the suggestion Jan.
I tried to compile the 32-bit libgdal with the 32bit FileGDB_API but
still throws the same error...
Is it possible that the osc tool is looking inside it's build
environment at /tmp or /usr/tmp instead of my local user files at
/usr/lib64?
I might take this problem to the package maintainer for libgdal on
openSUSE 12.2 to see if they have attempted to compile with FileGDB
support.
On Fri, Jan 25, 2013 at 1:19 AM, Jan Heckman <a href="mailto:jan.heckman@gmail.com" target="_blank"><jan.heckman@gmail.com></a>
</pre>
</blockquote>
<pre>wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>Hi,
On windows, using visual studio (2008 and 2012), I could compile both 32
bits and 64 bits, but only the 32 bits version actually worked.
I haven't tried to figure out why the 64 bits version didn't work, 32
</pre>
</blockquote>
</blockquote>
<pre>bits
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>was good enough for me.
Hope this is an option for you as well,
Jan
On Fri, Jan 25, 2013 at 5:23 AM, Donovan Cameron <a href="mailto:sault.don@gmail.com" target="_blank"><sault.don@gmail.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre>Looks like over in the [qgis-user] list, someone is having similar
problems:
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre><a href="https://groups.google.com/d/msg/qgis_user_remote/B2J9sOsSLbo/BIpAHZ84bhgJ" target="_blank">https://groups.google.com/d/msg/qgis_user_remote/B2J9sOsSLbo/BIpAHZ84bhgJ</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>On Thu, Jan 24, 2013 at 9:05 PM, Donovan Cameron <a href="mailto:sault.don@gmail.com" target="_blank"><sault.don@gmail.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre>I can't seem to compile GDAL with FileGDB support on openSUSE.
I'm compiling locally using the OBS tools (osc) and have checked-out
the libgdal package from the Application:Geo project.
Steps I've taken:
1) Download FileGDB_API_1_2-64.tar.gz
2) tar xzvf FileGDB_API_1_2-64.tar.gz -C /usr/lib64/
3) export LD_LIBRARY_PATH=/usr/lib64/FileGDB_API/lib
cd /usr/lib64/FileGDB_API/samples
make
cd bin
./Querying #Works, so the API is fine.
4) su -
$ vi /etc/ld.so.conf.d/fgdb.conf #Added a single entry:
/usr/lib64/FileGDB_API/lib
$ ldconfig #A grep of this with the -v flag shows it registered fine
5) #Some openSUSE specific stuff, b/c I'm building locally via the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre>OBS
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>$ zypper in osc
cd /home/saultdon/Development/obs
osc co Application:Geo libgdal
cd Application:Geo/libgdal
vi libgdal.spec #added "--with-fgdb=/usr/lib64/FileGDB_API" in
%configure section
#I also did a test build without that configure param. first and it
compiled fine with working RPMs
osc build openSUSE_12.2 x86_64 libgdal.spec --clean
Resulting Error:
[ 209s] checking for libFileGDBAPI.so in in
/usr/lib64/FileGDB_API/lib... configure: error: not found.
[ 209s] error: Bad exit status from /var/tmp/rpm-tmp.7SOa8g (%build)
[ 209s] RPM build errors:
[ 209s] Bad exit status from /var/tmp/rpm-tmp.7SOa8g (%build)
The buildroot was: /var/tmp/build-root
libFileGDBAPI.so file exists, ldconfig registered it, and the API
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre>test
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>worked fine, the env. var. LD_LIBRARY_PATH is also set, but I don't
even think that's necessary. I only had to set that to get the API
test to work.
I'm not sure where this is going wrong. If anyone has any input or
needs more information, let me know.
Thanks!
Donovan
</pre>
</blockquote>
<pre>_______________________________________________
gdal-dev mailing list
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a>
</pre>
</blockquote>
<pre>
</pre>
</blockquote>
</blockquote>
<pre></pre>
</blockquote>
<pre></pre>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
gdal-dev mailing list
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a href="http://users.ntua.gr/tzotsos" target="_blank">http://users.ntua.gr/tzotsos</a></pre>
</font></span></div>
</blockquote></div><br></div>