Re: Problem when making index in /usr/ports

From: Norberto Meijome (freebsd_at_meijome.net)
Date: 08/31/05

  • Next message: Ronald Klop: "mount_msdosfs gives read-only error" 
    Date: Thu, 01 Sep 2005 02:47:34 +1000
To: bsd <bsd@todoo.biz>

    bsd wrote:
    > Hello,
    >

    >> root:newmail 12:16 /usr/ports # make index
    >> Generating INDEX-5 - please wait..p5-Unicode-MapUTF8-1.09: "/usr/
    >> ports/japanese/p5-Jcode" non-existent -- dependency list incomplete
    >> ===> converters/p5-Unicode-MapUTF8 failed
    >> *** Error code 1
    >> 1 error
    >>
    >> ********************************************************************
    >> Before reporting this error, verify that you are running a supported
    >> version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
    >> have a complete and up-to-date ports collection. (INDEX builds are
    >> not supported with partial or out-of-date ports collections -- in
    >> particular, if you are using cvsup, you must cvsup the "ports-all"
    >> collection, and have no "refuse" files.) If that is the case, then
    >> report the failure to ports@FreeBSD.org together with relevant
    >> details of your ports configuration (including FreeBSD version,
    >> your architecture, your environment, and your /etc/make.conf
    >> settings, especially compiler flags and WITH/WITHOUT settings).
    >>

    make sure you dont' have the japanese tree excluded via
    /usr/local/sup/refuse. these dependencies are the main reason I gave up
    on refuse files and started using pkgtools.conf and the port* tools.
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

  • Next message: Ronald Klop: "mount_msdosfs gives read-only error"

    Relevant Pages

    • Re: portsdb error
      ... > Understudy wrote: ... >>Before reporting this error, verify that you are running a supported ... >>report the failure to ports@FreeBSD.org together with relevant ...
      (comp.unix.bsd.freebsd.misc)
    • Re: 1352 NUL bytes at the end of a page?
      ... Andrew Morton wrote: ... >> We've got a user who's reporting BK problems which we've traced down to ... >> correct file data picks up again after the hole. ... at the same time as the bk failure, ...
      (Linux-Kernel)
    • Re: [Lit.] Buffer overruns
      ... percent of failures/exploits for the specific environment that are ... detailed study of the reported types of failures and the failure ... occurances of a specific failure cause to a single failure reporting ... and/or using pointers after the related operations had all be ...
      (sci.crypt)
    • Re: dts Logging
      ... errorFlag is True and package is reporting a failure to the GUI. ... DTSPackageLog.WriteStringToLog errMsg ... > www.SQLDTS.com - The site for all your DTS needs. ...
      (microsoft.public.sqlserver.dts)
    • Re: Disc error 13
      ... > in verify function which is available via the *verify command or from the ... reporting the same ... and used the defect command to map ...
      (comp.sys.acorn.hardware)