Jeff Morriss writes:
> > Jeff Morriss ...> writes:
> >
> It turns out that RHEL's rpmbuild doesn't let you %exclude a file that
> doesn't exist. Should be fixed with:
>
> https://code.wireshark.org/review/#/c/3586/
Yes, that fixed it!
__
Jeff Morriss writes:
> Hmm, what did you do before that? I don't have that problem in a
> freshly untar'd source tree. As I said earlier in the thread I can do
> this without a problem:
>
> % cd /tmp && tar xjf /path/to/wireshark-1.12.0.tar.bz2 && cd
> wireshark-1.12.0 && ./configure --with
On 08/13/14 17:19, Christopher Maynard wrote:
Jeff Morriss writes:
I noticed above that you did not run ./autogen.sh. I tried once again, this
time *without* running autogen.sh just as you've shown, but unfortunately
the results were the same.
Source tarballs don't need ./autogen.sh run on
On 08/13/14 16:28, Christopher Maynard wrote:
Jeff Morriss writes:
Anyway, I had been running this test on Fedora (20) but since I didn't
want to accuse you of operator error I decided to try it on RHEL 6.
Sure enough, I saw the problem.
Well that's nice to know. Thanks for confirming!
Jeff Morriss writes:
> > I noticed above that you did not run ./autogen.sh. I tried once again, this
> > time *without* running autogen.sh just as you've shown, but unfortunately
> > the results were the same.
>
> Source tarballs don't need ./autogen.sh run on them--that's part of the
> magic
Jeff Morriss writes:
> Anyway, I had been running this test on Fedora (20) but since I didn't
> want to accuse you of operator error I decided to try it on RHEL 6.
> Sure enough, I saw the problem.
Well that's nice to know. Thanks for confirming!
_
On 08/12/14 18:51, Christopher Maynard wrote:
Jeff Morriss writes:
That's odd; I just tried it (starting from the wireshark-1.12.0 source
tarball[1]) and did not have any problems. I wonder if your
wireshark.spec file isn't being regenerated (from wireshark.spec.in)?
You could try comparing t
On Tue, Aug 12, 2014 at 10:51:06PM +, Christopher Maynard wrote:
> Jeff Morriss writes:
>
> > That's odd; I just tried it (starting from the wireshark-1.12.0 source
> > tarball[1]) and did not have any problems. I wonder if your
> > wireshark.spec file isn't being regenerated (from wiresha
On 8/12/14 5:03 PM, Evan Huus wrote:
> There have been repeated fuzzing failures over the last day that
> haven't resulted in bugs. Result of the bugzilla upgrade?
Bugzilla's WebService API switched from cookie authentication to tokens.
It should be fixed now.
_
On Sun, Aug 10, 2014 at 2:07 PM, Evan Huus wrote:
>
>
>> On Aug 10, 2014, at 7:06, Bálint Réczey wrote:
>>
>> Hi Evan,
>>
>> 2014-08-10 4:41 GMT+02:00 Evan Huus :
>>> http://buildbot.wireshark.org/trunk/builders/Clang%20Code%20Analysis/builds/2911/steps/check-abi/logs/stdio
>>>
>>> I took a quick
10 matches
Mail list logo
