Re: [blfs-dev] wget and curl built without OpenSSL.
On 04/26/2014 02:07 PM, TheOldFellow wrote: > Note to file. > > The Python server addressed in the book 301's to the https. So unless you > build (e.g Wget or curl) something with SSL support you can't download Python > sources except from Anduin. > > Richard. > > Both can be built without openssl, but with gnutls to provide ssl/tls support. Note that most packages recommend ssl packages just because SSL is widely used nowadays in various protocols. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] poppler-0.26.0 breaks inkscape [Was: ... r12997 ...]
On 04/26/2014 12:24 PM, Fernando de Oliveira wrote: > Em 25-04-2014 21:36, Armin K. escreveu: >> On 04/26/2014 02:17 AM, Armin K. wrote: >>> On 04/26/2014 01:54 AM, Armin K. wrote: >>>> On 04/25/2014 10:43 PM, ferna...@higgs.linuxfromscratch.org wrote: >>>>> Author: fernando >>>>> Date: Fri Apr 25 13:43:47 2014 >>>>> New Revision: 12997 >>>>> >>>>> Log: >>>>> poppler-0.26.0. >>>>> >>>> >>>> This version breaks inkscape build. > > I was worried, tested only evince. > >>>> >>>> Also, qt5 sed is no longer needed, it was the upstream patch that I >>>> modified into sed back then. > > My bad. I read it several times, in the book, in my script. Usually it > is the first thing I check. But I really completely forgot, yesterday, > was so concentrated in the tests... > >>>> >>>> >>> >>> These 3 seds fix the build for me ... Waiting for it to finish to test >>> runtime (given that I manage to find out how). >>> >>> sed -i "/GfxColorSpace::parse/s|NULL|&, NULL|g" >>> src/extension/internal/pdfinput/pdf-parser.cpp >>> sed -i "/lookupPattern/s:NULL:&, NULL:g" >>> src/extension/internal/pdfinput/pdf-parser.cpp >>> sed -i "/lookupShading/s:NULL:&, NULL:g" >>> src/extension/internal/pdfinput/pdf-parser.cpp >>> >> >> Seems to display pdf files just fine after being built with the seds above. >> > > Just to be sure: those sed's are to be applied to poppler? > No, inkscape. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12997 - in trunk/BOOK: . general/graphlib gnome/applications introduction/welcome networking/netutils
On 04/26/2014 02:17 AM, Armin K. wrote: > On 04/26/2014 01:54 AM, Armin K. wrote: >> On 04/25/2014 10:43 PM, ferna...@higgs.linuxfromscratch.org wrote: >>> Author: fernando >>> Date: Fri Apr 25 13:43:47 2014 >>> New Revision: 12997 >>> >>> Log: >>> poppler-0.26.0. >>> >> >> This version breaks inkscape build. >> >> Also, qt5 sed is no longer needed, it was the upstream patch that I >> modified into sed back then. >> >> > > These 3 seds fix the build for me ... Waiting for it to finish to test > runtime (given that I manage to find out how). > > sed -i "/GfxColorSpace::parse/s|NULL|&, NULL|g" > src/extension/internal/pdfinput/pdf-parser.cpp > sed -i "/lookupPattern/s:NULL:&, NULL:g" > src/extension/internal/pdfinput/pdf-parser.cpp > sed -i "/lookupShading/s:NULL:&, NULL:g" > src/extension/internal/pdfinput/pdf-parser.cpp > Seems to display pdf files just fine after being built with the seds above. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12997 - in trunk/BOOK: . general/graphlib gnome/applications introduction/welcome networking/netutils
On 04/26/2014 01:54 AM, Armin K. wrote: > On 04/25/2014 10:43 PM, ferna...@higgs.linuxfromscratch.org wrote: >> Author: fernando >> Date: Fri Apr 25 13:43:47 2014 >> New Revision: 12997 >> >> Log: >> poppler-0.26.0. >> > > This version breaks inkscape build. > > Also, qt5 sed is no longer needed, it was the upstream patch that I > modified into sed back then. > > These 3 seds fix the build for me ... Waiting for it to finish to test runtime (given that I manage to find out how). sed -i "/GfxColorSpace::parse/s|NULL|&, NULL|g" src/extension/internal/pdfinput/pdf-parser.cpp sed -i "/lookupPattern/s:NULL:&, NULL:g" src/extension/internal/pdfinput/pdf-parser.cpp sed -i "/lookupShading/s:NULL:&, NULL:g" src/extension/internal/pdfinput/pdf-parser.cpp -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12997 - in trunk/BOOK: . general/graphlib gnome/applications introduction/welcome networking/netutils
On 04/25/2014 10:43 PM, ferna...@higgs.linuxfromscratch.org wrote: > Author: fernando > Date: Fri Apr 25 13:43:47 2014 > New Revision: 12997 > > Log: > poppler-0.26.0. > This version breaks inkscape build. Also, qt5 sed is no longer needed, it was the upstream patch that I modified into sed back then. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] #4977: D-Bus-1.8.0: messagebus group and user already exist
On 04/25/2014 04:13 AM, Bruce Dubbs wrote: > Ken Moffat wrote: >> On Thu, Apr 24, 2014 at 08:02:58PM -0500, Bruce Dubbs wrote: >>> Ken Moffat wrote: >>> Thanks for the pointer (I have not built systemd at the moment, still trying to sort out enough details for me to have a chance of getting the whole thing working). But your use of sysctl looks unnecessarily long-winded : why not just something like this ? : sed -i 's/#LogLevel=info/LogLevel=warning/' \ /etc/systemd/system.conf >>> >>> I'm a bit confused. Are you referring to what's in the -dev book right >>> now? Or the part about sysctl that I abandoned as possible but too complex? >> >> The latter - when you first mentioned it, it was the main thing >> that I noticed for setting the log level. The change to permit >> systemd was large, and mostly went in as a single commit (compare >> good uses of git, where there are a series of patches, hopefully >> each small enough to review). You have spent a few weeks on >> sysv-with-systemd, and got it to your liking. The rest of us have a >> steep learing curve, and many areas where we need to find out how to >> change things. >> >> For me, log level is a fairly minor thing, but with a _lot_ of >> scope to make the system awkward to use _when_ other things are not >> correct. >> >> I think examples are always useful, and had read your posting about >> sysctl as an example. > > OK. There is a learning curve. I've only gotten slightly familiar with > it. However I keep picking up things. A couple of rules to keep in mind: > > /etc/systemd entries override /lib/systemd entries. >Remove /lib/systemd entries with ln -s /dev/null /etc/systemd/whatever > > .network and .link files go in /etc/systemd/network/ > > Boot scripts are .service configuration files and go in > /lib/systemd/system/ > They are enabled or disabled at boot time with >systemctl enable|disable name.service. > Individual services are brought up or down with >systemctl start|stop name.service. > >-- Bruce > You can drop .service here. If there's no extension, .service is assumed. You need to use an extension if .socket or .timer is in question though. systemctl enable|disable service (without .service), etc. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Installing Gnome Observations
On 04/23/2014 02:29 PM, Wayne Blaszczyk wrote: > On 23/04/14 22:04, Armin K. wrote: >> On 04/23/2014 01:59 PM, Wayne Blaszczyk wrote: >>> On 23/04/14 19:56, Christopher Gregory wrote: >>>> Hello, >>>> >>>> After just on two weeks and many rebuilds later I can say that we ARE >>>> able to install gnome on top of a base linux from scratch SYSTEMD build. >>>> >>>> >>> >>> >>>> The one thing that remains broken is GDM (gnome display manager). It >>>> will not start up even though all of the permissions are set up >>>> correctly, and the developers only seem interested in making sure that >>>> it works in a red hat environment as red hat have thrown vast sums of >>>> money their way and all the gnome documentation on line states that it >>>> works on the latest red hat. >>> >>> What are the actual error(s) you are getting? I've been running with GDM >>> 3.12 with no issues, mind you, I have Gnome installed under /usr. >>> Are you using a common libexecdir? I know in the past that GDM assumed >>> this directory to be shared with packages such as gnome-settings-daemon, >>> polkit-gnome, and gnome-session. >>> >>> Wayne. >>> >>> >> >> Thing is gdm being installed in /opt. At least pam files should be in >> the right place. Upstream ships pam files for lfs and it will install >> them automatically, given that /etc/lfs-release is found. >> > > Speaking of pam, I also have an extra line added to > /etc/pam.d/system-session > -session optionalpam_systemd.so > Should be the same as with consolekit, but instead of pam_consolekit you use pam_systemd (and drop the nox11 thing). pam_loginuid is also necessary. This is handled in my post lfs systemd notes though. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Installing Gnome Observations
On 04/23/2014 01:59 PM, Wayne Blaszczyk wrote: > On 23/04/14 19:56, Christopher Gregory wrote: >> Hello, >> >> After just on two weeks and many rebuilds later I can say that we ARE >> able to install gnome on top of a base linux from scratch SYSTEMD build. >> >> > > >> The one thing that remains broken is GDM (gnome display manager). It >> will not start up even though all of the permissions are set up >> correctly, and the developers only seem interested in making sure that >> it works in a red hat environment as red hat have thrown vast sums of >> money their way and all the gnome documentation on line states that it >> works on the latest red hat. > > What are the actual error(s) you are getting? I've been running with GDM > 3.12 with no issues, mind you, I have Gnome installed under /usr. > Are you using a common libexecdir? I know in the past that GDM assumed > this directory to be shared with packages such as gnome-settings-daemon, > polkit-gnome, and gnome-session. > > Wayne. > > Thing is gdm being installed in /opt. At least pam files should be in the right place. Upstream ships pam files for lfs and it will install them automatically, given that /etc/lfs-release is found. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] BLFS and systemd
Hello, Right after LFS/BLFS 7.5 releases I started doing some work to make a standalone BLFS systemd incorporating my notes into BLFS 7.5 book. I stopped doing it after I found out that LFS itself is getting systemd. Here is some of my work in form of patches in hope someone might find it useful at some point. It's against way older BLFS revision, but it gives the idea. Work is mostly about eliminating deps on packages that are now in LFS. -- Note: My last name is not Krejzi. patches.tar.xz Description: application/xz -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] html5
On 19.4.2014 1:18, Armin K. wrote: > > > On 19.4.2014 1:05, Bruce Dubbs wrote: >> Ken Moffat wrote: >>>> >>>> Thanks Ken. I was given a URL to check out for teaching. Please >>>> see if >>>> you can use www.TestOut.com/newlabsim >>>> >>>> I don't think there's a password for the beta test but I didn't get >>>> that >>>> far. If it seems to work for you, then I'll go build FF for this >>>> platform. >> >>>It opened a new window, occupying the whole screen. And then it >>> appears to need me to set up an ID, including email and activation >>> code - from that I guess that they (whoever they are) will use the >>> email to send me the activation code. I'm not inclined to do that. >>> >>>Going back to the the site itself, I don't think you need to >>> bother. The first item in "List of Known Issues and Bugs" is: >>> >>> Mozilla Firefox not supported >>> >>> Mozilla Firefox is not yet supported. For now, we encourage Linux OS >>> users to use Chrome to sign in to the HTML5 LabSim. >> >> OK, thanks. At least they are getting away from silverlight. >> >> Has anyone looked into building chrome from source? >> >> -- Bruce >> > > Chrome itself is just Open Source Chromium Browser (www.chromium.org) > with few extra non-free additions and Google branding. You are probably > looking for the second. > > The answer is yes, I do. I combined Archlinux and Gentoo build > instructions to get it to build. It does however require awful amount of > deps which I haven't checked yet. > > Sent using Windows version of Thunderbird, so forgive me if something's > wrong with the attachment. > Oh, and please use own Google API key, this one was tied to my account which doesn't exist anymore (don't know if it still works). -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] html5
On 19.4.2014 1:05, Bruce Dubbs wrote:
Ken Moffat wrote:
Thanks Ken. I was given a URL to check out for teaching. Please see if
you can use www.TestOut.com/newlabsim
I don't think there's a password for the beta test but I didn't get that
far. If it seems to work for you, then I'll go build FF for this platform.
It opened a new window, occupying the whole screen. And then it
appears to need me to set up an ID, including email and activation
code - from that I guess that they (whoever they are) will use the
email to send me the activation code. I'm not inclined to do that.
Going back to the the site itself, I don't think you need to
bother. The first item in "List of Known Issues and Bugs" is:
Mozilla Firefox not supported
Mozilla Firefox is not yet supported. For now, we encourage Linux OS
users to use Chrome to sign in to the HTML5 LabSim.
OK, thanks. At least they are getting away from silverlight.
Has anyone looked into building chrome from source?
-- Bruce
Chrome itself is just Open Source Chromium Browser (www.chromium.org)
with few extra non-free additions and Google branding. You are probably
looking for the second.
The answer is yes, I do. I combined Archlinux and Gentoo build
instructions to get it to build. It does however require awful amount of
deps which I haven't checked yet.
Sent using Windows version of Thunderbird, so forgive me if something's
wrong with the attachment.
#!/bin/bash -e
#export PKGVER=30.0.1599.114
export PKGVER=34.0.1847.116
export TOOLCHAINVER=12773
export DEST=/binary/chromium-${PKGVER}
export -n CFLAGS="-march=native -mtune=native -O3"
export -n CXXFLAGS="-march=native -mtune=native -O3"
chromium_conf=(
-Dgoogle_api_key=AIzaSyCnwAWeKPGN7pGmQJyDitvcb1uTSlE2R1w
-Dgoogle_default_client_id=11433373901.apps.googleusercontent.com
-Dgoogle_default_client_secret=xZ5yO6MG_uMyrh0srUAkJ4KG
-Dwerror=
-Dpython_ver=2.7
-Dlinux_link_gsettings=1
-Dlinux_link_libpci=1
-Dlinux_link_libspeechd=1
-Dlinux_link_pulseaudio=1
-Dlinux_strip_binary=1
-Dlinux_use_gold_binary=0
-Dlinux_use_gold_flags=0
-Dlogging_like_official_build=1
-Drelease_extra_cflags="$CFLAGS -Wno-unused-local-typedefs"
-Dlibspeechd_h_prefix=speech-dispatcher/
-Dffmpeg_branding=Chrome
-Dproprietary_codecs=1
-Duse_system_bzip2=1
-Duse_system_flac=1
-Duse_system_ffmpeg=0
-Duse_system_harfbuzz=1
-Duse_system_libevent=1
-Duse_system_libjpeg=1
-Duse_system_libpng=1
-Duse_system_libvpx=1
-Duse_system_libwebp=1
-Duse_system_libxml=1
-Duse_system_libxslt=1
-Duse_system_minizip=1
-Duse_system_nspr=1
-Duse_system_openssl=1
-Duse_system_opus=1
-Duse_system_snappy=0
-Duse_system_speex=1
-Duse_system_ssl=0
-Duse_system_xdg_utils=1
-Duse_system_yasm=1
-Duse_system_zlib=1
-Duse_gconf=0
-Dusb_ids_path=/usr/share/misc/usb.ids
-Dtarget_arch=x64
-Dcups=1
-Duse_gnome_keyring=1
-Dlinux_link_gnome_keyring=1
-Ddisable_glibc=1
-Ddisable_sse2=1)
#-Duse_system_icu=1
case "$1" in
fetch)
wget -c
https://commondatastorage.googleapis.com/chromium-browser-official/chromium-${PKGVER}.tar.xz
wget -c
https://commondatastorage.googleapis.com/nativeclient-archive2/toolchain/${TOOLCHAINVER}/naclsdk_linux_x86.tgz
wget -c
https://commondatastorage.googleapis.com/nativeclient-archive2/toolchain/${TOOLCHAINVER}/naclsdk_pnacl_linux_x86.tgz
wget -c
https://commondatastorage.googleapis.com/nativeclient-archive2/toolchain/${TOOLCHAINVER}/naclsdk_pnacl_translator.tgz
wget -c
https://commondatastorage.googleapis.com/nativeclient-archive2/toolchain/${TOOLCHAINVER}/naclsdk_pnacl_translator.tgz.sha1hash
rm -rf chromium-${PKGVER}
tar xf chromium-${PKGVER}.tar.xz
pushd chromium-${PKGVER}
mkdir -p native_client/toolchain/.tars
native_client/toolchain/pnacl_translator
ln -sf $OLDPWD/naclsdk_linux_x86.tgz native_client/toolchain/.tars/
ln -sf $OLDPWD/naclsdk_pnacl_linux_x86.tgz
native_client/toolchain/.tars/
ln -sf $OLDPWD/naclsdk_pnacl_translator.tgz
native_client/toolchain/.tars/
ln -sf $OLDPWD/naclsdk_pnacl_translator.tgz.sha1hash
native_client/toolchain/pnacl_translator/SOURCE_SHA1
sed -i "/not RunGN/,+1d" build/gyp_chromium
sed -i "/import find_depot_tools/d" build/gyp_chromium
#if [ -e /media/ntfs/Other/Linux/patches/chromium-fixes.patch ]; then
# patch -Np1 -i /media/ntfs/Other/Linux/patches/chromium-fixes.patch
#fi
popd
;;
build)
pushd chromium-${PKGVER}
build/linux/unbundle/replace_gyp_files.py "${chromium_conf[@]}"
build/gyp_chromium -f make --depth=. "${chromium_conf[@]}"
make chrome chrome_sandbox chromedriver BUILDTYPE=Release -j4
popd
;;
install)
install -dm755 ${DEST}/etc/chromium \
${DEST}/usr/
Re: [blfs-dev] [lfs-patches] r2872 - trunk/kde-runtime
On 17.4.2014 11:35, rthom...@higgs.linuxfromscratch.org wrote: > Author: rthomsen > Date: Thu Apr 17 02:35:17 2014 > New Revision: 2872 > > Log: > kde-runtime-4.13.0 patch > > Added: > trunk/kde-runtime/kde-runtime-4.13.0-rpc_fix-1.patch (contents, props > changed) > > Added: trunk/kde-runtime/kde-runtime-4.13.0-rpc_fix-1.patch > == > --- /dev/null 00:00:00 1970 (empty, because file is newly added) > +++ trunk/kde-runtime/kde-runtime-4.13.0-rpc_fix-1.patch Thu Apr 17 > 02:35:17 2014(r2872) > @@ -0,0 +1 @@ > +link kde-runtime-4.8.2-rpc_fix-1.patch > \ No newline at end of file > This patch is not needed since LFS-7.5. Also, dependency on libtirpc can be dropped. Qt's can also be built without -no-nis, all thanks to --enable-obsolete-rpc in LFS-7.5 Glibc instructions. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12935 - in trunk/BOOK: . gnome/applications introduction/welcome networking/netutils postlfs/security pst/printing xfce/apps
On 04/06/2014 09:52 PM, ferna...@higgs.linuxfromscratch.org wrote: > Author: fernando > Date: Sun Apr 6 12:52:43 2014 > New Revision: 12935 > > Log: > NetworkManager-0.9.8.9, network-manager-applet-0.9.8.9, nss-3.16, > cups-filters-1.0.51 and Midori-0.5.8. > > Modified: >trunk/BOOK/general.ent >trunk/BOOK/gnome/applications/network-manager-applet.xml >trunk/BOOK/introduction/welcome/changelog.xml >trunk/BOOK/networking/netutils/networkmanager.xml >trunk/BOOK/postlfs/security/nss.xml >trunk/BOOK/pst/printing/cups-filters.xml >trunk/BOOK/xfce/apps/midori.xml > ... > > > + The tarball is not compressed from a directory, thus it is better to > + create a directory to uncompress it: > + > + > +make -v midori-&midori-version; && mkdir -v ? > +tar xf midori_&midori-version;_all_.tar.bz2 -C midori-&midori-version; > && > +cd midori-&midori-version; > + -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Add new package appdata-tools-0.1.7
On 04/02/2014 02:27 PM, Fernando de Oliveira wrote: > Em 02-04-2014 09:09, Fernando de Oliveira escreveu: >> >> http://people.freedesktop.org/~hughsient/releases/appdata-tools-0.1.7.tar.xz >> >> Tool used to validate AppData files to conform to standard specification. >> >> It is required for gnome-terminal-3.12.0. >> >> Any objections? >> >> I have created ticket #4887. >> > > > Forgot to ask: include in General Utilities? > It appears to be doing something as intltool, but for appdata files. So you could squash them in the same category. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] PHP-5.5.10 error: 'tsrm_ls' undeclared [Was: ... #4813: SWIG 3.0.0]
On 03/22/2014 11:34 PM, Pierre Labastie wrote: > Le 22/03/2014 22:40, Armin K. a écrit : >> On 03/22/2014 09:36 PM, Pierre Labastie wrote: > >>> No errors in the test now: when I first tried, I built with the sed, but did >>> not remove the previous, non-sed, build. Now I cleaned up everything and it >>> works. >>> >>> I make a ticket and assign it to myself. Will commit tomorrow if not >>> tonight... >>> regards >>> Pierre >>> >> >> Here's the thing: >> >> Default MPM in httpd-2.4.x is threaded mpm, mpm_event. You can't use >> non-ZTS PHP apache module with it. The solution is to use non-threaded >> MPM which is awful (prefork or something like that) or use php-fpm via >> mod_proxy_fcgid or php-cgi via mod_fcgid (separate package). I, for one, >> use php-fpm. >> > > Yes, I found that: '/usr/sbin/httpd -V' returns: > [Sat Mar 22 23:33:07.977944 2014] [:crit] [pid 11932:tid 140408511129472] > Apache is running a threaded MPM, but your PHP Module is not compiled to be > threadsafe. You need to recompile PHP. > AH00013: Pre-configuration failed > > So the sed is not a solution... > > Will try php-fpm tomorrow. > > Pierre > sed is the solution, you just need to switch MPM in httpd. But you really don't want to do that since it will drastically reduce performance. php-fpm or php-cgi are the way to go nowadays. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] PHP-5.5.10 error: 'tsrm_ls' undeclared [Was: ... #4813: SWIG 3.0.0]
On 03/22/2014 09:36 PM, Pierre Labastie wrote: > Le 22/03/2014 20:10, Pierre Labastie a écrit : >> Le 22/03/2014 19:42, Fernando de Oliveira a écrit : >>> Em 22-03-2014 14:57, Pierre Labastie escreveu: >>> Well, I am sorry to tell that the tests do not pass after building php with the sed. There is also this thread: http://sourceforge.net/p/swig/mailman/message/31802171/ where a test case showing the exact same bug is reported, but it is said the bug is fixed in 3.0.0 >>> >>> >>> I don't know if we are talking abaout the same thing, but fir me the >>> "PHP-5.5.10 error: 'tsrm_ls' undeclared ..." is gone also in swig's test: >>> >>> $ grep -i tsrm >>> /home/fernando/Downloads/blfs/swig-3.0.0-make-k-check-2014.03.22-14h48m07s.log >>> >>> gives me nothing. Actually, in the whole build it is not referenced: >>> >>> $ xzgrep tsrm >>> /home/fernando/Downloads/blfs/swig-3.0.0-simulation-2014.03.22-14h48m07s.log.xz >>> >> I believe you. I must have done something wrong. Give me just some more time. >> >> Actually, what amazes me, is that applying the sed or not, php config.log >> does >> not change... >> >> Let me try again: I am puzzled! >> >> Pierre >> > No errors in the test now: when I first tried, I built with the sed, but did > not remove the previous, non-sed, build. Now I cleaned up everything and it > works. > > I make a ticket and assign it to myself. Will commit tomorrow if not > tonight... > regards > Pierre > Here's the thing: Default MPM in httpd-2.4.x is threaded mpm, mpm_event. You can't use non-ZTS PHP apache module with it. The solution is to use non-threaded MPM which is awful (prefork or something like that) or use php-fpm via mod_proxy_fcgid or php-cgi via mod_fcgid (separate package). I, for one, use php-fpm. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] PHP-5.5.10 error: 'tsrm_ls' undeclared [Was: ... #4813: SWIG 3.0.0]
On 03/22/2014 02:32 PM, Fernando de Oliveira wrote: > Em 22-03-2014 08:48, BLFS Trac escreveu: >> #4813: SWIG 3.0.0 >> -+-- >> Reporter: pierre.labastie | Owner: pierre.labastie >> Type: enhancement | Status: assigned >> Priority: normal | Milestone: 7.6 >> Component: BOOK | Version: SVN >> Severity: normal | Resolution: >> Keywords: | >> -+-- >> >> Comment (by pierre.labastie): >> >> All tests passed, except some with PHP: several tests have an issue with >> 'tsrm_ls' undeclared, and I do not know whether it comes form our php >> build or from swig. This issue was also present in older versions. > > I think the problem is php. > > I have mentioned this error, building graphviz and asked for help. > > Title "[blfs-dev] graphviz-2.36.0 and PHP-5.5.10" > > http://permalink.gmane.org/gmane.linux.lfs.beyond.devel/26100 > > Em 19-03-2014 20:07, Fernando de Oliveira escreveu: > >> ... > >> Found references to this error, but no solution. >> >> I am worried, because recently I updated php, and it may be a problem in >> the book. >> >> For my particular use, I am not worried. >> >> Please, somene confirm if this is a local or a general problem (in this >> case, a solution would be muc welcomed). > > ... > >> gv_php_init.c: In function 'gv_string_writer': >> /usr/include/php/Zend/../TSRM/TSRM.h:167:18: error: 'tsrm_ls' undeclared >> (first use in this function) >> #define TSRMLS_C tsrm_ls > > Thanks for confirming that it is a general problem. > > I will investigate again, if cannot find a solution, will open a ticket. > > Default php that's built against apache 2.4.x is thread safe php, also known as ZTS which is kind of experimental feature. tsrm_ls is probably wrapped and exported when ZTS is enabled and SWIG doesn't assume that php is built with ZTS enabled. I wish I could help more, but I don't know that much about php. Hope that I helped at least a bit. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Avahi options and dependencies
On 03/17/2014 08:50 PM, Fernando de Oliveira wrote: > Em 17-03-2014 16:04, Armin K. escreveu: >> On 03/17/2014 07:57 PM, Fernando de Oliveira wrote: >>> When trying new python, I arrived to playing with avahi build, for some >>> reasons. Then I discovered some facts I am trying to understand. >>> >>> >>> First, I discovered that it not only depends on D-Bus Python, but also >>> on pygtk, former being recommended. But in the switches, we have > > >>> >>> Second, if I use >>> >>> --disable-gtk3 >>> >>> and remove "--disable-python", both modules are linked. >>> > > >>> >>> I am reporting, so someone more experienced could give here a solution >>> or make a cleanup in the referred page (ticket, commit, ...). >>> >> >> You need to explicitly disable a dependency in Avahi if it isn't >> present. You are correct that both dbus-python and pygtk are required to >> remove --disable-python. Nothing that I know requires the module so >> maybe that's why it's disabled by default. As for why dbus-python is a >> recommended dep and pygtk optional, I can't say. > > Thanks, Armin, > > OK, will move from recommended to optional. pygtk isn't mentioned, will > include as optional. > > >> Since Qt4 is optional, >> it makes no sense to enable it by default, and given that nothing >> explicitly requires libavahi-qt4 it's disabled. Qt3 isn't even present >> in the book. > > Here, I made a confusion: qt3 for qt5. > > >> Epiphany requires GTK+3 library so it's enabled by default >> and GTK+3 is in recommended deps. I don't know the real reason behind >> enabling GTK+2 library by default though. > > In conclusion, for the time being, just two modifications, regarding the > python modules. Perhaps the qt3 switch isn't necessary anymore? > > It is. As I said, if you *don't* have a dependency, then you need to *explicitly* disable it. Qt3 (not Qt5, there isn't Qt5 library for Avahi that I'm aware of) isn't in the book so it needs to be explicitly disabled in the same way as mono and monodoc and what not. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Avahi options and dependencies
On 03/17/2014 07:57 PM, Fernando de Oliveira wrote: > When trying new python, I arrived to playing with avahi build, for some > reasons. Then I discovered some facts I am trying to understand. > > > First, I discovered that it not only depends on D-Bus Python, but also > on pygtk, former being recommended. But in the switches, we have > > --disable-python > > thus, none of the above packages will be linked. > > Second, if I use > > --disable-gtk3 > > and remove "--disable-python", both modules are linked. > > Third, if both switches aren't used, configure fails: > > "configure: error: Could not find Python module gtk" > > Finally, > > we use: > > --disable-qt3\ > --disable-qt4\ > > but only Qt4 is listed as optional. > > Some of the problems in the page may even been introduced by me, can't > remember if/when it was updated. > > I am reporting, so someone more experienced could give here a solution > or make a cleanup in the referred page (ticket, commit, ...). > You need to explicitly disable a dependency in Avahi if it isn't present. You are correct that both dbus-python and pygtk are required to remove --disable-python. Nothing that I know requires the module so maybe that's why it's disabled by default. As for why dbus-python is a recommended dep and pygtk optional, I can't say. Since Qt4 is optional, it makes no sense to enable it by default, and given that nothing explicitly requires libavahi-qt4 it's disabled. Qt3 isn't even present in the book. Epiphany requires GTK+3 library so it's enabled by default and GTK+3 is in recommended deps. I don't know the real reason behind enabling GTK+2 library by default though. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Git server instructions
On 03/15/2014 08:05 PM, Fernando de Oliveira wrote: > Em 15-03-2014 14:01, Armin K. escreveu: > > >> git server instructions >> for BLFS. So it might take some time unless someone beats me to it. > > I don't know how you are thinking. This subjects is extremely > disagreeable for me to discuss. But I have to. > > > One thing I do not understand is: systemd wants a BLFS version, because > of that, BLFS has to change. I have seen gnucash transition from svn to > git. IIRC, almost one year with both versions, testing. Commits in svn, > then mapped somehow in git. Many many problems, ghosts branches > appearing, master disappearing, only later svn was turned off. > > As in CLFS, where there are git for the books and svn for the > patches, why would not create a git version of LFS-Systemd? This would > serve as a proof -f concept. Then it would be shown to work ok, and then > try to create a map from svn to git versions, and when everyting is > prooed, create the BLFS-systemd git, mapped from aa BLFS-systemd svn, > this mapped from a BLFS svn, and only when nothing else could be done, > perhaps, we would need start considering a discussion about alternatives. > > >>From a basic logic, before even creating BLFS-systemd, there is no need > to discuss anything. First create LFS-systemd git, then proof the > concept, show how things could be done, then go to BLFS-systemd in svn > and/or git, show the problems you have to maintain it in sync with BLFS, > and then lets start discussing. > > I am not feeling very comfortable, discussing this, but I have to. > > I curse the day when systemd ate udev inside the monster that it is. > > We are all in peace, a lot of difficulties to get the book updated, and > then, have to think about this other subject. > > I went to the site that Bruce created. Could do nothing there. It is the > same felling I have when I need some info from sites using git. > The git server instructions will be there for everyone, not just for LFS - same way as the svn server instructions. As for BLFS, I already told that I won't be maintaining BLFS in any way (not even for systemd) even if it migrated to git. I have already converted LFS, BLFS, JHALFS (not entire ALFS repository, it has a bit strange layout), PATCHES and WWW (www2 on lfs server) and everything is hosted on my laptop. It's accessible from outside, send me a message off list if you want to check it out. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Package Currency
On 03/15/2014 10:50 AM, Fernando de Oliveira wrote: > Em 14-03-2014 12:53, Bruce Dubbs escreveu: >> Fernando de Oliveira wrote: >> >>> According to Armin, yesterday, >>> >>> cairomm 1.10.0 1.11.2 * >>> >>> book is good, must be even. >> >> OK, I made cairo even only also even though there are no odd tarballs >> for that. > > > Thanks. > > Three new problems, sorry. Think dbus.freedesktop.org reorganized the > repositories. > > Chapter 9 > dbus-glib 0.102 0 * book is good > > 0.102 still is the greatest number at > http://dbus.freedesktop.org/releases/dbus-glib/ > > I think it was working yesterday. > > Chapter 12 > dbus 1.8.0 0 * book is good > > I think dbus.freedesktop.org has made some modification, both above > worked yesterday. > > Chapter 13 > dbus-python 1.2.0 0 * book is good > > same as above > > > There was a problem with dbus.freedesktop.org server yesterday so I guess the script ran when it was still present and simply timed out. As Bruce said, it will say "0" when it can't get the version from website (timeout, error, whatever). -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Package Currency
On 03/14/2014 12:42 PM, Fernando de Oliveira wrote: > Em 14-03-2014 04:28, Bruce Dubbs escreveu: >> Olaf wrote: >>> On 2014-03-12 04:30, Bruce Dubbs wrote: >>> If you notice something wrong, please let me know, but please also tell me what the correct URL is that I can use to determine the most recent released version of the package. >>> >>> I recently stumbled over nano, BLFS has 2.3.2 which is actually a devel >>> release. 2.2.6 is the latest stable. >>> >>> Release scheme seems to be even=stable, odd=devel >>> Version should be retrievable from here http://www.nano-editor.org/ >>> With a release history (for reference) here >>> http://www.nano-editor.org/overview.php >> >> Ok thanks. I was just taking the max value at >> ftp://ftp.gnu.org/gnu/nano/, but I can change that to the last even >> numbered minor version. >> >> Fixed. > > Armin updated to 2.3.1 and I did it to 2.3.2, I think (cannot fine > changelog, though). Should it be reverted to 2.2 series? > > At that time I didn't know that it was development version. But I never saw any problems and it does seem to have more features than the one on archlinux, which is 2.2.x. Last stable release was quite a while ago and I don't think it really hurts having the latest release of the editor. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Package Currency
On 03/13/2014 12:09 PM, Fernando de Oliveira wrote: > > Chapter 9 > libsigc++ 2.3.1 2.2.11 * book is good > http://ftp.gnome.org/pub/gnome/sources/libsigc++/2.3/libsigc++-2.3.1.tar.xz > > > Chapter 13 > cmake 2.8.12.23.0.0-rc1 * (think we do not want rc1?) > http://www.cmake.org/files/v2.8/cmake-2.8.12.2.tar.gz > > > Chapters 14-16 > wireshark 1.10.6 1.11.2 * (minor not odd) > https://www.wireshark.org/download/src/all-versions/wireshark-1.10.6.tar.bz2 > > > Chapters 20-23 > mariadb 10.0.8 5.5.36 * (you already know, just recalling) > > virtuoso 6.1.8 7.1.0 * > Modificado 26 horas atrás por rt > We may want to stay with Virtuoso 6, as it seems Virtuoso 7 requires 64-bit. > > > Chapter 24 > xf86-input-wacom 0.23.0 0.22.1 * book is good > http://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/ > > > Chapter 30 > libpeas 1.9.0 1.8.1 * book is good > http://ftp.gnome.org/pub/gnome/sources/libpeas/1.9/libpeas-1.9.0.tar.xz > > > Chapters 32-33 > midori0.5.7 1.1 * book is good (at least, could not find 1.1) > http://www.midori-browser.org/downloads/midori_0.5.7_all_.tar.bz2 > > > Chapter 39 > libass0.11.1 0.10.2 * book is good > https://github.com/libass/libass/releases/download/0.11.1/libass-0.11.1.tar.xz > > soundtouch1.8.0 1.7.1 * book is good > http://www.surina.net/soundtouch/soundtouch-1.8.0.tar.gz > > Thanks for the effort making this script! > > I don't know if I am right in all the points above. > > Add kde-workspace and phonon to this list. Both show same version as KDE but neither of these uses their versioning scheme. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Package Currency
On 03/11/2014 06:29 AM, Bruce Dubbs wrote: > Today I've been working on the package currency scripts at > http://anduin.linuxfromscratch.org/~bdubbs/blfs-currency.html > > Most of the scripts are working, but I still need to address a few > issues that have changed since I first wrote them last Fall. > > In any case the info there seems to be mostly correct. I'll finish up > the outstanding issues in the next day or so. > > There are a fair number of packages out of date that are not in the > ticket system. If someone want to go through and add new tickets for > the out of date packages, please do so. > >-- Bruce > Few naming issues: icu 4c-52_1 -> icu4c 52_1 libxml 2-2.9.1 -> libxml2 2.9.1 graphite 2-1.2.4 -> graphite2 1.2.4 raptor 2-2.0.13 -> raptor2 2.0.13 imlib 2-1.4.6 -> imlib2 1.4.6 -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Upcoming BLFS-7.5 release
On 03/06/2014 05:48 PM, Ken Moffat wrote: > On Thu, Mar 06, 2014 at 09:40:31AM +0100, Armin K. wrote: >> >> Then again, when it comes to header changes it most likely results in an >> ABI break too or simply removing deprecated functionality (yay ffmpeg), >> so you have to rebuild one way or another. But then still, you only need >> to rebuild what gets linked against the libraries. Exceptions are gcc >> and glibc. >> > Yes, this is my point. The book is about starting from a minimal > LFS system and building from source. I'm hoping that no minor > breakage like this will show up, but it certainly would not be the > first time. > > ĸen > But then again, rebuilding entire system because of change in gnutls, which is rather not very important part of ones' system was waste of time. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Upcoming BLFS-7.5 release
On 03/06/2014 05:32 AM, Ken Moffat wrote: > On Thu, Mar 06, 2014 at 04:18:45AM +0100, Armin K. wrote: >> >> That's rather not correct. >> >> If a package a is dynamically linked to package b and package b gets >> updated to new version that doesn't have an ABI break (soname in b v1.2 >> is same as in b v1.0, ie libb.so.1), you *don't* need to recompile >> package a or anything else. >> >> In case of ABI break (b v1.4 has libb.so.2 and b v1.2 has libb.so.1), >> only the packages that link against libb.so.1 have to be recompiled >> against libb.so.2, NOTHING ELSE. >> >> In the gnutls case, you didn't need to recompile anything since there >> was no ABI break (there was, but it was reverted since it was not >> intentional). >> >> So even when you upgrade glibc from version 2.12 to version 2.19, you >> don't need to rebuild anything, since libc.so.6 in 2.19 still exports >> the same interfaces it did in 2.12 and also some aditional ones that got >> introduced later, but they are not important since they are not used by >> the software compiled against 2.12. >> > That is a correct statement of how things ought to be. But many > developers are like me - we make mistakes. For a distro which ships > binaries, no big deal. Similarly, fixing an existing BLFS-7.5 with > latest gnutls works. > > But there have been many cases over the years where minor changes > cause accidental breakage. I'm thinking of changes to headers - > those sorts of things only show up when building a fresh system. > Based on your previous mail, I've moved gnutls, glib-networking, and > their required/recommended dependencies, to _much_ earlier in my > build so that I can hope to exercise most possible users. > > ĸen > I don't recall any major changes on this scale that could probably break something. One of the examples might be Glibc 2.14 or upgrading between major versions of gcc (4.6->4.7, 4.7->4.8). Then again, when it comes to header changes it most likely results in an ABI break too or simply removing deprecated functionality (yay ffmpeg), so you have to rebuild one way or another. But then still, you only need to rebuild what gets linked against the libraries. Exceptions are gcc and glibc. (As a side note, header change in readline might break a package or two in BLFS). -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Upcoming BLFS-7.5 release
On 03/06/2014 03:47 AM, Ken Moffat wrote: > On Wed, Mar 05, 2014 at 08:17:50PM -0600, Bruce Dubbs wrote: >> Ken Moffat wrote: >>> >>> For anyone who wasn't aware of this vulnerability (I suspect that >>> in this case I'm behind the curve, and you've probably all already >>> fixed your own affected systems), 3.2.12.1 builds with the current >>> instructions, and links to the book's current version of p11-kit. >>> The timings for make check and for rebuilding the docs are, however, >>> quite different on my machine. I'll put it in the book when svn is >>> open, >> >> The book is released. svn is open now. >> >>-- Bruce >> > Thanks. >> >> and then do a chroot gnome build to try to spot anything which >>> fails to build. > > Started a few minutes ago. Unfortunately, gnutls is near the end > of those desktop builds on which I use it (gnome, or normal+xfce), > so it is going to take some time. At least I've got through gcc > pass 1 with make -j4. > > This makes me understand why debian stable updates take so long : > test everything, get ready, get hit by a new vulnerability, rebuild > everything. At least the BLFS book, and my own builds using gnutls, > don't have so many packages as debian. > > BTW I haven't seen a release announcemnt yet, so I'll take this > opportunity to thank you for all the work you've put into 7.5. > > ĸen > That's rather not correct. If a package a is dynamically linked to package b and package b gets updated to new version that doesn't have an ABI break (soname in b v1.2 is same as in b v1.0, ie libb.so.1), you *don't* need to recompile package a or anything else. In case of ABI break (b v1.4 has libb.so.2 and b v1.2 has libb.so.1), only the packages that link against libb.so.1 have to be recompiled against libb.so.2, NOTHING ELSE. In the gnutls case, you didn't need to recompile anything since there was no ABI break (there was, but it was reverted since it was not intentional). So even when you upgrade glibc from version 2.12 to version 2.19, you don't need to rebuild anything, since libc.so.6 in 2.19 still exports the same interfaces it did in 2.12 and also some aditional ones that got introduced later, but they are not important since they are not used by the software compiled against 2.12. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Upcoming BLFS-7.5 release
On 03/06/2014 02:49 AM, Ken Moffat wrote: > On Wed, Mar 05, 2014 at 11:03:15PM +, Ken Moffat wrote: >> >> Those who are able to read https://lwn.net/Articles/589291/ (might >> be subscriber-only for the next 2 weeks, I'm not sure) will see from >> nix's comment that there is already a second "fix" version of gnutls >> (perhaps the first will be fine for BLFS), and _apparently_ it needs >> a new version of p11-kit. >> >> My gut feeling is that we should get the current book out the door, >> but continue to recommend that people use the development version of >> the book. > > For anyone who wasn't aware of this vulnerability (I suspect that > in this case I'm behind the curve, and you've probably all already > fixed your own affected systems), 3.2.12.1 builds with the current > instructions, and links to the book's current version of p11-kit. > The timings for make check and for rebuilding the docs are, however, > quite different on my machine. I'll put it in the book when svn is > open, and then do a chroot gnome build to try to spot anything which > fails to build. > > What I can't do at the moment is confirm what uses this. I suspect > that it is dynamically loaded when https:// has to be negotiated. > Can somebody remind me, please, of the package which identifies > dynamically loaded libraries ? I think Igor mentioned it a while > back, and I'm fairly sure that Fernando showed some output from it, > but I can't find it in my notes. Thanks. > > ĸen > For your information, this is list of executables and libraries that's linked to libgnutls.so.28 on my system: /usr/bin/gnutls-serv /usr/bin/gvnccapture /usr/bin/gnutls-cli-debug /usr/bin/p11tool /usr/bin/crywrap /usr/bin/certtool /usr/bin/ocsptool /usr/bin/danetool /usr/bin/srptool /usr/bin/psktool /usr/bin/gnutls-cli /usr/lib/libgvnc-1.0.so.0.0.1 /usr/lib/libgtk-vnc-2.0.so.0.0.2 /usr/lib/libavformat.so.55.19.104 /usr/lib/samba/libauthkrb5.so /usr/lib/gstreamer-1.0/libgstfragmented.so /usr/lib/gio/modules/libgiognutls.so /usr/lib/libgnutls-openssl.so.27.0.2 /usr/lib/libgnutls-xssl.so.0.0.0 /usr/lib/vlc/plugins/misc/libgnutls_plugin.so /usr/lib/libgvncpulse-1.0.so.0.0.1 /usr/lib/libgnutlsxx.so.28.1.0 /usr/lib32/libgnutls-openssl.so.27.0.2 /usr/lib32/libgnutls-xssl.so.0.0.0 /usr/lib32/libgnutlsxx.so.28.1.0 Most of these are actually executables and libraries installed by gnutls package itself. Others include glib-networking, which is glib's tls implementation and any GTK+/GLib app that uses TLS is actually using GnuTLS (including epiphany), gtk-vnc, ffmpeg, samba, vlc, gstreamer-plugins-notsure-1.0. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12824 - trunk/BOOK/general/sysutils
On 03/05/2014 08:57 PM, bdu...@higgs.linuxfromscratch.org wrote: > Author: bdubbs > Date: Wed Mar 5 11:57:50 2014 > New Revision: 12824 > > Log: > punctuation > > Modified: >trunk/BOOK/general/sysutils/strigi.xml > > Modified: trunk/BOOK/general/sysutils/strigi.xml > == > --- trunk/BOOK/general/sysutils/strigi.xmlWed Mar 5 11:54:37 2014 > (r12823) > +++ trunk/BOOK/general/sysutils/strigi.xmlWed Mar 5 11:57:50 2014 > (r12824) > @@ -61,7 +61,7 @@ > Strigi Dependencies > > Required > - > + and > , > or > > Typo. "and" is on the wrong line. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] ...] r12822 - trunk/BOOK/multimedia/videoutils
On 03/05/2014 06:58 PM, Fernando de Oliveira wrote: > Em 05-03-2014 13:16, Armin K. escreveu: >> On 03/05/2014 04:44 PM, ferna...@higgs.linuxfromscratch.org wrote: >>> Author: fernando >>> Date: Wed Mar 5 07:44:02 2014 >>> New Revision: 12822 >>> >>> Log: >>> Uncomment URLs for libmatroska and libebml in VLC-2.1.3, that were not >>> working during update. >>> >>> Modified: >>>trunk/BOOK/multimedia/videoutils/vlc.xml >>> >>> Modified: trunk/BOOK/multimedia/videoutils/vlc.xml >>> == >>> --- trunk/BOOK/multimedia/videoutils/vlc.xmlTue Mar 4 15:56:10 >>> 2014(r12821) >>> +++ trunk/BOOK/multimedia/videoutils/vlc.xmlWed Mar 5 07:44:02 >>> 2014(r12822) >>> @@ -118,11 +118,8 @@ >>>>> url="http://sourceforge.net/projects/sidplay2/";>sidplay-libs, >>>, >>>>> url="http://downloads.xiph.org/releases/libshout/";>libshout, >>> - >>>>> url="http://sourceforge.net/projects/modplug-xmms/";>libmodplug and >>>http://www.musepack.net/";>Musepack >>> >>> >> >> >> http://dl.matroska.org/downloads/libebml/libebml-1.3.0.tar.bz2 >> http://dl.matroska.org/downloads/libmatroska/libmatroska-1.4.1.tar.bz2 >> >> Both work for me. You have to use "make -C make/linux" to build it >> correctly. >> > Thanks. > > > OK. URL are the same, they are there, we do not give the urll versioned, > for packages not in the book. > > They work for me too. But I used cd make/linux && make. Does this make a > difference, i.e., should I reinstall? > No, both is correct. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12822 - trunk/BOOK/multimedia/videoutils
On 03/05/2014 04:44 PM, ferna...@higgs.linuxfromscratch.org wrote: > Author: fernando > Date: Wed Mar 5 07:44:02 2014 > New Revision: 12822 > > Log: > Uncomment URLs for libmatroska and libebml in VLC-2.1.3, that were not > working during update. > > Modified: >trunk/BOOK/multimedia/videoutils/vlc.xml > > Modified: trunk/BOOK/multimedia/videoutils/vlc.xml > == > --- trunk/BOOK/multimedia/videoutils/vlc.xml Tue Mar 4 15:56:10 2014 > (r12821) > +++ trunk/BOOK/multimedia/videoutils/vlc.xml Wed Mar 5 07:44:02 2014 > (r12822) > @@ -118,11 +118,8 @@ > url="http://sourceforge.net/projects/sidplay2/";>sidplay-libs, >, > url="http://downloads.xiph.org/releases/libshout/";>libshout, > - > url="http://sourceforge.net/projects/modplug-xmms/";>libmodplug and >http://www.musepack.net/";>Musepack > > http://dl.matroska.org/downloads/libebml/libebml-1.3.0.tar.bz2 http://dl.matroska.org/downloads/libmatroska/libmatroska-1.4.1.tar.bz2 Both work for me. You have to use "make -C make/linux" to build it correctly. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Git server instructions
On 03/05/2014 03:53 PM, akhiezer wrote:
>> Date: Wed, 05 Mar 2014 14:15:07 +
>> From: lf...@cruziero.com (akhiezer)
>> To: BLFS Development List
>> Subject: Re: [blfs-dev] Git server instructions
>>
> Link to bootscripts at foot of page ('in the blfs-bootscripts-20140301
> package') links to:
>
>
http://www.linuxfromscratch.org/~krejzi/blfs-git/introduction/bootscripts.html
>
> On that page, the link 'Refer to
> ../../../../lfs/view/development/chapter07/bootscripts.html for more
info',
> seems to go to old _lfS_ bootscripts page:
>
>
http://www.linuxfromscratch.org/lfs/view/development/chapter07/bootscripts.html
> "7.6. LFS-Bootscripts-20130821"
>
> Maybe the relative path would be ok if/when the relevant xml files are
> slotted into main blfs tree; but as-is, it seems to give the above old
page.
I don't think this is relevant at the moment. It's a temporary location
after all. I didn't even manage to write the script yet since I have no
means of testing it.
> Typos:
>
> s/controling/controlling/
> s/incomming/incoming/
>
Okay.
>
> Small-ish point:
>
> (Consistency?: for every command the preceding text finishes with a
':', execpt for the last:
>
> " ... package.
>
> make install-git-daemon "
>
> Is that because there's the slightly-indirect step re bootscripts?
> )
It was rather based on svn server page, just s/svnserver/gitserver/ and
that part remained the same. I can change it if it matters.
>
>
> OK, I see you do that for the add user/repo, in referring to
> '/srv/git/gitolite/README.txt': is there a similar local doc for the third
> link ('http://gitolite.com/gitolite/g2/confother_.html') ?
>
>
Yes, everything is in that file, further down.
> Also: 'modify the gitolite.conf filename' : s/fielname/file/ ? (Or is it
> really literally the filename that's to be changed?)
>
Aw, snap. Yes, you're right.
Lesson learned: Don't write instructions at 4am.
And again, thanks for your input.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Git server instructions
On 03/05/2014 03:15 PM, akhiezer wrote:
>> Date: Wed, 05 Mar 2014 04:40:07 +0100
>> From: "Armin K."
>> To: BLFS Development List
>> Subject: [blfs-dev] Git server instructions
>>
>> Hello, I've taken some time to write some basic instructions on how to
>> get a basic git server up and running.
>>
>> The instructions can be found at:
>>
>> http://www.linuxfromscratch.org/~krejzi/blfs-git/general/gitserver.html
>>
>> Patch against latest blfs svn can be found at:
>>
>> http://www.linuxfromscratch.org/~krejzi/git-server.patch
>>
>> Any comments and suggestions are welcome.
>>
>
>
> The three off-site docs that you link to, are already showing the
> usual signs of 'chopping'n'changing version'-itis: in your doc, the
> 'Adding and removing users' and 'Adding and removing repositories'
> link to gitolite v3 docs ('http://gitolite.com/gitolite/users.html' &
> 'http://gitolite.com/gitolite/repos.html' resp), whereas the link 'modify the
> gitolite.conf filename as explained in [...] [url]this[/url] document' gives
> a v2 page ('http://gitolite.com/gitolite/g2/confother_.html'), that says at
> its top, "WARNING: This is not the latest gitolite; please see the README" .
>
Oops, my bad.
Unfortunately, I can't find the same page online for v3 (but this also
works for me).
There's an entry in README.txt though, but I see no clean way of
pointing user to it.
>
> That's the kind of thing that happens when working with not a fixed
> tarball/git-tag target, and instead using a moving target; ref preceding
> email re tarball &c.
>
>
> Overall, ideally if possible give example code for how the user would
> walkthrough setup of a simple config; and refer the user to the gitolite
> tarball infos &/or off-site docs for fuller details, in the usual way.
>
>
> And, of course, I'd really recommend nailing down a fixed gitolite version
> and using that.
>
Thanks for the input.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Git server instructions
On 03/05/2014 02:59 PM, akhiezer wrote: >> Date: Wed, 05 Mar 2014 04:40:07 +0100 >> From: "Armin K." >> To: BLFS Development List >> Subject: [blfs-dev] Git server instructions >> >> Hello, I've taken some time to write some basic instructions on how to >> get a basic git server up and running. >> >> The instructions can be found at: >> >> http://www.linuxfromscratch.org/~krejzi/blfs-git/general/gitserver.html >> >> Patch against latest blfs svn can be found at: >> >> http://www.linuxfromscratch.org/~krejzi/git-server.patch >> >> Any comments and suggestions are welcome. >> > > > Might it be better to include 'Gitolite' under required/recommended deps, > or inline in page as an 'additional download'; but in any case have it > downloading a fixed-version tarball - or a fixed git tag - rather than > just implicitly downloading the latest git head commit that may no longer > work well with the particular fixed git/openssh versions that _are_ listed. > I have followed gitolite instructions in README.txt. I was rather in a hurry to get working instructions. There's lot of room for improvement. Will wait for freeze break to incorporate everything that's necessary. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Git server instructions
Hello, I've taken some time to write some basic instructions on how to get a basic git server up and running. The instructions can be found at: http://www.linuxfromscratch.org/~krejzi/blfs-git/general/gitserver.html Patch against latest blfs svn can be found at: http://www.linuxfromscratch.org/~krejzi/git-server.patch Any comments and suggestions are welcome. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Project contributor names
Hello everyone, I'm in process of looking at what would be necessary and how hard it would be to convert current LFS repositories from subversion to git. One of the steps (optional though) is conversion of subversion user names to proper git format "Real name ". I have extracted the following usernames from all repositories that are hosted on the server and managed to find names of many people. Some still remain unknown and I was hoping that some of you may remember them. I also ask, if possible, to correct the already existing names for mistakes. I've left out e-mail addresses, but the format will be username AT linuxfromscratch DOT org (written correctly, of course). ag = Ag Hatzimanikas alex = Alex Groenewoud alexander = Alexander E. Patrakov andy = Andrew Benton balu = Thomas "Balu" Walter bdubbs = Bruce Dubbs billyoc = Billy O'Connor bryan = Bryan Kadzban chris = Chris Staub craigthulu = Craig M. Reece cwurst = Christian Wurst dj = DJ Lucas djensen = David Jensen dnicholson = Dan Nicholson fernando = Fernando de Oliveira gbeekmans = Gerard Beekmans gdalziel = Guy Dalziel georgeb = George Boudreau gerard = Gerard Beekmans gimli = Marc Heerdink greg = Greg Schafer highos = Jesse Tie-Ten-Quee ian = Ian Chilton igor = Igor Živković jamie = Jamie Bennett jbeckers = Joachim Beckers jeremy = Jeremy Utley jeroen = Jeroen Coumans jhuntwork = Jeremy Huntwork jim = Jim Gifford justin = Justin P. Mattock jwrober = James Robertson ken = Ken Moffat kpfleming = Kevin P. Fleming krejzi = Armin K larry = Larry Lawrence lizardo = Anderson Lizardo manuel = Manuel Canales Esparcia markh = Mark Hymers matthew = Matthew Burgess nathan = Nathan Coulson pierre = Pierre Labastie randy = Randy McMurchy rbaker = Robert Baker rdaniels = Robert Daniels richard = Richard Downing robert = Robert Connolly rthomsen = Ragnar Thomsen sklein = Seth W. Klein thomasp = Thomas Pegg thomas = Thomas Trepl timothy = Timothy Bauscher tushar = Tushar Teredesai wblaszcz = Wayne Blaszczyk winkie = Zack Winkles # Not sure neocool = Boris Buegling neven = Neven Has nomis80 = Simon Perreault spyro = Ian Molton # Unknown archaic = archaic flake = flake jesse = jesse jon = jon turiya = turiya vdzuba = vdzuba Thanks in advance. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] ... pygobject patch
On 03/04/2014 08:52 PM, Fernando de Oliveira wrote:
> Em 04-03-2014 13:32, Armin K. escreveu:
>> On 03/04/2014 05:06 PM, Fernando de Oliveira wrote:
>>> Em 04-03-2014 12:05, Armin K. escreveu:
>>>> I've missed one step (for future reference), see below:
>>>>
>>>> On 03/04/2014 04:04 PM, Armin K. wrote:
>>>>> On 03/04/2014 03:33 PM, Fernando de Oliveira wrote:
>>>>>> Em 03-03-2014 11:30, Armin K. escreveu:
>>>>>>> On 03/03/2014 03:06 PM, thomas kaeding wrote:
>>>>>>>> This might be important for anyone wanting to build pygtk.
>>>>>>>> It's a patch to pygobject.
>>>>>>>>
>>>>>>>> https://bug668522.bugzilla-attachments.gnome.org/attachment.cgi?id=209543
>>>>>>>>
>>>>>>>
>>>>>>> Forwarding to blfs-dev since it's a blfs package, not lfs. Be sure to
>>>>>>> subscribe to the list before replying.
>>>>>>>
>>>>>>> The git repository contains 15 patches for pygobject after the last 2.28
>>>>>>> release, so I propose that all should be included in the book in a
>>>>>>> single patch. Note that the patch from that bug and the one that is
>>>>>>> currently in the blfs will also be the part of that patch, given that
>>>>>>> all fixes are included.
>>>>>>>
>>>>>>> https://git.gnome.org/browse/pygobject/log/?h=pygobject-2-28
>>>>>>>
>>>>>>
>>>>>> I don't know what exactly to do. Please, someone could have a look at
>>>>>> this?
>>>>>>
>>>>>>
>>>>>
>>>>> git clone git://git.gnome.org/pygobject -b pygobject-2-28
>>>>> cd pygobject
>>>> git format-patch -15
>>>>> cat 00*.patch > ../pygobject.patch
>>>>> cd ..
>>>>> wget
>>>>> http://ftp.gnome.org/pub/gnome/sources/pygobject/2.28/pygobject-2.28.6.tar.xz
>>>>> tar xf pygobject-2.28.6.tar.xz
>>>>> mv pygobject-2.28.6 b
>>>>> cp -a b a
>>>>> cd b
>>>>> patch -Np1 -i ../pygobject.patch
>>>>> cd ..
>>>>> diff -Naur a b > pygobject-2.28.6-git_fixes-1.patch
>>>>> sed -i "/diff -Naur/d" pygobject-2.28.6-git_fixes-1.patch
>>>>>
>>>>> Final patch is in attachment.
>>>>>
>>>>
>>>>
>>>
>>> Thanks, Armin,
>
>
>>>
>>> 1. That patch you attached can be used, otr I need to redo the process
>>> you tought me?
>>>
>>
>> Yes, this is the final patch. I've included commands here so they might
>> help you later.
>>
>>> 2. The patch is to be included and keep also the one already in the book?
>>>
>>
>> This patch includes the one that's currently in the book.
>>
>>> 3. Target is 7.5, or I can do it a little later for 7.6?
>>>
>>>
>>>
>>
>> Your choice. It contains bugfixes only so I believe it's suitable for
>> 7.5 too.
>>
>
> Didn't you get a problem, when testing the patch?
>
> Only if I first apply pygobject-2.28.6-introspection-1.patch that is in
> the book, then, apply pygobject-2.28.6-git_fixes-1.patch, it works.
>
> With just
>
> patch -Np1 -i ../pygobject-2.28.6-git_fixes-1.patch, "make" breaks with
> messages:
>
> {{{
> pygi-repository.c: In function '_wrap_g_irepository_require':
> pygi-repository.c:92:15: warning: variable 'typelib' set but not used
> [-Wunused-but-set-variable]
> GTypelib *typelib;
>^
> CC _gi_la-pygi-info.lo
> pygi-info.c: In function '_pygi_info_new':
> pygi-info.c:165:14: error: 'GI_INFO_TYPE_ERROR_DOMAIN' undeclared (first
> use in this function)
> case GI_INFO_TYPE_ERROR_DOMAIN:
> ^
> pygi-info.c:165:14: note: each undeclared identifier is reported only
> once for each function it appears in
> pygi-info.c:135:5: warning: enumeration value 'GI_INFO_TYPE_INVALID_0'
> not handled in switch [-Wswitch]
> switch (info_type)
> ^
> pygi-info.c: In function '_pygi_g_type_info_size':
> pygi-info.c:484:22: error: 'GI_INFO_TYPE_ERROR_DOMAIN' undeclared (first
> use in this function)
> case GI_INFO_TYPE_ERROR_DOMAIN:
>
Re: [blfs-dev] ... pygobject patch
On 03/04/2014 05:06 PM, Fernando de Oliveira wrote: > Em 04-03-2014 12:05, Armin K. escreveu: >> I've missed one step (for future reference), see below: >> >> On 03/04/2014 04:04 PM, Armin K. wrote: >>> On 03/04/2014 03:33 PM, Fernando de Oliveira wrote: >>>> Em 03-03-2014 11:30, Armin K. escreveu: >>>>> On 03/03/2014 03:06 PM, thomas kaeding wrote: >>>>>> This might be important for anyone wanting to build pygtk. >>>>>> It's a patch to pygobject. >>>>>> >>>>>> https://bug668522.bugzilla-attachments.gnome.org/attachment.cgi?id=209543 >>>>>> >>>>> >>>>> Forwarding to blfs-dev since it's a blfs package, not lfs. Be sure to >>>>> subscribe to the list before replying. >>>>> >>>>> The git repository contains 15 patches for pygobject after the last 2.28 >>>>> release, so I propose that all should be included in the book in a >>>>> single patch. Note that the patch from that bug and the one that is >>>>> currently in the blfs will also be the part of that patch, given that >>>>> all fixes are included. >>>>> >>>>> https://git.gnome.org/browse/pygobject/log/?h=pygobject-2-28 >>>>> >>>> >>>> I don't know what exactly to do. Please, someone could have a look at this? >>>> >>>> >>> >>> git clone git://git.gnome.org/pygobject -b pygobject-2-28 >>> cd pygobject >> git format-patch -15 >>> cat 00*.patch > ../pygobject.patch >>> cd .. >>> wget >>> http://ftp.gnome.org/pub/gnome/sources/pygobject/2.28/pygobject-2.28.6.tar.xz >>> tar xf pygobject-2.28.6.tar.xz >>> mv pygobject-2.28.6 b >>> cp -a b a >>> cd b >>> patch -Np1 -i ../pygobject.patch >>> cd .. >>> diff -Naur a b > pygobject-2.28.6-git_fixes-1.patch >>> sed -i "/diff -Naur/d" pygobject-2.28.6-git_fixes-1.patch >>> >>> Final patch is in attachment. >>> >> >> > > Thanks, Armin, > > You must have read Bruces's reply. > > I am not feeling very well, now (nothing serious), so I have three > questions: > > 1. That patch you attached can be used, otr I need to redo the process > you tought me? > Yes, this is the final patch. I've included commands here so they might help you later. > 2. The patch is to be included and keep also the one already in the book? > This patch includes the one that's currently in the book. > 3. Target id 7.5, or I can do it a little later for 7.6? > > > Your choice. It contains bugfixes only so I believe it's suitable for 7.5 too. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Libexec WebKitGTK [Was ... r12813 ...]
On 03/04/2014 02:22 PM, akhiezer wrote: >> Date: Tue, 04 Mar 2014 09:22:52 -0300 >> From: Fernando de Oliveira >> To: BLFS Development List >> Subject: Re: [blfs-dev] Libexec WebKitGTK [Was ... r12813 ...] >> >> Em 04-03-2014 02:17, Armin K. escreveu: >>> > . > . >>>> I am thinking of adding, after "make install": >>>> >>>> webkitgtk-2.2.4: >>rm -rf /usr/share/gtk-doc/html/webkitgtk-2.0 >>>> mv -vi /usr/share/gtk-doc/html/webkitgtk \ >>>> /usr/share/gtk-doc/html/webkitgtk-2.0 >>>> >>>> webkitgtk-1.10.2 >>rm -rf /usr/share/gtk-doc/html/webkitgtk-1.0 >>>> mv -vi /usr/share/gtk-doc/html/webkitgtk \ >>>> /usr/share/gtk-doc/html/webkitgtk-1.0 >>>> >>>> >>> >>> For 3. I'd suggest the same as for python docs. Since they are developer >>> docs and developer should only use latest version to develop against, > > > No, not in the wider real-world picture: developers often maintain against > two+ major-ver strands of a package; especially when the strands are very > different and contain paradigm shifts (for want of a better term). > > > Yes, they'll likely focus on the latest version within each strand; and > often will only support particular strands (cf e.g. kernel LTS); but not > _only_ the latest release of the latest strand. > > Those who maintain against a stable release might already know the API and as such it won't change. But for those who write new software often tend to use latest API (git checkouts and such) to develop against. Then again, in case of this package, there is no "stable" release except the latest one - 2.2.x now. There's no longterm release at all. More elegant solution will be to merge back 1.* and 2.* versions of webkitgtk into one package since it's possible to build gtk+2 version of webkitgtk from latest 2.* version, but it uses gstreamer-1.0 as opposed to gstreamer-0.10 which 1.* uses and which some apps might require - not that I know any of these that are in BLFS. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] ... pygobject patch
On 03/04/2014 03:33 PM, Fernando de Oliveira wrote: > Em 03-03-2014 11:30, Armin K. escreveu: >> On 03/03/2014 03:06 PM, thomas kaeding wrote: >>> This might be important for anyone wanting to build pygtk. >>> It's a patch to pygobject. >>> >>> https://bug668522.bugzilla-attachments.gnome.org/attachment.cgi?id=209543 >>> >> >> Forwarding to blfs-dev since it's a blfs package, not lfs. Be sure to >> subscribe to the list before replying. >> >> The git repository contains 15 patches for pygobject after the last 2.28 >> release, so I propose that all should be included in the book in a >> single patch. Note that the patch from that bug and the one that is >> currently in the blfs will also be the part of that patch, given that >> all fixes are included. >> >> https://git.gnome.org/browse/pygobject/log/?h=pygobject-2-28 >> > > I don't know what exactly to do. Please, someone could have a look at this? > > git clone git://git.gnome.org/pygobject -b pygobject-2-28 cd pygobject cat 00*.patch > ../pygobject.patch cd .. wget http://ftp.gnome.org/pub/gnome/sources/pygobject/2.28/pygobject-2.28.6.tar.xz tar xf pygobject-2.28.6.tar.xz mv pygobject-2.28.6 b cp -a b a cd b patch -Np1 -i ../pygobject.patch cd .. diff -Naur a b > pygobject-2.28.6-git_fixes-1.patch sed -i "/diff -Naur/d" pygobject-2.28.6-git_fixes-1.patch Final patch is in attachment. -- Note: My last name is not Krejzi. --- a/configure.ac 2011-06-13 18:33:56.0 +0200 +++ b/configure.ac 2014-03-04 16:02:54.501423815 +0100 @@ -85,7 +85,7 @@ AM_PROG_CC_STDC AM_PROG_CC_C_O -# check that we have the minimum version of python necisary to build +# check that we have the minimum version of python necessary to build JD_PATH_PYTHON(python_min_ver) # check if we are building for python 3 @@ -236,7 +236,7 @@ AC_ARG_ENABLE(introspection, AC_HELP_STRING([--enable-introspection], [Use introspection information]), enable_introspection=$enableval, - enable_introspection=yes) + enable_introspection=no) if test "$enable_introspection" != no; then AC_DEFINE(ENABLE_INTROSPECTION,1,Use introspection information) PKG_CHECK_MODULES(GI, @@ -262,6 +262,9 @@ AC_SUBST(INTROSPECTION_SCANNER) AC_SUBST(INTROSPECTION_COMPILER) +dnl Do not install codegen for Python 3. +AM_CONDITIONAL(ENABLE_CODEGEN, test $build_py3k = false) + dnl add required cflags ... if test "x$GCC" = "xyes"; then JH_ADD_CFLAG([-Wall]) @@ -281,8 +284,6 @@ Makefile pygobject-2.0.pc pygobject-2.0-uninstalled.pc - codegen/Makefile - codegen/pygobject-codegen-2.0 docs/Makefile docs/reference/entities.docbook docs/xsl/fixxref.py @@ -295,6 +296,13 @@ examples/Makefile tests/Makefile PKG-INFO) + +if test $build_py3k = false; then + AC_CONFIG_FILES( +codegen/Makefile +codegen/pygobject-codegen-2.0) +fi + AC_OUTPUT echo --- a/gi/module.py 2011-06-13 18:30:25.0 +0200 +++ b/gi/module.py 2014-03-04 16:02:54.499423777 +0100 @@ -24,7 +24,11 @@ import os import gobject -import string +try: +maketrans = ''.maketrans +except AttributeError: +# fallback for Python 2 +from string import maketrans import gi from .overrides import registry @@ -124,7 +128,7 @@ # Don't use upper() here to avoid locale specific # identifier conversion (e. g. in Turkish 'i'.upper() == 'i') # see https://bugzilla.gnome.org/show_bug.cgi?id=649165 -ascii_upper_trans = string.maketrans( +ascii_upper_trans = maketrans( 'abcdefgjhijklmnopqrstuvwxyz', 'ABCDEFGJHIJKLMNOPQRSTUVWXYZ') for value_info in info.get_values(): --- a/gi/overrides/Gtk.py 2011-06-13 18:33:49.0 +0200 +++ b/gi/overrides/Gtk.py 2014-03-04 16:02:54.499423777 +0100 @@ -35,6 +35,18 @@ Gtk = modules['Gtk']._introspection_module __all__ = [] +if Gtk._version == '2.0': +import warnings +warn_msg = "You have imported the Gtk 2.0 module. Because Gtk 2.0 \ +was not designed for use with introspection some of the \ +interfaces and API will fail. As such this is not supported \ +by the pygobject development team and we encourage you to \ +port your app to Gtk 3 or greater. PyGTK is the recomended \ +python module to use with Gtk 2.0" + +warnings.warn(warn_msg, RuntimeWarning) + + class Widget(Gtk.Widget): def translate_coordinates(self, dest_widget, src_x, src_y): @@ -401,16 +413,22 @@ def __init__(self, parent=None, flags=0, - type=Gtk.MessageType.INFO, + message_type=Gtk.MessageType.INFO, buttons=Gtk.ButtonsType.NONE,
Re: [blfs-dev] ... pygobject patch
I've missed one step (for future reference), see below: On 03/04/2014 04:04 PM, Armin K. wrote: > On 03/04/2014 03:33 PM, Fernando de Oliveira wrote: >> Em 03-03-2014 11:30, Armin K. escreveu: >>> On 03/03/2014 03:06 PM, thomas kaeding wrote: >>>> This might be important for anyone wanting to build pygtk. >>>> It's a patch to pygobject. >>>> >>>> https://bug668522.bugzilla-attachments.gnome.org/attachment.cgi?id=209543 >>>> >>> >>> Forwarding to blfs-dev since it's a blfs package, not lfs. Be sure to >>> subscribe to the list before replying. >>> >>> The git repository contains 15 patches for pygobject after the last 2.28 >>> release, so I propose that all should be included in the book in a >>> single patch. Note that the patch from that bug and the one that is >>> currently in the blfs will also be the part of that patch, given that >>> all fixes are included. >>> >>> https://git.gnome.org/browse/pygobject/log/?h=pygobject-2-28 >>> >> >> I don't know what exactly to do. Please, someone could have a look at this? >> >> > > git clone git://git.gnome.org/pygobject -b pygobject-2-28 > cd pygobject git format-patch -15 > cat 00*.patch > ../pygobject.patch > cd .. > wget > http://ftp.gnome.org/pub/gnome/sources/pygobject/2.28/pygobject-2.28.6.tar.xz > tar xf pygobject-2.28.6.tar.xz > mv pygobject-2.28.6 b > cp -a b a > cd b > patch -Np1 -i ../pygobject.patch > cd .. > diff -Naur a b > pygobject-2.28.6-git_fixes-1.patch > sed -i "/diff -Naur/d" pygobject-2.28.6-git_fixes-1.patch > > Final patch is in attachment. > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Libexec WebKitGTK [Was ... r12813 ...]
On 4.3.2014 5:51, Fernando de Oliveira wrote: > There are definitely problems, here. > > 1. Directories have wrong names and one is missing in webkitgtk-1.10.2. > > /usr/include/webkitgtk-1.0 > /usr/share/gtk-doc/html/webkitgtk > /usr/share/webkitgtk-1.0 > > > 2. Libraries with wrong names: libwebkitgtk-1.0.so and > libjavascriptcoregtk-1.0.so (latter is correct). > > > 3. A common directory, with many files with same name. > > > webkitgtk-2.2.4webkitgtk-1.10.2 > /usr/share/gtk-doc/html/webkitgtk /usr/share/gtk-doc/html/webkitgtk > > It is easy to fix 1. and 2. But what can be done with 3? > > I am thinking of adding, after "make install": > > webkitgtk-2.2.4: > mv -vi /usr/share/gtk-doc/html/webkitgtk \ > /usr/share/gtk-doc/html/webkitgtk-2.0 > > webkitgtk-1.10.2 > mv -vi /usr/share/gtk-doc/html/webkitgtk \ > /usr/share/gtk-doc/html/webkitgtk-1.0 > > For 3. I'd suggest the same as for python docs. Since they are developer docs and developer should only use latest version to develop against, the docs for the latter (1.10.x) should be disabled explicitly. --disable-gtk-doc or --disable-gtk-doc-html ... Try one. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Upcoming BLFS-7.5 release
On 03/03/2014 11:22 PM, Pierre Labastie wrote: > > The full switch --with-apache-libexecdir=$(/usr/bin/apxs -q libexecdir) is not > very good, because it runs apxs unconditionally, even if apache is not > installed. Since apxs is part of apache, it throws a warning (IIRC again) when > apache is not there. Since the behavior is the same without the =$(...) > part, I do not see a reason for having it. Now removing the switch completely > is not wrong either. > I disagree. libexecdir is for "executables" that shouldn't be run by user. Apache modules are not "executables" there are rather DSO's. Another reason is that all modules are in /usr/lib/httpd/modules, so that would be a non-standard location. As a side note, I believe that svn instructions should also contain instructions to use those modules for setting up svn over http:// but that's not very important. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [lfs-dev] pygobject patch
On 03/03/2014 03:06 PM, thomas kaeding wrote: > This might be important for anyone wanting to build pygtk. > It's a patch to pygobject. > > https://bug668522.bugzilla-attachments.gnome.org/attachment.cgi?id=209543 > Forwarding to blfs-dev since it's a blfs package, not lfs. Be sure to subscribe to the list before replying. The git repository contains 15 patches for pygobject after the last 2.28 release, so I propose that all should be included in the book in a single patch. Note that the patch from that bug and the one that is currently in the blfs will also be the part of that patch, given that all fixes are included. https://git.gnome.org/browse/pygobject/log/?h=pygobject-2-28 -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] LFS systemd 7.5 is out
On 03/03/2014 11:38 AM, Fernando de Oliveira wrote: > Em 02-03-2014 21:41, Armin K. escreveu: >> I am pleased to announce the first stable release of the Linux From >> Scratch book that is using systemd as the init system. > > Congratulations! I am pleased we have LFS systemd. > Thanks. >> Unfortunately, there is no release of BLFS that follows this book. There >> are notes[4] for building packages from current BLFS svn (soon to be >> BLFS 7.5) book on LFS systemd. > > As I said, I would not like to have BLFS become hybrid. However I really > would like to have a BLFS systemd. What I am opposed is to mix them in > the same tree. > > I have questions. > > (1) In [4], you seem to show that I can make a copy of my BLFS-7.5-c1 > and transform it in systemd. > I just show what is necessary to modify when using official BLFS book. I think I have missed cups though, I need to correct that. > (2) Some packages would need to be reinstalled to provide units. > Not reinstalled, but rather what (not) to do in order to get the services to work natively with systemd. > (3) I remember it has been asked, but do not remember the answer: can > jhalfs build LFS systemd? If not it would be good to include it. > I believe that Pierre said that it's possible, but he has yet to confirm. > I would like to try systemd, to see how difficult it would be for me to > include systemd updates to BLFS systemd. > > Because, I wanted the same as with LFS: two books. And wanted to see how > much I could contribute. If what Bruce says that only about 25% of > packages would need modifications, I think that Armin and I could take > care of those. > I don't think I'd personally like to do that. I might come up with something else since I disagree with some instructions in the official book and the systemd book might include modifications for shared, non init system specific packages. I might be able to provide patches on top of BLFS 7.5 that just modify the xml as akh suggested once, but that's still long way to go, so don't expect much any time soon. >> >> [4] http://www.linuxfromscratch.org/~krejzi/notes.txt >> >> -- >> Armin K. >> >> Note: My last name is not Krejzi. >> > > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] LFS systemd 7.5 is out
I am pleased to announce the first stable release of the Linux From Scratch book that is using systemd as the init system. For a quick summary about differences between this and the official LFS book see the first release candidate announcement[1]. The book can be read online[2] or downloaded[3] to read locally. Unfortunately, there is no release of BLFS that follows this book. There are notes[4] for building packages from current BLFS svn (soon to be BLFS 7.5) book on LFS systemd. Once again, thanks to everyone who made this release possible. [1] http://www.mail-archive.com/lfs-dev@linuxfromscratch.org/msg19432.html [2] http://www.linuxfromscratch.org/lfs/view/7.5-systemd/ [3] http://www.linuxfromscratch.org/lfs/downloads/7.5-systemd/ f5894fbe2aa482e028a016c89a3ee3df LFS-BOOK-7.5-systemd-NOCHUNKS.html ee5e98a2809ce30f43bae786529f1124 LFS-BOOK-7.5-systemd.pdf 3da4d24da2264e375a4f99e8b9347eb8 LFS-BOOK-7.5-systemd.tar.bz2 3f25106ace9c17b7fe759076b482e321 lfs-network-scripts-20140214.tar.bz2 3c6e98a815615d61b4c210030bd6ee91 md5sums 85134bfc9576352d9a0eb0f41f85ee81 wget-list [4] http://www.linuxfromscratch.org/~krejzi/notes.txt -- Armin K. Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Tags
On 03/01/2014 11:21 AM, Fernando de Oliveira wrote: > Em 01-03-2014 01:02, Bruce Dubbs escreveu: >> Fernando de Oliveira wrote: >>> Em 28-02-2014 17:16, Bruce Dubbs escreveu: Fernando de Oliveira wrote: > > Will try > ekiga > transmission > wireshark >>> >>> Done. All built and working. >>> >>> I think that it would be a good idea, not sure about how vulnerable it >>> would be, to add to wireshark's page: >>> >>> usermod -a -G wireshark >> >> I think we already do that as a last part of the install instructions. >> We also do it for qemu, alsa-utils, simpleburn, and svn. Each package >> has a slightly different location though. >> >>> That is why I did not tag, leaving for you to decide and tag. >>> >>> Transmission was with qt5, testing at the same time source setqt5. >>> >>> Also installed keepassx to test setqt4. >> >> Very good. >> >> I can do the tags if you don't want to, but since you did the work, then >> it's OK with me if you do the tags. >> >>-- Bruce >> >> >> > > Done. > > Still missing info from Armin about chesse, to move from built to > checked. And gnash. > > If nobady is gona do gnash, I can try, although it isrealy old version, > IIRC. But will have to install Xulrunner tha I do not have yet. > I haven't built Xorg at all in my testing environment and don't plan to build new system for at least some time now. My current system is more up to date than LFS-svn and BLFS-svn, but Glibc and Qt instructions are older ones and I don't use libexecdir (system built way before any of these were changed), so I'm sorry but I can't check it for LFS 7.5 since I am not running it. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] kde and nouveau
On 02/28/2014 06:59 AM, Bruce Dubbs wrote: > I've been working to get KDE up to speed for 7.7 and have finally > finished the core modules. I did have a problem at first when I was > testing. I want to document the issues. > > My video is NVIDIA Corporation NV37GL [Quadro PCI-E Series]. > > When I configure the kernel, it wants to use the nouveau kernel driver. > When the system starts up, it was going into framebuffer mode, but it > was giving me problems. The cursor was disappearing often. For > instance going into vim and exiting caused it to disappear every time. > Executing a terminal reset (echo -e \\033c) brought it back, but only > until something else ran. > > When entering X, twm was OK, but KDE was giving a lot of weird hashed > colors and the startup hung. > > What I found was that adding nomodeset to the kernel command line fixed > both the text mode problem and KDE, but KDE performance is poor. > > My kernel configuration has > > CONFIG_DRM_NOUVEAU=y > CONFIG_NOUVEAU_DEBUG=5 > CONFIG_NOUVEAU_DEBUG_DEFAULT=3 > CONFIG_DRM_NOUVEAU_BACKLIGHT=y > > In KDE, the resolution is 1024x768 even though the monitor is 1366x768. > It looks like NOUVEAU is completely disabled: > > [ 1117.328] (II) VESA: driver for VESA chipsets: vesa > [ 1117.328] (--) using VT number 8 > [ 1117.338] (EE) [drm] KMS not enabled > > Reenabling modeset on the kernel line allows twm to come up and the > nouveau driver appears to give normal results in twm. > > I don't particularly want to disable Nvidia/Nouveau > support, but I suppose I could and use the proprietary drivers. I don't > recall the problem in earlier kernels, but I'm not sure. > > If anyone has any ideas about the apparent interference between the > nouveau drivers and KDE, please let me know. > >-- Bruce > Lot of people got nouveau working (for some values of working) for such basic tasks. The driver is far from complete though. My suggestion is to report a bug and see what it can be done. Disabling modeset basically disables nouveau entirely and vesa drivers are used, which isn't a good idea for KDE since it enables lots of fancy stuff that requires some 3D. You could try to combine xf86-video-modesetting and llvmpipe (swrast) drivers and see if it works for you. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Akonadi and cmake
On 02/27/2014 04:47 AM, Armin K. wrote: > On 02/27/2014 04:19 AM, Bruce Dubbs wrote: >> Armin K. wrote: >> >>>> >>>> No, the check is right. It is supposed to fail if the function isn't found. >> >> OK. But it seems that it should be: >> >> #ifndef xyx >>#error xyx >> #endif >> >> Instead of what they have. >> >>-- Bruce >> > > No. If Windows windowing backend isn't enabled, then it *should* fail, > and that is only possible if you call a function that is only available > when that backend is enabled. > Or even better: Even if the define isn't available, still try to call the function just in case it's defined but not picked up somehow (should not happen, but meh I trust them they know what they're doing even if I must admit that it's a bit odd). > So, if it isn't defined, call the function and fail on purpose. If it > is, just do a simple compile that always succeeds which means the > backend is available. > > A bit strange, but works (tm). I still doubt that it is the root of the > issue you are facing. > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Akonadi and cmake
On 02/27/2014 04:19 AM, Bruce Dubbs wrote: > Armin K. wrote: > >>> >>> No, the check is right. It is supposed to fail if the function isn't found. > > OK. But it seems that it should be: > > #ifndef xyx >#error xyx > #endif > > Instead of what they have. > >-- Bruce > No. If Windows windowing backend isn't enabled, then it *should* fail, and that is only possible if you call a function that is only available when that backend is enabled. So, if it isn't defined, call the function and fail on purpose. If it is, just do a simple compile that always succeeds which means the backend is available. A bit strange, but works (tm). I still doubt that it is the root of the issue you are facing. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12791 - in trunk/BOOK: general/sysutils gnome/applications introduction/welcome networking/netutils postlfs/security
On 02/27/2014 01:16 AM, k...@higgs.linuxfromscratch.org wrote: > Author: ken > Date: Wed Feb 26 16:16:09 2014 > New Revision: 12791 > > Log: > Remove another 5 libexecdirs. > > Modified: >trunk/BOOK/general/sysutils/colord.xml >trunk/BOOK/gnome/applications/gnome-terminal.xml >trunk/BOOK/introduction/welcome/changelog.xml >trunk/BOOK/networking/netutils/networkmanager.xml >trunk/BOOK/postlfs/security/acl.xml I'd suggest leaving libexecdir switch for this one. Without it, it will install /usr/libexec/libacl.so and /usr/libexec/libacl.la as symlinks to /usr/lib counterparts and these do not belong in there. >trunk/BOOK/postlfs/security/consolekit.xml > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Akonadi and cmake
On 02/27/2014 12:25 AM, Armin K. wrote:
> On 02/27/2014 12:02 AM, Bruce Dubbs wrote:
>> Armin K. wrote:
>>> On 02/26/2014 11:41 PM, Bruce Dubbs wrote:
>>>> I'm having a problem building Akonadi. When running cmake, I get an
>>>> error. The build/CMakeFiles/CMakeError.log gives:
>>>>
>>>>
>>>> File
>>>> /tmp/akonadi/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
>>>> /* */
>>>> #include
>>>>
>>>> int main(int argc, char** argv)
>>>> {
>>>> (void)argv;
>>>> #ifndef Q_WS_WIN
>>>> return ((int*)(&Q_WS_WIN))[argc];
>>>> #else
>>>> (void)argc;
>>>> return 0;
>>>> #endif
>>>> }
>>>>
>>>> This is a file generated by
>>>> /usr/share/cmake-2.8/Modules/CheckSymbolExists.cmake:
>>>>
>>>> set(CMAKE_CONFIGURABLE_FILE_CONTENT
>>>> "${CMAKE_CONFIGURABLE_FILE_CONTENT}\nint main(int argc, char**
>>>> argv)\n{\n (void)argv;\n#ifndef ${SYMBOL}\n return
>>>> ((int*)(&${SYMBOL}))[argc];\n#else\n (void)argc;\n return
>>>> 0;\n#endif\n}\n")
>>>>
>>>>
>>>> Now I may be misreadign this completely, but I'd think that if the
>>>> tested symbol, in this case Q_WS_WIN does not exist, then it should
>>>> never be referenced.
>>>>
>>>> Should the #ifndef really be #ifdef?
>>>>
>>>> Changing that allows the build to complete.
>>>>
>>>> -- Bruce
>>>>
>>>
>>> Can you post the output of CMake from a clean build directory? (not the
>>> log, just the output on the screen).
>>
>> Now that's odd. I had commend out the offending line in
>> CheckSymbolExists.cmake so I reset it and commented out the new line.
>>
>> When rechecking, it now works. I'll keep an eye on it and we can
>> revisit the problem if it occurs again. I still think the logic in the
>> cmake modules is wrong.
>>
>>-- Bruce
>>
>>
>
> No, the check is right. It is supposed to fail if the function isn't found.
>
> See my logs. I tend to believe that new Qt instructions will cause more
> than this problem.
>
Oh, forgot the logs.
Also, works for me.
--
Note: My last name is not Krejzi.
Determining if the Q_WS_WIN exist failed with the following output:
Change Dir: /home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make "cmTryCompileExec3684553827/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec3684553827.dir/build.make CMakeFiles/cmTryCompileExec3684553827.dir/build
make[1]: Entering directory '/home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building CXX object CMakeFiles/cmTryCompileExec3684553827.dir/CheckSymbolExists.cxx.o
/usr/bin/c++-I/usr/include/qt4-o CMakeFiles/cmTryCompileExec3684553827.dir/CheckSymbolExists.cxx.o -c /home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
/home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx: In function âint main(int, char**)â:
/home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19: error: âQ_WS_WINâ was not declared in this scope
return ((int*)(&Q_WS_WIN))[argc];
^
CMakeFiles/cmTryCompileExec3684553827.dir/build.make:60: recipe for target 'CMakeFiles/cmTryCompileExec3684553827.dir/CheckSymbolExists.cxx.o' failed
make[1]: *** [CMakeFiles/cmTryCompileExec3684553827.dir/CheckSymbolExists.cxx.o] Error 1
make[1]: Leaving directory '/home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp'
Makefile:117: recipe for target 'cmTryCompileExec3684553827/fast' failed
make: *** [cmTryCompileExec3684553827/fast] Error 2
File /home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
/* */
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef Q_WS_WIN
return ((int*)(&Q_WS_WIN))[argc];
#else
(void)argc;
return 0;
#endif
}
Determining if the Q_WS_QWS exist failed with the following output:
Change Dir: /home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make "cmTryCompileExec3093707305/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec3093707305.dir/build.make CMakeFiles/cmTryCompileExec3093707305.dir/build
make[1]: Entering directory '/home/armin/src/akonadi-1.11.0/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report
Re: [blfs-dev] Akonadi and cmake
On 02/27/2014 12:02 AM, Bruce Dubbs wrote:
> Armin K. wrote:
>> On 02/26/2014 11:41 PM, Bruce Dubbs wrote:
>>> I'm having a problem building Akonadi. When running cmake, I get an
>>> error. The build/CMakeFiles/CMakeError.log gives:
>>>
>>>
>>> File
>>> /tmp/akonadi/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
>>> /* */
>>> #include
>>>
>>> int main(int argc, char** argv)
>>> {
>>> (void)argv;
>>> #ifndef Q_WS_WIN
>>> return ((int*)(&Q_WS_WIN))[argc];
>>> #else
>>> (void)argc;
>>> return 0;
>>> #endif
>>> }
>>>
>>> This is a file generated by
>>> /usr/share/cmake-2.8/Modules/CheckSymbolExists.cmake:
>>>
>>> set(CMAKE_CONFIGURABLE_FILE_CONTENT
>>> "${CMAKE_CONFIGURABLE_FILE_CONTENT}\nint main(int argc, char**
>>> argv)\n{\n (void)argv;\n#ifndef ${SYMBOL}\n return
>>> ((int*)(&${SYMBOL}))[argc];\n#else\n (void)argc;\n return
>>> 0;\n#endif\n}\n")
>>>
>>>
>>> Now I may be misreadign this completely, but I'd think that if the
>>> tested symbol, in this case Q_WS_WIN does not exist, then it should
>>> never be referenced.
>>>
>>> Should the #ifndef really be #ifdef?
>>>
>>> Changing that allows the build to complete.
>>>
>>> -- Bruce
>>>
>>
>> Can you post the output of CMake from a clean build directory? (not the
>> log, just the output on the screen).
>
> Now that's odd. I had commend out the offending line in
> CheckSymbolExists.cmake so I reset it and commented out the new line.
>
> When rechecking, it now works. I'll keep an eye on it and we can
> revisit the problem if it occurs again. I still think the logic in the
> cmake modules is wrong.
>
>-- Bruce
>
>
No, the check is right. It is supposed to fail if the function isn't found.
See my logs. I tend to believe that new Qt instructions will cause more
than this problem.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Akonadi and cmake
On 02/26/2014 11:41 PM, Bruce Dubbs wrote:
> I'm having a problem building Akonadi. When running cmake, I get an
> error. The build/CMakeFiles/CMakeError.log gives:
>
>
> File
> /tmp/akonadi/akonadi-1.11.0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
> /* */
> #include
>
> int main(int argc, char** argv)
> {
>(void)argv;
> #ifndef Q_WS_WIN
>return ((int*)(&Q_WS_WIN))[argc];
> #else
>(void)argc;
>return 0;
> #endif
> }
>
> This is a file generated by
> /usr/share/cmake-2.8/Modules/CheckSymbolExists.cmake:
>
> set(CMAKE_CONFIGURABLE_FILE_CONTENT
>"${CMAKE_CONFIGURABLE_FILE_CONTENT}\nint main(int argc, char**
> argv)\n{\n (void)argv;\n#ifndef ${SYMBOL}\n return
> ((int*)(&${SYMBOL}))[argc];\n#else\n (void)argc;\n return
> 0;\n#endif\n}\n")
>
>
> Now I may be misreadign this completely, but I'd think that if the
> tested symbol, in this case Q_WS_WIN does not exist, then it should
> never be referenced.
>
> Should the #ifndef really be #ifdef?
>
> Changing that allows the build to complete.
>
>-- Bruce
>
Can you post the output of CMake from a clean build directory? (not the
log, just the output on the screen).
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Cyrus SASL
On 02/26/2014 09:46 PM, Armin K. wrote: > On 02/26/2014 09:34 PM, Bruce Dubbs wrote: >> I had a problem with the instructions for Cyrus SASL. Using them as >> they are in the book gives me: >> >> gcc -shared -fPIC -DPIC .libs/sasldb.o .libs/sasldb_init.o >> .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a >> -Wl,--no-whole-archive -ldb -lresolv -O2 -Wl,-soname >> -Wl,libsasldb.so.3 -o .libs/libsasldb.so.3.0.0 >> >> /usr/bin/ld: ../sasldb/.libs/libsasldb.a(allockey.o): relocation >> R_X86_64_32 against `.rodata.str1.1' can not be used when making a >> shared object; recompile with -fPIC >> >> ../sasldb/.libs/libsasldb.a(allockey.o): error adding symbols: Bad value >> >> Adding CFLAGS=-fPIC to the configure line fixes this for me. Has anyone >> else seen the problem? >> >> I can add it to the book easily enough, but wanted to check if it was >> only me first. >> >>-- Bruce >> > > Hm. I asked myself why there was -fPIC in the instructions. When I > checked it, that wasn't necessary and I removed it. So everything I can > say is "works for me". > Also, I've found this patch at Gentoo, submitted by the debian developer which sort of looks what you need. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/cyrus-sasl/files/cyrus-sasl-2.1.25-avoid_pic_overwrite.patch?revision=1.1&view=markup Also, consider using the following patch to fix parallel build: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/cyrus-sasl/files/cyrus-sasl-2.1.25-lib_before_plugin.patch?revision=1.1&view=markup -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Cyrus SASL
On 02/26/2014 09:34 PM, Bruce Dubbs wrote: > I had a problem with the instructions for Cyrus SASL. Using them as > they are in the book gives me: > > gcc -shared -fPIC -DPIC .libs/sasldb.o .libs/sasldb_init.o > .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a > -Wl,--no-whole-archive -ldb -lresolv -O2 -Wl,-soname > -Wl,libsasldb.so.3 -o .libs/libsasldb.so.3.0.0 > > /usr/bin/ld: ../sasldb/.libs/libsasldb.a(allockey.o): relocation > R_X86_64_32 against `.rodata.str1.1' can not be used when making a > shared object; recompile with -fPIC > > ../sasldb/.libs/libsasldb.a(allockey.o): error adding symbols: Bad value > > Adding CFLAGS=-fPIC to the configure line fixes this for me. Has anyone > else seen the problem? > > I can add it to the book easily enough, but wanted to check if it was > only me first. > >-- Bruce > Hm. I asked myself why there was -fPIC in the instructions. When I checked it, that wasn't necessary and I removed it. So everything I can say is "works for me". -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Reverting my work
On 25.2.2014 23:54, Randy McMurchy wrote: > > Though I strongly disagree with your decision to remove the docs, > the more important part of your commit is removing the work done > by another editor without discussion. Another editor went to the > trouble of adding the instructions to build and install the docs, > and you just decide to remove it because you don't use pdf docs. > We have seen lot of that lately though and I really feel sorry. Someone wastes the time to get everything to play along as best as possible with everything and then it gots removed/reverted by someone just because "I know better" (no offense) approach even though sometimes it has been explained why something is like it currently is. I wouldn't complain however if the approach worked for all situations, not just the "I use this, everyone should do this" instead of "Lets try to make everyone happy" approach. I did however sometimes remove doc build procedures but only because they didn't work for me (texinfo 5.0 comes to my mind), although they did work for someone else. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] discussion about sendmail
On 02/25/2014 12:39 PM, akhiezer wrote: >> Date: Tue, 25 Feb 2014 11:26:19 +0100 >> From: Pierre Labastie >> To: BLFS Development List >> Subject: [blfs-dev] discussion about sendmail >> >> Hi, >> >> Recently, sendmail has been archived, (see ticket #4723). There has not >> been a real discussion about that. The reason is that the current >> building instructions do not lead to a functional package, although >> Armin and Igor have tried to do so. Furthermore, there are alternatives >> (exim4 and postfix), which are deemed better than sendmail anyway. OTOH, >> I suppose that folks monitoring this list not all follow BLFS trac, and >> it may be interesting to hear what they have to say. That is the purpose >> of this thread. >> > > > Yes, I was about to post here on that. > > > Wouldn't normally such a discussion take place on -dev and only after that > would any -book actions happen - per the notes: > > Ref: http://www.linuxfromscratch.org/mail.html > -- > "blfs-book > The blfs-book list is used for coordinating the BLFS Book's > maintenance. Traffic on it is mostly Trac and SVN commit messages. It > is important that all development discussion of interest to the Book's > users take place on blfs-dev, not here." > > > > The trac item is: > > http://wiki.linuxfromscratch.org/blfs/ticket/4723 > > That's a _very_ summary-'removal' of sendmail; and doesn't reflect well > on b/lfs. > > > "Since its build system requires IQ over 9000 to understand, I won't > bother to try to fix it." (ibid). There are plenty of distros that build > and use sendmail perfectly well. Very often b/lfs will avail itself of > such instructions from other distros, for all sorts of packages, and to > a very wide range of degrees of complexity. Yet in this case the package > is dropped like a hot potato(/coal). > I've advised that it either should be fixed or dropped if nobody cares about it. Current configuration (build went fine, maybe I missed that - but the build system is still like nothing I've seen before) options do not work, as it is pasted in the ticket. The package was lfs74_built; so it was just indeed build tested only for previous release(s) and from the look of that, seems that its instructions went a bit obsolete. > > What was (really) going on there, in that trac ticket? > > > Also, the tone of "The current situation is terrible and is not copy/paste > friendly at all. See Xorg, Qt, KDE instructions for more information." (re > libreoffice: ref 'http://wiki.linuxfromscratch.org/blfs/ticket/4725'), > together with the above sendmail stuff, sounds more like someone is in a > rather irascible mood? > If you look at libreoffice page, you can notice that it uses in its instructions. That's insanely hard to script (you need to use sed and all that stuff when you copy/paste it), you can't simply copy paste it to the console (need to change to the desired prefix). My advice was that it either uses hardcoded prefix like /usr or /opt/libreoffice or that it uses environment variables for prefix like in Xorg, KDE, Qt instructions. I apologize if I meant something bad by that, it was never my intention but to make instructions work good and work for everyone. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Further software builds
On 02/21/2014 10:06 PM, Armin K. wrote: > On 02/19/2014 07:01 PM, Armin K. wrote: >> FYI, I'll be building anything that has an init script in blfs in order >> to provide the same for systemd, and doing so I can correct something >> and/or mark them as checked. >> > > This should be final one from me for the time being. > > > Ping? -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/22/2014 01:57 PM, Pierre Labastie wrote: > Le 22/02/2014 09:59, DJ Lucas a écrit : >> >> On 02/21/14 13:20, Bruce Dubbs wrote: >>> Armin K. wrote: >>> >>>> I know what you meant. I have no problems with shipping package specific >>>> notes for now. Maintaining seperate BLFS is something I can't do alone >>>> and maintaining same instructions in one branch, then generating two >>>> different books is something I don't know a) to do b) if it's possible. >>> a. Can be cured. >>> b. Yes, it's possible. >> Though I've never messed with it, it really doesn't look too difficult. >> Lookup use of . Since this direction interests me, I'll take a >> look maybe next week. >> >> --DJ >> > I can help with the xsl, and there is already some knowledge about "variable" > books in the CLFS community, but I am somewhat worried that if we take this > direction, all the BLFS editors will have to cope with both sets (systemd and > sysvinit) of instructions. > > Pierre > There are different ways than with playing with xsl (shell subsitutions and such, generating .xml files from .xml.in files using templates) but given that some already say that they wouldn't like systemd and sysv instructions in the same repository, I didn't speak up. As for maintenance, it would be still the same. systemd specific instructions are mostly related to bootscript part in more than 70% of the packages anyways so that wouldn't need to be touched for the time being. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 10:12 PM, Ken Moffat wrote: > On Fri, Feb 21, 2014 at 08:51:55AM -0600, Bruce Dubbs wrote: >> Fernando de Oliveira wrote: >>> Em 20-02-2014 23:00, LFS Trac escreveu: #3505: linux-3.13.4 --+ Reporter: bdubbs@… | Owner: lfs-book@… Type: task | Status: new Priority: normal| Milestone: 7.5 Component: Book |Version: SVN Severity: normal| Keywords: --+ New point version. We can do this for 7.5. The rule here is that we can update point versions but not major or minor versions. >>> >>> Couldn't it be the same for blfs, for almost all packages? >> >> That's worthy of discussion. Perhaps end packages and not libraries >> would be amenable to this type of rule. I'm hesitant to update >> libraries right now because of possible breakages of programs already >> marked as lfs75_checked. For the few packages that are marked >> lfs75_built, then there is no good reason not to update. >> >> Is that a reasonable compromise? >> >>-- Bruce > > I'm somewhat reluctant to update even end packages, unless there is > a wrthwhile fix (either a vulnerability fix, or a documented fix for > a problem). For libraries and toolkits, particularly once they have > been tagged, my general opinion is that they should wait until after > the release - again, unless there is a major fix [ and if there is, > all tags are off ]. On that basis, no to updating x264 (#4732). > > ĸen > My opinion (given that it matters here) is more or less the same. See lfs-dev response. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Further software builds
On 02/19/2014 07:01 PM, Armin K. wrote: > FYI, I'll be building anything that has an init script in blfs in order > to provide the same for systemd, and doing so I can correct something > and/or mark them as checked. > This should be final one from me for the time being. -- Note: My last name is not Krejzi. Index: server/other/unbound.xml === --- server/other/unbound.xml (revision 12758) +++ server/other/unbound.xml (working copy) @@ -37,7 +37,7 @@ library API as an integral part of the architecture. -&lfs74_checked; +&lfs75_checked; Package Information Index: server/other/xinetd.xml === --- server/other/xinetd.xml (revision 12758) +++ server/other/xinetd.xml (working copy) @@ -34,7 +34,7 @@ xinetd is the eXtended InterNET services daemon, a secure replacement for inetd. -&lfs74_checked; +&lfs75_checked; Package Information @@ -60,11 +60,10 @@ xinetd Dependencies -Required - - Optional -ftp://ftp.porcupine.org/pub/security/";>tcpwrappers (deprecated) + + ftp://ftp.porcupine.org/pub/security/";>TCP Wrappers (deprecated) + User Notes: @@ -77,10 +76,9 @@ Install xinetd by running the following commands: -sed -i -e "/^LIBS/s/-lpset/& -ltirpc/" xinetd/Makefile.in && -sed -i -e "/register unsigned count/s/register//" xinetd/itox.c && - -./configure --prefix=/usr --with-loadavg&& +sed -i -e "s/exec_server/child_process/" xinetd/builtins.c && +sed -i -e "/register unsigned count/s/register//" xinetd/itox.c && +./configure --prefix=/usr --mandir=/usr/share/man --with-loadavg && make This package does not come with a test suite. @@ -94,11 +92,12 @@ Command Explanations - sed ... xinetd/Makefile.in: Ensure the program - links against the libtirpc library. + + sed ... xinetd/builtins.c: This command fixes + a security issue. - sed ... xinetd/itox.c: Fix some compiler - warnings. + sed ... xinetd/itox.c: This command fixes some + compiler warnings. @@ -109,7 +108,7 @@ Config Files /etc/xinetd.conf and - /etc/xinetd.d/* + /etc/xinetd.d/* /etc/xinetd.conf @@ -177,7 +176,7 @@ socket_type = stream wait = no user = nobody - server= /usr/bin/ps + server= /bin/ps server_args = -auwwx only_from = 128.138.209.0 log_on_success= HOST -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 08:34 PM, akhiezer wrote: >> Date: Fri, 21 Feb 2014 20:04:15 +0100 >> From: "Armin K." >> To: BLFS Development List >> Subject: Re: [blfs-dev] BLFS Systemd Additions >> > . > . >> >> I know what you meant. I have no problems with shipping package specific >> notes for now. > > > Yes, but could they be shipped as, say, diffs/patches against e.g. blfs-7.4 > release (just an example - but in any case a known baseline); so that > folks can apply them as wanted (& against a known baseline - hence the > 'blfs-7.4 rel' example). > > Current-format shipping is not making best use, results-wise, of the work > that you have obviously done in obtaining that info: the info is not as > readily re-usable as it really could be - and I'd expect could quite readily > be, as the blfs-sysd changes that you've made look generally fairly 'clean'. > > Do you maintain your internal changes as changes to xml tree, or what; is it > amenable to generating diffs/patches that folks could apply to main blfs > xml? This is realy the crux of what I was meaning: can you generate such > diffs 'at no(t much) extra cost', from the internal-format info that you're > creating anyhow? Would that be better expenditure of your resources than > writing up the large-ish text/wiki documents? > > >> Maintaining seperate BLFS is something I can't do alone > > > If the blfs-sysd changes are avail as patches, then I'd expect folks'd > come on-board more readily. > > >> and maintaining same instructions in one branch, then generating two >> different books is something I don't know a) to do b) if it's possible. >> > > > Had expected here that there _would_ be two separate xml trees, at least > for foreseeable, like for lfs. And then in time see how 'clean' the diffs > between the two can be; and from there if want to merge. > > Didn't mean to be distracting folks away from blfs testing. > > > > akh > > Even patches require maintenance and given how fast the book changes, the notes I wrote might become obsolete sooner or later. Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 08:20 PM, Bruce Dubbs wrote: > Armin K. wrote: > >> I know what you meant. I have no problems with shipping package specific >> notes for now. Maintaining seperate BLFS is something I can't do alone >> and maintaining same instructions in one branch, then generating two >> different books is something I don't know a) to do b) if it's possible. > > a. Can be cured. > b. Yes, it's possible. > If you can give me few hints on how to do it, or even point me to the right places (I can't think of right term to search online) to look at, I might look at fixing that for 7.6 release. >-- Bruce > > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 07:57 PM, Bruce Dubbs wrote: > Armin K. wrote: >> On 02/21/2014 06:01 PM, Bruce Dubbs wrote: >>> Armin K. wrote: >>> >>>> I'm only one person and keeping up with LFS which is at least 10 times >>>> smaller and making sure it's perfect is hard enough. >>> >>> That's an understatement. >>> >>>> BLFS requires >>>> modifications to more packages than the entire LFS has. Easiest approach >>>> would be for both instructions to co-exist, with some kinds of >>>> role="systemd" xml tags to indicate it's required for systemd and >>>> role=sysvinit to indicate it's required for sysv (mostly configuration >>>> parts). but I believe it has been said once that BLFS should not mix >>>> instructions for those two books, so I'm not going to try. >>> >>> I don't have a problem with using role to generate two versions of the >>> book from the same source. It will take a lot of up front work though. > >> No, it's not two versions of the book, but one version with "Do this if >> you are using sysvinit and do this if you are using systemd". I believe >> it was you who said that we shouldn't mix those when Ragnar suggested it >> back ... ugh long time ago anyways. > > What I said, or at least intended to say, was that users shouldn't be > constantly reminded that "if you have x, do y, otherwise z". I don't > have an objection to doing that in the source by developers and creating > the xsl to generate a 'standard' blfs version and a 'systemd' blfs version. > >-- Bruce > I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 06:02 PM, Bruce Dubbs wrote: > Bruce Dubbs wrote: >> Armin K. wrote: >> >>>>>>>We can do this for 7.5. The rule here is that we can update point >>>>>>>versions but not major or minor versions. >>>>>> >>>>>> Couldn't it be the same for blfs, for almost all packages? >>>>> >>>>> That's worthy of discussion. Perhaps end packages and not libraries >>>>> would be amenable to this type of rule. I'm hesitant to update >>>>> libraries right now because of possible breakages of programs already >>>>> marked as lfs75_checked. For the few packages that are marked >>>>> lfs75_built, then there is no good reason not to update. >>>>> >>>>> Is that a reasonable compromise? >> >>>> I'd prefer not to touch anything (especially modify dependencies at this >>>> late cycle) unless it's really worth upgrading, ie security issues, >>>> feature required by some other packages present in newer version but not >>>> older, etc. >> >>> Also, there's a note in LFS telling people to use latest kernel 3.13.x, >>> so it matters little. API headers don't change much (if all) anyways. >> >> Well there was a pretty big change in the kernel from 3.12 -> 3.13 that >> allowed pftables. Agree that API doesn't change for point versions. >> >> The note is in LFS Chapter3, but we also have a wget-list and md5sums >> file that isn't updated unless we update the book. I'd prefer to have >> that up-to-date at the -stable release. >> >> What I'm suggesting is that packages at the end of the chain such as >> goffice and firefox could be updated within the package freeze period >> without harming the integrity of the overall book if they are built and >> tested using lfs75 components. > > Here are the packages updates we might consider: > > xfburn > gptfdisk > gparted > mpg > goffice > gnumeric > >-- Bruce > Add libreoffice to that list too. It's minor update anyways and I didn't notice any big change. One could argue to update gdk-pixbuf too since it contains bugfixes, but I don't think any of these is important at the moment. Same goes for webkitgtk-2.2.5. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 06:01 PM, Bruce Dubbs wrote: > Armin K. wrote: > >> I'm only one person and keeping up with LFS which is at least 10 times >> smaller and making sure it's perfect is hard enough. > > That's an understatement. > >> BLFS requires >> modifications to more packages than the entire LFS has. Easiest approach >> would be for both instructions to co-exist, with some kinds of >> role="systemd" xml tags to indicate it's required for systemd and >> role=sysvinit to indicate it's required for sysv (mostly configuration >> parts). but I believe it has been said once that BLFS should not mix >> instructions for those two books, so I'm not going to try. > > I don't have a problem with using role to generate two versions of the > book from the same source. It will take a lot of up front work though. > >-- Bruce > No, it's not two versions of the book, but one version with "Do this if you are using sysvinit and do this if you are using systemd". I believe it was you who said that we shouldn't mix those when Ragnar suggested it back ... ugh long time ago anyways. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 06:05 PM, Bruce Dubbs wrote: > Armin K. wrote: > >> I believe we need a policy to exactly define what exactly "package >> freeze" means. > > It means don't upgrade a package unless we talk it over and agree that > it can be upgraded without creating additional work during the release > testing period. > >-- Bruce > > Yeah, that seems the easiest thing to do :P I accept. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 05:44 PM, Bruce Dubbs wrote: > Armin K. wrote: > >>>>>>We can do this for 7.5. The rule here is that we can update point >>>>>>versions but not major or minor versions. >>>>> >>>>> Couldn't it be the same for blfs, for almost all packages? >>>> >>>> That's worthy of discussion. Perhaps end packages and not libraries >>>> would be amenable to this type of rule. I'm hesitant to update >>>> libraries right now because of possible breakages of programs already >>>> marked as lfs75_checked. For the few packages that are marked >>>> lfs75_built, then there is no good reason not to update. >>>> >>>> Is that a reasonable compromise? > >>> I'd prefer not to touch anything (especially modify dependencies at this >>> late cycle) unless it's really worth upgrading, ie security issues, >>> feature required by some other packages present in newer version but not >>> older, etc. > >> Also, there's a note in LFS telling people to use latest kernel 3.13.x, >> so it matters little. API headers don't change much (if all) anyways. > > Well there was a pretty big change in the kernel from 3.12 -> 3.13 that > allowed pftables. Agree that API doesn't change for point versions. > > The note is in LFS Chapter3, but we also have a wget-list and md5sums > file that isn't updated unless we update the book. I'd prefer to have > that up-to-date at the -stable release. > Kernel gets released often, so even after the book releases, you'll have new kernel version and if anyone cares about the note, they'll use newer kernel instead of the provided one and get the same result - wrong md5 sum and such. > What I'm suggesting is that packages at the end of the chain such as > goffice and firefox could be updated within the package freeze period > without harming the integrity of the overall book if they are built and > tested using lfs75 components. > >-- Bruce I don't have anything against that as long as they don't install libraries that *others* link to (goffice is that, but gnumeric isn't) and if dependencies don't change (major upgrades or switch additions/removals). So I believe even you said that such should be bugfix (minor) upgrades, and not feature (major) upgrades. But note that some packages even on minor upgrades can add/remove features (but very few do that) so I don't know how's that going to work. I believe we need a policy to exactly define what exactly "package freeze" means. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 11:40 AM, akhiezer wrote: >> Date: Fri, 21 Feb 2014 00:27:53 +0100 >> From: "Armin K." >> To: BLFS Development List >> Subject: Re: [blfs-dev] BLFS Systemd Additions >> >> On 02/19/2014 11:00 PM, Armin K. wrote: >>> Hello, I've taken some time to write "modifications" that are necessarry >>> for the current BLFS book to get some packages to work with native >>> systemd units or to utilize features that they can use from systemd >>> components itself. >>> >>> The notes are available here if anyone wants to play with it. >>> >>> http://www.linuxfromscratch.org/~krejzi/notes.txt >>> >>> This is incredibly ugly to read, but I'm not very friendly with wikis >>> and such to put them there. Note that instructions only up to >>> >>> IV. Networking >>> >>> for now. I hope to continue tomorrow since it's getting late now. >>> >>> Cheers >>> >> >> Notes have been updated for remaining server packages. Only Iptables, >> CUPS and Cups Filters modifications remain to be added. >> >> The following packages need to be modified and/or (not) installed when >> using LFS systemd as a base. >> >> Chapter 3: The Bash Shell Startup Files > . > # + 58 pkgs. > . >> Chapter 39: alsa-utils-1.0.27.2 >> >> If anyone cares enough to add the instructions to the wiki, let me know. >> Otherwise, I'll keep them at the same address. >> > > > Might it be better all-round if you retained these as sets of patches > against your own working copy of blfs book xml, and then apply/rebase > them with mainline blfs book xml? That way, you kind-of get a de-facto > blfs-systemd book? > I've tried that approach (sort of) and failed because I couldn't keep up with all the changes and such. Note that using a systemd branch of blfs would also bring GNOME back and that would add a lot more packages and I'll be left by myself for those. > > Yeah, I know it'd be likely not quite as straightforward as that. But, > you're putting a non-trivial amount of resource expenditure into the above > work: and then it's being stored/presented in a very un-structured way; > thus, I'd suggest, wasting/undoing a non-trivial part of your effort. > > > I'm aware of the issues last year whereby - if I may presume to word it - > it seems you felt inter alia that your work was being wasted on mainstream > blfs book; and so perhaps want to avoid getting back into that scenario. But, > it doesn't have to be either _that_ or the present (wiki/notes) approach: I > think that the suggest patches or similar structured (parseable/programmable) > route be considered as a good intermediate option. > > >>From here, it looks like you've more-or-less got a blfs-systemd book > there. Why not publish it just like for lfs-systemd? > > > > rgds, > > akh > > > p.s. For the avoidance of doubt: I still think sysd has, to say the least, > serious issues. However, I really think it's not good for such work as what > you've done above, to be shovelled into largely-unstructured notes/wiki > that makes it awkward to work with in an automated fashion. > > I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role="systemd" xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 05:29 PM, Armin K. wrote: > On 02/21/2014 03:51 PM, Bruce Dubbs wrote: >> Fernando de Oliveira wrote: >>> Em 20-02-2014 23:00, LFS Trac escreveu: >>>> #3505: linux-3.13.4 >>>> --+ >>>> Reporter: bdubbs@… | Owner: lfs-book@… >>>> Type: task | Status: new >>>> Priority: normal| Milestone: 7.5 >>>> Component: Book |Version: SVN >>>> Severity: normal| Keywords: >>>> --+ >>>> New point version. >>>> >>>> We can do this for 7.5. The rule here is that we can update point >>>> versions but not major or minor versions. >>> >>> Couldn't it be the same for blfs, for almost all packages? >> >> That's worthy of discussion. Perhaps end packages and not libraries >> would be amenable to this type of rule. I'm hesitant to update >> libraries right now because of possible breakages of programs already >> marked as lfs75_checked. For the few packages that are marked >> lfs75_built, then there is no good reason not to update. >> >> Is that a reasonable compromise? >> >>-- Bruce >> > > I'd prefer not to touch anything (especially modify dependencies at this > late cycle) unless it's really worth upgrading, ie security issues, > feature required by some other packages present in newer version but not > older, etc. > Also, there's a note in LFS telling people to use latest kernel 3.13.x, so it matters little. API headers don't change much (if all) anyways. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Couldn't it be the same for blfs? [Was: ... #3505: linux-3.13.4]
On 02/21/2014 03:51 PM, Bruce Dubbs wrote: > Fernando de Oliveira wrote: >> Em 20-02-2014 23:00, LFS Trac escreveu: >>> #3505: linux-3.13.4 >>> --+ >>> Reporter: bdubbs@… | Owner: lfs-book@… >>> Type: task | Status: new >>> Priority: normal| Milestone: 7.5 >>> Component: Book |Version: SVN >>> Severity: normal| Keywords: >>> --+ >>> New point version. >>> >>> We can do this for 7.5. The rule here is that we can update point >>> versions but not major or minor versions. >> >> Couldn't it be the same for blfs, for almost all packages? > > That's worthy of discussion. Perhaps end packages and not libraries > would be amenable to this type of rule. I'm hesitant to update > libraries right now because of possible breakages of programs already > marked as lfs75_checked. For the few packages that are marked > lfs75_built, then there is no good reason not to update. > > Is that a reasonable compromise? > >-- Bruce > I'd prefer not to touch anything (especially modify dependencies at this late cycle) unless it's really worth upgrading, ie security issues, feature required by some other packages present in newer version but not older, etc. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/19/2014 11:00 PM, Armin K. wrote: > Hello, I've taken some time to write "modifications" that are necessarry > for the current BLFS book to get some packages to work with native > systemd units or to utilize features that they can use from systemd > components itself. > > The notes are available here if anyone wants to play with it. > > http://www.linuxfromscratch.org/~krejzi/notes.txt > > This is incredibly ugly to read, but I'm not very friendly with wikis > and such to put them there. Note that instructions only up to > > IV. Networking > > for now. I hope to continue tomorrow since it's getting late now. > > Cheers > Notes have been updated for remaining server packages. Only Iptables, CUPS and Cups Filters modifications remain to be added. The following packages need to be modified and/or (not) installed when using LFS systemd as a base. Chapter 3: The Bash Shell Startup Files Chapter 4: acl-2.2.52 Chapter 4: attr-2.4.47 Chapter 4: ConsoleKit-0.4.6 Chapter 4: Cyrus SASL-2.1.26 Chapter 4: Iptables-1.4.21 Chapter 4: libcap-2.24 Chapter 4: MIT Kerberos V5-1.12.1 Chapter 4: OpenSSH-6.5p1 Chapter 4: Polkit-0.112 Chapter 4: Stunnel-4.56 Chapter 9: Expat-2.1.0 Chapter 11: Gperf-3.0.4 Chapter 11: Intltool-0.50.2 Chapter 12: acpid-2.0.21 Chapter 12: at-3.1.14 Chapter 12: autofs-5.0.8 Chapter 12: BlueZ-4.101 Chapter 12: Colord-1.0.6 Chapter 12: D-Bus-1.8.0 Chapter 12: Fcron-3.1.2 Chapter 12: GPM-1.20.7 Chapter 12: Sysstat-10.2.1 Chapter 12: Udev Extras (from systemd) Chapter 12: UDisks-2.1.2 Chapter 12: UPower-0.9.23 Chapter 13: Git-1.9.0 Chapter 13: Perl Modules: XML::Parser-2.41 Chapter 13: Running a Subversion Server Chapter 14: DHCP-4.3.0 Chapter 15: NFS-Utils-1.2.9 Chapter 15: ntp-4.2.6p5 Chapter 15: rpcbind-0.2.1 Chapter 15: rsync-3.1.0 Chapter 15: Samba-4.1.4 Chapter 15: wpa_supplicant-2.1 Chapter 16: Avahi-0.6.31 Chapter 16: NetworkManager-0.9.8.8 Chapter 16: Wicd-1.7.2.4 Chapter 20: Apache-2.4.7 Chapter 20: BIND-9.9.5 Chapter 20: ProFTPD-1.3.4d Chapter 20: vsftpd-3.0.2 Chapter 21: Dovecot-2.2.12 Chapter 21: Exim-4.82 Chapter 21: Postfix-2.11.0 Chapter 21: sendmail-8.14.8 Chapter 22: MariaDB-10.0.8 Chapter 22: MySQL-5.6.16 Chapter 22: PostgreSQL-9.3.2 Chapter 23: OpenLDAP-2.4.39 Chapter 23: Soprano-2.9.4 Chapter 23: Unbound-1.4.21 Chapter 23: Virtuoso-6.1.8 Chapter 23: xinetd-2.3.15 Chapter 28: Kde-workspace-4.11.6 Chapter 28: Starting KDE Chapter 32: xfce4-session-4.10.1 Chapter 34: LXSession-0.4.9.2 Chapter 39: alsa-utils-1.0.27.2 If anyone cares enough to add the instructions to the wiki, let me know. Otherwise, I'll keep them at the same address. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Further software builds
On 02/19/2014 07:01 PM, Armin K. wrote: > FYI, I'll be building anything that has an init script in blfs in order > to provide the same for systemd, and doing so I can correct something > and/or mark them as checked. > More updates, for server software mostly. I've dropped OpenLDAP ntlm patch since it isn't that much useful today. -- Note: My last name is not Krejzi. Index: networking/netlibs/ldns.xml === --- networking/netlibs/ldns.xml (revision 12754) +++ networking/netlibs/ldns.xml (working copy) @@ -36,7 +36,7 @@ includes the drill tool. -&lfs74_checked; +&lfs75_checked; Package Information Index: server/databases/mariadb.xml === --- server/databases/mariadb.xml (revision 12754) +++ server/databases/mariadb.xml (working copy) @@ -35,7 +35,7 @@ database management system. -&lfs74_checked; +&lfs75_checked; Package Information @@ -137,15 +137,14 @@ -DINSTALL_MANDIR=share/man \ -DINSTALL_MYSQLSHAREDIR=share/mysql \ -DINSTALL_MYSQLTESTDIR=share/mysql/test \ - -DINSTALL_PLUGINDIR=lib/mysql \ + -DINSTALL_PLUGINDIR=lib/mysql/plugin \ -DINSTALL_SBINDIR=sbin \ -DINSTALL_SCRIPTDIR=bin \ - -DINSTALL_SQLBENCHDIR=share/mysql \ + -DINSTALL_SQLBENCHDIR=share/mysql/bench \ -DINSTALL_SUPPORTFILESDIR=share/mysql \ -DMYSQL_DATADIR=/srv/mysql \ -DMYSQL_UNIX_ADDR=/run/mysqld/mysqld.sock \ -DWITH_EXTRA_CHARSETS=complex \ - -DWITH_LIBEVENT=system \ -DTOKUDB_OK=0 \ .. && make @@ -175,11 +174,12 @@ support for the complex character sets. + -DWITHOUT_SERVER=ON -DWITH_UNIT_TESTS=OFF: Use these @@ -321,7 +321,7 @@ class="username">root user: -install -v -m755 -o mysql -g mysql -d /var/run/mysqld && +install -v -m755 -o mysql -g mysql -d /run/mysqld && mysqld_safe --user=mysql 2>&1 >/dev/null & Index: server/databases/mysql.xml === --- server/databases/mysql.xml (revision 12754) +++ server/databases/mysql.xml (working copy) @@ -35,7 +35,7 @@ server daemon and many different client programs and libraries. -&lfs74_checked; +&lfs75_checked; Package Information @@ -379,7 +379,7 @@ class="username">root user: -install -v -m755 -o mysql -g mysql -d /var/run/mysqld && +install -v -m755 -o mysql -g mysql -d /run/mysqld && mysqld_safe --user=mysql 2>&1 >/dev/null & Index: server/mail/dovecot.xml === --- server/mail/dovecot.xml (revision 12754) +++ server/mail/dovecot.xml (working copy) @@ -38,7 +38,7 @@ easily extensible with plugins. -&lfs74_checked; +&lfs75_checked; Package Information @@ -118,8 +118,6 @@ ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ ---libexecdir=/usr/lib \ ---with-moduledir=/usr/lib/dovecot/modules \ --docdir=/usr/share/doc/dovecot-&dovecot-version; \ --disable-static && make @@ -141,14 +139,6 @@ href="../../xincludes/static-libraries.xml"/> - --with-moduledir=/usr/lib/dovecot/modules: Use this - directory instead of /usr/lib/dovecot - for the modules so that the installed auth program in - the specified libexecdir does not prevent the creation of an - auth/ directory for a module. - - - --with-ldap: This switch enables OpenLDAP authentication support. @@ -282,7 +272,8 @@ /etc/dovecot, /usr/include/dovecot, - /usr/lib/dovecot, and + /usr/lib/dovecot, + /usr/libexec/dovecot, and /usr/share/doc/dovecot-&dovecot-version; Index: server/mail/exim.xml === --- server/mail/exim.xml (revision 12754) +++ server/mail/exim.xml (working copy) @@ -33,7 +33,7 @@ Transport Agent written by the University of Cambridge, released under the GNU Public License. -&lfs74_built; +&lfs75_checked; Package Information Index: server/mail/sendmail.xml === --- server/mail/sendmail.xml (revision 12754) +++ server/mail/sendmail.xml (working copy) @@ -113,7 +113,8 @@ define(`confMANOWN',`root') define(`confSBINGRP',`root') define(`confUBINGRP',`root') -define(`confUBINOWN',`root') +define(`confUBINOWN',`root&#
Re: [blfs-dev] [blfs-book] r12752 - in trunk/BOOK: general/genutils general/prog general/sysutils introduction/welcome multimedia/libdriv
On 02/20/2014 10:17 PM, k...@higgs.linuxfromscratch.org wrote: > Author: ken > Date: Thu Feb 20 13:17:44 2014 > New Revision: 12752 > > Log: > Remove some libexecdirs I overlooked earlier. > > Modified: trunk/BOOK/general/sysutils/cpio.xml > == > --- trunk/BOOK/general/sysutils/cpio.xml Thu Feb 20 13:02:22 2014 > (r12751) > +++ trunk/BOOK/general/sysutils/cpio.xml Thu Feb 20 13:17:44 2014 > (r12752) > @@ -68,10 +68,9 @@ > commands: > > sed -i -e '/gets is a/d' gnu/stdio.in.h && > -./configure --prefix=/usr \ > ---bindir=/bin \ > ---libexecdir=/tmp \ > ---enable-mt \ > +./configure --prefix=/usr \ > +--bindir=/bin \ > +--enable-mt \ > --with-rmt=/usr/sbin/rmt && There is no /usr/sbin/rmt anymore, it's now /usr/libexec/rmt. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Further software builds
On 02/19/2014 07:01 PM, Armin K. wrote: > FYI, I'll be building anything that has an init script in blfs in order > to provide the same for systemd, and doing so I can correct something > and/or mark them as checked. > More updates in attachment -- Note: My last name is not Krejzi. Index: general/genlib/libdaemon.xml === --- general/genlib/libdaemon.xml (revision 12749) +++ general/genlib/libdaemon.xml (working copy) @@ -34,7 +34,7 @@ library that eases the writing of UNIX daemons. -&lfs74_checked; +&lfs75_checked; Package Information Index: networking/netlibs/libnl.xml === --- networking/netlibs/libnl.xml (revision 12749) +++ networking/netlibs/libnl.xml (working copy) @@ -35,7 +35,7 @@ providing APIs to netlink protocol based Linux kernel interfaces. -&lfs74_checked; +&lfs75_checked; Package Information Index: networking/netlibs/libtirpc.xml === --- networking/netlibs/libtirpc.xml (revision 12749) +++ networking/netlibs/libtirpc.xml (working copy) @@ -72,6 +72,8 @@ + libtirpc Dependencies @@ -102,10 +104,10 @@ commands: -patch -Np1 -i ../libtirpc-&libtirpc-version;-remove_nis-1.patch && +./configure --prefix=/usr \ --sysconfdir=/etc \ --disable-static \ --disable-gssapi && Index: networking/netprogs/net-tools.xml === --- networking/netprogs/net-tools.xml (revision 12749) +++ networking/netprogs/net-tools.xml (working copy) @@ -33,7 +33,7 @@ of programs for controlling the network subsystem of the Linux kernel. -&lfs74_checked; +&lfs75_checked; Package Information Index: networking/netprogs/rpcbind.xml === --- networking/netprogs/rpcbind.xml (revision 12749) +++ networking/netprogs/rpcbind.xml (working copy) @@ -72,11 +72,12 @@ Installation of rpcbind + In order to get rpcbind to work -properly, first fix /etc/services. As the -root user: +properly, first fix the package to use correct service name: -sed -i 's/^sunrpc/rpcbind/' /etc/services +sed -i "/servname/s:rpcbind:sunrpc:" src/rpcbind.c && +sed -i "/error = getaddrinfo/s:rpcbind:sunrpc:" src/rpcinfo.c Install rpcbind by running the following commands: @@ -111,7 +112,7 @@ included in the package. - portmap + rpcbind make install-rpcbind Index: networking/netprogs/samba.xml === --- networking/netprogs/samba.xml (revision 12749) +++ networking/netprogs/samba.xml (working copy) @@ -38,7 +38,7 @@ Active Directory domain and a NetBIOS (rfc1001/1002) nameserver (which among other things provides LAN browsing support). -&lfs74_checked; +&lfs75_checked; Package Information @@ -66,7 +66,6 @@ Required - and @@ -111,9 +110,7 @@ Install Samba by running the following commands: -sed -i -e "/dmapi_lib/s/$/ldflags='-ltirpc',/" source3/wscript_build && - -./configure\ +./configure\ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ @@ -166,18 +163,6 @@ Command Explanations -sed ... source3/wscript_build: -This command enables the build to complete when using libtirpc instead of -the deprecated glibc rpc functions. - ---sysconfdir=/etc: Sets the configuration -file directory to avoid the default of -/usr/etc. - ---localstatedir=/var: Sets the variable -data directory to avoid the default of -/usr/var. - --enable-fhs: Assigns all other file paths in a manner compliant with the Filesystem Hierarchy Standard (FHS). Index: networking/netprogs/wpa_supplicant.xml === --- networking/netprogs/wpa_supplicant.xml (revision 12749) +++ networking/netprogs/wpa_supplicant.xml (working copy) @@ -40,7 +40,7 @@ access point. -&lfs74_checked; +&lfs75_checked; Package Information Index: networking/netutils/avahi.xml === --- networking/netutils/avahi.xml (revision 12749) +++ networking/netutils/avahi.xml (working copy) @@ -34,7 +34,7 @@ facilitates service discovery on a local network. -&lfs74_checked; +&lfs75_checked; Pac
Re: [blfs-dev] [blfs-book] r12744 - in trunk/BOOK: general/genlib general/prog gnome/platform kde/core lxde/apps lxde/desktop multimedia/libdriv networking/netlibs networking/netprogs postlfs/security
On 02/20/2014 01:20 PM, ferna...@higgs.linuxfromscratch.org wrote: > Author: fernando > Date: Thu Feb 20 04:20:28 2014 > New Revision: 12744 > > Log: > More tags and other fixes. > > Modified: trunk/BOOK/gnome/platform/notification-daemon.xml > == > --- trunk/BOOK/gnome/platform/notification-daemon.xml Thu Feb 20 03:30:41 > 2014(r12743) > +++ trunk/BOOK/gnome/platform/notification-daemon.xml Thu Feb 20 04:20:28 > 2014(r12744) > @@ -36,7 +36,7 @@ >that displays passive pop-up notifications. > > > -&lfs74_checked; > +&lfs75_checked; > > Package Information > > libexecdir > Modified: trunk/BOOK/gnome/platform/vte.xml > == > --- trunk/BOOK/gnome/platform/vte.xml Thu Feb 20 03:30:41 2014(r12743) > +++ trunk/BOOK/gnome/platform/vte.xml Thu Feb 20 04:20:28 2014(r12744) > @@ -34,7 +34,7 @@ >file implementation for terminal emulators. > > > -&lfs74_checked; > +&lfs75_checked; > This package or vte2 one should have libexecdir switch, since they would collide that way. Or the other one can have the pty agent disabled or whatever. > Modified: trunk/BOOK/networking/netlibs/glib-networking.xml > == > --- trunk/BOOK/networking/netlibs/glib-networking.xml Thu Feb 20 03:30:41 > 2014(r12743) > +++ trunk/BOOK/networking/netlibs/glib-networking.xml Thu Feb 20 04:20:28 > 2014(r12744) > @@ -36,7 +36,7 @@ >Network related gio modules for GLib. > > > -&lfs74_checked; > +&lfs75_checked; > > Package Information > > @@ -105,7 +105,6 @@ > > > ./configure --prefix=/usr > \ > ---libexecdir=/usr/lib/glib-networking \ > --with-ca-certificates=/etc/ssl/ca-bundle.crt \ > --disable-static && > make > Please try to check if "installed dirs" changed when removing libexec switch. iirc for this package there is no other directories when you remove it. Same applies for other packages that used libexecdir. > Modified: trunk/BOOK/x/lib/qt5.xml > == > --- trunk/BOOK/x/lib/qt5.xml Thu Feb 20 03:30:41 2014(r12743) > +++ trunk/BOOK/x/lib/qt5.xml Thu Feb 20 04:20:28 2014(r12744) > @@ -333,12 +333,13 @@ > > make install && > > +install -v -dm755 /usr/share/pixmaps/ && You shouldn't need this iirc. install -D will create directories if they are not present. And below install -v -D ... is being used. > install -v -Dm644 qttools/src/assistant/assistant/images/assistant-128.png \ >/usr/share/pixmaps/assistant-qt5.png && > install -v -Dm644 qttools/src/designer/src/designer/images/designer.png \ > - /usr/share/pixmaps/designer-qt5.png && > + /usr/share/pixmaps/designer-qt5.png && > install -v -Dm644 > qttools/src/linguist/linguist/images/icons/linguist-128-32.png \ > - /usr/share/pixmaps/linguist-qt5.png && > + /usr/share/pixmaps/linguist-qt5.png && > install -v -Dm644 qttools/src/qdbus/qdbusviewer/images/qdbusviewer-128.png \ >/usr/share/pixmaps/qdbusviewer-qt5.png > > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] BLFS Systemd Additions
Hello, I've taken some time to write "modifications" that are necessarry for the current BLFS book to get some packages to work with native systemd units or to utilize features that they can use from systemd components itself. The notes are available here if anyone wants to play with it. http://www.linuxfromscratch.org/~krejzi/notes.txt This is incredibly ugly to read, but I'm not very friendly with wikis and such to put them there. Note that instructions only up to IV. Networking for now. I hope to continue tomorrow since it's getting late now. Cheers -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Further software builds
On 02/19/2014 07:01 PM, Armin K. wrote: > FYI, I'll be building anything that has an init script in blfs in order > to provide the same for systemd, and doing so I can correct something > and/or mark them as checked. > Chapter 12, postfix and libatasmart. -- Note: My last name is not Krejzi. Index: general/genlib/libatasmart.xml === --- general/genlib/libatasmart.xml (revision 12740) +++ general/genlib/libatasmart.xml (working copy) @@ -34,7 +34,7 @@ library. It only supports a subset of the ATA S.M.A.R.T. functionality. -&lfs74_checked; +&lfs75_checked; Package Information @@ -122,7 +122,7 @@ libatasmart.so - /usr/share/doc/libatasmart + /usr/share/doc/libatasmart-&libatasmart-version; Index: general/sysutils/acpid.xml === --- general/sysutils/acpid.xml (revision 12740) +++ general/sysutils/acpid.xml (working copy) @@ -38,7 +38,7 @@ be dropped into place by packages or by the user. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/sysutils/at.xml === --- general/sysutils/at.xml (revision 12740) +++ general/sysutils/at.xml (working copy) @@ -33,7 +33,7 @@ and batch processing. It is required for Linux Standards Base (LSB) conformance. -&lfs74_checked; +&lfs75_checked; Package Information @@ -92,8 +92,10 @@ Install at with the following commands: -./configure --with-daemon_username=atd \ ---with-daemon_groupname=atd && +./configure --docdir=/usr/share/doc/at-&at-version; \ +--with-daemon_username=atd\ +--with-daemon_groupname=atd \ +SENDMAIL=/usr/sbin/sendmail && make This package does not come with a test suite. Index: general/sysutils/autofs.xml === --- general/sysutils/autofs.xml (revision 12740) +++ general/sysutils/autofs.xml (working copy) @@ -36,7 +36,7 @@ based on a set of pre-configured maps. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/sysutils/bluez.xml === --- general/sysutils/bluez.xml (revision 12740) +++ general/sysutils/bluez.xml (working copy) @@ -34,7 +34,7 @@ Bluetooth protocol stack for Linux. -&lfs74_checked; +&lfs75_checked; Package Information @@ -129,8 +129,7 @@ commands: - -./configure --prefix=/usr\ +./configure --prefix=/usr\ --sysconfdir=/etc\ --localstatedir=/var \ --libexecdir=/lib\ @@ -142,8 +141,7 @@ --enable-pand\ --enable-tools \ --enable-wiimote \ ---disable-test \ ---without-systemdunitdir && +--disable-test && make @@ -222,11 +220,6 @@ - --without-systemdunitdir: This switch disables installation - of the systemd units. - - - --enable-cups: This switch enables CUPS backend support. Note that CUPS does not need to be installed for this support. Index: general/sysutils/dbus.xml === --- general/sysutils/dbus.xml (revision 12740) +++ general/sysutils/dbus.xml (working copy) @@ -129,7 +129,6 @@ ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ ---libexecdir=/usr/lib/dbus-1.0 \ --with-console-auth-dir=/run/console/ \ --without-systemdsystemunitdir \ --disable-systemd \ Index: general/sysutils/gpm.xml === --- general/sysutils/gpm.xml (revision 12740) +++ general/sysutils/gpm.xml (working copy) @@ -86,7 +86,7 @@ install-info --dir-file=/usr/share/info/dir \ /usr/share/info/gpm.info && -ln -v -sfn libgpm.so.2.1.0 /usr/lib/libgpm.so && +ln -sfv libgpm.so.2.1.0 /usr/lib/libgpm.so&& install -v -m644 conf/gpm-root.conf /etc && install -v -m755 -d /usr/share/doc/gpm-&gpm-version;/support && Index: general/sysutils/sysstat.xml === --- general/sysutils/sysstat.xml (revision 12740) +++ general/sysutils/sysstat.xml (working copy) @@ -35,7 +35,7 @@ utility, common to many commercial Unixes
Re: [blfs-dev] Further software builds
On 02/19/2014 07:01 PM, Armin K. wrote: > FYI, I'll be building anything that has an init script in blfs in order > to provide the same for systemd, and doing so I can correct something > and/or mark them as checked. > Chapter 4 patch in attachment -- Note: My last name is not Krejzi. Index: postlfs/security/cyrus-sasl.xml === --- postlfs/security/cyrus-sasl.xml (revision 12738) +++ postlfs/security/cyrus-sasl.xml (working copy) @@ -39,7 +39,7 @@ protocol and the connection. -&lfs74_checked; +&lfs75_checked; Package Information @@ -118,6 +118,12 @@ Installation of Cyrus SASL + + +This package does not support parallel build. + + + Install Cyrus SASL by running the following commands: @@ -132,8 +138,7 @@ --sysconfdir=/etc\ --enable-auth-sasldb \ --with-dbpath=/var/lib/sasl/sasldb2 \ ---with-saslauthd=/var/run/saslauthd \ -CFLAGS=-fPIC +--with-saslauthd=/var/run/saslauthd && make Index: postlfs/security/mitkrb.xml === --- postlfs/security/mitkrb.xml (revision 12738) +++ postlfs/security/mitkrb.xml (working copy) @@ -38,7 +38,7 @@ networks or the Internet. -&lfs74_checked; +&lfs75_checked; Package Information Index: postlfs/security/openssh.xml === --- postlfs/security/openssh.xml (revision 12738) +++ postlfs/security/openssh.xml (working copy) @@ -5,9 +5,9 @@ %general-entities; http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-&openssh-version;.tar.gz";> + "http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-&openssh-version;.tar.gz";> ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-&openssh-version;.tar.gz";> + "ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-&openssh-version;.tar.gz";> @@ -32,16 +32,16 @@ Introduction to OpenSSH - -The OpenSSH package contains -ssh clients and the sshd daemon. This -is useful for encrypting authentication and subsequent traffic over a -network. The ssh and scp commands are -secure implementions of telnet and rcp -respectively. - + + The OpenSSH package contains + ssh clients and the sshd daemon. This + is useful for encrypting authentication and subsequent traffic over a + network. The ssh and scp commands are + secure implementions of telnet and rcp + respectively. + - &lfs75_checked; +&lfs75_checked; Package Information @@ -100,7 +100,7 @@ -User Notes: +User Notes: @@ -129,7 +129,6 @@ ./configure --prefix=/usr \ --sysconfdir=/etc/ssh \ ---datadir=/usr/share/sshd \ --with-md5-passwords \ --with-privsep-path=/var/lib/sshd && make @@ -185,12 +184,6 @@ - --datadir=/usr/share/sshd: This switch puts the - Ssh.bin file (used for SmartCard authentication) in - /usr/share/sshd. - - - --with-md5-passwords: This enables the use of MD5 passwords. Index: postlfs/security/stunnel.xml === --- postlfs/security/stunnel.xml (revision 12738) +++ postlfs/security/stunnel.xml (working copy) @@ -38,7 +38,7 @@ SMTP and HTTP, and in tunneling PPP over network sockets without changes to the server package source code. -&lfs74_checked; +&lfs75_checked; Package Information @@ -97,10 +97,10 @@ the stunnel daemon. If you own, or have already created a signed SSL Certificate you wish to use, copy it to /etc/stunnel/stunnel.pem before starting the build - (ensure only root has read and + (ensure only root has read and write access), otherwise you will be prompted to create one during the installation process. The - .pem file must be formatted as + .pem file must be formatted as shown below: -BEGIN PRIVATE KEY- @@ -120,7 +120,7 @@ ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ ---disable-libwrap && +--disable-fips && make This package does not come with a test suite. @@ -134,25 +134,15 @@ Command Explanations ---sysconfdir=/etc: This parameter forces -the configuration directory to /etc -instead of /usr/etc. +--disable-fips: This switch disables FIPS support +which will cause Stunnel to fail to
[blfs-dev] Further software builds
FYI, I'll be building anything that has an init script in blfs in order to provide the same for systemd, and doing so I can correct something and/or mark them as checked. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libexecdir
On 02/19/2014 02:43 PM, Pierre Labastie wrote: > Le 19/02/2014 12:58, Armin K. a écrit : >> Please try to remove and update references to libexecdir when checking >> blfs packages or the change wasn't really worth a while if it won't get used >> >> >> >> networking/connect/dhcpcd.xml:./configure >> --libexecdir=/lib/dhcpcd \ >> > Will take care of this one (I have updated just one tag, and did it wrong!). > > Can somebody recall what the rules are here? I guess dhcpcd can be started > early, and that is the reason why the default installation dir is / > > Now, without switch, the libexecdir is /libexec. Do we want this one? > > Well, maybe I should read the FHS... > > Pierre > Uhm, then better leave it that way. I don't think we also want /libexec and /usr/libexec for dhcpcd isn't really suitable for seperate /usr. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Spell checker?
On 02/19/2014 12:14 PM, Igor Živković wrote: > On 2014-02-18 19:46, Armin K. wrote: >> Hi, I recall someone (a developer) running some kind of spell checking >> script/program on LFS svn some time ago and I'd like to know what was >> the script/program used, if it's not the problem? > > https://pypi.python.org/pypi/misspellings > Thanks! That's exactly it. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] dbus-1.8.0 and xmlto-0.0.25
On 02/18/2014 11:20 PM, Fernando de Oliveira wrote: > Sending again. Title was wrong, I had solved my problem. > > I think this sentence is wrong: > > "Note that the configure script will look for xmlto-0.0.25 but it does > nothing as the XML/HTML documentation is already shipped in the source > tree." > > If there is no xmlto installed: > > $ xzgrep xmlto > /home/fernando/Downloads/blfs/dbus-1.8.0-simulation-2014.02.18-19h14m30s.log.xz > checking for xmlto... no > xmlto:no > > But if it finds: > > $ xzgrep xmlto > /home/fernando/Downloads/blfs/dbus-1.8.0-2014.02.18-19h08m29s.log.xz > checking for xmlto... /usr/bin/xmlto > xmlto:/usr/bin/xmlto > /usr/bin/xmlto man dbus-cleanup-sockets.1.xml > /usr/bin/xmlto man dbus-daemon.1.xml > /usr/bin/xmlto man dbus-launch.1.xml > /usr/bin/xmlto man dbus-monitor.1.xml > /usr/bin/xmlto man dbus-run-session.1.xml > /usr/bin/xmlto man dbus-send.1.xml > /usr/bin/xmlto man dbus-uuidgen.1.xml > /usr/bin/xmlto html-nochunks dbus-faq.xml > /usr/bin/xmlto html-nochunks dbus-specification.xml > /usr/bin/xmlto html-nochunks dbus-test-plan.xml > /usr/bin/xmlto html-nochunks dbus-tutorial.xml > /usr/bin/xmlto html-nochunks dbus-cleanup-sockets.1.xml > /usr/bin/xmlto html-nochunks dbus-daemon.1.xml > /usr/bin/xmlto html-nochunks dbus-launch.1.xml > /usr/bin/xmlto html-nochunks dbus-monitor.1.xml > /usr/bin/xmlto html-nochunks dbus-run-session.1.xml > /usr/bin/xmlto html-nochunks dbus-send.1.xml > /usr/bin/xmlto html-nochunks dbus-uuidgen.1.xml > > > I recall seeing in the 1.8.0 NEWS that D-Bus doesn't ship documentation anymore. And I did notice in lfs systemd that D-Bus 1.8.0 didn't install any man pages, although it did before. So, as you said, the text needs modification. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] My BLFS checks
On 02/18/2014 06:29 PM, Armin K. wrote: > Hi, I have finished building the part of BLFS I required to get full > build from the systemd source package and have also updated gcc-4.8.2 > instructions. > > The attached patch contains changes I made. I only ask the patch to be > applied without any changes and then the changes can be made later if > necessary so I can see what was I doing wrong (no hard feelings here). > > All packages were run with testsuites (yeah, I can't believe it either), > so I had to build a bit more packages than I actually needed. I still > can't get glib testsuite to finish ... It has been running for half an > hour yet. If it finishes, I'll post the result. > > The build logs of current BLFS packages that I have built are available at: > > http://www.linuxfromscratch.org/~krejzi/7.5-systemd-rc1/logs/postlfs/ > > If the glib manages to complete today, I'll post it too. > "make check" was running for 90 minutes and I canceled it. If anyone manages to get it to work, please let me know. Most of the time it spent idling on the same test - gio one, not sure exactly which is it. > -- > Note: My last name is not Krejzi. > > > -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Spell checker?
Hi, I recall someone (a developer) running some kind of spell checking script/program on LFS svn some time ago and I'd like to know what was the script/program used, if it's not the problem? Thanks. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] My BLFS checks
On 02/18/2014 07:28 PM, akhiezer wrote: >> Date: Tue, 18 Feb 2014 18:29:50 +0100 >> From: "Armin K." >> To: BLFS Development List >> Subject: [blfs-dev] My BLFS checks >> > . > . >> >> The attached patch contains changes I made. I only ask the patch to be >> applied without any changes and then the changes can be made later if >> necessary so I can see what was I doing wrong (no hard feelings here). >> > . > . >> @@ -183,23 +180,28 @@ >>refer to the information found in the GCC >>section of Chapter 6 in the LFS book (>url="&lfs-root;/chapter06/gcc.html"/>). >> - >> >> >> -The instructions below let the build machinery perform a >> -bootstrap intentionally. This is necessary if you >> -install the Ada compiler anyway. Even >> -if you don't, a bootstrap is recommended for robustness. >> +The instructions below will make sure that >> bootstrap >> +is preformed intentionally. This is necessary if the > > > s/pref/perf/ ? > > > > akh > > D'oh, thanks. Fernando (or anyone else), please apply this patch too. -- Note: My last name is not Krejzi. Index: general/prog/gcc.xml === --- general/prog/gcc.xml (revision 12729) +++ general/prog/gcc.xml (working copy) @@ -134,7 +134,7 @@ The GNAT compiler can be invoked by executing the gcc binary installed in /opt/gnat/bin. +class="directory">/opt/gnat/bin. You may now remove the GNAT source directory if desired. @@ -183,7 +183,7 @@ The instructions below will make sure that bootstrap -is preformed intentionally. This is necessary if the +is performed intentionally. This is necessary if the Ada compiler is being built anyway. Even if it isn't, a bootstrap is recommended for robustness. To disable bootstrap anyways, pass --disable-bootstrap to the -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] My BLFS checks
On 02/18/2014 06:29 PM, Armin K. wrote: > Hi, I have finished building the part of BLFS I required to get full > build from the systemd source package and have also updated gcc-4.8.2 > instructions. > > The attached patch contains changes I made. I only ask the patch to be > applied without any changes and then the changes can be made later if > necessary so I can see what was I doing wrong (no hard feelings here). > > All packages were run with testsuites (yeah, I can't believe it either), > so I had to build a bit more packages than I actually needed. I still > can't get glib testsuite to finish ... It has been running for half an > hour yet. If it finishes, I'll post the result. > > The build logs of current BLFS packages that I have built are available at: > > http://www.linuxfromscratch.org/~krejzi/7.5-systemd-rc1/logs/postlfs/ > > If the glib manages to complete today, I'll post it too. > > -- > Note: My last name is not Krejzi. > > > I forgot to mark shared-mime-info and desktop-file-utils for LFS 7.5 in my patch. Please mark them too, they seem to work here. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] My BLFS checks
On 02/18/2014 06:38 PM, Bruce Dubbs wrote: > Armin K. wrote: >> Hi, I have finished building the part of BLFS I required to get full >> build from the systemd source package and have also updated gcc-4.8.2 >> instructions. >> >> The attached patch contains changes I made. I only ask the patch to be >> applied without any changes and then the changes can be made later if >> necessary so I can see what was I doing wrong (no hard feelings here). >> >> All packages were run with testsuites (yeah, I can't believe it either), >> so I had to build a bit more packages than I actually needed. I still >> can't get glib testsuite to finish ... It has been running for half an >> hour yet. If it finishes, I'll post the result. >> >> The build logs of current BLFS packages that I have built are available at: >> >> http://www.linuxfromscratch.org/~krejzi/7.5-systemd-rc1/logs/postlfs/ > > Just to verify, was your base system LFS/trunk or LFS/branches/systemd? > >-- Bruce > The latter, but most packages won't know the difference (except Polkit) since the packages they use are same in both versions - none depends on anything systemd specific. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] My BLFS checks
Hi, I have finished building the part of BLFS I required to get full build from the systemd source package and have also updated gcc-4.8.2 instructions. The attached patch contains changes I made. I only ask the patch to be applied without any changes and then the changes can be made later if necessary so I can see what was I doing wrong (no hard feelings here). All packages were run with testsuites (yeah, I can't believe it either), so I had to build a bit more packages than I actually needed. I still can't get glib testsuite to finish ... It has been running for half an hour yet. If it finishes, I'll post the result. The build logs of current BLFS packages that I have built are available at: http://www.linuxfromscratch.org/~krejzi/7.5-systemd-rc1/logs/postlfs/ If the glib manages to complete today, I'll post it too. -- Note: My last name is not Krejzi. Index: general/genlib/dbus-glib.xml === --- general/genlib/dbus-glib.xml (revision 12726) +++ general/genlib/dbus-glib.xml (working copy) @@ -35,7 +35,7 @@ D-Bus API. -&lfs74_checked; +&lfs75_checked; Package Information @@ -98,9 +98,8 @@ commands: -./configure --prefix=/usr \ ---sysconfdir=/etc \ ---libexecdir=/usr/lib/dbus-1.0 \ +./configure --prefix=/usr \ +--sysconfdir=/etc \ --disable-static && make Index: general/genlib/gobject-introspection.xml === --- general/genlib/gobject-introspection.xml (revision 12726) +++ general/genlib/gobject-introspection.xml (working copy) @@ -37,7 +37,7 @@ machine readable format. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/genlib/js.xml === --- general/genlib/js.xml (revision 12726) +++ general/genlib/js.xml (working copy) @@ -36,7 +36,7 @@ written in C/C++. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/genlib/libgcrypt.xml === --- general/genlib/libgcrypt.xml (revision 12726) +++ general/genlib/libgcrypt.xml (working copy) @@ -38,7 +38,7 @@ API. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/genlib/libgpg-error.xml === --- general/genlib/libgpg-error.xml (revision 12726) +++ general/genlib/libgpg-error.xml (working copy) @@ -35,7 +35,7 @@ GnuPG components. . -&lfs74_checked; +&lfs75_checked; Package Information Index: general/genlib/nspr.xml === --- general/genlib/nspr.xml (revision 12726) +++ general/genlib/nspr.xml (working copy) @@ -36,7 +36,7 @@ platform-neutral API for system level and libc like functions. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/graphlib/freetype2.xml === --- general/graphlib/freetype2.xml (revision 12726) +++ general/graphlib/freetype2.xml (working copy) @@ -41,7 +41,7 @@ TrueType fonts. -&lfs74_checked; +&lfs75_checked; Package Information Index: general/prog/dbus-python.xml === --- general/prog/dbus-python.xml (revision 12726) +++ general/prog/dbus-python.xml (working copy) @@ -29,7 +29,7 @@ D-Bus. - &lfs74_checked; + &lfs75_checked; Package Information @@ -107,8 +107,7 @@ mkdir python2 && pushd python2 && PYTHON=/usr/bin/python \ -../configure --prefix=/usr \ - --docdir=/usr/share/doc/dbus-python-&dbus-python-version; && +../configure --prefix=/usr --docdir=/usr/share/doc/dbus-python-&dbus-python-version; && make && popd @@ -125,8 +124,7 @@ mkdir python3 && pushd python3 && PYTHON=/usr/bin/python3\ -../configure --prefix=/usr \ - --docdir=/usr/share/doc/dbus-python-&dbus-python-version; && +../configure --prefix=/usr --docdir=/usr/share/doc/dbus-python-&dbus-python-version; && make && popd Index: general/prog/gcc.xml === --- general/prog/gcc.xml (revision 12726) +++ general/prog/gcc.xml (working copy) @@ -8,8 +8,8 @@ ftp://ftp.gnu.org/gnu/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.bz2";> - - + + https://libre.adacore.com/download/";> + GNAT GPL 2013 Package Information @@ -163,11 +164,7 @@ Installation of GCC -Install GCC by running the -following commands: - - The installation process may overwrite your existi
Re: [blfs-dev] D-Bus testsuite requires pygobject
On 02/18/2014 05:48 PM, Armin K. wrote:
> configure: Full test coverage (--enable-tests=yes) requires Python,
> dbus-python, pygobject
>
> checking for a Python interpreter with version >= 2.6... python
> checking for python... /usr/bin/python
> checking for python version... 2.7
> checking for python platform... linux2
> checking for python script directory...
> ${prefix}/lib/python2.7/site-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.7/site-packages
> checking for Python modules for full test coverage... Traceback (most
> recent call last):
> File "", line 1, in
> ImportError: No module named gobject
> no
> configure: error: cannot import dbus, gobject, dbus.mainloop.glib Python
> modules
>
Also, the testsuite seems to need to be ran as an unprivileged user from
a local session, tests fail through ssh.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] D-Bus testsuite requires pygobject
configure: Full test coverage (--enable-tests=yes) requires Python,
dbus-python, pygobject
checking for a Python interpreter with version >= 2.6... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/site-packages
checking for Python modules for full test coverage... Traceback (most
recent call last):
File "", line 1, in
ImportError: No module named gobject
no
configure: error: cannot import dbus, gobject, dbus.mainloop.glib Python
modules
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Some notes, when building/tagging (B)LFS-7.5-rc1
On 02/18/2014 02:14 PM, Fernando de Oliveira wrote:
> Em 18-02-2014 09:49, Armin K. escreveu:
>> On 02/18/2014 11:37 AM, Fernando de Oliveira wrote:
>>> Some notes and questions, from the work yesterday.
>>>
>>>
>>> 1. At "Count Me"
>>>
>>> http://www.linuxfromscratch.org/cgi-bin/lfscounter.php
>>>
>>> No tag for 7.5-rc1.
>>>
>>> 2. Problem with Valgrind (not in the book, but used in many tests)
>>>
>>> checking the GLIBC_VERSION version... unsupported version 2.19
>>> configure: error: Valgrind requires glibc version 2.2 - 2.17
>>>
>>
>> https://projects.archlinux.org/svntogit/packages.git/tree/trunk/valgrind-3.9.0-glibc-2.19.patch?h=packages/valgrind
>
> Thanks. Had just found it (before reading, but after you sent the message).
>
>>
>>> 3. fcron-3.1.2
>>>
>>> checking Looking for docbook2man-spec file... default
>>> checking Looking for dsssl stylsheets... configure: error:
>>> /usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/docbook.dsl does not
>>> exist.
>>>
>>> I cannot use the switch
>>>
>>> --with-dsssl-dir=/usr/share/sgml/docbook/dsssl-stylesheets-1.79
>>>
>>
>> Do you have docbok-dsssl installed, along with the sgml stack (docbook,
>> open{jade,sp}, sgml-common)?
>
> No. It is always one of the first that I install.
>
>> Did you try removing it entirely?
>
>
>>> I wanted to remove this switch, but am not sure. Since 7.4 or even
>>> before, I have a problem with it.
>>>
>>> Perhaps if a directory is created before, it would work? (only now had
>>> this idea).
>>>
The directory is created by docbook-dsssl package from sgml chapter. If
you didn't install it, either install it or try without using a switch.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] GCC-4.8.2 and bootstrap, uncertain instructions
On 02/18/2014 01:47 PM, Armin K. wrote: > On 02/18/2014 10:18 AM, Pierre Labastie wrote: >> Le 18/02/2014 05:10, Armin K. a écrit : >>> In BLFS, GCC-4.8.2 page has the following: >>> >>> >>> >>> The instructions below let the build machinery perform a “bootstrap” >>> intentionally. This is necessary if you install the Ada compiler anyway. >>> Even if you don't, a bootstrap is recommended for robustness. >>> >>> >>> >>> Which is, ihmo, a correct thing to do - a bootstrap. But yet, >>> instructions down below contain: >>> >>> --disable-bootstrap \ >>> >>> Is this intentional or what? This disables bootstrapping, but the >>> explanation just before the configure block says that bootstrap is being >>> preformed. >>> >>> Also, I'll check this package and post a patch if necessary. >>> >> Well, I had suppressed the disable-bootstrap when I worked on this, >> but later Bruce put it back (while removing ADA instructions at >> the same time). I consider bootstrapping is the correct thing to >> do, unless maybe you are rebuilding the same version of GCC as in >> LFS. >> >> Regards >> Pierre >> > > You are building GCC-4.8.2 with GNAT Core compiler, which is 4.7.4 > xx (snapshot), so the bootstrap is highly recommended. I've done a > build and I'll need to make few changes before submitting them, and one > of them is removing disable-bootstrap and mention to add it back if ada > compiler isn't being built and the same gcc version as in LFS is being > used. Does that sound fair enough? > Okay the build was finished long ago. The full buildlog is available here, along with test results. http://www.linuxfromscratch.org/~krejzi/7.5-systemd-rc1/logs/postlfs/007-gcc.log Just search for "cat <<" phrase when file finishes loading (it's 12 MB). There are few test suite failures. namely FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test These are addressed in LFS, and the instructions need to be brought forward in BLFS, too. FAIL: sourcelocation output - source compiled test FAIL: sourcelocation -findirect-dispatch output - source compiled test FAIL: sourcelocation -O3 output - source compiled test These are Java tests. I am not sure if they were present before but I'm not going to spend my time investigating the reason of the failure. There's also autogen error which has also been fixed in LFS. Other than that, looks good to me. Built without --disable-bootstrap using gnat-gpl-2013. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Some notes, when building/tagging (B)LFS-7.5-rc1
On 02/18/2014 11:37 AM, Fernando de Oliveira wrote:
> Some notes and questions, from the work yesterday.
>
>
> 1. At "Count Me"
>
> http://www.linuxfromscratch.org/cgi-bin/lfscounter.php
>
> No tag for 7.5-rc1.
>
> 2. Problem with Valgrind (not in the book, but used in many tests)
>
> checking the GLIBC_VERSION version... unsupported version 2.19
> configure: error: Valgrind requires glibc version 2.2 - 2.17
>
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/valgrind-3.9.0-glibc-2.19.patch?h=packages/valgrind
> 3. fcron-3.1.2
>
> checking Looking for docbook2man-spec file... default
> checking Looking for dsssl stylsheets... configure: error:
> /usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/docbook.dsl does not
> exist.
>
> I cannot use the switch
>
> --with-dsssl-dir=/usr/share/sgml/docbook/dsssl-stylesheets-1.79
>
Do you have docbok-dsssl installed, along with the sgml stack (docbook,
open{jade,sp}, sgml-common)? Did you try removing it entirely?
> Yesterday, I did one commit and reverted it: was not correct.
>
> I wanted to remove this switch, but am not sure. Since 7.4 or even
> before, I have a problem with it.
>
> Perhaps if a directory is created before, it would work? (only now had
> this idea).
>
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] GCC-4.8.2 and bootstrap, uncertain instructions
On 02/18/2014 10:18 AM, Pierre Labastie wrote: > Le 18/02/2014 05:10, Armin K. a écrit : >> In BLFS, GCC-4.8.2 page has the following: >> >> >> >> The instructions below let the build machinery perform a “bootstrap” >> intentionally. This is necessary if you install the Ada compiler anyway. >> Even if you don't, a bootstrap is recommended for robustness. >> >> >> >> Which is, ihmo, a correct thing to do - a bootstrap. But yet, >> instructions down below contain: >> >> --disable-bootstrap \ >> >> Is this intentional or what? This disables bootstrapping, but the >> explanation just before the configure block says that bootstrap is being >> preformed. >> >> Also, I'll check this package and post a patch if necessary. >> > Well, I had suppressed the disable-bootstrap when I worked on this, > but later Bruce put it back (while removing ADA instructions at > the same time). I consider bootstrapping is the correct thing to > do, unless maybe you are rebuilding the same version of GCC as in > LFS. > > Regards > Pierre > You are building GCC-4.8.2 with GNAT Core compiler, which is 4.7.4 xx (snapshot), so the bootstrap is highly recommended. I've done a build and I'll need to make few changes before submitting them, and one of them is removing disable-bootstrap and mention to add it back if ada compiler isn't being built and the same gcc version as in LFS is being used. Does that sound fair enough? -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] GCC-4.8.2 and bootstrap, uncertain instructions
In BLFS, GCC-4.8.2 page has the following: The instructions below let the build machinery perform a “bootstrap” intentionally. This is necessary if you install the Ada compiler anyway. Even if you don't, a bootstrap is recommended for robustness. Which is, ihmo, a correct thing to do - a bootstrap. But yet, instructions down below contain: --disable-bootstrap \ Is this intentional or what? This disables bootstrapping, but the explanation just before the configure block says that bootstrap is being preformed. Also, I'll check this package and post a patch if necessary. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] lsb_release configuration [Was: ... Iced Tea 2.4.1 and iced tea 2.4.5 sed unknown option to `s']
On 02/17/2014 08:33 PM, Bruce Dubbs wrote: > Fernando de Oliveira wrote: >> Em 17-02-2014 14:34, Pierre Labastie escreveu: >> >>> I do not know the icedtea installer, so I do not know how >>> it gets its information about the LSB. But I think the best >>> would be to consider that everything, which is in LFS, is installed >>> (including /etc/lsb-release), and that lsb-release executable is >>> optional. Ideally, then, the icedtea installer should be taught >>> not to use the executable. Now, if the executable is needed >>> for an easier installation of icedtea-JDK, then it should go to >>> recommended. >> >> Once more: >> >> icedtea install OK without lsb_release >> >> icedtea does not install OK if lsb_release accidentally was installed, >> but the user did not configure it in LFS. >> >> Problem is the divide in configuring before installing, in LFS >> (optional), but nothing being written about configuration in BLFS. > > Add a sed to the lsb_release install instructions: > > sed -i "s|n/a|unavailable|" lsb_release > > Also add a note about configuration and point to LFS. > > If it's really necessary, we can create an LFS specific lsb-release-1.5 > tarball. But I think that's overkill. It really is only a bash script > and a man page generated from the script. > >-- Bruce > The simple fix is just to link to LFS page and say that /etc/lsb-release must be set up using the instructions in LFS. http://www.linuxfromscratch.org/lfs/view/stable/chapter09/theend.html -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] [blfs-book] r12717 - trunk/BOOK/postlfs/security
On 02/17/2014 07:00 PM, ferna...@higgs.linuxfromscratch.org wrote: > Author: fernando > Date: Mon Feb 17 10:00:17 2014 > New Revision: 12717 > > Log: > OpenSSL-1.0.1f: typo. > > Modified: >trunk/BOOK/postlfs/security/openssl.xml > > Modified: trunk/BOOK/postlfs/security/openssl.xml > == > --- trunk/BOOK/postlfs/security/openssl.xml Sun Feb 16 23:08:43 2014 > (r12716) > +++ trunk/BOOK/postlfs/security/openssl.xml Mon Feb 17 10:00:17 2014 > (r12717) > @@ -118,7 +118,7 @@ > > ./config --prefix=/usr \ > --openssldir=/etc/ssl \ > - --libdir=lib \ > + --libdir=/lib \ > shared\ > zlib-dynamic && > make > whoa whoa whoa, this isn't a typo. It is as it should be. It's just a name of subdirectory in /usr for libraries. On i686 it's lib, on x86_64 it's lib64 which is a symlink, so instead of writing through symlink just use lib on x86_64 too. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] LFS systemd 7.5-rc1 is out
On 17.2.2014 4:49, Bruce Dubbs wrote: > Armin K. wrote: > >> http://www.linuxfromscratch.org/lfs/view/7.5-systemd-rc1/ > > Here is a patch to consider: > > --- prologue/bookinfo.xml (revision 10368) > +++ prologue/bookinfo.xml (working copy) > @@ -16,8 +16,7 @@ > Beekmans > > > - Edited by Matthew Burgess > - and Bruce Dubbs > + Edited by Armin K. > > > > Or just delete the 2nd section if you prefer. > > -- Bruce > I'll keep Matt's name, because he originally created the systemd branch. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
