Hi, 

That would be an interesting idea. Now if I can get a file
handle on it.... 

Thanks,
Jaap 

On Mon, 15 Nov 2010 13:28:08 +0100,
Anders Broman  wrote:  
Hi, 
FWIW on windows I have (cygwin)flex 2.5.35
and that works. 
Jaap: Would it be possible to import the text from the
clipboard? that would make this even greater.  
Regards 
Anders


-------------------------
 FROM: [email protected]
[mailto:[email protected]] ON BEHALF OF Jaap
Keuter
SENT: den 15 november 2010 13:21
TO: Developer support list for
Wireshark
SUBJECT: Re: [Wireshark-dev] [Wireshark-commits] rev 34860:
/trunk/gtk/ /trunk/gtk/: text_import.c

Hi, 

I hear you. I'm already
taking that step back, first of all splitting text_import.h and working
without this access function so gracefully provided by newer flex
versions. 

On that matter, AFAIK your version should provide this
function. Can you have a look at text2pcap.c for instance? That should
have the function yyset_in(). 

Thanks,
Jaap 

On Mon, 15 Nov 2010
08:57:52 +0100, Pascal Quantin wrote:  

Hi

2010/11/13 Jaap Keuter 

Hi,

That seems to be the result of the flex version being used. What
platform are
you using? We'll probably need to take a step back and
rework using older
mechanisms.

I'm facing the same issue with my Debian
Lenny. Updating my flex version to 2.5.35 did not solve the
issue.

Regards,
Pascal.

Thanks,
Jaap

On 11/13/2010 05:06 PM, Martin
Mathieson wrote:
> This still doesn't fix the build for me.
> There is
an undefined reference to text_importset_in() in
>
gtk/file_import_dlg.c:504
>
> Martin
>
> On Sat, Nov 13, 2010 at 4:04
PM,  [email protected] [3]>> wrote:
>
>
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=34860
[4]
> 
>
> User: martinm
> Date: 2010/11/13 08:04 AM
>
> Log:
> Add
newline at end of file.
>
> Directory: /trunk/gtk/
> Changes Path
Action
> +1 -1 text_import.c Modified
>
>
___________________________________________________________________________
>
Sent via: Wireshark-commits mailing list


___________________________________________________________________________
Sent
via: Wireshark-dev mailing list 
Archives:
http://www.wireshark.org/lists/wireshark-dev [7]
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev [8]

mailto:[email protected] [9]?subject=unsubscribe




Links:
------
[1] mailto:[email protected]
[2]
mailto:[email protected]
[3] mailto:[email protected]
[4]
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=34860
[5]
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=34860
[6]
mailto:[email protected]
[7]
http://www.wireshark.org/lists/wireshark-dev
[8]
https://wireshark.org/mailman/options/wireshark-dev
[9]
mailto:[email protected]
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to