bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error: redefinition of 'struct option'


From: Bruno Haible
Subject: Re: error: redefinition of 'struct option'
Date: Thu, 18 Feb 2010 11:29:53 +0100
User-agent: KMail/1.9.9

Hi Bruce,

> My build procedure is to blow away the build tree, copy in the
> repository source files and do the build.  It doesn't get any cleaner.

Can you give us a recipe how to reproduce it? In the worst case, you can
do a "make distclean", tar up your source tarball on some site and let us
investigate.

I tried it like this:
  - Checked out the sharutils CVS according to the instructions on
    http://savannah.gnu.org/cvs/?group=sharutils
  - Installed autogen 5.9.8
  - $ ./bootstrap

    This resulted in some messages:
      Replacing file lib/inttostr.c (non-gnulib code backed up in 
lib/inttostr.c~) !!
      Replacing file lib/inttostr.h (non-gnulib code backed up in 
lib/inttostr.h~) !!
      Replacing file lib/offtostr.c (non-gnulib code backed up in 
lib/offtostr.c~) !!
      Replacing file lib/xalloc.h (non-gnulib code backed up in lib/xalloc.h~) 
!!
      Replacing file lib/xgetcwd.c (non-gnulib code backed up in 
lib/xgetcwd.c~) !!
      Replacing file lib/xgetcwd.h (non-gnulib code backed up in 
lib/xgetcwd.h~) !!
      Replacing file lib/xmalloc.c (non-gnulib code backed up in 
lib/xmalloc.c~) !!
    This means that you can probably remove these files from your CVS 
repository.

    It ended with
      autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.ac
                     file requires the infrastructure from gettext-0.18-pre8 
but this version
                     is older. Please upgrade to gettext-0.18-pre8 or newer.
      autopoint: *** Stop.
      autoreconf: autopoint failed with exit status: 1
      chmod: Zugriff auf „COPYING“ nicht möglich: Datei oder Verzeichnis nicht 
gefunden
      chmod: Zugriff auf „INSTALL“ nicht möglich: Datei oder Verzeichnis nicht 
gefunden
      chmod: Zugriff auf „doc/texinfo.tex“ nicht möglich: Datei oder 
Verzeichnis nicht gefunden
    This was because I have gettext prereleases installed. I worked around it 
by changing
    the version number to 0.17 and disabling the corresponding part of 
bootstrap.

  - $ ./bootstrap
    bash: ./bootstrap: Keine Berechtigung

    This was because the bootstrap script contains a "chmod ugo-x" command that 
has the
    effect that you can run 'bootstrap' only once. I worked around it by doing
    "chmod a+x bootstrap".

  - $ ./bootstrap
    This time it got to completion, but gave a number of autoconf related 
warnings.
    In particular:
      $ autoconf
      configure.ac:98: warning: gl_FUNC_GLIBC_UNLOCKED_IO was called before 
gl_LOCK_EARLY_BODY
      m4/lock.m4:29: gl_LOCK_EARLY_BODY is expanded from...
      m4/lock.m4:22: gl_LOCK_EARLY is expanded from...
      m4/lock.m4:253: gl_LOCK is expanded from...
      m4/intl.m4:186: gt_INTL_SUBDIR_CORE is expanded from...
      m4/intl.m4:25: AM_INTL_SUBDIR is expanded from...
      m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from...
      configure.ac:98: the top level
    I worked around it by moving the two lines
      AM_GNU_GETTEXT
      AM_GNU_GETTEXT_VERSION([0.17])
    between gl_EARLY and gl_INIT.

  - Then I could configure and make the package (with builddir = srcdir),
    with no error.

  - "make check" resulted in 1 failed test:

      *** shar-1-27710.sample 2010-02-18 11:13:32.000000000 +0100
      --- shar-1-27710.outf   2010-02-18 11:13:32.000000000 +0100
      ***************
      *** 1,5 ****
        #!/bin/sh
      ! # This is a shell archive (produced by GNU GNU sharutils 4.7.1).
        # To extract the files from this archive, save it to some FILE, remove
        # everything before the `#!/bin/sh' line above, then type `sh FILE'.
        #
      --- 1,5 ----
        #!/bin/sh
      ! # This is a shell archive (produced by GNU sharutils 4.7.1).
        # To extract the files from this archive, save it to some FILE, remove
        # everything before the `#!/bin/sh' line above, then type `sh FILE'.
        #
      FAIL: shar-1

  - A VPATH build worked the same way.

In summary, I don't know how to reproduce your problem.

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]