devil-linux-develop Mailing List for Devil-Linux (Page 13)

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
> It was attached to my mail.

Oops didn't see it.
Anyway, you attached the wrong file (both times ;-) ), you sent the  
'build' instead of the 'install' log.

Please send /usr/src/lfssystem//build/tmp/LOGS/install/minicom

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

It was attached to my mail.

But also here it is:

checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for ranlib... ranlib
checking for library containing strerror... none required
checking whether NLS is requested... no
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking whether to use NLS... no
checking for kermit... no
checking for tputs in -ltinfo... no
checking for tputs in -lncurses... yes
checking ncurses/termcap.h usability... no
checking ncurses/termcap.h presence... no
checking for ncurses/termcap.h... no
checking for socket in -lsocket... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be included... yes
checking POSIX termios... yes
checking whether termios.h defines TIOCGWINSZ... no
checking whether sys/ioctl.h defines TIOCGWINSZ... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking varargs.h usability... no
checking varargs.h presence... no
checking for varargs.h... no
checking termcap.h usability... yes
checking termcap.h presence... yes
checking for termcap.h... yes
checking termio.h usability... yes
checking termio.h presence... yes
checking for termio.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sgtty.h usability... yes
checking sgtty.h presence... yes
checking for sgtty.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for sys/stat.h... (cached) yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/ttold.h usability... no
checking sys/ttold.h presence... no
checking for sys/ttold.h... no
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for unistd.h... (cached) yes
checking posix1_lim.h usability... no
checking posix1_lim.h presence... no
checking for posix1_lim.h... no
checking for sgtty.h... (cached) yes
checking features.h usability... yes
checking features.h presence... yes
checking for features.h... yes
checking for an ANSI C-conforming const... yes
checking for function prototypes... yes
checking for string.h... (cached) yes
checking for uid_t in sys/types.h... yes
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking return type of signal handlers... void
checking for error_at_line... yes
checking whether closedir returns void... no
checking if malloc debugging is wanted... no
checking for getcwd... yes
checking for getwd... yes
checking for memmove... yes
checking for strerror... yes
checking for strstr... yes
checking for vsnprintf... yes
checking for vprintf... yes
checking for select... yes
checking for snprintf... yes
checking for usleep... yes
checking for getopt... yes
checking for getopt_long... yes
checking for long file names... yes
checking for com line lock directory... /var/lock
checking for default serial port device... /dev/ttyS1
checking for default baud rate... 115200
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating extras/Makefile
config.status: creating extras/linux/Makefile
config.status: creating extras/tables/Makefile
config.status: creating extras/termcap/Makefile
config.status: creating extras/terminfo/Makefile
config.status: creating man/Makefile
config.status: creating lib/Makefile
config.status: creating src/Makefile
config.status: creating po/Makefile.in
config.status: creating minicom.spec
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
make  all-recursive
make[1]: Entering directory `/build/tmp/minicom-2.4'
Making all in doc
make[2]: Entering directory `/build/tmp/minicom-2.4/doc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/build/tmp/minicom-2.4/doc'
Making all in extras
make[2]: Entering directory `/build/tmp/minicom-2.4/extras'
Making all in linux
make[3]: Entering directory `/build/tmp/minicom-2.4/extras/linux'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/tmp/minicom-2.4/extras/linux'
Making all in tables
make[3]: Entering directory `/build/tmp/minicom-2.4/extras/tables'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/tmp/minicom-2.4/extras/tables'
Making all in termcap
make[3]: Entering directory `/build/tmp/minicom-2.4/extras/termcap'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/tmp/minicom-2.4/extras/termcap'
Making all in terminfo
make[3]: Entering directory `/build/tmp/minicom-2.4/extras/terminfo'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/tmp/minicom-2.4/extras/terminfo'
make[3]: Entering directory `/build/tmp/minicom-2.4/extras'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/build/tmp/minicom-2.4/extras'
make[2]: Leaving directory `/build/tmp/minicom-2.4/extras'
Making all in man
make[2]: Entering directory `/build/tmp/minicom-2.4/man'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/build/tmp/minicom-2.4/man'
Making all in po
make[2]: Entering directory `/build/tmp/minicom-2.4/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/build/tmp/minicom-2.4/po'
Making all in lib
make[2]: Entering directory `/build/tmp/minicom-2.4/lib'
rm -f libport.a
ar cru libport.a
ranlib libport.a
make[2]: Leaving directory `/build/tmp/minicom-2.4/lib'
Making all in src
make[2]: Entering directory `/build/tmp/minicom-2.4/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT minicom.o -MD -MP -MF .deps/minicom.Tpo -c
-o minicom.o minicom.c
mv -f .deps/minicom.Tpo .deps/minicom.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT vt100.o -MD -MP -MF .deps/vt100.Tpo -c -o
vt100.o vt100.c
mv -f .deps/vt100.Tpo .deps/vt100.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT config.o -MD -MP -MF .deps/config.Tpo -c
-o config.o config.c
config.c: In function 'loadconv':
config.c:1810: warning: ignoring return value of 'fread', declared
with attribute warn_unused_result
config.c:1811: warning: ignoring return value of 'fread', declared
with attribute warn_unused_result
config.c: In function 'saveconv':
config.c:1824: warning: ignoring return value of 'fwrite', declared
with attribute warn_unused_result
config.c:1825: warning: ignoring return value of 'fwrite', declared
with attribute warn_unused_result
mv -f .deps/config.Tpo .deps/config.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT help.o -MD -MP -MF .deps/help.Tpo -c -o
help.o help.c
mv -f .deps/help.Tpo .deps/help.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT updown.o -MD -MP -MF .deps/updown.Tpo -c
-o updown.o updown.c
updown.c: In function 'mcd':
updown.c:55: warning: ignoring return value of 'getcwd', declared with
attribute warn_unused_result
updown.c:58: warning: ignoring return value of 'chdir', declared with
attribute warn_unused_result
updown.c: In function 'updown':
updown.c:249: warning: ignoring return value of 'pipe', declared with
attribute warn_unused_result
updown.c: In function 'lockfile_create':
updown.c:398: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
updown.c: In function 'runscript':
updown.c:608: warning: ignoring return value of 'pipe', declared with
attribute warn_unused_result
mv -f .deps/updown.Tpo .deps/updown.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT util.o -MD -MP -MF .deps/util.Tpo -c -o
util.o util.c
mv -f .deps/util.Tpo .deps/util.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT dial.o -MD -MP -MF .deps/dial.Tpo -c -o
dial.o dial.c
dial.c: In function 'mputs':
dial.c:230: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
dial.c: In function 'v5_read':
dial.c:742: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'v4_read':
dial.c:751: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'v3_read':
dial.c:770: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'v2_read':
dial.c:785: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'v1_read':
dial.c:801: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'readdialdir':
dial.c:876: warning: ignoring return value of 'fread', declared with
attribute warn_unused_result
dial.c: In function 'dedit_toggle_entry':
dial.c:1093: warning: not protecting local variables: variable length buffer
mv -f .deps/dial.Tpo .deps/dial.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT window.o -MD -MP -MF .deps/window.Tpo -c
-o window.o window.c
mv -f .deps/window.Tpo .deps/window.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT wkeys.o -MD -MP -MF .deps/wkeys.Tpo -c -o
wkeys.o wkeys.c
wkeys.c: In function '_initkeys':
wkeys.c:128: warning: passing argument 1 of 'tgetstr' discards
qualifiers from pointer target type
wkeys.c:110: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
wkeys.c:116: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
wkeys.c:119: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
mv -f .deps/wkeys.Tpo .deps/wkeys.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT ipc.o -MD -MP -MF .deps/ipc.Tpo -c -o
ipc.o ipc.c
mv -f .deps/ipc.Tpo .deps/ipc.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT windiv.o -MD -MP -MF .deps/windiv.Tpo -c
-o windiv.o windiv.c
mv -f .deps/windiv.Tpo .deps/windiv.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT sysdep1.o -MD -MP -MF .deps/sysdep1.Tpo -c
-o sysdep1.o sysdep1.c
mv -f .deps/sysdep1.Tpo .deps/sysdep1.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT sysdep1_s.o -MD -MP -MF
.deps/sysdep1_s.Tpo -c -o sysdep1_s.o sysdep1_s.c
mv -f .deps/sysdep1_s.Tpo .deps/sysdep1_s.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT sysdep2.o -MD -MP -MF .deps/sysdep2.Tpo -c
-o sysdep2.o sysdep2.c
mv -f .deps/sysdep2.Tpo .deps/sysdep2.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT rwconf.o -MD -MP -MF .deps/rwconf.Tpo -c
-o rwconf.o rwconf.c
mv -f .deps/rwconf.Tpo .deps/rwconf.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o
main.o main.c
main.c: In function 'do_output':
main.c:311: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
main.c:313: warning: ignoring return value of 'write', declared with
attribute warn_unused_result
mv -f .deps/main.Tpo .deps/main.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT file.o -MD -MP -MF .deps/file.Tpo -c -o
file.o file.c
file.c: In function 'new_filedir':
file.c:331: warning: ignoring return value of 'chdir', declared with
attribute warn_unused_result
mv -f .deps/file.Tpo .deps/file.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT getsdir.o -MD -MP -MF .deps/getsdir.Tpo -c
-o getsdir.o getsdir.c
mv -f .deps/getsdir.Tpo .deps/getsdir.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT wildmat.o -MD -MP -MF .deps/wildmat.Tpo -c
-o wildmat.o wildmat.c
mv -f .deps/wildmat.Tpo .deps/wildmat.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT common.o -MD -MP -MF .deps/common.Tpo -c
-o common.o common.c
mv -f .deps/common.Tpo .deps/common.Po
gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o
minicom minicom.o vt100.o config.o help.o updown.o util.o dial.o
window.o wkeys.o ipc.o windiv.o sysdep1.o sysdep1_s.o sysdep2.o
rwconf.o main.o file.o getsdir.o wildmat.o common.o ../lib/libport.a
-lncurses -liconv
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT script.o -MD -MP -MF .deps/script.Tpo -c
-o script.o script.c
script.c: In function 'expect':
script.c:514: warning: variable 'seq' might be clobbered by 'longjmp' or 'vfork'
script.c:517: warning: variable 'toact' might be clobbered by
'longjmp' or 'vfork'
mv -f .deps/script.Tpo .deps/script.Po
gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o
runscript script.o sysdep1_s.o common.o ../lib/libport.a -lncurses
-liconv
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
-mtune=i686 -march=i686 -MT ascii-xfr.o -MD -MP -MF
.deps/ascii-xfr.Tpo -c -o ascii-xfr.o ascii-xfr.c
ascii-xfr.c: In function 'check_answer':
ascii-xfr.c:132: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
mv -f .deps/ascii-xfr.Tpo .deps/ascii-xfr.Po
gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o
ascii-xfr ascii-xfr.o ../lib/libport.a -lncurses -liconv
make[2]: Leaving directory `/build/tmp/minicom-2.4/src'
make[2]: Entering directory `/build/tmp/minicom-2.4'
make[2]: Leaving directory `/build/tmp/minicom-2.4'
make[1]: Leaving directory `/build/tmp/minicom-2.4'
removing debug symbols from binaries




2010/12/7 Heiko Zuerker <he...@zu...>:
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>> Still got an error, but later:
>
> At least we got one step further. ;-)
>
>> install: lsof                                     log:
>> /build/tmp/LOGS/install/lsof
>> install: lynx                                     log:
>> /build/tmp/LOGS/install/lynx
>> install: xz                                       log:
>> /build/tmp/LOGS/install/xz
>> install: make                                     log:
>> /build/tmp/LOGS/install/make
>> install: mc                                       log:
>> /build/tmp/LOGS/install/mc
>> install: memcached                                log:
>> /build/tmp/LOGS/install/memcached
>> install: memtest86                                log:
>> /build/tmp/LOGS/install/memtest86
>> install: mgetty                                   log:
>> /build/tmp/LOGS/install/mgetty
>> install: minicom                                  log:
>> /build/tmp/LOGS/install/minicom
>> make: *** [minicom] Error 1
>> make: Leaving directory `/build'
>> make: *** [install] Error 1
>>
>> Attached you will find the file
>> /usr/src/lfssystem//build/tmp/LOGS/build/minicom
>
> Can you please provide the log?
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
> Still got an error, but later:

At least we got one step further. ;-)

> install: lsof                                     log:
> /build/tmp/LOGS/install/lsof
> install: lynx                                     log:
> /build/tmp/LOGS/install/lynx
> install: xz                                       log:
> /build/tmp/LOGS/install/xz
> install: make                                     log:
> /build/tmp/LOGS/install/make
> install: mc                                       log:
> /build/tmp/LOGS/install/mc
> install: memcached                                log:
> /build/tmp/LOGS/install/memcached
> install: memtest86                                log:
> /build/tmp/LOGS/install/memtest86
> install: mgetty                                   log:
> /build/tmp/LOGS/install/mgetty
> install: minicom                                  log:
> /build/tmp/LOGS/install/minicom
> make: *** [minicom] Error 1
> make: Leaving directory `/build'
> make: *** [install] Error 1
>
> Attached you will find the file  
> /usr/src/lfssystem//build/tmp/LOGS/build/minicom

Can you please provide the log?

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

Still got an error, but later:

install: lsof                                     log:
/build/tmp/LOGS/install/lsof
install: lynx                                     log:
/build/tmp/LOGS/install/lynx
install: xz                                       log:
/build/tmp/LOGS/install/xz
install: make                                     log:
/build/tmp/LOGS/install/make
install: mc                                       log:
/build/tmp/LOGS/install/mc
install: memcached                                log:
/build/tmp/LOGS/install/memcached
install: memtest86                                log:
/build/tmp/LOGS/install/memtest86
install: mgetty                                   log:
/build/tmp/LOGS/install/mgetty
install: minicom                                  log:
/build/tmp/LOGS/install/minicom
make: *** [minicom] Error 1
make: Leaving directory `/build'
make: *** [install] Error 1

Attached you will find the file /usr/src/lfssystem//build/tmp/LOGS/build/minicom

Regards.

2010/12/7 mailing dl2 <mai...@gm...>:
> Ok, I will try again.
>
>
> 2010/12/6 Heiko Zuerker <he...@zu...>:
>> Hey,
>>
>> I think I see the issue:
>> Don't use "-r rel-1-4-0 build" when you check out the sources from
>> CVS. I removed that tag, I'm surprised it's still working.
>>
>> Start over with a "make mrproper" please.
>>
>> Heiko
>>
>> Quoting mailing dl2 <mai...@gm...>:
>>
>>> Hello,
>>>
>>>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>>>
>>> Off course!
>>>
>>> Here it is.
>>>
>>> root@dl-rd:/# cat /usr/src/lfssystem/build/tmp/LOGS/build/glibc
>>> grep: ../glibc-patches/0list: No such file or directory
>>> applying patch: ../glibc-patches/0030_all_glibc-respect-env-CPPFLAGS.patch
>>> patching file Makeconfig
>>> patching file config.make.in
>>> Hunk #1 succeeded at 103 (offset 8 lines).
>>> applying patch:
>>> ../glibc-patches/0044_all_glibc-2.10-resolv-nameserver-fallback.patch
>>> patching file resolv/res_init.c
>>> applying patch: ../glibc-patches/0060_all_binutils-2.20-compat.patch
>>> patching file configure
>>> patching file configure.in
>>> applying patch:
>>> ../glibc-patches/0063_all_glibc-2.10-output-int-overflow.patch
>>> patching file stdio-common/printf_fp.c
>>> Hunk #1 succeeded at 888 (offset -3 lines).
>>> patching file stdio-common/vfprintf.c
>>> applying patch:
>>> ../glibc-patches/0066_all_glibc-2.10-malloc-check-race-crash.patch
>>> patching file malloc/hooks.c
>>> applying patch:
>>> ../glibc-patches/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
>>> can't find file to patch at input line 16
>>> Perhaps you used the wrong -p or --strip option?
>>> The text leading up to this was:
>>> --------------------------
>>> |revert cfi additions to clone on i386/x86_64 to workaround problems in
>>> |gcc's unwinder code.  this is not a bug in glibc, it triggers problems
>>> |elsewhere.  this cfi code does not gain us a whole lot anyways.
>>> |
>>> |http://bugs.gentoo.org/202055
>>> |http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
>>> |
>>> |Index: sysdeps/unix/sysv/linux/i386/clone.S
>>> |===================================================================
>>> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/i386/clone.S,v
>>> |retrieving revision 1.27
>>> |retrieving revision 1.26
>>> |diff -u -p -r1.27 -r1.26
>>> |--- sysdeps/unix/sysv/linux/i386/clone.S       3 Dec 2006 23:12:36
>>> -0000       1.27
>>> |+++ sysdeps/unix/sysv/linux/i386/clone.S       4 May 2005 17:52:08
>>> -0000       1.26
>>> --------------------------
>>> File to patch:
>>> Skip this patch? [y]
>>> Skipping patch.
>>> 2 out of 2 hunks ignored
>>> can't find file to patch at input line 42
>>> Perhaps you used the wrong -p or --strip option?
>>> The text leading up to this was:
>>> --------------------------
>>> |Index: sysdeps/unix/sysv/linux/x86_64/clone.S
>>> |===================================================================
>>> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/x86_64/clone.S,v
>>> |retrieving revision 1.7
>>> |retrieving revision 1.6
>>> |diff -u -p -r1.7 -r1.6
>>> |--- sysdeps/unix/sysv/linux/x86_64/clone.S     3 Dec 2006 23:12:36
>>> -0000       1.7
>>> |+++ sysdeps/unix/sysv/linux/x86_64/clone.S     31 Mar 2005 10:00:12
>>> -0000      1.6
>>> --------------------------
>>> File to patch:
>>> Skip this patch? [y]
>>> Skipping patch.
>>> 2 out of 2 hunks ignored
>>>
>>> Regards.
>>>
>>> 2010/12/6 Heiko Zuerker <he...@zu...>:
>>>> Hey,
>>>>
>>>> Quoting mailing dl2 <mai...@gm...>:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to build DL 1.4 with a recent computer and since now I did
>>>>> not succeeded:
>>>>>
>>>>> Here are my step to step process:
>>>>>
>>>>> root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
>>>>> root@dl-rd:/usr/src# cd lfssystem
>>>>> root@dl-rd:/usr/src/lfssystem# cvs
>>>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>>>> login
>>>>> Logging in to
>>>>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>>>>> CVS password:
>>>>> root@dl-rd:/usr/src/lfssystem# cvs -z3
>>>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>>>> co -r rel-1-4-0 build
>>>>> root@dl-rd:/usr/src/lfssystem# cd build/
>>>>> root@dl-rd:/usr/src/lfssystem/build# ./update_src
>>>>> root@dl-rd:/usr/src/lfssystem/build# cr
>>>>>
>>>>> root:/# cd build
>>>>> root:/build# make mrproper unpack
>>>>> root:/build# make menuconfig
>>>>> (no change: use default, and save it when exiting)
>>>>> root:/build# make all
>>>>> mount: proc already mounted
>>>>> mount: none already mounted or /sys busy
>>>>> mount: according to mtab, none is already mounted on /sys
>>>>> make: Entering directory `/build'
>>>>> prepare: prepare                                  log:
>>>>> /build/tmp/LOGS/prepare/prepare
>>>>> prepare: distcc                                   log:
>>>>> /build/tmp/LOGS/prepare/distcc
>>>>> prepare: binutils                                 log:
>>>>> /build/tmp/LOGS/prepare/binutils
>>>>> prepare: gcc-4                                    log:
>>>>> /build/tmp/LOGS/prepare/gcc-4
>>>>> prepare: libtool                                  log:
>>>>> /build/tmp/LOGS/prepare/libtool
>>>>> prepare: autoconf                                 log:
>>>>> /build/tmp/LOGS/prepare/autoconf
>>>>> prepare: bison                                    log:
>>>>> /build/tmp/LOGS/prepare/bison
>>>>> prepare: makedepend                               log:
>>>>> /build/tmp/LOGS/prepare/makedepend
>>>>> prepare: nasm                                     log:
>>>>> /build/tmp/LOGS/prepare/nasm
>>>>> prepare: automake                                 log:
>>>>> /build/tmp/LOGS/prepare/automake
>>>>> prepare: dev86                                    log:
>>>>> /build/tmp/LOGS/prepare/dev86
>>>>> make: Leaving directory `/build'
>>>>> mount: proc already mounted
>>>>> mount: none already mounted or /sys busy
>>>>> mount: according to mtab, none is already mounted on /sys
>>>>> make: Entering directory `/build'
>>>>> build: prepare                                  log:
>>>>> /build/tmp/LOGS/build/prepare
>>>>> build: glibc                                    log:
>>>>> /build/tmp/LOGS/build/glibc
>>>>> make: *** [glibc] Error 1
>>>>> make: Leaving directory `/build'
>>>>> make: *** [build] Error 1
>>>>
>>>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>   Heiko Zuerker
>>>>   http://www.devil-linux.org
>>>>
>>>>
>>>> ----------------------------------------------------------------
>>>> This message was sent using IMP, the Internet Messaging Program.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> What happens now with your Lotus Notes apps - do you make another costly
>>>> upgrade, or settle for being marooned without product support? Time to move
>>>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>>>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>>>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>>>> _______________________________________________
>>>> Devil-linux-develop mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What happens now with your Lotus Notes apps - do you make another costly
>>> upgrade, or settle for being marooned without product support? Time to move
>>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>
>>
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What happens now with your Lotus Notes apps - do you make another costly
>> upgrade, or settle for being marooned without product support? Time to move
>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>

Ok, I will try again.


2010/12/6 Heiko Zuerker <he...@zu...>:
> Hey,
>
> I think I see the issue:
> Don't use "-r rel-1-4-0 build" when you check out the sources from
> CVS. I removed that tag, I'm surprised it's still working.
>
> Start over with a "make mrproper" please.
>
> Heiko
>
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>>
>> Off course!
>>
>> Here it is.
>>
>> root@dl-rd:/# cat /usr/src/lfssystem/build/tmp/LOGS/build/glibc
>> grep: ../glibc-patches/0list: No such file or directory
>> applying patch: ../glibc-patches/0030_all_glibc-respect-env-CPPFLAGS.patch
>> patching file Makeconfig
>> patching file config.make.in
>> Hunk #1 succeeded at 103 (offset 8 lines).
>> applying patch:
>> ../glibc-patches/0044_all_glibc-2.10-resolv-nameserver-fallback.patch
>> patching file resolv/res_init.c
>> applying patch: ../glibc-patches/0060_all_binutils-2.20-compat.patch
>> patching file configure
>> patching file configure.in
>> applying patch:
>> ../glibc-patches/0063_all_glibc-2.10-output-int-overflow.patch
>> patching file stdio-common/printf_fp.c
>> Hunk #1 succeeded at 888 (offset -3 lines).
>> patching file stdio-common/vfprintf.c
>> applying patch:
>> ../glibc-patches/0066_all_glibc-2.10-malloc-check-race-crash.patch
>> patching file malloc/hooks.c
>> applying patch:
>> ../glibc-patches/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
>> can't find file to patch at input line 16
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |revert cfi additions to clone on i386/x86_64 to workaround problems in
>> |gcc's unwinder code.  this is not a bug in glibc, it triggers problems
>> |elsewhere.  this cfi code does not gain us a whole lot anyways.
>> |
>> |http://bugs.gentoo.org/202055
>> |http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
>> |
>> |Index: sysdeps/unix/sysv/linux/i386/clone.S
>> |===================================================================
>> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/i386/clone.S,v
>> |retrieving revision 1.27
>> |retrieving revision 1.26
>> |diff -u -p -r1.27 -r1.26
>> |--- sysdeps/unix/sysv/linux/i386/clone.S       3 Dec 2006 23:12:36
>> -0000       1.27
>> |+++ sysdeps/unix/sysv/linux/i386/clone.S       4 May 2005 17:52:08
>> -0000       1.26
>> --------------------------
>> File to patch:
>> Skip this patch? [y]
>> Skipping patch.
>> 2 out of 2 hunks ignored
>> can't find file to patch at input line 42
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |Index: sysdeps/unix/sysv/linux/x86_64/clone.S
>> |===================================================================
>> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/x86_64/clone.S,v
>> |retrieving revision 1.7
>> |retrieving revision 1.6
>> |diff -u -p -r1.7 -r1.6
>> |--- sysdeps/unix/sysv/linux/x86_64/clone.S     3 Dec 2006 23:12:36
>> -0000       1.7
>> |+++ sysdeps/unix/sysv/linux/x86_64/clone.S     31 Mar 2005 10:00:12
>> -0000      1.6
>> --------------------------
>> File to patch:
>> Skip this patch? [y]
>> Skipping patch.
>> 2 out of 2 hunks ignored
>>
>> Regards.
>>
>> 2010/12/6 Heiko Zuerker <he...@zu...>:
>>> Hey,
>>>
>>> Quoting mailing dl2 <mai...@gm...>:
>>>
>>>> Hello,
>>>>
>>>> I am trying to build DL 1.4 with a recent computer and since now I did
>>>> not succeeded:
>>>>
>>>> Here are my step to step process:
>>>>
>>>> root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
>>>> root@dl-rd:/usr/src# cd lfssystem
>>>> root@dl-rd:/usr/src/lfssystem# cvs
>>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>>> login
>>>> Logging in to
>>>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>>>> CVS password:
>>>> root@dl-rd:/usr/src/lfssystem# cvs -z3
>>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>>> co -r rel-1-4-0 build
>>>> root@dl-rd:/usr/src/lfssystem# cd build/
>>>> root@dl-rd:/usr/src/lfssystem/build# ./update_src
>>>> root@dl-rd:/usr/src/lfssystem/build# cr
>>>>
>>>> root:/# cd build
>>>> root:/build# make mrproper unpack
>>>> root:/build# make menuconfig
>>>> (no change: use default, and save it when exiting)
>>>> root:/build# make all
>>>> mount: proc already mounted
>>>> mount: none already mounted or /sys busy
>>>> mount: according to mtab, none is already mounted on /sys
>>>> make: Entering directory `/build'
>>>> prepare: prepare                                  log:
>>>> /build/tmp/LOGS/prepare/prepare
>>>> prepare: distcc                                   log:
>>>> /build/tmp/LOGS/prepare/distcc
>>>> prepare: binutils                                 log:
>>>> /build/tmp/LOGS/prepare/binutils
>>>> prepare: gcc-4                                    log:
>>>> /build/tmp/LOGS/prepare/gcc-4
>>>> prepare: libtool                                  log:
>>>> /build/tmp/LOGS/prepare/libtool
>>>> prepare: autoconf                                 log:
>>>> /build/tmp/LOGS/prepare/autoconf
>>>> prepare: bison                                    log:
>>>> /build/tmp/LOGS/prepare/bison
>>>> prepare: makedepend                               log:
>>>> /build/tmp/LOGS/prepare/makedepend
>>>> prepare: nasm                                     log:
>>>> /build/tmp/LOGS/prepare/nasm
>>>> prepare: automake                                 log:
>>>> /build/tmp/LOGS/prepare/automake
>>>> prepare: dev86                                    log:
>>>> /build/tmp/LOGS/prepare/dev86
>>>> make: Leaving directory `/build'
>>>> mount: proc already mounted
>>>> mount: none already mounted or /sys busy
>>>> mount: according to mtab, none is already mounted on /sys
>>>> make: Entering directory `/build'
>>>> build: prepare                                  log:
>>>> /build/tmp/LOGS/build/prepare
>>>> build: glibc                                    log:
>>>> /build/tmp/LOGS/build/glibc
>>>> make: *** [glibc] Error 1
>>>> make: Leaving directory `/build'
>>>> make: *** [build] Error 1
>>>
>>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>>>
>>>
>>> --
>>>
>>> Regards
>>>   Heiko Zuerker
>>>   http://www.devil-linux.org
>>>
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What happens now with your Lotus Notes apps - do you make another costly
>>> upgrade, or settle for being marooned without product support? Time to move
>>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>
>> ------------------------------------------------------------------------------
>> What happens now with your Lotus Notes apps - do you make another costly
>> upgrade, or settle for being marooned without product support? Time to move
>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
>
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Hey,

I think I see the issue:
Don't use "-r rel-1-4-0 build" when you check out the sources from  
CVS. I removed that tag, I'm surprised it's still working.

Start over with a "make mrproper" please.

Heiko

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>
> Off course!
>
> Here it is.
>
> root@dl-rd:/# cat /usr/src/lfssystem/build/tmp/LOGS/build/glibc
> grep: ../glibc-patches/0list: No such file or directory
> applying patch: ../glibc-patches/0030_all_glibc-respect-env-CPPFLAGS.patch
> patching file Makeconfig
> patching file config.make.in
> Hunk #1 succeeded at 103 (offset 8 lines).
> applying patch:
> ../glibc-patches/0044_all_glibc-2.10-resolv-nameserver-fallback.patch
> patching file resolv/res_init.c
> applying patch: ../glibc-patches/0060_all_binutils-2.20-compat.patch
> patching file configure
> patching file configure.in
> applying patch:  
> ../glibc-patches/0063_all_glibc-2.10-output-int-overflow.patch
> patching file stdio-common/printf_fp.c
> Hunk #1 succeeded at 888 (offset -3 lines).
> patching file stdio-common/vfprintf.c
> applying patch:
> ../glibc-patches/0066_all_glibc-2.10-malloc-check-race-crash.patch
> patching file malloc/hooks.c
> applying patch:
> ../glibc-patches/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
> can't find file to patch at input line 16
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |revert cfi additions to clone on i386/x86_64 to workaround problems in
> |gcc's unwinder code.  this is not a bug in glibc, it triggers problems
> |elsewhere.  this cfi code does not gain us a whole lot anyways.
> |
> |http://bugs.gentoo.org/202055
> |http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
> |
> |Index: sysdeps/unix/sysv/linux/i386/clone.S
> |===================================================================
> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/i386/clone.S,v
> |retrieving revision 1.27
> |retrieving revision 1.26
> |diff -u -p -r1.27 -r1.26
> |--- sysdeps/unix/sysv/linux/i386/clone.S       3 Dec 2006 23:12:36
> -0000       1.27
> |+++ sysdeps/unix/sysv/linux/i386/clone.S       4 May 2005 17:52:08
> -0000       1.26
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 2 out of 2 hunks ignored
> can't find file to patch at input line 42
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |Index: sysdeps/unix/sysv/linux/x86_64/clone.S
> |===================================================================
> |RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/x86_64/clone.S,v
> |retrieving revision 1.7
> |retrieving revision 1.6
> |diff -u -p -r1.7 -r1.6
> |--- sysdeps/unix/sysv/linux/x86_64/clone.S     3 Dec 2006 23:12:36
> -0000       1.7
> |+++ sysdeps/unix/sysv/linux/x86_64/clone.S     31 Mar 2005 10:00:12
> -0000      1.6
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 2 out of 2 hunks ignored
>
> Regards.
>
> 2010/12/6 Heiko Zuerker <he...@zu...>:
>> Hey,
>>
>> Quoting mailing dl2 <mai...@gm...>:
>>
>>> Hello,
>>>
>>> I am trying to build DL 1.4 with a recent computer and since now I did
>>> not succeeded:
>>>
>>> Here are my step to step process:
>>>
>>> root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
>>> root@dl-rd:/usr/src# cd lfssystem
>>> root@dl-rd:/usr/src/lfssystem# cvs
>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>> login
>>> Logging in to
>>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>>> CVS password:
>>> root@dl-rd:/usr/src/lfssystem# cvs -z3
>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>> co -r rel-1-4-0 build
>>> root@dl-rd:/usr/src/lfssystem# cd build/
>>> root@dl-rd:/usr/src/lfssystem/build# ./update_src
>>> root@dl-rd:/usr/src/lfssystem/build# cr
>>>
>>> root:/# cd build
>>> root:/build# make mrproper unpack
>>> root:/build# make menuconfig
>>> (no change: use default, and save it when exiting)
>>> root:/build# make all
>>> mount: proc already mounted
>>> mount: none already mounted or /sys busy
>>> mount: according to mtab, none is already mounted on /sys
>>> make: Entering directory `/build'
>>> prepare: prepare                                  log:
>>> /build/tmp/LOGS/prepare/prepare
>>> prepare: distcc                                   log:
>>> /build/tmp/LOGS/prepare/distcc
>>> prepare: binutils                                 log:
>>> /build/tmp/LOGS/prepare/binutils
>>> prepare: gcc-4                                    log:
>>> /build/tmp/LOGS/prepare/gcc-4
>>> prepare: libtool                                  log:
>>> /build/tmp/LOGS/prepare/libtool
>>> prepare: autoconf                                 log:
>>> /build/tmp/LOGS/prepare/autoconf
>>> prepare: bison                                    log:
>>> /build/tmp/LOGS/prepare/bison
>>> prepare: makedepend                               log:
>>> /build/tmp/LOGS/prepare/makedepend
>>> prepare: nasm                                     log:
>>> /build/tmp/LOGS/prepare/nasm
>>> prepare: automake                                 log:
>>> /build/tmp/LOGS/prepare/automake
>>> prepare: dev86                                    log:
>>> /build/tmp/LOGS/prepare/dev86
>>> make: Leaving directory `/build'
>>> mount: proc already mounted
>>> mount: none already mounted or /sys busy
>>> mount: according to mtab, none is already mounted on /sys
>>> make: Entering directory `/build'
>>> build: prepare                                  log:
>>> /build/tmp/LOGS/build/prepare
>>> build: glibc                                    log:
>>> /build/tmp/LOGS/build/glibc
>>> make: *** [glibc] Error 1
>>> make: Leaving directory `/build'
>>> make: *** [build] Error 1
>>
>> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>>
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What happens now with your Lotus Notes apps - do you make another costly
>> upgrade, or settle for being marooned without product support? Time to move
>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

> Can you please attach the file /build/tmp/LOGS/build/glibc ?

Off course!

Here it is.

root@dl-rd:/# cat /usr/src/lfssystem/build/tmp/LOGS/build/glibc
grep: ../glibc-patches/0list: No such file or directory
applying patch: ../glibc-patches/0030_all_glibc-respect-env-CPPFLAGS.patch
patching file Makeconfig
patching file config.make.in
Hunk #1 succeeded at 103 (offset 8 lines).
applying patch:
../glibc-patches/0044_all_glibc-2.10-resolv-nameserver-fallback.patch
patching file resolv/res_init.c
applying patch: ../glibc-patches/0060_all_binutils-2.20-compat.patch
patching file configure
patching file configure.in
applying patch: ../glibc-patches/0063_all_glibc-2.10-output-int-overflow.patch
patching file stdio-common/printf_fp.c
Hunk #1 succeeded at 888 (offset -3 lines).
patching file stdio-common/vfprintf.c
applying patch:
../glibc-patches/0066_all_glibc-2.10-malloc-check-race-crash.patch
patching file malloc/hooks.c
applying patch:
../glibc-patches/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|revert cfi additions to clone on i386/x86_64 to workaround problems in
|gcc's unwinder code.  this is not a bug in glibc, it triggers problems
|elsewhere.  this cfi code does not gain us a whole lot anyways.
|
|http://bugs.gentoo.org/202055
|http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
|
|Index: sysdeps/unix/sysv/linux/i386/clone.S
|===================================================================
|RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/i386/clone.S,v
|retrieving revision 1.27
|retrieving revision 1.26
|diff -u -p -r1.27 -r1.26
|--- sysdeps/unix/sysv/linux/i386/clone.S       3 Dec 2006 23:12:36
-0000       1.27
|+++ sysdeps/unix/sysv/linux/i386/clone.S       4 May 2005 17:52:08
-0000       1.26
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 42
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: sysdeps/unix/sysv/linux/x86_64/clone.S
|===================================================================
|RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/x86_64/clone.S,v
|retrieving revision 1.7
|retrieving revision 1.6
|diff -u -p -r1.7 -r1.6
|--- sysdeps/unix/sysv/linux/x86_64/clone.S     3 Dec 2006 23:12:36
-0000       1.7
|+++ sysdeps/unix/sysv/linux/x86_64/clone.S     31 Mar 2005 10:00:12
-0000      1.6
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored

Regards.

2010/12/6 Heiko Zuerker <he...@zu...>:
> Hey,
>
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>> I am trying to build DL 1.4 with a recent computer and since now I did
>> not succeeded:
>>
>> Here are my step to step process:
>>
>> root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
>> root@dl-rd:/usr/src# cd lfssystem
>> root@dl-rd:/usr/src/lfssystem# cvs
>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>> login
>> Logging in to
>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>> CVS password:
>> root@dl-rd:/usr/src/lfssystem# cvs -z3
>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>> co -r rel-1-4-0 build
>> root@dl-rd:/usr/src/lfssystem# cd build/
>> root@dl-rd:/usr/src/lfssystem/build# ./update_src
>> root@dl-rd:/usr/src/lfssystem/build# cr
>>
>> root:/# cd build
>> root:/build# make mrproper unpack
>> root:/build# make menuconfig
>> (no change: use default, and save it when exiting)
>> root:/build# make all
>> mount: proc already mounted
>> mount: none already mounted or /sys busy
>> mount: according to mtab, none is already mounted on /sys
>> make: Entering directory `/build'
>> prepare: prepare                                  log:
>> /build/tmp/LOGS/prepare/prepare
>> prepare: distcc                                   log:
>> /build/tmp/LOGS/prepare/distcc
>> prepare: binutils                                 log:
>> /build/tmp/LOGS/prepare/binutils
>> prepare: gcc-4                                    log:
>> /build/tmp/LOGS/prepare/gcc-4
>> prepare: libtool                                  log:
>> /build/tmp/LOGS/prepare/libtool
>> prepare: autoconf                                 log:
>> /build/tmp/LOGS/prepare/autoconf
>> prepare: bison                                    log:
>> /build/tmp/LOGS/prepare/bison
>> prepare: makedepend                               log:
>> /build/tmp/LOGS/prepare/makedepend
>> prepare: nasm                                     log:
>> /build/tmp/LOGS/prepare/nasm
>> prepare: automake                                 log:
>> /build/tmp/LOGS/prepare/automake
>> prepare: dev86                                    log:
>> /build/tmp/LOGS/prepare/dev86
>> make: Leaving directory `/build'
>> mount: proc already mounted
>> mount: none already mounted or /sys busy
>> mount: according to mtab, none is already mounted on /sys
>> make: Entering directory `/build'
>> build: prepare                                  log:
>> /build/tmp/LOGS/build/prepare
>> build: glibc                                    log:
>> /build/tmp/LOGS/build/glibc
>> make: *** [glibc] Error 1
>> make: Leaving directory `/build'
>> make: *** [build] Error 1
>
> Can you please attach the file /build/tmp/LOGS/build/glibc ?
>
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Hey,

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
> I am trying to build DL 1.4 with a recent computer and since now I did
> not succeeded:
>
> Here are my step to step process:
>
> root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
> root@dl-rd:/usr/src# cd lfssystem
> root@dl-rd:/usr/src/lfssystem# cvs
> -d:pserver:ano...@de...:/cvsroot/devil-linux  
> login
> Logging in to  
> :pserver:ano...@de...:2401/cvsroot/devil-linux
> CVS password:
> root@dl-rd:/usr/src/lfssystem# cvs -z3
> -d:pserver:ano...@de...:/cvsroot/devil-linux
> co -r rel-1-4-0 build
> root@dl-rd:/usr/src/lfssystem# cd build/
> root@dl-rd:/usr/src/lfssystem/build# ./update_src
> root@dl-rd:/usr/src/lfssystem/build# cr
>
> root:/# cd build
> root:/build# make mrproper unpack
> root:/build# make menuconfig
> (no change: use default, and save it when exiting)
> root:/build# make all
> mount: proc already mounted
> mount: none already mounted or /sys busy
> mount: according to mtab, none is already mounted on /sys
> make: Entering directory `/build'
> prepare: prepare                                  log:
> /build/tmp/LOGS/prepare/prepare
> prepare: distcc                                   log:
> /build/tmp/LOGS/prepare/distcc
> prepare: binutils                                 log:
> /build/tmp/LOGS/prepare/binutils
> prepare: gcc-4                                    log:
> /build/tmp/LOGS/prepare/gcc-4
> prepare: libtool                                  log:
> /build/tmp/LOGS/prepare/libtool
> prepare: autoconf                                 log:
> /build/tmp/LOGS/prepare/autoconf
> prepare: bison                                    log:
> /build/tmp/LOGS/prepare/bison
> prepare: makedepend                               log:
> /build/tmp/LOGS/prepare/makedepend
> prepare: nasm                                     log:
> /build/tmp/LOGS/prepare/nasm
> prepare: automake                                 log:
> /build/tmp/LOGS/prepare/automake
> prepare: dev86                                    log:
> /build/tmp/LOGS/prepare/dev86
> make: Leaving directory `/build'
> mount: proc already mounted
> mount: none already mounted or /sys busy
> mount: according to mtab, none is already mounted on /sys
> make: Entering directory `/build'
> build: prepare                                  log:
> /build/tmp/LOGS/build/prepare
> build: glibc                                    log:  
> /build/tmp/LOGS/build/glibc
> make: *** [glibc] Error 1
> make: Leaving directory `/build'
> make: *** [build] Error 1

Can you please attach the file /build/tmp/LOGS/build/glibc ?


-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

I am trying to build DL 1.4 with a recent computer and since now I did
not succeeded:

Here are my step to step process:

root@dl-rd:/usr/src# tar xjf lfssystem-SVN-20070314-cleaned.tar.bz2
root@dl-rd:/usr/src# cd lfssystem
root@dl-rd:/usr/src/lfssystem# cvs
-d:pserver:ano...@de...:/cvsroot/devil-linux login
Logging in to :pserver:ano...@de...:2401/cvsroot/devil-linux
CVS password:
root@dl-rd:/usr/src/lfssystem# cvs -z3
-d:pserver:ano...@de...:/cvsroot/devil-linux
co -r rel-1-4-0 build
root@dl-rd:/usr/src/lfssystem# cd build/
root@dl-rd:/usr/src/lfssystem/build# ./update_src
root@dl-rd:/usr/src/lfssystem/build# cr

root:/# cd build
root:/build# make mrproper unpack
root:/build# make menuconfig
(no change: use default, and save it when exiting)
root:/build# make all
mount: proc already mounted
mount: none already mounted or /sys busy
mount: according to mtab, none is already mounted on /sys
make: Entering directory `/build'
prepare: prepare                                  log:
/build/tmp/LOGS/prepare/prepare
prepare: distcc                                   log:
/build/tmp/LOGS/prepare/distcc
prepare: binutils                                 log:
/build/tmp/LOGS/prepare/binutils
prepare: gcc-4                                    log:
/build/tmp/LOGS/prepare/gcc-4
prepare: libtool                                  log:
/build/tmp/LOGS/prepare/libtool
prepare: autoconf                                 log:
/build/tmp/LOGS/prepare/autoconf
prepare: bison                                    log:
/build/tmp/LOGS/prepare/bison
prepare: makedepend                               log:
/build/tmp/LOGS/prepare/makedepend
prepare: nasm                                     log:
/build/tmp/LOGS/prepare/nasm
prepare: automake                                 log:
/build/tmp/LOGS/prepare/automake
prepare: dev86                                    log:
/build/tmp/LOGS/prepare/dev86
make: Leaving directory `/build'
mount: proc already mounted
mount: none already mounted or /sys busy
mount: according to mtab, none is already mounted on /sys
make: Entering directory `/build'
build: prepare                                  log:
/build/tmp/LOGS/build/prepare
build: glibc                                    log: /build/tmp/LOGS/build/glibc
make: *** [glibc] Error 1
make: Leaving directory `/build'
make: *** [build] Error 1

Thanks.

Regards.

Hey,

I'm currently playing with buildroot to see if we can get it to work  
as our new build environment.
If everything works out, we'll be able to support all kinds of  
platforms (ARM,PPC,X86_64, iX86).

There's still a long way to go and a lot of packages to add to  
buildroot if my initial tests are successful.
I'll let you guys know once things are ready for other folks to start helping.

If things don't work out with buildroot, then we'll have to go back to  
our original idea of using 2 different lfssystems for 32bit and 64bit  
builds, but stick with our current compile scripts.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hey,

I deleted the cvs branch rel-1-4-patches.

We'll be switching to GIT anyway for 1.5, so there's no need for a  
separate branch for 1.4.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Great idea.
I added it to CVS, it'll be included in the next build.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


-----Original Message-----
From: Andrzej Odyniec [mailto:an...@ma...] 
Sent: Monday, November 22, 2010 6:37 PM
To: dev...@li...
Subject: [Devil-linux-develop] mount_cdrom suggestion

Dear Heiko,

I have suggestion about finding proper cdrom in mount_cdrom script. When I
have more, than one device with bootable DL image, sometime improper media
is found as CD-rom, because the only criterion is presence of file
DEVIL_LINUX. 
But if wrong media with different kernel version will be accepted, then boot
proces can be impossible. When machine is in remote place, there is no
method to solve problem.

This situation is probable, when I remotely upgrade image, but new version
is hot, risky and will not boot, so revert to previous image will be
impossible. 
In this situation writing new, hot image as bootcd.*.new is risky and the
only solution is to install-on-usb new image version on other USB device and
change remotely via SOL boot sequence in BIOS. When new version will not
work at all, we can revert to old boot sequence without working OS, but...
this old version from now will find new media (or this new will find old
media).

So maybe better is to modify CD test in mount_cdrom from:

[ -e ${mountpoint}/DEVIL-LINUX ]

to

[ -e ${mountpoint}/DEVIL-LINUX ] && [ "`cat ${mountpoint}/DEVIL-LINUX`" ==
"`cat VERSION`" ]

and like this in other place.

But after this change initrd must be always from this same build (and builds
from this same date will be still undistinguishable, because in version is
no hour).

What do You think about this?

Regards

Andrzej Odyniec

----------------------------------------------------------------------------
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Dear Heiko,

I have suggestion about finding proper cdrom in mount_cdrom script. When I 
have more, than one device with bootable DL image, sometime improper media is 
found as CD-rom, because the only criterion is presence of file DEVIL_LINUX. 
But if wrong media with different kernel version will be accepted, then boot 
proces can be impossible. When machine is in remote place, there is no method 
to solve problem.

This situation is probable, when I remotely upgrade image, but new version is 
hot, risky and will not boot, so revert to previous image will be impossible. 
In this situation writing new, hot image as bootcd.*.new is risky and the only 
solution is to install-on-usb new image version on other USB device and change 
remotely via SOL boot sequence in BIOS. When new version will not work at all, 
we can revert to old boot sequence without working OS, but... this old version 
from now will find new media (or this new will find old media).

So maybe better is to modify CD test in mount_cdrom from:

[ -e ${mountpoint}/DEVIL-LINUX ]

to

[ -e ${mountpoint}/DEVIL-LINUX ] && [ "`cat ${mountpoint}/DEVIL-LINUX`" == 
"`cat VERSION`" ]

and like this in other place.

But after this change initrd must be always from this same build (and builds 
from this same date will be still undistinguishable, because in version is no 
hour).

What do You think about this?

Regards

Andrzej Odyniec

Hey,

After looking around I can confirm that we should stay away from a multilib
system, since it just gets too complicated.
I'm going to play around with "sysroot", this way we may be able support
different architectures better.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org

Hey,

Sorry I may not have been clear on the static thing.
I was only contemplating to have the initial lfssystem statically linked, to
prevent the multilb issues Serge mentioned.

Speaking of the multilib issues, I'm glad you made me aware of that.
I'll play around with it a bit, maybe I find a good workaround. Worst case
scenario, we'll do 2 lfssystems as you guys already said.

On the topic of support for other architectures (which I really would like
to see for DL):
I was once contemplating if we should get rid of our build system completely
and use one maintained by somebody else.
I played around with "buildroot" beginning of this year and I liked it.
Maybe we need to change our approach completely and move to something like
that.
I'm not sure how this would be handled best, we'd probably need to create a
fork of their sources.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org

>>> I’m contemplating on how the lfssystem for 1.5 should look like.
>>>
>>> DL 1.5 will be available as 32 and 64 bit version, so we need to either have
>>> 2 different lfssystems  or one multilib.
>>>
>>> I’m currently more leaning towards the multilib.
>>
>> Yes, I'd go with multilib.
> You know, I've been trying to build 64bit DL during a couple of years. And I
> even managed to get it several times, but the result didn't satisfy me. The main
> problem we'll face is compilation failures due to multi-arch libs availability.
> In my case a lot of 64bit applications try to link against 32lib :( Most cases
> are autoconf mistakes, which are possible to minimize by libs separation, but
> the efforts are huge. The easiest way was a pure 64bit lfssystems. However, I'm
> not the best release engineer and my problems might be related to lack of
> knowledge/experience/etc. So, lets try with the most attractive approach for
> majority of developers. As a plan B, I'd suggest thinking about 2 pure 32bit and
> 64bit systems, but single source and script base. Plus maybe some additional
> logic for handling this environment. More difficulties here, but less
> difficulties in the future.

Good point, I hadn't thought of sloppy autoconf's in the packages.

It's more work to make 2 LFSsystems up front, but much less work
afterwords, not having to fix a bunch of packages.

Plus with 2 LFS's, we're sure a 64 bit compile is really 64 bit.

I change my vote to 2 LFS's.   :-)

 - BS

Hi, let me add my 2 cents.

On 11/19/2010 04:59 PM, Bruce Smith wrote:
>> I’m contemplating on how the lfssystem for 1.5 should look like.
>>
>> DL 1.5 will be available as 32 and 64 bit version, so we need to either have
>> 2 different lfssystems  or one multilib.
>>
>> I’m currently more leaning towards the multilib.
>
> Yes, I'd go with multilib.
You know, I've been trying to build 64bit DL during a couple of years. And I 
even managed to get it several times, but the result didn't satisfy me. The main 
problem we'll face is compilation failures due to multi-arch libs availability. 
In my case a lot of 64bit applications try to link against 32lib :( Most cases 
are autoconf mistakes, which are possible to minimize by libs separation, but 
the efforts are huge. The easiest way was a pure 64bit lfssystems. However, I'm 
not the best release engineer and my problems might be related to lack of 
knowledge/experience/etc. So, lets try with the most attractive approach for 
majority of developers. As a plan B, I'd suggest thinking about 2 pure 32bit and 
64bit systems, but single source and script base. Plus maybe some additional 
logic for handling this environment. More difficulties here, but less 
difficulties in the future.

oftopp: x86 arch is not the only architecture for routers/firewalls/special 
servers. I'll be happy to see DL on arm some day. The "stackable" build 
environment could simplify that.

>
> Do you know if there is any issues compiling DL (1.4 or 32bit) on a
> 64bit host system?  I just upgraded from Ubuntu 10.04 32bit to Ubuntu
> 10.10 64bit, and I haven't tried a DL compile yet.
I use 64bit system and there is no problem. Host system are RHEL5/6 and OpenSuse.

>
>> All the tools which get compiled for DL itself would of course then be only
>> for the target platform.
>
>> One other thought I have is to potentially compile everything statically, so
>> we don’t have to worry about any libraries.
>
> It's been while since I compiled anything static, but it seems like
> the resulting binaries are a HUGE compared; we might have to switch
> from a CD to a DVD distro.  Plus it seems like the memory requirements
> of a static system may increase a lot too.
>
> I'm not a static expert, so please correct me if if I'm wrong.
I have to agree, static linking demands additional memory and disk resources. 
Overhead might be too much. However, we can calculate it - just make test 
"static" system and compare sizes..


Serge

> I’m contemplating on how the lfssystem for 1.5 should look like.
>
> DL 1.5 will be available as 32 and 64 bit version, so we need to either have
> 2 different lfssystems  or one multilib.
>
> I’m currently more leaning towards the multilib.

Yes, I'd go with multilib.

Do you know if there is any issues compiling DL (1.4 or 32bit) on a
64bit host system?  I just upgraded from Ubuntu 10.04 32bit to Ubuntu
10.10 64bit, and I haven't tried a DL compile yet.

> All the tools which get compiled for DL itself would of course then be only
> for the target platform.

> One other thought I have is to potentially compile everything statically, so
> we don’t have to worry about any libraries.

It's been while since I compiled anything static, but it seems like
the resulting binaries are a HUGE compared; we might have to switch
from a CD to a DVD distro.  Plus it seems like the memory requirements
of a static system may increase a lot too.

I'm not a static expert, so please correct me if if I'm wrong.

 - BS

Hey,

 

I'm contemplating on how the lfssystem for 1.5 should look like.

DL 1.5 will be available as 32 and 64 bit version, so we need to either have
2 different lfssystems  or one multilib.

I'm currently more leaning towards the multilib.

 

All the tools which get compiled for DL itself would of course then be only
for the target platform.

 

One other thought I have is to potentially compile everything statically, so
we don't have to worry about any libraries.

 

Thoughts?

 

-- 

 

Regards

   Heiko Zuerker

    <http://www.devil-linux.org> http://www.devil-linux.org

 

 

Hey everyone,

 

I just created a CVS branch "rel-1-4-patches", which is for bugfixes of the
current 1.4 only.

 

You'll have to check the 1.4 out like this:

cvs -z3
-d:pserver:ano...@de...:/cvsroot/devil-linux co
-r rel-1-4-patches build

(I hope this command still works, I copied it out of the docs)

 

The "head" branch will be for the next development release 1.5.

 

-- 

 

Regards

   Heiko Zuerker

    <http://www.devil-linux.org> http://www.devil-linux.org

 

 

Hey,

I just checked all changes into CVS.
The upload to the FTP server is also started, but will probably take another
2 hours to finish.

I upgraded all my VMs to 1.4.1 and everything works fine.

The only issue people will have is that Samba needs to be reconfigured with:
Unix extensions = no
Wide links = yes
So far I couldn't figure out a way around this.
This is a default the samba team changed in samba 3.5.x and improves
security.

I'll upload a test version tomorrow once the clean i686 compile is finished.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org

I was just about to start another test compile, perfect timing!

I added it, we'll know more tomorrow morning.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



-----Original Message-----
From: Serge Leschinsky [mailto:ser...@gm...] 
Sent: Wednesday, November 17, 2010 5:46 PM
To: dev...@li...
Subject: Re: [Devil-linux-develop] glibc 2.10.1

You are welcome :)

Could you please also update openssl? It's a huge security problem actually
(http://marc.info/?l=openssl-announce&m=128992699401945&w=2)

I suppose we should update openssl as a part of the nearest DL update.

Serge

On 11/17/2010 03:38 PM, Heiko Zuerker wrote:
> Thank you sir!
>
> I'll take a closer look at it once I'm done with the glibc stuff.
>


----------------------------------------------------------------------------
--
Beautiful is writing same markup. Internet Explorer 9 supports standards for
HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

You are welcome :)

Could you please also update openssl? It's a huge security problem actually 
(http://marc.info/?l=openssl-announce&m=128992699401945&w=2)

I suppose we should update openssl as a part of the nearest DL update.

Serge

On 11/17/2010 03:38 PM, Heiko Zuerker wrote:
> Thank you sir!
>
> I'll take a closer look at it once I'm done with the glibc stuff.
>

Thank you sir!

I'll take a closer look at it once I'm done with the glibc stuff.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



-----Original Message-----
From: Serge Leschinsky [mailto:ser...@gm...] 
Sent: Wednesday, November 17, 2010 5:03 PM
To: dev...@li...
Subject: Re: [Devil-linux-develop] glibc 2.10.1

Here you are:

ftp://olga.mooo.com/DL_64/scripts.tar.bz2
ftp://olga.mooo.com/DL_64/packages.list

Serge

On 11/17/2010 06:05 AM, Heiko Zuerker wrote:
> Hey,
>
> just the scripts and a list of files you're using should be enough.
>
> Heiko
>
> Quoting Serge Leschinsky<ser...@gm...>:
>
>> Hm.... scripts with sources or just scripts?
>> I tried to keep everything in form of patches, so I guess it's better 
>> to upload everything. Expected size is about 1G.
>>
>> I need some time to clean it up from my mess. Hopefully, it will be 
>> done tonight.
>>
>> Serge
>>
>>
>> On 11/16/2010 02:50 PM, Heiko Zuerker wrote:
>>> I was actually hoping to use the Gentoo security patches, which 
>>> should make our life a bit easier.
>>> Could you upload your scripts so I can take a look at the 64 bit stuff?
>>> I have a couple of ideas which you probably already implemented. ;-)
>>>
>>> Otherwise I agree with your statement, it's probably best to give 
>>> the new glibc a shot.
>>> I'll do some more testing and then upload it.
>>>
>>> Heiko
>>>
>>> Quoting Serge Leschinsky<ser...@gm...>:
>>>
>>>> Heiko,
>>>>
>>>> I think we should migrate to updated lfssytem eventually. However, 
>>>> it will take some time to adapt all current scripts and packages. 
>>>> I'd rather update glibc in
>>>> 1.4 (in order to update dovecot) then freeze 1.4 (open for for 
>>>> bugfixes/security updates only) and start building/using new 
>>>> lfssystem for 1.5.
>>>>
>>>> Probably we will be able to merge DL and DL_64 at this point at 
>>>> least for sources (for now  I use the toolchain with gcc-4.5.1, 
>>>> glibc-2.12,
>>>> binutils-2.20.51.tar.bz2 (it's snapshot 2.20 actually) ).
>>>>
>>>>
>>>> Serge
>>>>
>>>> On 11/16/2010 06:04 AM, Heiko Zuerker wrote:
>>>>> No opinions on this?
>>>>>
>>>>> Heiko
>>>>>
>>>>> Quoting Heiko Zuerker<he...@zu...>:
>>>>>
>>>>>> Hey, I just added glibc 2.10.1 to a test compile, with dovecot 
>>>>>> 2.0.7 and a couple of other updates. I?m looking for opinions if 
>>>>>> we should ?backport? this to DL 1.4, or only make it available in 
>>>>>> the Dev version (1.5.x). --
>>>>>> Regards    Heiko Zuerker http://www.devil-linux.org
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> ----------- Beautiful is writing same markup. Internet Explorer 9 
>>>> supports
>>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&   L3.
>>>> Spend less time writing and  rewriting code and more time creating 
>>>> great experiences on the web. Be a part of the beta today 
>>>> http://p.sf.net/sfu/msIE9-sfdev2dev
>>>> _______________________________________________
>>>> Devil-linux-develop mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> --------- Beautiful is writing same markup. Internet Explorer 9 
>> supports standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM 
>> L2&  L3.
>> Spend less time writing and  rewriting code and more time creating 
>> great experiences on the web. Be a part of the beta today 
>> http://p.sf.net/sfu/msIE9-sfdev2dev
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
>
>


----------------------------------------------------------------------------
--
Beautiful is writing same markup. Internet Explorer 9 supports standards for
HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Works!

Thanks!

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


-----Original Message-----
From: Serge Leschinsky [mailto:ser...@gm...] 
Sent: Wednesday, November 17, 2010 3:47 PM
To: dev...@li...
Subject: Re: [Devil-linux-develop] ippool

Here you are:

sed -i "/^#include.*<sys\/time.h>/a\#include <limits.h>" usl/usl_timer.c ||
exit
1

I also have a patch for it, but it seems to be necessary only for x64 arch.

Serge

PS. Sorry, I'm still not ready to upload sources and scripts :(

On 11/17/2010 08:08 AM, Heiko Zuerker wrote:
> Hey,
>
> is anybody using ippool ?
> Its compilation breaks with the new glibc and I couldn't find a patch yet.
> Just wondering how much effort I need to put in it.
>


----------------------------------------------------------------------------
--
Beautiful is writing same markup. Internet Explorer 9 supports standards for
HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop