hi guys i know that ReiserFS was built into the RH7.3 kernel and i thought that sme5.6 was using that very same kernel. Has anyone tried setting this up on the the 5.6alpha? yours Julian Luton
-----Original Message----- From: Juan Jesus Prieto [mailto:[EMAIL PROTECTED]] Sent: 13 September 2002 10:35 To: E-smith List Subject: Re: [e-smith-devinfo] new kernel+reiserFS: problems with ppp-2.4.0-12.src.rpm Hi charlie, > The other alternative is to build ReiserFS modules to be compatible > with the already installed kernel. The latest RedHat kernels come with > a reiserfs.o module, so it looks quite possible to build it as a > module. No, we need the ReiserFS support in the kernel to mount the root filesystem under reiserfs mode. > > When i try to execute 'rpm -ba ppp.spec' the compiler fails in > > the auth.c because it doesn't found the smbpwd.h. I was trying to > > use the libsmb packages, but this seems not to work. > > Seems not to work? How? Did you install the libsmbpw RPM on your build > host? Yes, I've installed the libsmbpw RPM package from: http://www.pergamentum.com/~atp/software/libsmb/libsmbpw-1.3-1.i386.rpm My build host is a RedHat7.1, with the kernel-source-2.2.19-7.0.8, gcc-2.95.1-3 (the gcc-2.96 version is not very stable). When I execute 'rpm -ba ppp.spec' it seems to compile fine, but when it starts compiling 'auth.c' the process stops and gives the following error: ---------------------------------------------------------------- (...) gcc -O2 -pipe -Wall -g -D_linux_=1 -DHAVE_PATHS_H -DIPX_CHANGE -DHAVE_MULTILINK -DHAVE_MMAP -I../include -DCHAPMS=1 -DUSE_CRYPT=1 -DHAVE_CRYPT_H=1 -DLIBSMB=1 -DHAS_SHADOW -DUSE_PAM -DMPPE=1 -DPLUGIN -c -o auth.o auth.c auth.c:82: smbpwd.h: No existe el fichero o el directorio (in english: The file or directory don't exist) auth.c: In function `scan_authfile': auth.c:1892: warning: implicit declaration of function `setsmbfilepath' auth.c:1893: warning: implicit declaration of function `setsmbpwent' auth.c:1896: warning: implicit declaration of function `getsmbpwent' auth.c:1896: warning: assignment makes pointer from integer without a cast auth.c:1898: dereferencing pointer to incomplete type (...) auth.c:1900: dereferencing pointer to incomplete type auth.c:1905: warning: implicit declaration of function `endsmbpwent' auth.c:1911: dereferencing pointer to incomplete type auth.c:1914: dereferencing pointer to incomplete type auth.c:1919: dereferencing pointer to incomplete type auth.c:1888: warning: `smb' might be used uninitialized in this function make[1]: *** [auth.o] Error 1 make[1]: Saliendo directorio `/root/rpms/BUILD/ppp-2.4.0/pppd' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.90572 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.90572 (%build) ------------------------------------------------------------- So I've tried to insert the smbpwd.h directly under the include directory in the ppp-2.4.0.tar.gz, but the result was: ---------------------------------------------------------------- gcc -O2 -pipe -Wall -g -D_linux_=1 -DHAVE_PATHS_H -DIPX_CHANGE -DHAVE_MULTILINK -DHAVE_MMAP -I../include -DCHAPMS=1 -DUSE_CRYPT=1 -DHAVE_CRYPT_H=1 -DLIBSMB=1 -DHAS_SHADOW -DUSE_PAM -DMPPE=1 -DPLUGIN -c -o auth.o auth.c In file included from auth.c:82: ../include/smbpwd.h:61: conflicting types for `putpwent' /usr/include/pwd.h:85: previous declaration of `putpwent' auth.c: In function `scan_authfile': auth.c:1893: warning: implicit declaration of function `setsmbpwent' auth.c:1905: warning: implicit declaration of function `endsmbpwent' make[1]: *** [auth.o] Error 1 make[1]: Saliendo directorio `/root/rpms/BUILD/ppp-2.4.0/pppd' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.15392 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.15392 (%build) ------------------------------------------------------------- What's your opinion? What am I doing wrong? > I don't believe that you should. smbpwd.h comes with the libsmbpw RPM. > You need to have that installed on your build host. The ppp.spec file > includes a BuildRequires tag to ensure that dependency is met. No, the BuildRequires tag appears like: BuildRequires: kernel-source = %{kversion}-%{krelease} in the ppp-2.4.0-12.src.rpm version. > > > How did you setup this ppp package, charlie?. > > "rpm -ba ppp.spec", after ensuring that pre-requisites are met. I know it :) > Are you sure that it is worth your trouble? Version 5.6 will be in > beta test soon, and that includes your choice of journalling file > system (although we are only supporting ext3, you might be able to > work out how to do a custom install of reiserfs or jfs if you really > care). Thats good news, but I need reiserfs for production servers, and I know reiserfs+kernel-2.2 is a good combination for a journaling system. My reiserfs+idea is to offer kernel-2.2.19-7.0.8rfs.i386.rpm (and the needed ppp-2.4.0-12rfs.i386.rpm) to the e-smith community like an alternative system with journaling support for production servers, while the new smeserver release is tested. Regards. -- Juan J. Prieto [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
