10:21 a.m.
On Sat, Jul 02, 2011 at 12:22:25 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
I can't continue to maintain qucs because it FTBS and i'm not
able to
solve the problem https://bugzilla.redhat.com/show_bug.cgi?id=631404
i need help or the package will be retired.
I'm taking a look at qucs now. I might be able to figure this out.
The users list isn't the right place for this question. The devel list
is a much better place to ask for help from other packagers.
It would have probably helped to included enough of the build log in your
request for help that people could judge where the problem was and whether
or not they'd likely to be able help with out going to the FTBFS bug
and downloading attachments until the found the one that indicated the
problem.
Something like:
There were a number of errors refering to an ambiguous type, for example:
spfile.cpp: In member function 'matrix spfile::correlationMatrix(double, nr_complex_t,
double, matrix)':
spfile.cpp:405:21: error: call of overloaded 'conj(nr_complex_t)' is ambiguous
/usr/lib/gcc/x86_64-redhat-linux/4.5.1/../../../../include/c++/4.5.1/complex:667:33: note:
candidates are: std::complex<_Tp> std::conj(const std::complex<_Tp>&)
[with _Tp = double]
10:30 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 02, 2011 at 10:21:48 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
On Sat, Jul 02, 2011 at 12:22:25 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
> I can't continue to maintain qucs because it FTBS and i'm not able to
> solve the problem https://bugzilla.redhat.com/show_bug.cgi?id=631404
> i need help or the package will be retired.
I'm taking a look at qucs now. I might be able to figure this out.
There is also a new upstream release. Since the issue is likely due to
new gcc pickiness, trying out the new release to see if it has fixes to
build with later versions of gcc/g++ is a good strategy.
1:05 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 02/07/2011 17:30, Bruno Wolff III a écrit :
On Sat, Jul 02, 2011 at 10:21:48 -0500,
Bruno Wolff III<bruno(a)wolff.to> wrote:
> On Sat, Jul 02, 2011 at 12:22:25 +0200,
> Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
>> I can't continue to maintain qucs because it FTBS and i'm not able to
>> solve the problem https://bugzilla.redhat.com/show_bug.cgi?id=631404
>> i need help or the package will be retired.
> I'm taking a look at qucs now. I might be able to figure this out.
There is also a new upstream release. Since the issue is likely due to
new gcc pickiness, trying out the new release to see if it has fixes to
build with later versions of gcc/g++ is a good strategy.
Thanks for the suggestion.
I have already tried the new version with the
same errors.
Eric
8:10 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 02, 2011 at 20:05:53 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
Thanks for the suggestion. I have already tried the new version with
the
same errors.
I eventually noticed that in the bug report as well. I think not using tr1
to provide complex functions is the way to go in the short run. Trying to
fix references doesn't seem to work. I suspect that somthing is pulling in
the normal complex definitions, but am not sure how to track it down.
That's something that upstream can look into. My first try at not using
tr1 failed, because some of the complex functions are not provided by
the normal complex definitions. But I think I have a simple hack to do
it now. The test build is still running, but if it works I'll post the
patches to the bug.
8:33 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sun, Jul 03, 2011 at 08:10:25 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
the normal complex definitions. But I think I have a simple hack to
do
it now. The test build is still running, but if it works I'll post the
patches to the bug.
The test build completed. I didn't actually try running the program.
I attached the two commits (one to go to 0.0.16 and the other the hack
to work around the problem) to the bug report. (As git format-patch
messages.)
3:30 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 03/07/2011 15:33, Bruno Wolff III a écrit :
On Sun, Jul 03, 2011 at 08:10:25 -0500,
Bruno Wolff III<bruno(a)wolff.to> wrote:
> the normal complex definitions. But I think I have a simple hack to do
> it now. The test build is still running, but if it works I'll post the
> patches to the bug.
The test build completed. I didn't actually try running the program.
I attached the two commits (one to go to 0.0.16 and the other the hack
to work around the problem) to the bug report. (As git format-patch
messages.)
Thank you very much. Now it builds fine in koji for f16 and f15.
At the same time qucs-0.0.16 were out a new version of freehdl appeared
0.0.8 but when i try to build it i have an error about rpath and i don't
know how to solve it :
+ /usr/lib/rpm/check-rpaths
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause
'rpmbuild'
* to fail. To ignore these errors, you can set the '$QA_RPATHS'
* environment variable which is a bitmask allowing the values
* below. The current value of QA_RPATHS is 0x0000.
*
* 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
* issue but are introducing redundant searchpaths without
* providing a benefit. They can also cause errors in multilib
* environments.
* 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
* nor relative filenames and can therefore be a SECURITY risk
* 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
* SECURITY risk
* 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
* RPATHs; this is just a minor issue but usually unwanted
* 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
* and they cause unneeded work while loading libraries
* 0x0020 ... an RPATH references '..' of an absolute path; this will
break
* the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute
check-rpaths like
* $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
*******************************************************************************
ERROR 0001: file '/usr/bin/freehdl-v2cc' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
erreur: Mauvais status de sortie pour /var/tmp/rpm-tmp.B5fP1y (%install)
Could you help me for this problem also ?
Thanks
Eric
11:22 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 04/07/2011 05:42, Bruno Wolff III a écrit :
On Sun, Jul 03, 2011 at 22:30:01 +0200,
Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
> Could you help me for this problem also ?
I can take a look at it, but probably not for a few days.
Ok thanks, the file is
difficult to find because the upstream web site
is not up to date.
Here is a link for the file :
http://sourceforge.net/projects/qucs/files/qucs/0.0.16/freehdl-0.0.8.tar.gz
Eric
7:47 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sun, Jul 03, 2011 at 22:30:01 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
At the same time qucs-0.0.16 were out a new version of freehdl
appeared 0.0.8 but when i try to build it i have an error about
rpath and i don't know how to solve it :
Could you help me for this problem also ?
I did a local build of freehdl 0.0.8 and I didn't get an rpath warning.
I ran rpmlint on the output rpm and didn't see any reference to rpath.
(There were some other things that were complained about.)
1:37 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 09/07/2011 02:47, Bruno Wolff III a écrit :
On Sun, Jul 03, 2011 at 22:30:01 +0200,
Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
> At the same time qucs-0.0.16 were out a new version of freehdl
> appeared 0.0.8 but when i try to build it i have an error about
> rpath and i don't know how to solve it :
> Could you help me for this problem also ?
I did a local build of freehdl 0.0.8 and I didn't get an rpath warning.
I ran rpmlint on the output rpm and didn't see any reference to rpath.
(There were some other things that were complained about.)
Ok so i just redo a
local build on my x86_64 system and i still have an
error not a warning about rpath :
ERROR 0001: file '/usr/bin/freehdl-v2cc' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
erreur: Mauvais status de sortie pour /var/tmp/rpm-tmp.3B2Wl7 (%install)
So it seems the problem is x86_64 related ?
Eric
2:29 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 09, 2011 at 08:37:05 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
Le 09/07/2011 02:47, Bruno Wolff III a écrit :
>On Sun, Jul 03, 2011 at 22:30:01 +0200,
> Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
>>At the same time qucs-0.0.16 were out a new version of freehdl
>>appeared 0.0.8 but when i try to build it i have an error about
>>rpath and i don't know how to solve it :
>>Could you help me for this problem also ?
>I did a local build of freehdl 0.0.8 and I didn't get an rpath warning.
>I ran rpmlint on the output rpm and didn't see any reference to rpath.
>(There were some other things that were complained about.)
Ok so i just redo a local build on my x86_64 system and i still have
an error not a warning about rpath :
ERROR 0001: file '/usr/bin/freehdl-v2cc' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
erreur: Mauvais status de sortie pour /var/tmp/rpm-tmp.3B2Wl7 (%install)
So it seems the problem is x86_64 related ?
Possibly. You might want to try to do a scratch build and see if you see
the same thing.
5:54 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 09/07/2011 09:29, Bruno Wolff III a écrit :
On Sat, Jul 09, 2011 at 08:37:05 +0200,
Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
> Le 09/07/2011 02:47, Bruno Wolff III a écrit :
>> On Sun, Jul 03, 2011 at 22:30:01 +0200,
>> Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
>>> At the same time qucs-0.0.16 were out a new version of freehdl
>>> appeared 0.0.8 but when i try to build it i have an error about
>>> rpath and i don't know how to solve it :
>>> Could you help me for this problem also ?
>> I did a local build of freehdl 0.0.8 and I didn't get an rpath warning.
>> I ran rpmlint on the output rpm and didn't see any reference to rpath.
>> (There were some other things that were complained about.)
> Ok so i just redo a local build on my x86_64 system and i still have
> an error not a warning about rpath :
>
> ERROR 0001: file '/usr/bin/freehdl-v2cc' contains a standard rpath
> '/usr/lib64' in [/usr/lib64]
> erreur: Mauvais status de sortie pour /var/tmp/rpm-tmp.3B2Wl7 (%install)
>
> So it seems the problem is x86_64 related ?
Possibly. You might want to try to do a scratch build and see if you see
the same thing.
You are right. The scratch build build fine and the package is now
on bodhi.
I can't understand why there was a problem on my local build!
Thanks
Eric
7:53 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 09, 2011 at 12:54:23 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
You are right. The scratch build build fine and the package is now on
bodhi.
I can't understand why there was a problem on my local build!
Thanks
Eric
If you aren't using fedpkg to do the local build, you might not be passing
the correct config options. I seem to remember that %config passes an
argument that says not to use rpath.
11:50 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 09/07/2011 14:53, Bruno Wolff III a écrit :
If you aren't using fedpkg to do the local build, you might not be passing
the correct config options. I seem to remember that %config passes an
argument that says not to use rpath.
It's correct. If i use fedpkg mockbuild
there is no error whereas if i
use rpmbuild -bb freehdl.spec i have an rpath error.
This a bug ? If yes i'm not sure how to report it.
Eric
11:39 a.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 09, 2011 at 18:50:43 +0200,
Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
Le 09/07/2011 14:53, Bruno Wolff III a écrit :
>
> If you aren't using fedpkg to do the local build, you might not be passing
> the correct config options. I seem to remember that %config passes an
> argument that says not to use rpath.
It's correct. If i use fedpkg mockbuild there is no error whereas if i
use rpmbuild -bb freehdl.spec i have an rpath error.
This a bug ? If yes i'm not sure how to report it.
No its not a bug. When you use fedpkg some different settings are made.
I am not sure of the exact mechanism.
12:30 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 9, 2011 at 6:50 PM, Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
Le 09/07/2011 14:53, Bruno Wolff III a écrit :
>
> If you aren't using fedpkg to do the local build, you might not be passing
> the correct config options. I seem to remember that %config passes an
> argument that says not to use rpath.
It's correct. If i use fedpkg mockbuild there is no error whereas if i
use rpmbuild -bb freehdl.spec i have an rpath error.
This a bug ? If yes i'm not sure how to report it.
I suspect the behavior is caused by
https://fedoraproject.org/wiki/PackagingGuidelines#Beware_of_Rpath :
your local system has rpmdevtools installed, which changes rpm
configuration to perform the rpath check. mock uses a minimal chroot
which doesn't include rpmdevtools, thus the check is not performed.
Mirek
12:20 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 09, 2011 at 19:30:56 +0200,
Miloslav Trmač <mitr(a)volny.cz> wrote:
On Sat, Jul 9, 2011 at 6:50 PM, Eric Tanguy
<eric.tanguy(a)gmail.com> wrote:
> Le 09/07/2011 14:53, Bruno Wolff III a écrit :
>>
>> If you aren't using fedpkg to do the local build, you might not be passing
>> the correct config options. I seem to remember that %config passes an
>> argument that says not to use rpath.
> It's correct. If i use fedpkg mockbuild there is no error whereas if i
> use rpmbuild -bb freehdl.spec i have an rpath error.
> This a bug ? If yes i'm not sure how to report it.
I suspect the behavior is caused by
https://fedoraproject.org/wiki/PackagingGuidelines#Beware_of_Rpath :
your local system has rpmdevtools installed, which changes rpm
configuration to perform the rpath check. mock uses a minimal chroot
which doesn't include rpmdevtools, thus the check is not performed.
In this case I don't think that applies. I used fedpkg to do a local
build without mock and have rpmdevtools installed and I didn't see
a warning about rpath.
1:03 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
Le 09/07/2011 19:20, Bruno Wolff III a écrit :
On Sat, Jul 09, 2011 at 19:30:56 +0200,
Miloslav Trmač<mitr(a)volny.cz> wrote:
> On Sat, Jul 9, 2011 at 6:50 PM, Eric Tanguy<eric.tanguy(a)gmail.com> wrote:
>> Le 09/07/2011 14:53, Bruno Wolff III a écrit :
>>> If you aren't using fedpkg to do the local build, you might not be
passing
>>> the correct config options. I seem to remember that %config passes an
>>> argument that says not to use rpath.
>> It's correct. If i use fedpkg mockbuild there is no error whereas if i
>> use rpmbuild -bb freehdl.spec i have an rpath error.
>> This a bug ? If yes i'm not sure how to report it.
> I suspect the behavior is caused by
> https://fedoraproject.org/wiki/PackagingGuidelines#Beware_of_Rpath :
> your local system has rpmdevtools installed, which changes rpm
> configuration to perform the rpath check. mock uses a minimal chroot
> which doesn't include rpmdevtools, thus the check is not performed.
In this case I don't think that applies. I used fedpkg to do a local
build without mock and have rpmdevtools installed and I didn't see
a warning about rpath.
If i do fedpkg local i obtain the same rpath error as
running rpmbuild.
The question is : why rpmdevtools make problem about rpath whereas koji
build fine ?
Eric
12:35 p.m.
New subject: Comaintaining and/or help for qucs and freehdl
On Sat, Jul 9, 2011 at 6:50 PM, Eric Tanguy <eric.tanguy(a)gmail.com> wrote:
Le 09/07/2011 14:53, Bruno Wolff III a écrit :
>
> If you aren't using fedpkg to do the local build, you might not be passing
> the correct config options. I seem to remember that %config passes an
> argument that says not to use rpath.
It's correct. If i use fedpkg mockbuild there is no error whereas if i
use rpmbuild -bb freehdl.spec i have an rpath error.
This a bug ? If yes i'm not sure how to report it.
I suspect the behavior is caused by
https://fedoraproject.org/wiki/PackagingGuidelines#Beware_of_Rpath :
your local system has rpmdevtools installed, which changes rpm
configuration to perform the rpath check. mock uses a minimal chroot
which doesn't include rpmdevtools, thus the check is not performed.
Mirek
4711
days inactive
4718
days old
18 comments
3 participants
participants (3)
-
Bruno Wolff III -
Miloslav Trmač -
Tanguy Eric