Re: 2.6.24-rc4-mm1: VDSOSYM build error
* Andrew Morton <[EMAIL PROTECTED]> wrote: > On Thu, 6 Dec 2007 18:28:25 -0500 > "Miles Lane" <[EMAIL PROTECTED]> wrote: > > > How can I find Roland's patches, so I can try backing them out? > > I looked in the broken out patches and only saw one related > > to VDSO. Backing it out did not help. I tried searching for > > messages to LKML sent by "roland" but mostly got a bunch of > > folks sending spam. > > They're all clumped into git-x86.patch. Hard. in theory the git merges could be generated as a flat series of patch files: x86.git.foo-fixes.patch x86.git.bar-updates.patch x86.git.foo-fixes-feh.patch ... which could also include the commit log. "git-log -p" might be a suitable generator. For example, x86.git can be processed per commit, via this script: for N in `git-rev-list --reverse --no-merges --remove-empty master..mm`; do git-log -p $N done the following git-export-quilt script (just wrote it, might be buggy, so careful - and it blows away the patches/ directory wherever you run it) will generate a series file into patches/series that can be applied via quilt: rm -rf patches mkdir patches for N in `git-rev-list --reverse --no-merges --remove-empty master..mm`; do git-log -p -1 $N > .tmp export SUBJECT=`head -5 .tmp | tail -1` # generate filename out of subject line: FILE=x86.git-"`echo $SUBJECT | cut -c10- | tr '[:punct:] \t' '-' | tr -s - | tr '[:upper:]' '[:lower:]'`" # generate unique name: while [ -f patches/$FILE.patch ]; do FILE="$FILE"_; done echo $FILE.patch mv .tmp patches/$FILE.patch echo $FILE.patch >> patches/series done ls -l patches/series i ran this script over x86.git and it produced a patch series with 247 patches that quilt was able to push correctly. (in theory this concept should work for other git trees too - but i have not tried it) this would increase the series size quite substantially though - but it would make cherry-picking and patch based bisection a lot easier. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
* Andrew Morton [EMAIL PROTECTED] wrote: On Thu, 6 Dec 2007 18:28:25 -0500 Miles Lane [EMAIL PROTECTED] wrote: How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by roland but mostly got a bunch of folks sending spam. They're all clumped into git-x86.patch. Hard. in theory the git merges could be generated as a flat series of patch files: x86.git.foo-fixes.patch x86.git.bar-updates.patch x86.git.foo-fixes-feh.patch ... which could also include the commit log. git-log -p might be a suitable generator. For example, x86.git can be processed per commit, via this script: for N in `git-rev-list --reverse --no-merges --remove-empty master..mm`; do git-log -p $N done the following git-export-quilt script (just wrote it, might be buggy, so careful - and it blows away the patches/ directory wherever you run it) will generate a series file into patches/series that can be applied via quilt: rm -rf patches mkdir patches for N in `git-rev-list --reverse --no-merges --remove-empty master..mm`; do git-log -p -1 $N .tmp export SUBJECT=`head -5 .tmp | tail -1` # generate filename out of subject line: FILE=x86.git-`echo $SUBJECT | cut -c10- | tr '[:punct:] \t' '-' | tr -s - | tr '[:upper:]' '[:lower:]'` # generate unique name: while [ -f patches/$FILE.patch ]; do FILE=$FILE_; done echo $FILE.patch mv .tmp patches/$FILE.patch echo $FILE.patch patches/series done ls -l patches/series i ran this script over x86.git and it produced a patch series with 247 patches that quilt was able to push correctly. (in theory this concept should work for other git trees too - but i have not tried it) this would increase the series size quite substantially though - but it would make cherry-picking and patch based bisection a lot easier. Ingo -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
I found: http://marc.info/?l=linux-kernel=119550978915647=2 through http://marc.info/?l=linux-kernel=119551057816829=2 (I was unable to locate the 6th patch in the set) When I tried backing out the patches, there were tons of errors. I guess I'll punt on trying to build this MM tree. Sorry. Miles -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
On Thu, 6 Dec 2007 18:28:25 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote: > How can I find Roland's patches, so I can try backing them out? > I looked in the broken out patches and only saw one related > to VDSO. Backing it out did not help. I tried searching for > messages to LKML sent by "roland" but mostly got a bunch of > folks sending spam. > They're all clumped into git-x86.patch. Hard. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by "roland" but mostly got a bunch of folks sending spam. Thanks, Miles -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
On Thu, 06 Dec 2007 23:28:38 +0100 Laurent Riffard <[EMAIL PROTECTED]> wrote: > Le 05.12.2007 06:17, Andrew Morton a écrit : > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.24-rc4-mm1/ > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/ > > LDS arch/x86/vdso/vdso32/vdso32.lds > AS arch/x86/vdso/vdso32/note.o > AS arch/x86/vdso/vdso32/int80.o > VDSOarch/x86/vdso/vdso32-int80.so.dbg > OBJCOPY arch/x86/vdso/vdso32-int80.so > AS arch/x86/vdso/vdso32/sysenter.o > VDSOarch/x86/vdso/vdso32-sysenter.so.dbg > OBJCOPY arch/x86/vdso/vdso32-sysenter.so > AS arch/x86/vdso/vdso32.o > CC arch/x86/vdso/vdso32-setup.o > VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds > VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds > VDSOSYM arch/x86/vdso/vdso32-syms.lds > --- - 2007-12-06 23:23:08.785302925 +0100 > +++ arch/x86/vdso/vdso32-int80-syms.lds 2007-12-06 23:23:08.0 +0100 > @@ -3,4 +3,3 @@ > VDSO32_sigreturn = 0x0400; > VDSO32_vsyscall = 0x0414; > VDSO32_vsyscall_eh_frame_size = 0x044; > -VDSO32_vsyscall_eh_frame_size = 0x058; > make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1 > make: *** [arch/x86/vdso] Error 2 Dunno. Maybe Roland's VDSO rework? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
Le 05.12.2007 06:17, Andrew Morton a écrit : > Temporarily at > http://userweb.kernel.org/~akpm/2.6.24-rc4-mm1/ > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/ LDS arch/x86/vdso/vdso32/vdso32.lds AS arch/x86/vdso/vdso32/note.o AS arch/x86/vdso/vdso32/int80.o VDSOarch/x86/vdso/vdso32-int80.so.dbg OBJCOPY arch/x86/vdso/vdso32-int80.so AS arch/x86/vdso/vdso32/sysenter.o VDSOarch/x86/vdso/vdso32-sysenter.so.dbg OBJCOPY arch/x86/vdso/vdso32-sysenter.so AS arch/x86/vdso/vdso32.o CC arch/x86/vdso/vdso32-setup.o VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds VDSOSYM arch/x86/vdso/vdso32-syms.lds --- - 2007-12-06 23:23:08.785302925 +0100 +++ arch/x86/vdso/vdso32-int80-syms.lds 2007-12-06 23:23:08.0 +0100 @@ -3,4 +3,3 @@ VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x044; -VDSO32_vsyscall_eh_frame_size = 0x058; make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1 make: *** [arch/x86/vdso] Error 2 # cat arch/x86/vdso/vdso32-int80-syms.lds VDSO32_PRELINK = 0x0; VDSO32_rt_sigreturn = 0x040c; VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x044; # cat arch/x86/vdso/vdso32-sysenter-syms.lds VDSO32_PRELINK = 0x0; VDSO32_SYSENTER_RETURN = 0x0424; VDSO32_rt_sigreturn = 0x040c; VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x058; # scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux calimero 2.6.24-rc4-g81b45b40 #2 PREEMPT Thu Dec 6 00:39:02 CET 2007 i686 GNU/Linux Gnu C 4.1.3 Gnu make 3.81 binutils 2.18 util-linux 2.13 mount 2.13 module-init-tools 3.3-pre2 e2fsprogs 1.40.2 reiserfsprogs 3.6.19 reiser4progs 1.0.6 pcmciautils014 PPP2.4.4 Linux C Library2.6.1 Dynamic linker (ldd) 2.6.1 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 oprofile 0.9.3 Sh-utils 5.97 udev 113 wireless-tools 29 Modules Loaded radeon drm lp nls_iso8859_1 nls_cp850 vfat fat reiser4 lzo_decompress lzo_compress eeprom w83781d hwmon_vid snd_ens1371 gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event firewire_ohci firewire_core snd_seq sg crc_itu_t snd_timer snd_seq_device sr_mod cdrom uhci_hcd snd i2c_viapro ohci1394 ata_generic pcspkr floppy 8250_pnp 8250 serial_core soundcore snd_page_alloc via686a rtc ieee1394 usbcore parport_pc parport ne2k_pci 8390 via_agp agpgart evdev dm_snapshot reiserfs sd_mod pata_via libata scsi_mod dm_mirror dm_mod .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.24-rc4-mm1 # Thu Dec 6 23:05:19 2007 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y # CONFIG_GENERIC_GPIO is not set CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=15 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_NAMESPACES is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y
Re: 2.6.24-rc4-mm1: VDSOSYM build error
Le 05.12.2007 06:17, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.24-rc4-mm1/ Will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/ LDS arch/x86/vdso/vdso32/vdso32.lds AS arch/x86/vdso/vdso32/note.o AS arch/x86/vdso/vdso32/int80.o VDSOarch/x86/vdso/vdso32-int80.so.dbg OBJCOPY arch/x86/vdso/vdso32-int80.so AS arch/x86/vdso/vdso32/sysenter.o VDSOarch/x86/vdso/vdso32-sysenter.so.dbg OBJCOPY arch/x86/vdso/vdso32-sysenter.so AS arch/x86/vdso/vdso32.o CC arch/x86/vdso/vdso32-setup.o VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds VDSOSYM arch/x86/vdso/vdso32-syms.lds --- - 2007-12-06 23:23:08.785302925 +0100 +++ arch/x86/vdso/vdso32-int80-syms.lds 2007-12-06 23:23:08.0 +0100 @@ -3,4 +3,3 @@ VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x044; -VDSO32_vsyscall_eh_frame_size = 0x058; make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1 make: *** [arch/x86/vdso] Error 2 # cat arch/x86/vdso/vdso32-int80-syms.lds VDSO32_PRELINK = 0x0; VDSO32_rt_sigreturn = 0x040c; VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x044; # cat arch/x86/vdso/vdso32-sysenter-syms.lds VDSO32_PRELINK = 0x0; VDSO32_SYSENTER_RETURN = 0x0424; VDSO32_rt_sigreturn = 0x040c; VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x058; # scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux calimero 2.6.24-rc4-g81b45b40 #2 PREEMPT Thu Dec 6 00:39:02 CET 2007 i686 GNU/Linux Gnu C 4.1.3 Gnu make 3.81 binutils 2.18 util-linux 2.13 mount 2.13 module-init-tools 3.3-pre2 e2fsprogs 1.40.2 reiserfsprogs 3.6.19 reiser4progs 1.0.6 pcmciautils014 PPP2.4.4 Linux C Library2.6.1 Dynamic linker (ldd) 2.6.1 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 oprofile 0.9.3 Sh-utils 5.97 udev 113 wireless-tools 29 Modules Loaded radeon drm lp nls_iso8859_1 nls_cp850 vfat fat reiser4 lzo_decompress lzo_compress eeprom w83781d hwmon_vid snd_ens1371 gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event firewire_ohci firewire_core snd_seq sg crc_itu_t snd_timer snd_seq_device sr_mod cdrom uhci_hcd snd i2c_viapro ohci1394 ata_generic pcspkr floppy 8250_pnp 8250 serial_core soundcore snd_page_alloc via686a rtc ieee1394 usbcore parport_pc parport ne2k_pci 8390 via_agp agpgart evdev dm_snapshot reiserfs sd_mod pata_via libata scsi_mod dm_mirror dm_mod .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.24-rc4-mm1 # Thu Dec 6 23:05:19 2007 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y # CONFIG_GENERIC_GPIO is not set CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=15 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_NAMESPACES is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y #
Re: 2.6.24-rc4-mm1: VDSOSYM build error
On Thu, 06 Dec 2007 23:28:38 +0100 Laurent Riffard [EMAIL PROTECTED] wrote: Le 05.12.2007 06:17, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.24-rc4-mm1/ Will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/ LDS arch/x86/vdso/vdso32/vdso32.lds AS arch/x86/vdso/vdso32/note.o AS arch/x86/vdso/vdso32/int80.o VDSOarch/x86/vdso/vdso32-int80.so.dbg OBJCOPY arch/x86/vdso/vdso32-int80.so AS arch/x86/vdso/vdso32/sysenter.o VDSOarch/x86/vdso/vdso32-sysenter.so.dbg OBJCOPY arch/x86/vdso/vdso32-sysenter.so AS arch/x86/vdso/vdso32.o CC arch/x86/vdso/vdso32-setup.o VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds VDSOSYM arch/x86/vdso/vdso32-syms.lds --- - 2007-12-06 23:23:08.785302925 +0100 +++ arch/x86/vdso/vdso32-int80-syms.lds 2007-12-06 23:23:08.0 +0100 @@ -3,4 +3,3 @@ VDSO32_sigreturn = 0x0400; VDSO32_vsyscall = 0x0414; VDSO32_vsyscall_eh_frame_size = 0x044; -VDSO32_vsyscall_eh_frame_size = 0x058; make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1 make: *** [arch/x86/vdso] Error 2 Dunno. Maybe Roland's VDSO rework? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by roland but mostly got a bunch of folks sending spam. Thanks, Miles -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
On Thu, 6 Dec 2007 18:28:25 -0500 Miles Lane [EMAIL PROTECTED] wrote: How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by roland but mostly got a bunch of folks sending spam. They're all clumped into git-x86.patch. Hard. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc4-mm1: VDSOSYM build error
I found: http://marc.info/?l=linux-kernelm=119550978915647w=2 through http://marc.info/?l=linux-kernelm=119551057816829w=2 (I was unable to locate the 6th patch in the set) When I tried backing out the patches, there were tons of errors. I guess I'll punt on trying to build this MM tree. Sorry. Miles -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
