Bug 26166 - no "./configure" file
Summary: no "./configure" file
Status: RESOLVED NOTABUG
Alias: None
Product: fontconfig
Classification: Unclassified
Component: conf (show other bugs)
Version: 2.8
Hardware: All All
: medium normal
Assignee: Keith Packard
QA Contact: Behdad Esfahbod
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2010-01-22 07:29 UTC by robert schaefer
Modified: 2010-01-28 13:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description robert schaefer 2010-01-22 07:29:16 UTC
no "./configure" file - cannot install
Comment 1 Behdad Esfahbod 2010-01-25 14:37:18 UTC
If you checkout from git, you need to run autogen.sh.
Comment 2 robert schaefer 2010-01-26 08:28:17 UTC
Hi, Behdad,

1.  I downloaded from cgit.freedesktop.org/fontconfig. Is this "checkout from git"?
2.  running autogen is not documented in either README or INSTALL.
3. I typed "source autogen.sh" and my terminal was killed with no Makefile generated.
    (fontconfig-2.8.0)

bob schaefer


bob s.

On Jan 25, 2010, at 5:37 PM, bugzilla-daemon@freedesktop.org wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=26166
> 
> 
> Behdad Esfahbod <freedesktop@behdad.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                 CC|                            |freedesktop@behdad.org
>             Status|NEW                         |RESOLVED
>         Resolution|                            |NOTABUG
> 
> 
> 
> 
> --- Comment #1 from Behdad Esfahbod <freedesktop@behdad.org>  2010-01-25 14:37:18 PST ---
> If you checkout from git, you need to run autogen.sh.
> 
> 
> -- 
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
> 
> !DSPAM:4b5e1d1f290281565226139!
> 
Comment 3 Behdad Esfahbod 2010-01-26 09:46:09 UTC
(In reply to comment #2)
> Hi, Behdad,
> 
> 1.  I downloaded from cgit.freedesktop.org/fontconfig. Is this "checkout from
> git"?

Yes.


> 2.  running autogen is not documented in either README or INSTALL.

Fixed.


> 3. I typed "source autogen.sh" and my terminal was killed with no Makefile
> generated.
>     (fontconfig-2.8.0)

You should run it, as in "./autogen.sh", not source it.



> bob schaefer
Comment 4 robert schaefer 2010-01-26 13:50:09 UTC
Hello,
  I got farther this time, but am still having problems.

  I am using "pacman" to install fontconfig and pacman is sensitive to warnings/errors.

  This is the message returned from either "make" or "make install":

Running autoheader
Running libtoolize --copy --force
Running automake -a
configure.in: installing `./install-sh'
configure.in: installing `./missing'
doc/Makefile.am: installing `./depcomp'
doc/Makefile.am:199: `doc_DATA' is used but `docdir' is undefined

I think pacman is taking the last statement as an error and fails the
installation.

Is this a "make" fault?

bob schaefer


On Jan 26, 2010, at 12:46 PM, bugzilla-daemon@freedesktop.org wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=26166
> 
> 
> 
> 
> 
> --- Comment #3 from Behdad Esfahbod <freedesktop@behdad.org>  2010-01-26 09:46:09 PST ---
> (In reply to comment #2)
>> Hi, Behdad,
>> 
>> 1.  I downloaded from cgit.freedesktop.org/fontconfig. Is this "checkout from
>> git"?
> 
> Yes.
> 
> 
>> 2.  running autogen is not documented in either README or INSTALL.
> 
> Fixed.
> 
> 
>> 3. I typed "source autogen.sh" and my terminal was killed with no Makefile
>> generated.
>>    (fontconfig-2.8.0)
> 
> You should run it, as in "./autogen.sh", not source it.
> 
> 
> 
>> bob schaefer
> 
> 
> -- 
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
> 
> !DSPAM:4b5f2a6716750421921051!
> 
Comment 5 Behdad Esfahbod 2010-01-28 13:36:56 UTC
I have no idea what pacman is or what the problem with your build is.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.