Configure error x window system libraries and header files are required

Xfce Forum

Sub domains

You are not logged in.

#1 2011-02-04 12:24:47

XFCE 4.8 on Debian lenny: dependency hell

I am trying to build XFCE 4.8 on Debian lenny, following the build instructions at http://www.xfce.org/download/building. It appears that these instructions use rather loose names for the prerequisite packages. So far I have encountered and believe I have solved the following oddities:
— package libxfce4util requires «gobject», which appears to be provided by libglib2.0-dev
— package xfconf requires «dbus-1», which appears to be provided by libdbus-1-dev
— package xfconf requires «dbus-glib-1», which appears to be provided by libdbus-glib-1-dev
— package xfconf requires «Extutils:depends», which appears to be provided by libextutils-depends-perl
— package xfconf requires «Extutils:pkgconfig», which appears to be provided by libextutils-pkgconfig-perl

I have now hit a brick wall with package libxfce4ui. The error message from configure/make is «configure: error: X Window system libraries and header files are required». I have tried installing xserver-xorg-dev, but the error message is still there.

Does anyone have any suggestions?

As an aside, I would make the following suggestions for the whole install procedure:
— provide a tar file for download that does not contain other tar files, but rather contains the whole directory structure in a form that can be obtained with a single tar x operation
— provide a preinstall script that checks whether all dependencies are in place, and outputs a list of those that are not (as mentioned, the existing build instructions use loose names, they also present the dependencies in a structure completely unsuited to quickly getting all missing ones, and they themselves seem to be missing some packages)
— provide a wrapper script that will build each component in turn, in the correct order, so that a single command will build the entire XFCE installation
— reduce (to almost zero) the number of informational messages that come out of configure/make: it is surely only error messages that we need to see?
With all this, it may take one less than the three hours that I have needed to get to this point.

#2 2011-02-10 10:42:53

Registered: 2005-02-17 Posts: 1,144 Website

Re: XFCE 4.8 on Debian lenny: dependency hell

You probably miss the libx11 devel package.

For the tars in the tar: there is a bug about that, it is indeed inconvenient, we’re working on it.

We’re not going to provide build scripts. There are too many distros and operating systems out there and it will for sure not work with all of them. That said, it is always recommended to use the packages of your distro. There is an installer for 4.8 (http://foo-projects.org/

nick/installers/), but it is not widely tested, so feel free to let me know you experience.

The make and configure output can be reduced, there are command line options for that (probably ./configure —quiet). Anyway, other people like to see what’s being done, so not up to use what’s outputted or not.

#3 2011-02-14 03:22:42

Re: XFCE 4.8 on Debian lenny: dependency hell

Thanks for your advice, which was correct: I needed the Debian package libx11-dev.

I might just as well document the other Debian packages I have needed subsequently, for the benefit of others:
— package libxfce4ui also requires libgtk2.0-dev
— package libxfcegui4 requires requires libglade2-dev
— package libxfce4menu does not exist in the release, even though it is referred to in the build instructions
— package garcon does not exist in the release, even though it is referred to in the build instructions

. and that last one is a showstopper, since garcon is a prerequisite for other XFCE packages. I raised bug 7283 for this, against the web site build instructions. Presumably it needs to be reassigned as a bug in the release.

#4 2011-02-15 15:39:04

Registered: 2005-02-17 Posts: 1,144 Website

Источник

Debian User Forums

Error in ./configure (SOLVED)

Error in ./configure (SOLVED)

#1 Post by garrincha » 2007-01-14 15:15

I checked ‘config.log’ but it wasn’t helpful. To be sure, I tried to build a different package and I got the same error as above.

#2 Post by mzilikazi » 2007-01-14 16:02

#3 Post by garrincha » 2007-01-14 19:05

When I typed ‘which gcc’, no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.

This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.

Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.

#4 Post by mzilikazi » 2007-01-14 23:53

#5 Post by garrincha » 2007-01-15 13:06

#6 Post by mzilikazi » 2007-01-15 13:53

#7 Post by garrincha » 2007-01-15 15:37

Yes, this is the same thing. I would have apt-get install it instead however I’m trying to test the compile and build features on my etch installation as I would like to build a kernel later on. Incidentally, I downloaded another tarball kde theme and I tried to run ./configure and I got the same error output as the one for above.

#8 Post by mzilikazi » 2007-01-15 16:04

Well I may be the last person you should ask about anything KDE.
You’d have much better luck with a KDE specific forum/mailing list/chat room. Of course, if you find a resolution to your problem it would be great for you to post it so others could read it too.

Last guess — Do you have these installed?

#9 Post by garrincha » 2007-01-15 17:02

I checked, apparently I did not have these installed, so I installed these packages for the etch version in my installation. Unfortunately, it didn’t do the trick.

It is not necessarily a KDE-specific problem. As I mentioned I tried to configure and make a tarball about 2 weeks ago and I got the same error as the one I printed at the top of this trend. I just downloaded the tarball fluxbox-1.0rc2.tar.bz2 and run ./configure and I got the same error.

#10 Post by plugwash » 2007-01-15 21:08

When I typed ‘which gcc’, no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.

This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.

Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.

it looks like you have installed the compiler but not the packages that create the symlinks to the current default compiler.

there should be a package simply named gcc, you need to install it

you might also wan’t to install build-essential as there are likely to be other things that are important for building stuff that you don’t currently have installed.

Источник

Xfce Forum

Sub domains

You are not logged in.

#1 2018-08-07 01:19:04

[Solved] Can’t Build xfce4-generic-slider

No doubt my own mistake.

Extracted to a folder:

i did not edit any files.

Building and Installing — It is a simple:
make && sudo make install.

Last edited by johnywhy (2018-09-06 18:43:05)

arch xfce x86_64

#2 2018-08-09 11:20:14

Re: [Solved] Can’t Build xfce4-generic-slider

you must install autogen and or autoconf , by your distro needed packagebuild-utils they are in the repo, i not knowing mint and
ubuntus
but i packaging xfce since a few years

then you open a terminal in the opened folder where the source .tar.gz is extracted
now you type
./autogen.sh
if its ready type
./configure —help -> to see more or specified option for your build before make
— if you would other than normaly options, try
./configure —your-option —next-option.

if ready try
make
if ready try
su -> for global install and if you give ./configure the option —prefix=/usr/?/? or what ever needed

now you should have a install of the package but it is not easy to remove
so you should install all needed building-packages and use your distribution-preferred package-installer

#3 2018-08-09 13:39:32

Re: [Solved] Can’t Build xfce4-generic-slider

it is not easy to remove
so you should install all needed building-packages and use your distribution-preferred package-installer

many thx, i will try it.
but what do you mean «not easy to remove»?
the make utilities? or the slider?

Update:
i got:

i installed that package. Then i got:

However, in Synaptic it looks like i do have glib2 installed, correct?

Not sure what to do now.

Last edited by johnywhy (2018-08-09 18:19:17)

arch xfce x86_64

#4 2018-08-10 14:43:09

Re: [Solved] Can’t Build xfce4-generic-slider

it is not easy to remove
so you should install all needed building-packages and use your distribution-preferred package-installer

many thx, i will try it.
but what do you mean «not easy to remove»?
the make utilities? or the slider?

Update:
i got:

i installed that package. Then i got:

However, in Synaptic it looks like i do have glib2 installed, correct?

Not sure what to do now.

yes you have glib2 installed, but not the headerfiles of the lib, they are include on glib2-devel packages
cheers

#5 2018-08-10 18:16:23

Re: [Solved] Can’t Build xfce4-generic-slider

thx, getting closer, but no cigar. i got:

i can see in Synaptic that libxfce4ui-1 is installed.

i installed xfce4-panel-dev

got same libxfce4ui-1 error.

got same libxfce4ui-1 error.

Last edited by johnywhy (2018-08-10 20:11:42)

arch xfce x86_64

#6 2018-08-11 18:55:04

Re: [Solved] Can’t Build xfce4-generic-slider

checking for libxfce4ui-1 >= 4.12.0. not found

There should be a package like «libxfce4ui-1-dev» in the repositories. You need to install that one.

#7 2018-08-11 21:42:17

Re: [Solved] Can’t Build xfce4-generic-slider

That worked! How did you know, ToZ?

After `./autogen.sh`, i did `make`. That seemed to work too.
Now, how to install the slider to a panel?

Last edited by johnywhy (2018-08-11 21:43:25)

arch xfce x86_64

#8 2018-08-12 00:27:56

Re: [Solved] Can’t Build xfce4-generic-slider

That worked! How did you know, ToZ?

The hint is in the error message. Debian-based distros separate the binary and development packages — usually appending «-dev» to the development ones.

After `./autogen.sh`, i did `make`. That seemed to work too.
Now, how to install the slider to a panel?

Because debian-based distros split the 32 and 64-bit library destinations, you need to specify the correct library location. Also, you can combine the «autogen.sh» and «configure» commands into one set.

Run this command:

However, if you’re running this on Mint 19, it won’t work. For some reason, Mint isn’t packaging the libxfce4panel-1.0 development/pc files that are required. It’s only providing the newer libxfce4panel-2.0 files and the generic slider is still built on the previous (ie. not upgraded to gtk3 yet).

#9 2018-08-12 00:53:44

Re: [Solved] Can’t Build xfce4-generic-slider

As Mint is Ubuntu-based, is there a PPA that would have that file? Or another location to download it from?

And how likely is it that a person could cause problems by using such (versions of) files, when they’re not already available? Dependency Hell?

Mountain Dew Maniac

#10 2018-08-12 01:18:55

Re: [Solved] Can’t Build xfce4-generic-slider

@MDM, not that I’m aware of. It’s interesting that Mint does it this way.

#11 2018-08-12 03:32:35

Re: [Solved] Can’t Build xfce4-generic-slider

However, if you’re running this on Mint 19, it won’t work.

you mean, no way to use the slider plugin on Mint 19?

arch xfce x86_64

#12 2018-08-12 04:30:36

Re: [Solved] Can’t Build xfce4-generic-slider

You might try to get Clem to add the older version of the libxfce4panel-1.0 development/pc files or the newer version of the generic slider (if one exists). Or to just compile the end product for us.

Mountain Dew Maniac

#13 2018-08-12 11:35:03

Re: [Solved] Can’t Build xfce4-generic-slider

However, if you’re running this on Mint 19, it won’t work.

you mean, no way to use the slider plugin on Mint 19?

I see you created a bug report on the Xfce bug tracker. This is not the correct place for the bug report — you should report it to the Mint bug tracker. They need to provide both the libxfce4panel-1.0 and libxfce4panel-2.0 libraries and development files/headers.

Edit: Although, based on what you posted to the bug tracker, it looks like it worked for you. You did this on Mint 19, right?

Last edited by ToZ (2018-08-12 11:37:09)

#14 2018-08-12 12:26:55

Re: [Solved] Can’t Build xfce4-generic-slider

Okay, my bad. Mint has the development files separated into 2 packages (xfce4-panel-dev & libxfce4panel-2-dev). It will work if both are installed.

So basically @johnywhy, there are two ways to do this:

1. The «make» way:
Run the following commands:

. and then add the panel plugin to the panel. However, this manual method makes it difficult to track the package using apt/dpkg and may lead to problems down the road.

2. The proper debian-based method of creating packages. See: https://coderwall.com/p/urkybq/how-to-c … rom-source

#15 2018-08-12 14:39:05

Re: [Solved] Can’t Build xfce4-generic-slider

Can you break down those switches?

problems down the road.

For the slider, the OS, or either?

arch xfce x86_64

#16 2018-08-12 16:27:03

Re: [Solved] Can’t Build xfce4-generic-slider

Can you break down those switches?

«—prefix» — means where to install to. Default is /usr/local. Most distros use «/usr».
«—libdir» — means where to install the libraries. For debian-based distros this needs to go to the appropriate architecture location which can be determined by «/usr/lib/`uname -m`-linux-gnu»
«—disable-static» — as I understand it, it means create dynamically-linkable shared libraries that can be loaded once and shared amongst many calling programs. For example, if you added 2 slider plugins to your panel, they would share the same plugin library instead of each loading its own. Its a more efficient use of space and memory.
«—disable-debug» — means don’t include debug information into the compiled programs. Alternatively, if you want extra debug information (in case you are trying to debug a problem, you would use «—enable-debug».

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

X Window System libraries and headers

X Window System libraries and headers

Сообщение kew » 07.03.2005 13:08

не могу поставить fluxbox. при ./configure пишет

у меня ASP Linix 10. Пробовал ставить разные rpm с названием иксов и тех самых libraries которых якобы нет. безполезно. одна рпм требует другую, та другая ещё 10 итд.
что делать. помогите чайнику =) если можно, поподробнее.
спасибо.

Re: X Window System libraries and headers

Сообщение alv » 07.03.2005 13:21

(kew @ Понедельник, 07 Марта 2005, 13:08) писал(а): не могу поставить fluxbox. при ./configure пишет

у меня ASP Linix 10. Пробовал ставить разные rpm с названием иксов и тех самых libraries которых якобы нет. безполезно. одна рпм требует другую, та другая ещё 10 итд.
что делать. помогите чайнику =) если можно, поподробнее.
спасибо.

Ну чем тут можно помочь — разве что посочувствовать — с rpm’ами завсегда так. Хотя врде в ASP’е yum должен быть — он зависимости отслеживает

Re: X Window System libraries and headers

Сообщение polachok » 07.03.2005 13:29

Re: X Window System libraries and headers

Сообщение kew » 12.03.2005 05:47

Re: X Window System libraries and headers

Сообщение demongloom » 12.03.2005 22:13

а потому что флуд развели. рпм тут не причем, зависимости и библиотеки для разработки есть и дебе. а конфигурЪ сам никаким макаром их скачать не может, он только скажет чего не хватает.

посмотри в составе пакетов дистрибутива пакеты с названиями xfree86* (xorg) и devel.
В названии пакета «devel» означает что содержит файлы требуемые для сборки других приложений использующие это приложение. Тебе нужны девелы от Х-сов.

Источник

Debian User Forums

Error in ./configure (SOLVED)

Error in ./configure (SOLVED)

#1 Post by garrincha » 2007-01-14 15:15

I checked ‘config.log’ but it wasn’t helpful. To be sure, I tried to build a different package and I got the same error as above.

#2 Post by mzilikazi » 2007-01-14 16:02

#3 Post by garrincha » 2007-01-14 19:05

When I typed ‘which gcc’, no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.

This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.

Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.

#4 Post by mzilikazi » 2007-01-14 23:53

#5 Post by garrincha » 2007-01-15 13:06

#6 Post by mzilikazi » 2007-01-15 13:53

#7 Post by garrincha » 2007-01-15 15:37

Yes, this is the same thing. I would have apt-get install it instead however I’m trying to test the compile and build features on my etch installation as I would like to build a kernel later on. Incidentally, I downloaded another tarball kde theme and I tried to run ./configure and I got the same error output as the one for above.

#8 Post by mzilikazi » 2007-01-15 16:04

Well I may be the last person you should ask about anything KDE.
You’d have much better luck with a KDE specific forum/mailing list/chat room. Of course, if you find a resolution to your problem it would be great for you to post it so others could read it too.

Last guess — Do you have these installed?

#9 Post by garrincha » 2007-01-15 17:02

I checked, apparently I did not have these installed, so I installed these packages for the etch version in my installation. Unfortunately, it didn’t do the trick.

It is not necessarily a KDE-specific problem. As I mentioned I tried to configure and make a tarball about 2 weeks ago and I got the same error as the one I printed at the top of this trend. I just downloaded the tarball fluxbox-1.0rc2.tar.bz2 and run ./configure and I got the same error.

#10 Post by plugwash » 2007-01-15 21:08

When I typed ‘which gcc’, no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.

This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.

Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.

it looks like you have installed the compiler but not the packages that create the symlinks to the current default compiler.

there should be a package simply named gcc, you need to install it

you might also wan’t to install build-essential as there are likely to be other things that are important for building stuff that you don’t currently have installed.

Источник

Debian Bug report logs — #533935
xfmedia: FTBFS: configure: error: X Window system libraries and header files are required

Date: Sun, 21 Jun 2009 15:21:51 UTC

Found in version xfmedia/0.9.2-6

Fixed in version xfmedia/0.9.2-7

Done: Yves-Alexis Perez

Bug is archived. No further changes may be made.

Report forwarded to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers

:
Bug#533935 ; Package xfmedia . (Sun, 21 Jun 2009 15:21:53 GMT) (full text, mbox, link).

Acknowledgement sent to Lucas Nussbaum :
New Bug report received and forwarded. Copy sent to Debian Xfce Maintainers

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers

:
Bug#533935 ; Package xfmedia . (Mon, 22 Jun 2009 17:09:06 GMT) (full text, mbox, link).

Acknowledgement sent to peter green

:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers

Tags added: patch Request was from peter green

to control@bugs.debian.org . (Mon, 22 Jun 2009 17:09:09 GMT) (full text, mbox, link).

Reply sent to Yves-Alexis Perez :
You have taken responsibility. (Wed, 01 Jul 2009 17:51:17 GMT) (full text, mbox, link).

Notification sent to Lucas Nussbaum :
Bug acknowledged by developer. (Wed, 01 Jul 2009 17:51:17 GMT) (full text, mbox, link).

—> Bug archived. Request was from Debbugs Internal Request to internal_control@bugs.debian.org . (Thu, 30 Jul 2009 07:37:58 GMT) (full text, mbox, link).

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.

Источник

Thread: Compiling fluxbox in Debian, error: requires the X Window libraries and headers

Thread Tools

Display

Compiling fluxbox in Debian, error: requires the X Window libraries and header

*** This problem is now solved ***
Thank you for your interest!

I was curious about installing Debian because I’ve heard many people talking about how good it is.
I used LordSutch mini-ISO to get a slim install, and then I used dselect to add what I needed, downloading it from the net.
Everything fine so far, but (there’s always a but. ):

I want to compile fluxbox from source (so I can add ‘remember-patch’).
When I run the configure script I get this error:
configure: error: Fluxbox requires the X Window System libraries and headers

Ok, so I figure I only need to use apt-get and download XFree86-devel (as it’s called in RedHat) but I can’t seem to find it.
From what I can see, Debian calls the X-packages xserver-* but I can’t seem to find any ‘xserver-xfree86-devel’ or ‘xserver-devel’.

I already have these packages installed:
xserver-common_4.1.0-16_i386.deb
xserver-xfree86_4.1.0-16_i386.deb

I checked packages.debian.org to see if I could get a clue of what the packages are called, but I couldn’t find any of interest besides the ones I already have.
I also checked the homepage of XFree86 to see if they had any binaries for Debian, but no such luck.

So, anyone have any suggestions to how I can add X libraries and headers in Debian. or am I digging in the wrong hole here?
Any suggestions would be much appreciated since I’m a complete n00b with Debian!

Last edited by apeekaboo; 12-08-2002 at 05:37 PM .

Debian GNU/Linux Posts 77

Use the search function on that page to find fluxbox, it will tell you the dependencies. Depending on the version of FB you are using you may need to change your sources list to the unstable or testing branches. Searching on the stable branch gave me this result:
http://packages.debian.org/stable/x11/fluxbox.html

If that’s not your version, search on the «unstable» and «testing » branches. Keep in mind that installing the latest and greatest (and their dependencies) can sometimes break a «stable» install. I use my box for work, so I stick with stable.

edit: BTW, the way, do yourself a favor and apt-get install synaptic. It’s a great gui browser and front end for apt-get, lets you see what you have installed and what’s available from your sources list. Must be run from su.

Last edited by Joe_Atlanta; 12-08-2002 at 12:54 PM .

Ok, synaptic seems like a good idea to install.

But I think you missunderstood me.
It’s not fluxbox I want to install from a package and when fluxbox is installed from package I don’t need the development kit for X (at least not in RedHat. )
I need to install fluxbox from source so I can patch it first.

will show you dependencies for a binary install. Not sure how to check for extras needed by source.
I believe Debian uses «dev» rather than «devel»
dpkg —list *dev*
will list «dev» packages available for install.

the solution

Aaaaaahhh.. Thanks guys, you are the greatest!

After doing some variants on
# dpkg —list *lib* |less
and
# dpkg —list *dev* |less

I decided that this package looked like a safe bet:
xlibs-dev 4.1.0-16 X Window System client library development

After doing an
# apt-get install xlibs-dev
I was able to configure and make the fluxbox source.

# which fluxbox
/usr/local/bin/fluxbox
showed that the binary was in place

After adding ‘exec /usr/local/bin/fluxbox’ to

/.xinitrc I was able to start fluxbox with startx.

Debian GNU/Linux Posts 77

Hey, congrats, welcome to Debian. Main thing I’ve had to keep in mind is that the different «branches» (stable, testing, and unstable) don’t always work together. To install the latest, greatest anything on stable (Woody) can be a chore. That being said, here’s a fun link, unofficial apt depositories.

BTW, how was the install with Lord Sutch?

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

X Window System library and headers?

Post by nick » Fri Jul 20, 2007 10:04 am

Have you tried installing xorg-dev and xlibs-dev from Synaptic?

Post by nick » Fri Jul 20, 2007 12:41 pm

First, it is an Alpha package, if you mean LainWM-1.3Alpha.tar.gz, so there usually is problems.

It does compile on my box:

/LainWM-1.3Alpha$ ./configure
checking for a BSD-compatible install. /usr/bin/install -c
checking whether build environment is sane. yes
/home/nick/LainWM-1.3Alpha/missing: Unknown `—run’ option
Try `/home/nick/LainWM-1.3Alpha/missing —help’ for more information
configure: WARNING: `missing’ script is too old or missing
checking for gawk. gawk
checking whether make sets $. yes
checking for gcc. gcc
checking for C compiler default output. a.out
checking whether the C compiler works. yes
checking whether we are cross compiling. no
checking for suffix of executables.
checking for suffix of object files. o
checking whether we are using the GNU C compiler. yes
checking whether gcc accepts -g. yes
checking for style of include used by make. GNU
checking dependency style of gcc. gcc3
checking for g++. g++
checking whether we are using the GNU C++ compiler. yes
checking whether g++ accepts -g. yes
checking dependency style of g++. gcc3
checking for a BSD-compatible install. /usr/bin/install -c
checking for sed. sed
checking for freetype-config. freetype-config
checking how to run the C preprocessor. gcc -E
checking for ANSI C header files. yes
checking for sys/types.h. yes
checking for sys/stat.h. yes
checking for stdlib.h. yes
checking for string.h. yes
checking for memory.h. yes
checking for strings.h. yes
checking for inttypes.h. yes
checking for stdint.h. yes
checking for unistd.h. yes
checking ctype.h usability. yes
checking ctype.h presence. yes
checking for ctype.h. yes
checking dirent.h usability. yes
checking dirent.h presence. yes
checking for dirent.h. yes
checking fcntl.h usability. yes
checking fcntl.h presence. yes
checking for fcntl.h. yes
checking libgen.h usability. yes
checking libgen.h presence. yes
checking for libgen.h. yes
checking locale.h usability. yes
checking locale.h presence. yes
checking for locale.h. yes
checking nl_types.h usability. yes
checking nl_types.h presence. yes
checking for nl_types.h. yes
checking process.h usability. no
checking process.h presence. no
checking for process.h. no
checking signal.h usability. yes
checking signal.h presence. yes
checking for signal.h. yes
checking stdarg.h usability. yes
checking stdarg.h presence. yes
checking for stdarg.h. yes
checking stdio.h usability. yes
checking stdio.h presence. yes
checking for stdio.h. yes
checking for stdlib.h. (cached) yes
checking for string.h. (cached) yes
checking time.h usability. yes
checking time.h presence. yes
checking for time.h. yes
checking for unistd.h. (cached) yes
checking sys/param.h usability. yes
checking sys/param.h presence. yes
checking for sys/param.h. yes
checking sys/select.h usability. yes
checking sys/select.h presence. yes
checking for sys/select.h. yes
checking sys/signal.h usability. yes
checking sys/signal.h presence. yes
checking for sys/signal.h. yes
checking for sys/stat.h. (cached) yes
checking sys/time.h usability. yes
checking sys/time.h presence. yes
checking for sys/time.h. yes
checking for sys/types.h. (cached) yes
checking sys/wait.h usability. yes
checking sys/wait.h presence. yes
checking for sys/wait.h. yes
checking whether time.h and sys/time.h may both be included. yes
checking for basename. yes
checking for getpid. yes
checking for setlocale. yes
checking for sigaction. yes
checking for strftime. yes
checking for strcasestr. yes
checking for snprintf. yes
checking for vsnprintf. yes
checking for catopen. yes
checking for catgets. yes
checking for catclose. yes
checking for t_open in -lnsl. no
checking for socket in -lsocket. no
checking for X. libraries , headers
checking for gethostbyname. yes
checking for connect. yes
checking for remove. yes
checking for shmat. yes
checking for IceConnectionNumber in -lICE. yes
checking for GCC. yes
checking for XOpenDisplay in -lX11. yes
checking whether to build support for the XShape extension. yes
checking for XShapeCombineShape in -lXext. yes
checking for X11/extensions/shape.h. yes
checking whether to include Pseudocolor ordered dithering code. no
checking whether to include verbose debugging code. no
checking whether to include NLS support. yes
checking for setlocale in -lxpg4. no
checking for gencat. gencat
checking whether to use the new timed pixmap cache. yes
checking return type of signal handlers. void
checking whether to enable maintainer-specific portions of Makefiles. no

lainwm version 1.3.0 configured successfully.

Using ‘/usr/local’ for installation.
Using ‘g++’ for C++ compiler.
Building with ‘-g -O2 -I/usr/include/freetype2 -Wall -W -pedantic’ for C++ comp
iler flags.
Building with ‘ -lfreetype -lz -lX11 -lXft -lXext’ for linker flags.

Источник

Reported by: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Date: Sun, 21 Jun 2009 15:21:51 UTC

Severity: serious

Tags: patch

Found in version xfmedia/0.9.2-6

Fixed in version xfmedia/0.9.2-7

Done: Yves-Alexis Perez <corsac@debian.org>

Bug is archived. No further changes may be made.

Report forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#533935; Package xfmedia.
(Sun, 21 Jun 2009 15:21:53 GMT) (full text, mbox, link).

Acknowledgement sent
to Lucas Nussbaum <lucas@lucas-nussbaum.net>:
New Bug report received and forwarded. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Sun, 21 Jun 2009 15:21:53 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>:
Bug#533935; Package xfmedia.
(Mon, 22 Jun 2009 17:09:06 GMT) (full text, mbox, link).

Acknowledgement sent
to peter green <plugwash@p10link.net>:
Extra info received and forwarded to list. Copy sent to Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>.
(Mon, 22 Jun 2009 17:09:06 GMT) (full text, mbox, link).

Tags added: patch
Request was from peter green <plugwash@p10link.net>
to control@bugs.debian.org.
(Mon, 22 Jun 2009 17:09:09 GMT) (full text, mbox, link).

Tags added: pending
Request was from Anibal Monsalve Salazar <anibal@debian.org>
to control@bugs.debian.org.
(Wed, 24 Jun 2009 08:18:04 GMT) (full text, mbox, link).

Reply sent
to Yves-Alexis Perez <corsac@debian.org>:
You have taken responsibility.
(Wed, 01 Jul 2009 17:51:17 GMT) (full text, mbox, link).

Notification sent
to Lucas Nussbaum <lucas@lucas-nussbaum.net>:
Bug acknowledged by developer.
(Wed, 01 Jul 2009 17:51:17 GMT) (full text, mbox, link).

Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Thu, 30 Jul 2009 07:37:58 GMT) (full text, mbox, link).

Модератор: Модераторы разделов

бла бла
бла...
checking for X... no
configure: error: Fluxbox requires the X Window System libraries and headers.