[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#643945: marked as done (Failed to build GCC from source: “No place specified to document hook TARGET_ASM_OPEN_PAREN”)

Your message dated Sat, 01 Oct 2011 11:21:42 +0200
with message-id <4E86DBA6.10803@debian.org>
and subject line Re: Bug#643945: Failed to build GCC from source: “No place specified to document hook TARGET_ASM_OPEN_PAREN”
has caused the Debian Bug report #643945,
regarding Failed to build GCC from source: “No place specified to document hook TARGET_ASM_OPEN_PAREN”
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
643945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643945
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.6 source
Version: 4.6.1-4 (same with 4.6.1-13 too)

Got error “No place specified to document hook TARGET_ASM_OPEN_PAREN” during install after a build of GCC 4.6 from source.

The bug is similar to this one:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48378

The above link is FSF GCC source specific, and as this one occurred with a Debian source archive, I though this would be better to submit it to Debian.

The above similar bug report states this may be due to an attempt to build GCC from within its source directory. But when the error occurs, I am building from a pear build directory.

Detailed context of operations:

I used GCC 4.6 source from Debian Wheezy (same result with source with Sid), which I built from Ubuntu Maverick.
Source archive was retrieved there:
http://packages.debian.org/source/wheezy/gcc-4.6

Source was unpacked in a directory named “source”, a pear “build” directory was created, and configure was invoked as “../source/configure” from the build directory.

Options passed to configure was “--enable-libada --enable-libssp --enable-languages=c,c++,ada --disable-rpath --disable-nls”. Then, “make” and then “sudo make install”. “make” is fine, error occurs only during “sudo make install”.

Retried multiple times after cleaning the “/usr/local” directory, the result is always the same; can't build.

This error does not occurs with original GCC 4.6 source as retrieved from:
ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.6.1/


Additional required informations:

Restult of “uname -a”:
>>>
Linux ***** 2.6.31-10-rt #153-Ubuntu SMP PREEMPT RT Tue Jan 12 10:42:21 UTC 2010 i686 GNU/Linux
<<<

Exact error message:
>>>
(null): No place specified to document hook TARGET_ASM_OPEN_PAREN

make[2]: *** [s-tm-texi] Erreur 1
make[2]: quittant le répertoire « /home/yannick/Bureau/gcc/gcc-4.6-4.6.1/build/gcc »
make[1]: *** [install-gcc] Erreur 2
make[1]: quittant le répertoire « /home/yannick/Bureau/gcc/gcc-4.6-4.6.1/build »
make: *** [install] Erreur 2
<<<

Exact sequence of commands:
>>>
../source/configure --enable-libada --enable-libssp --enable-languages=c,c++,ada --disable-rpath --disable-nls
make
sudo make install
<<<


Apologizes if I ever made something wrong (I am not very versed at Debian stuff and processes).


--
Yannick Duchêne

--- End Message ---
--- Begin Message --- 
invalid. you need to apply the patches to build the sources from the package.

--- End Message ---
Reply to: