public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: cihan <cihan@enderunix.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 2.95.3 building problem
Date: Thu, 14 Aug 2008 19:01:00 -0000	[thread overview]
Message-ID: <48A473CE.6060101@enderunix.org> (raw)
In-Reply-To: <m3r68sk6gx.fsf@google.com>

Hi
I fixed previous problem but another problem is going on.
output is here
make[1]: Entering directory
checking host system type... i486-slackware-linux-gnu
checking build system type... i486-slackware-linux-gnu
checking for ar... (cached) ar
checking for ranlib... (cached) ranlib
checking for gcc... (cached) /home/cihan/gcc-2.95.3/gcc/xgcc 
-B/home/cihan/gcc-2.95.3/gcc/ -B/usr/local/i486-slackware-linux/bin/
checking whether we are using GNU C... (cached) yes
checking whether /home/cihan/gcc-2.95.3/gcc/xgcc 
-B/home/cihan/gcc-2.95.3/gcc/ -B/usr/local/i486-slackware-linux/bin/ 
accepts -g... (cached) yes
checking for POSIXized ISC... no
checking for a BSD compatible install... (cached) /bin/ginstall -c
checking how to run the C preprocessor... (cached) 
/home/cihan/gcc-2.95.3/gcc/xgcc -B/home/cihan/gcc-2.95.3/gcc/ 
-B/usr/local/i486-slackware-linux/bin/ -E
checking for sys/file.h... (cached) yes
checking for sys/param.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for sys/resource.h... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking whether the C compiler (/home/cihan/gcc-2.95.3/gcc/xgcc 
-B/home/cihan/gcc-2.95.3/gcc/ -B/usr/local/i486-slackware-linux/bin/ -g 
-O2 ) works... yes
checking whether the C compiler (/home/cihan/gcc-2.95.3/gcc/xgcc 
-B/home/cihan/gcc-2.95.3/gcc/ -B/usr/local/i486-slackware-linux/bin/ -g 
-O2 ) is a cross-compiler... no
checking for asprintf... (cached) yes
checking for atexit... (cached) yes
checking for basename... (cached) yes
checking for bcmp... (cached) yes
checking for bcopy... (cached) yes
checking for bzero... (cached) yes
checking for calloc... (cached) yes
checking for clock... (cached) yes
checking for getcwd... (cached) yes
checking for getpagesize... (cached) yes
checking for index... (cached) yes
checking for insque... (cached) yes
checking for memchr... (cached) yes
checking for memcmp... (cached) yes
checking for memcpy... (cached) yes
checking for memmove... (cached) yes
checking for memset... (cached) yes
checking for mkstemps... (cached) no
checking for putenv... (cached) yes
checking for random... (cached) yes
checking for rename... (cached) yes
checking for rindex... (cached) yes
checking for setenv... (cached) yes
checking for sigsetmask... (cached) yes
checking for strcasecmp... (cached) yes
checking for strchr... (cached) yes
checking for strdup... (cached) yes
checking for strncasecmp... (cached) yes
checking for strrchr... (cached) yes
checking for strstr... (cached) yes
checking for strtod... (cached) yes
checking for strtol... (cached) yes
checking for strtoul... (cached) yes
checking for tmpnam... (cached) yes
checking for vasprintf... (cached) yes
checking for vfprintf... (cached) yes
checking for vprintf... (cached) yes
checking for vsprintf... (cached) yes
checking for waitpid... (cached) yes
checking for working alloca.h... (cached) yes
checking for alloca... (cached) yes
checking for ANSI C header files... (cached) yes
checking for pid_t... (cached) yes
checking for vfork.h... (cached) no
checking for working vfork... (cached) yes
checking for sys_errlist... (cached) yes
checking for sys_nerr... (cached) yes
checking for sys_siglist... (cached) yes
checking for getrusage... (cached) yes
checking for on_exit... (cached) yes
checking for psignal... (cached) yes
checking for strerror... (cached) yes
checking for strsignal... (cached) yes
checking for sysconf... (cached) yes
checking for times... (cached) yes
checking for sbrk... (cached) yes
checking for gettimeofday... (cached) yes
creating ./config.status
creating Makefile
creating testsuite/Makefile
creating config.h
make[1]: Entering directory 
`/home/cihan/gcc-2.95.3/i486-slackware-linux/libiberty'
if [ x"no" = xyes ] && [ ! -d pic ]; then \
      mkdir pic; \
    else true; fi
touch stamp-picdir
make[1]: *** No rule to make target `../include/libiberty.h', needed by 
`argv.o'.  Stop.
make[1]: Leaving directory 
`/home/cihan/gcc-2.95.3/i486-slackware-linux/libiberty'
make: *** [all-target-libiberty] Error 2



Ian Lance Taylor wrote:
> cihan <cihan@enderunix.org> writes:
>
>   
>> In file included from /usr/include/sys/types.h:270,
>>                 from /usr/include/stdlib.h:320,
>>                 from ./libgcc2.c:41:
>> /usr/include/bits/pthreadtypes.h:69: warning: unnamed struct/union
>> that defines no instances
>>     
>
> This looks like gcc 2.95.3 can't compile your C library.
> /usr/include/bits/pthreadtypes.h is not part of gcc.
>
>   
>> ./frame.c:55: extra brace group at end of initializer
>> ./frame.c:55: (near initialization for `object_mutex.__data')
>> ./frame.c:55: warning: excess elements in struct initializer
>> ./frame.c:55: warning: (near initialization for `object_mutex.__data')
>>     
>
> This is an attempt to use PTHREAD_MUTEX_INIT, and it looks like your C
> library defines it in a way which gcc 2.95.3 can't handle.
>
> In short, you are in a world of pain.  Why do you want gcc 2.95.3
> anyhow?
>
> Ian
>
>
>   

  reply	other threads:[~2008-08-14 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 20:32 cihan
2008-08-12 20:54 ` Ian Lance Taylor
2008-08-13 19:47   ` cihan
2008-08-14  4:05     ` Ian Lance Taylor
2008-08-14 19:01       ` cihan [this message]
2008-08-14 21:42         ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A473CE.6060101@enderunix.org \
    --to=cihan@enderunix.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).