fnmatch version with and without FNM_EXTMATCH

setupray · #1 14-Jun-2004, 10:55

Hello,

please help!!!

I am a newbie to programming..in C

recently I have downloaded an open source code that was orginally ran in debian linux,

But, my uni only support Sun soloaris unix.

Everything seems to be ok...until

the open source code used fnmatch that used FNM_EXTMATCh flag.

The library of sun soloaris only has fnmatch ver 1.3, which does not have the FNM_EXTMATCH flag stuff.

Please help...what is the best way to solve this problem, please.

yours sincerely,

littel ray

aaroncohn · #2 14-Jun-2004, 11:27

WELCOME! I'm so glad you've found our forums. However, I really don't understand what your problem is. It appears that English is not your first language, so I'll go easy on you, but this problem really needs more explanation before a detailed answer can be given. So far the only conflict I see is between the debian fnmatch version and your operating system. Install the latest version of fnmatch for your operating system, or port their code to Solaris so that it'll run on your system. Why did you download the debian version, anyway?

setupray · #3 14-Jun-2004, 22:08

Sorry, I had left UK for almost three years now, so my English is a little small.

The aurthor of the program orginally build it on Debian Linux.

Now I am trying to use thie program on a solaris machine in my University.

The program used a library called fnmatch.h, which requires this FNM_EXTMATCH flag.

The version of fnmatch.h located in the soloaris machine is ver 1.3, which does not have the FNM_EXTMATCH.

I am not sure, which version is eariler.

I don't know where I guess you suggestion on downloading the fnmatch library is a good solution, but I am not too sure where I can download just that? Can you help me please.

yours sincerely,

little ray

Quote:

Originally Posted by aaroncohn

WELCOME! I'm so glad you've found our forums. However, I really don't understand what your problem is. It appears that English is not your first language, so I'll go easy on you, but this problem really needs more explanation before a detailed answer can be given. So far the only conflict I see is between the debian fnmatch version and your operating system. Install the latest version of fnmatch for your operating system, or port their code to Solaris so that it'll run on your system. Why did you download the debian version, anyway?

aaroncohn · #4 14-Jun-2004, 22:56

I've only done a small amount of searching, but it appears that 1.3 is the latest version.

dsmith · #5 15-Jun-2004, 08:11

Hi Little Ray.

What is the context in which FNM_EXTMATCH is used in this program? I think that you may want to look at what it is trying to do and see if you can get around it. Here is the definition of FNM_EXTMATCH from a linux system:

CPP / C++ / C Code:

#if !defined _POSIX_C_SOURCE || _POSIX_C_SOURCE < 2 || defined _GNU_SOURCE
# define FNM_FILE_NAME	 FNM_PATHNAME	/* Preferred GNU name.  */
# define FNM_LEADING_DIR (1 << 3)	/* Ignore `/...' after a match.  */
# define FNM_CASEFOLD	 (1 << 4)	/* Compare without regard to case.  */
# define FNM_EXTMATCH	 (1 << 5)	/* Use ksh-like extended matching. */
#endif

So it is using a Korn Shell extended matching. Having never used ksh, I am not sure of what this is exactly, but it may not be available in the Sun system. Anyway, if we could see the context of the call, perhaps we could see why it is important to use FNM_EXTMATCH.

setupray · #6 18-Jun-2004, 05:00

The original code was not writtne by me.
I can barely understand why.
I think its because it content some ksh structure in the string to be compare.
I think the simiplest way is to find a complete version of fnmatch.h for sun that support FNM_EXTMATCH. Does any one know where I can download that please?

little ray

the code below is part of the extraction from near the FNM_EXTMATCH of the source code.

CPP / C++ / C Code:

      if (strcmp(temptd->state,"@(any)")==0 ||
          strcmp(temptd->state,"@(*)")==0)
      {
        fprintf(cfile,"1 ");
      }
      else
      {
        the_first = 1;
        temps = my_states;
        while (temps)
        {
          if (fnmatch(temptd->state,temps->base_state_name,FNM_EXTMATCH)==0)
          {
            if (!the_first) fprintf(cfile, " ||");
            else the_first = 0;
            fprintf(cfile, " fsm == %s ",temps->state_name);
          }

Quote:

Originally Posted by dsmith

Hi Little Ray.

What is the context in which FNM_EXTMATCH is used in this program? I think that you may want to look at what it is trying to do and see if you can get around it. Here is the definition of FNM_EXTMATCH from a linux system:

CPP / C++ / C Code:

#if !defined _POSIX_C_SOURCE || _POSIX_C_SOURCE < 2 || defined _GNU_SOURCE
# define FNM_FILE_NAME	 FNM_PATHNAME	/* Preferred GNU name.  */
# define FNM_LEADING_DIR (1 << 3)	/* Ignore `/...' after a match.  */
# define FNM_CASEFOLD	 (1 << 4)	/* Compare without regard to case.  */
# define FNM_EXTMATCH	 (1 << 5)	/* Use ksh-like extended matching. */
#endif

So it is using a Korn Shell extended matching. Having never used ksh, I am not sure of what this is exactly, but it may not be available in the Sun system. Anyway, if we could see the context of the call, perhaps we could see why it is important to use FNM_EXTMATCH.

dsmith · #7 18-Jun-2004, 08:05

This seems to be a GNU C library specific flag. You can get the entire library here. You could then try to compile only the fnmatch object files and see if you could make your own fnmatch version. This does not seem to be available as a single library.

That is why this works on gnu/linux, because it uses the gnu C library. While fnmatch is a standard routine, the gnu C library has "extended" it to include this flag. While this is a nice feature, it is going to break across other *nixes, unless you can use the Gnu C Library.

Sorry. If you knew more about why the FNM_EXTMATCH was needed, you may be able to write around it.

setupray · #8 20-Jun-2004, 09:21

Thanks for the link to the library, I 'll give it a try, see if I can drag the fnmatch library out.

I wanted to write around it as well, but I didn't wrote the code. Also, its very complicated. First of all the code is generated by from a yacc file to start with...then, it builds a compiler that compile .mac script file, then, from than script file it can either generates ns-2 script or c++ script. I can barely understand the concept, never mind trying to go around it

I'll try it out, if it doesn't work. I'll ask agian.

little ray

Quote:

Originally Posted by dsmith

This seems to be a GNU C library specific flag. You can get the entire library ftp.gnu.org. You could then try to compile only the fnmatch object files and see if you could make your own fnmatch version. This does not seem to be available as a single library.

That is why this works on gnu/linux, because it uses the gnu C library. While fnmatch is a standard routine, the gnu C library has "extended" it to include this flag. While this is a nice feature, it is going to break across other *nixes, unless you can use the Gnu C Library.

Sorry. If you knew more about why the FNM_EXTMATCH was needed, you may be able to write around it.

:-(

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Rate This Thread
Rate This Thread:

fnmatch version with and without FNM_EXTMATCH

Fnm_extmatch

Why FNM_EXTMATCH

Don't know where to begin...