On Tue, 15 Sep 2009 11:36:29 +0400, Kyrill Detinov wrote:

Tuesday 15 September 2009

On Tuesday 15 September 2009 11:18:49 doiggl@velocitynet.com.au wrote:

...

I have a link to another project called wfnetobjs too (no wfnetobjs rpm installed yet)

Last set of wflog errors: configure: error: wfnetobjs-incdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build)

RPM build errors: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build) System halted.

Can someone assist me to compile this package please. 1. I think Ive got to install wfnetobjs rpm but dont know to set that in the spec file. 2. Also I got to do the configure bit with a call like (but unsure how to set in the spec file)

# ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/

Add to spec file

BuildRequires: libwfnetobjs-devel

Hello, I added BuildRequires: libwfnetobjs-devel to wflogs.spec for package wflogs I get this error when building a package called wflogs. configure: error: wfnetobjs-libdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.16934 (%build) Built wfnetobjs rpms are located in a external project located at https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia Questions: How do I install the remote rpm e.g libwfnetobjs0-0.2.4-5.1.x86_64.rpm and how do I specify that in the wflogs.spec and in which section, or will BuildRequires: libwfnetobjs-devel install that module ?. Also how should I format the following line in the wflogs.spec ? %build %configure --with-wfnetobjs-libdir=/usr/include/wallfire/ wflogs Specfile -> https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflogs&project=home%3Adoiggl wflogs Build log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflogs&project=home%3Adoiggl&repository=openSUSE_11.1 wflogs Package -> https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl Thankyou Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 12/14/2009 08:24 AM, doiggl@velocitynet.com.au wrote:

Hello.

I'm compiling a package called wflogs, it needs to have libwfnetobjs rpm installed. It has 'BuildRequires: libwfnetobjs-devel as part of the .spec file. Now i get a 'expansion error' 'nothing provides libwfnetobjs-devel'

There is a libwfnetobjs located at -> https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia

Question: How do I get libwfnetobjs rpm installed so the compile can continue ?.

wflogs specfile ->https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflogs&project=home%3Adoiggl

wflogs package ->https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl

wflogs last attempted compile log ->https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflogs&project=home%3Adoiggl&repository=openSUSE_11.2

Any help appreciated. Thankyou Glenn

You can create a new package link to the available libwfnetobjs package in the same project as your package wflogs and let it build. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 12/14/2009 10:21 AM, doiggl@velocitynet.com.au wrote:

On Mon, 14 Dec 2009 08:48:09 +0200, Dave Plater wrote:

...

On 12/14/2009 08:24 AM, doiggl@velocitynet.com.au wrote:

...

Hello.

I'm compiling a package called wflogs, it needs to have libwfnetobjs

rpm

...

...

installed. It has 'BuildRequires: libwfnetobjs-devel as part of the .spec file. Now i get a 'expansion error' 'nothing provides libwfnetobjs-devel'

There is a libwfnetobjs located at ->

https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia

...

...

Question: How do I get libwfnetobjs rpm installed so the compile can continue ?.

wflogs specfile

->https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflogs&project=home%3Adoiggl

...

...

wflogs package

->https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl

...

...

wflogs last attempted compile log

->https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflogs&project=home%3Adoiggl&repository=openSUSE_11.2

...

...

Any help appreciated. Thankyou Glenn

You can create a new package link to the available libwfnetobjs package in the same project as your package wflogs and let it build. Regards Dave P

Hello, I opened the package wflogs package in https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl

I see a [Add File] option but no linkage options

So I went to my 'Home Project' and saw option [Link Package from other Project] I see these items: Name of original project:

Name of project where the package to be linked is ie. home:elvigia in this case

Name of package in original project:

libwfnetobjs in this case.

Name of linked package in target project:

Question: Whats the proper way to fill these items in ?

package info: https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia

Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 12/14/2009 02:51 PM, doiggl@velocitynet.com.au wrote:

...

...

Hello, I opened the package wflogs package in

https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl

...

...

I see a [Add File] option but no linkage options

So I went to my 'Home Project' and saw option [Link Package from other Project] I see these items: Name of original project:

Name of project where the package to be linked is ie. home:elvigia in this case

...

Name of package in original project:

libwfnetobjs in this case.

...

Name of linked package in target project:

Question: Whats the proper way to fill these items in ?

package info:

https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl

...

...

https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia

...

Regards Dave P

Hello, This entry worked- > Name of original project -> home:elvigia

This entry Failed -> Name of package in original project-> libwfnetobjs

Error message is: Unable to find package 'libwfnetobjs' in project 'home:elvigia'.

Question: What should this entry be ? Thanks Glenn

Whatever the name of the project is where the package is. If you go to the project page you will find the package is called wfnetobjs https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Aelvigia. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Wed, 07 Apr 2010 07:54:44 +0000, wrote:

configure: error: wfnetobjs-libdir: no directory found, use configure option

This tells me that it's looking for the library and as this is here

/usr/lib64/libwfconfig.a /usr/lib64/libwfnetobjs.so

you should try %configure --with-wfnetobjs-libdir=%{_libdir} or patch configure so that the test also looks into lib64 in addition to lib. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

...

...

On 04/07/2010 at 3:36 PM, wrote: I installed the rpms, 1 at a time on a local pc and run this command after each install

This was the result I think the test was looking for file wfnetobjs.h location

# ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/

you should use %configure --with-wfnetobjs-libdir=%{_libdir} in your spec file. If you have to define a libdir, then /usr/include is most likely wrong. you can apply the attached diff to your spec file, then the 'build' process get's over this very error (warning: it does stop during build due to missing #include statements). Hope this helps. Dominique how to apply the patch: Save it in the same folder you have your package / spec file, then patch < specfile.diff And you get a changed spec file. Make sure to get those lengthy comments out... sometimes RPM is nasty with macros in comments.