Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 46608: /trunk/ /trunk/: Makefile.am

From: Evan Huus <eapache@xxxxxxxxx>
Date: Wed, 19 Dec 2012 18:11:30 -0500
That did the trick, thanks.

Evan

On Wed, Dec 19, 2012 at 6:00 PM, Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> wrote:
> I had that problem too actually: do a make clean.  It appears that the
> dumpcap-*.o files aren't being rebuilt automatically (and they need to be so
> they get compiled with -fPIE so they can be linked into dumpcap).
>
> Evan Huus wrote:
>>
>> I have been getting a link error for dumpcap since this revision that
>> doesn't appear to be showing up in the buildbots.
>>
>> Output as follows:
>> /usr/bin/ld.bfd.real: dumpcap-capture-pcap-util-unix.o: relocation
>> R_X86_64_32 against `.rodata.str1.8' can not be used when making a
>> shared object; recompile with -fPIC
>> dumpcap-capture-pcap-util-unix.o: could not read symbols: Bad value
>>
>> This is on a bleeding-edge Ubuntu pre-release, so it's possibly a
>> toolchain issue on my end, but I think that's unlikely.
>>
>> Evan
>>
>> On Tue, Dec 18, 2012 at 9:09 PM,  <morriss@xxxxxxxxxxxxx> wrote:
>>>
>>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=46608
>>>
>>> User: morriss
>>> Date: 2012/12/18 06:09 PM
>>>
>>> Log:
>>>  As suggested in https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8076
>>> :
>>>
>>>  Enable PIE (if the compiler supports it) when compiling dumpcap.  Do
>>> this
>>>  regardless of whether we're configured to install dumpcap setuid-root
>>> because
>>>  some users will end up running dumpcap as root regardless of how we were
>>>  configured.
>>>
>>> Directory: /trunk/
>>>   Changes    Path            Action
>>>   +3 -2      Makefile.am     Modified
>>>   +24 -0     configure.ac    Modified
>>>
>>>
>>> ___________________________________________________________________________
>>> Sent via:    Wireshark-commits mailing list
>>> <wireshark-commits@xxxxxxxxxxxxx>
>>> Archives:    http://www.wireshark.org/lists/wireshark-commits
>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
>>>
>>> mailto:wireshark-commits-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>> Archives:    http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>
>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe