Re: [Devil-linux-develop] Build DL 1.4 failed

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

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
>