Hello sir, It is ok and thank you very much for the assistance. This level of support is even more than what I expected. I will check out the patch and try to use it in my end. Best regards, David
On Thu, Aug 15, 2013 at 5:07 AM, Guy Harris <g...@alum.mit.edu> wrote: > > On Aug 13, 2013, at 9:18 PM, Guy Harris <g...@alum.mit.edu> wrote: > > > On Aug 13, 2013, at 8:24 PM, DbdM Tbt <spin....@gmail.com> wrote: > > > >> I would like to update I just now used an SVN checkout of wireshark and > error C2133 will not anymore occur. > >> I was mistaken. I didn't expect that I needed the updates to other > files aside from etypes.h. > >> About my development situation is that my target is the latest release > (of which i assume, meant latest 'stable' release). > >> I will try to ask if the higher-ups will agree to using the development > version of wireshark. > >> But in the meantime, I will try to update my working copy with any > other files needed to be updated (i.e. ws_symbol_export.h was mentioned). > > > > If by "working copy" you mean your 1.10.1 tree, there are more files for > this fix than just ws_symbol_export.h, and in order for us to find what > files they are, we'd have to do the work necessary to backport the fixes in > question to the 1.10.1 tree. That might be the right thing to do. > > I tried, but the resulting version of TShark crashed when the buildbot ran > some capturing tests. > > I've attached a patch with the changes. I have no time to try to figure > out what would need to be done, so you're on your own there; note that we > don't develop C++ dissectors as part of the project, and don't guarantee > that they'll work. > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
