On 07/13/2013 09:20 PM, Aleksandar Kuktin wrote:
> After you try it all again with logging, and if it fails, check to see
> if there are any mention (in the sense of definitions) of LONG64 in the
> log, and also in the working directory.
>
> grep --color -Hn -C1 LONG64 your_log_file.log
> find /your/working/directory -exec grep --color -Hn -C1 LONG64 {} \;
>
> If there are no results, and especially if noone else has a solution,
> then things are about to get really, really messy.
>
> What architecture are you using? What does `uname -m' say?
x86_64 is my arch.I find no mention of LONG64 in the log file. Incidentally, the log file is on pastebin at... http://pastebin.com/MUnQH92w The... find /your/working/directory -exec grep --color -Hn -C1 LONG64 {} \; ...command produces: ../SDL-1.2.15/src/video/x11/SDL_x11sym.h-165- */ ../SDL-1.2.15/src/video/x11/SDL_x11sym.h:166:#ifdef LONG64 ../SDL-1.2.15/src/video/x11/SDL_x11sym.h-167-SDL_X11_MODULE(IO_32BIT) From SDL_x11sym.h: #ifdef LONG64 SDL_X11_MODULE(IO_32BIT) SDL_X11_SYM(int,_XData32,(Display *dpy,register long *data,unsigned len),(dpy,data,len),return) SDL_X11_SYM(void,_XRead32,(Display *dpy,register long *data,long len),(dpy,data,len),) #endif -- -=[Ty]=- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
