Dana 13.11.2012 22:26, Fernando de Oliveira je napisao: > --- Em ter, 13/11/12, Armin K. <kre...@email.com> escreveu: > >> De: Armin K. <kre...@email.com> >> Assunto: Re: [blfs-dev] libsoup-2.40.1 >> Para: "BLFS Development List" <blfs-dev@linuxfromscratch.org> >> Data: Terça-feira, 13 de Novembro de 2012, 18:01 >> Dana 13.11.2012 21:43, Fernando de >> Oliveira je napisao: >>> --- Em ter, 13/11/12, Armin K. escreveu: >>> >>>> De: Armin K. <kre...@email.com> >>>> Assunto: Re: [blfs-dev] libsoup-2.40.1 >>>> Para: "BLFS Development List" >>>> Data: Terça-feira, 13 de Novembro de 2012, 16:33 >>>> On 11/13/2012 06:01 PM, Fernando de >>>> Oliveira wrote: >>>>> >>>>> Armin, I have it erased, glib-2.34.1 installed, >> so >>>> libsoup-2.40.1 has configured , mde and installed >> properly. >>>>> >>>>> Thus, I have trimmed a copy of the whole build >> log to >>>> just the first unfinished one and attached, perhaps >> it will >>>> be enough. >>>>> >>>> >>>> Apparently you were missing either glib pkg-config >> files >>>> (.pc ones) or >>>> development headers. This was error in your >> config.log >>>> >>>> configure:12019: checking for GLIB - version >= >> 2.33.1 >>>> configure:12152: result: no >>>> configure:12180: gcc -o conftest -g -O2 >>>> conftest.c >&5 >>>> conftest.c:24:18: fatal error: glib.h: No such file >> or >>>> directory >>>> >>>> Glad you've fixed it. >>> >>> Thanks, Armin, for your attention. >>> >>> But they both are there (I left VMWLFS7.1 with libsoup >> in its older >>> version for a while, to discuss better this matter): >>> >>> $ find /usr -name glib.h -exec ls -lh {} \; -o >> -name glib\*.pc -exec ls -lh {} \; 2>/dev/null >>> -rw-r--r-- 1 root root 3,3K Mai 8 2012 >> /usr/include/glib-2.0/glib.h >>> -rw-r--r-- 1 root root 392 Mai 8 2012 >> /usr/lib/pkgconfig/glib-2.0.pc >>> -rw-r--r-- 1 root root 579 Abr 17 2012 >> /usr/lib/pkgconfig/glibmm-2.4.pc >>> >>> Problem was with the version, as I understood in the >> first reference to >>> the error. That is the reason I upgraded it, so fixed >> the problem. >>> >>> My real question is related to the libsoup's "Required" >> section in the >>> book. >>> >>> If a package A cannot be built for some dependency B is >> missing or >>> obsolete, should not it be included as required >> directly? >>> >>> I did not need to upgrade any other dependency, just >> glib-2.32.3 to >>> glib-2.34.1. >>> >>> []s, >>> Fernando >>> >> >> It really depends on a package. If you are upgrading, I >> suggest that you >> upgrade everything or you might get strange results at >> runtime. >> >> Required packages ARE required, recommended are recommended >> and you're >> on your own if you don't install some of them. The >> instructions are >> originaly meant to pick up where LFS left off, so we set >> dependencies >> according to it. > > Sorry, I have not made myself clear yet: > > I am just following the book. But libsoup could not be installed without > glib. > > I think glib should be *required* in libsoup. It cannot be built without > glib. At this moment, it is not in the required list in that page. > > Configure script looks for it. > > []s, > Fernando >
We tend to use "dependency chains". On libsoup page it says that it depends on glib-networking. glib-networking itself depends on gsettings-desktop-schemas gsettings-desktop-schemas depends on glib. So, you should have had glib installed before you've built libsoup or you didn't build mentioned deps. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page