Re: Failure During Building

[-xlan- via Gcc]

I tried compiling version 12.2.0 and it attempts to access system headers
at /usr/include, but on mac the system headers are stored at

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include.

Here's my error:
rm -rf include-fixed; mkdir include-fixed
chmod a+rx include-fixed
if [ -d ../prev-gcc ]; then \
  cd ../prev-gcc && \
  /Library/Developer/CommandLineTools/usr/bin/make
real-install-headers-tar DESTDIR=`pwd`/../gcc/ \
libsubdir=. ; \
else \
  set -e; for ml in `cat fixinc_list`; do \
sysroot_headers_suffix=`echo ${ml} | sed -e 's/;.*$//'`; \
multi_dir=`echo ${ml} | sed -e 's/^[^;]*;//'`; \
fix_dir=include-fixed${multi_dir}; \
if ! false && test ! -d `echo /usr/include | sed -e :a -e
's,[^/]*/\.\.\/,,' -e ta`; then \
  echo The directory that should contain system headers does not
exist: >&2 ; \
  echo "  `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e
ta`" >&2 ; \
  tooldir_sysinc=`echo
"/lib/gcc/x86_64-apple-darwin21.6.0/12.2.0/../../../../x86_64-apple-darwin21.6.0/sys-include"
| sed -e :a -e "s,[^/]*/\.\.\/,," -e ta`; \
  if test "x`echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,'
-e ta`" = "x${tooldir_sysinc}"; \
  then sleep 1; else exit 1; fi; \
fi; \
/bin/sh ../../gcc-12.2.0/gcc/../mkinstalldirs ${fix_dir}; \
chmod a+rx ${fix_dir} || true; \
(TARGET_MACHINE='x86_64-apple-darwin21.6.0'; srcdir=`cd
../../gcc-12.2.0/gcc; ${PWDCMD-pwd}`; \
  SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \
  gcc_dir=`${PWDCMD-pwd}` ; \
  export TARGET_MACHINE srcdir SHELL MACRO_LIST && \
  cd ../build-x86_64-apple-darwin21.6.0/fixincludes && \
  /bin/sh ./fixinc.sh "${gcc_dir}/${fix_dir}" \
`echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`  ); 
\
rm -f ${fix_dir}/syslimits.h; \
if [ -f ${fix_dir}/limits.h ]; then \
  mv ${fix_dir}/limits.h ${fix_dir}/syslimits.h; \
else \
  cp ../../gcc-12.2.0/gcc/gsyslimits.h ${fix_dir}/syslimits.h; \
fi; \
chmod a+r ${fix_dir}/syslimits.h; \
  done; \
fi
The directory that should contain system headers does not exist:
  /usr/include
make[1]: *** [stmp-fixinc] Error 1
make: *** [all-gcc] Error 2


On Fri, Feb 17, 2023 at 8:04 AM Iain Sandoe  wrote:

>
>
> > On 17 Feb 2023, at 15:37, Jonathan Wakely via Gcc 
> wrote:
> >
> > On Fri, 17 Feb 2023, 15:17 -xlan- via Gcc,  wrote:
> >
> >> I was building gcc version 4.9.1
> >
> >
> > Why?
>
> Indeed, what is the use-case?
> trying to build such an old GCC version on modern macOS could be
> problematic.
>
> > on Mac OS version when I got this error:
> >>
> >> In file included from ../../gcc-4.9.1/gcc/c/c-objc-common.c:33:
> >> In file included from
> >>
> >>
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/new:93:
> >>
> >>
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/exception:184:5:
> >> error: no member named 'fancy_abort' in namespace 'std::__1'; did you
> mean
> >> simply 'fancy_abort'?
> >>_VSTD::abort();
> >>^~~
> >>
> >
> >
> > The GCC sources define 'abort' as a macro, which appears to be
> incompatible
> > with LLVM's libc++.
> >
> > You might be able to compile using -stdlib=libstdc++ instead.
>
> There are no headers for libstdc++ in SDKs for OSX 10.13 + (so you would
> need also to find an
> older SDK and then build with an OSX target of say 10.12).
>
> What you are trying to do is going to required quite advanced techniques
> to deal with the difference in the OS, compiler and bootstrap tools.  I
> have not attempted anything < GCC-5 on newer machines.
>
> Iain
>
>
>
>

gcc-12-20230218 is now available

[GCC Administrator via Gcc]

Snapshot gcc-12-20230218 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/12-20230218/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-12 revision 5fa1f732537883908f071f0b0c32f0e9dc5194ff

You'll find:

 gcc-12-20230218.tar.xz   Complete GCC

  SHA256=0cfb181f9988cf389c85e55933b44fe5136752a5905901a22dfcce8510d0ec0c
  SHA1=0cbd17aa8ccf7f45b7981b69ed406f3f9594ac64

Diffs from 12-20230211 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-12
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

Re: Failure During Building

[Iain Sandoe]

Hi

> On 18 Feb 2023, at 20:28, -xlan-  wrote:
> 
> I tried compiling version 12.2.0 and it attempts to access system headers at 
> /usr/include, but on mac the system headers are stored at 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include.

For supported x86_64 GCC versions (at present 12 and trunk) on macOS12.

It is usually easiest to install the Xcode Command Line Tools - the SDK path is 
then /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk

then add the following to your configure line:

—with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk

If you want to use the set in Xcode then add the following to your configure 
line:

—with-sysroot=`xcrun --show-sdk-path`

I prefer/recommend the first option.
HTH,
Iain

Re: GSOC 2023 Contribution Request

[Kritika Rag via Gcc]

Hello Team,

Just want to know is there any update on my application?

On Mon, 13 Feb, 2023, 19:04 Kritika Rag,  wrote:

> Hello Sir/Mam,
>
>
>
> I’m Kritika Rag, a Computer Science pre-final year undergraduate student
> from India. I’m quite passionate about web development and competitive
> programming and now I’m looking forward to contributing to open-source
> projects. I believe that GSOC 2023 would provide me with the best way to
> start my open-source contribution journey.
>
>
>
> Since I’m a competitive programmer, I have excellent command over Data
> Structures & Algorithms and my primary language is C++, so C++ and GCC are
> something that I use daily, therefore I would love to make my contributions
> to GCC projects. After going through all the projects listed on GCC Wiki
> , these are
> the projects(any one of them) to which I would like to contribute:
>
>1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm
>practicing algorithms on Leetcode, GFG, etc., or giving CP contests on
>CodeChef, Codeforces, etc., Test case failures are something I encounter
>daily. Working on the project would be an interesting dig for me to learn
>about the inner workings of something that I see daily and make
>improvements to it.
>2.  Library Infrastructure - As quoted *"These tasks are about
>improving the utility routine library used by GCC. If you like data
>structures, these may be for you", *and being a data structures
>enthusiast I do believe that I'll be able to put my best knowledge to use
>in this project.
>
> Lastly, thank you so much for providing these opportunities, I would be
> grateful if you would provide me the opportunity to work with your
> organization. Looking forward to hearing from you soon.
>
> Thanks and Regards,
> Kritika Rag
>
>
>
> Sent from Mail  for
> Windows
>
>
>