Hi,

I am running openSUSE 11.0 (x86) and wanted to update the darcs RPMs that are
available via the openSUSE Build service (they currently provide darcs-1.0.9).

The package has been built with git support, by running "./configure
--enable-git".

However, when trying to enable this feature in darcs 2.0.2, I get a
compilation failure.

Here are the steps to reproduce the error:

$ tar zxvf darcs-2.0.2.tar.gz
$ cd darcs-2.0.2
$ tar jxvf ../git-1.5.6.5.tar.bz2
$ ln -s git-1.5.6.5 git
$ make -C git libgit.a
$ ./configure --enable-git
$ make

At this point, the compilation fails with the following error:

[ghc] src/c_compat.o
/tmp/ghc32206_0/ghc32206_0.s: Assembler messages:

/tmp/ghc32206_0/ghc32206_0.s:199:0:
     Error: file number 2 already allocated
make: *** [src/c_compat.o] Error 1

$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 6.8.2
$ gcc --version
gcc (SUSE Linux) 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036]
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I attached the config.log file. Let me know if you need anything else. Thanks!

Bye,
	LenZ
-- 
------------------------------------------------------------------
 Lenz Grimmer <lenz@grimmer.com>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@jabber.org]                /\\
 http://www.lenzg.org/                                       V_V

Attachments

• config.log

On Mon, Aug 18, 2008 at 8:34 PM, Lenz Grimmer <bugs@darcs.net> wrote:
>
> New submission from Lenz Grimmer <lenz@grimmer.com>:
>
> Hi,
>
> I am running openSUSE 11.0 (x86) and wanted to update the darcs RPMs that are
> available via the openSUSE Build service (they currently provide darcs-1.0.9).
>
> The package has been built with git support, by running "./configure
> --enable-git".
>
> However, when trying to enable this feature in darcs 2.0.2, I get a
> compilation failure.

Sorry, but due to bitrot and lack of interest we have remove git
support from darcs.  We may have missed something in the configure
script though.

Jason

Thanks for the bug report!  I've checked the configure script: no references to
git, so I suppose the script is correct.

The code is always there in version control if somebody wants to take it on :-)

Hi Jason,

thanks for your message!

On Tue, Aug 19, 2008 at 5:35 AM, Jason Dagit <dagit@codersbase.com> wrote:

> Sorry, but due to bitrot and lack of interest we have remove git
> support from darcs.  We may have missed something in the configure
> script though.

I see - thanks for the clarification! I will update the darcs RPM on
the openSUSE build service to 2.0.2 now and disable the git support
from there.

Thanks! Keep up the good work.

LenZ

Hi,

On 08/19/2008 08:42 AM, Eric Kow wrote:

> Thanks for the bug report!  I've checked the configure script: no references to
> git, so I suppose the script is correct.
> 
> The code is always there in version control if somebody wants to take it on :-)

I apologize for the confusion - as it turns out the error message isn't
actually coming from the git code.

I now tried to compile 2.0.2 on my openSUSE 11.0 system without git, and the
error still occurs, when building via RPM. A plain "configure ; make" does not
trigger this error, so I suspect one of the additional compile flags that RPM
uses is to blame here.

This is the configure line and the compile options RPM uses:

$ export CFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
-D_FORTIFY_SOURCE=2'
$ export CXXFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
-D_FORTIFY_SOURCE=2'
$ export FFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
-D_FORTIFY_SOURCE=2'
$ ./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu
--target=i586-suse-linux --program-prefix= --prefix=/usr --exec-prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
--includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib
--localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man
--infodir=/usr/share/info

After running "make", the build stops with the following error:

[ghc] src/c_compat.o
/tmp/ghc16314_0/ghc16314_0.s: Assembler messages:

/tmp/ghc16314_0/ghc16314_0.s:199:0:
     Error: file number 2 already allocated
make: *** [src/c_compat.o] Error 1

$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 6.8.2

I wonder if any of the "--host", "--target" or "--build" configure options are
to blame here? I doubt that ghc cares about CFLAGS or CXXFLAGS. I will try to
isolate the offending option.

Bye,
	LenZ
-- 
------------------------------------------------------------------
 Lenz Grimmer <lenz@grimmer.com>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@jabber.org]                /\\
 http://www.lenzg.org/                                       V_V

Attachments

• config.log

On Tue, Aug 19, 2008 at 3:46 AM, Lenz Grimmer <lenz@grimmer.com> wrote:
> Hi,
>
> On 08/19/2008 08:42 AM, Eric Kow wrote:
>
>> Thanks for the bug report!  I've checked the configure script: no references to
>> git, so I suppose the script is correct.
>>
>> The code is always there in version control if somebody wants to take it on :-)
>
> I apologize for the confusion - as it turns out the error message isn't
> actually coming from the git code.
>
> I now tried to compile 2.0.2 on my openSUSE 11.0 system without git, and the
> error still occurs, when building via RPM. A plain "configure ; make" does not
> trigger this error, so I suspect one of the additional compile flags that RPM
> uses is to blame here.
>
> This is the configure line and the compile options RPM uses:
>
> $ export CFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=2'
> $ export CXXFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=2'
> $ export FFLAGS='-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=2'
> $ ./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu
> --target=i586-suse-linux --program-prefix= --prefix=/usr --exec-prefix=/usr
> --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
> --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib
> --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man
> --infodir=/usr/share/info
>
> After running "make", the build stops with the following error:
>
> [ghc] src/c_compat.o
> /tmp/ghc16314_0/ghc16314_0.s: Assembler messages:
>
> /tmp/ghc16314_0/ghc16314_0.s:199:0:
>     Error: file number 2 already allocated
> make: *** [src/c_compat.o] Error 1
>
> $ ghc --version
> The Glorious Glasgow Haskell Compilation System, version 6.8.2
>
> I wonder if any of the "--host", "--target" or "--build" configure options are
> to blame here? I doubt that ghc cares about CFLAGS or CXXFLAGS. I will try to
> isolate the offending option.

This looks like a GHC or gcc bug to me.  In particular, src/c_compat.o
was compiled by gcc, but /tmp/ghc16314_0/ghc16314_0.s is probably
output by GHC.  Either removing the very specific compilation flags or
adding -fvia-C to GHC's flags would probably fix the problem.  With
the command line you gave above I'm not sure how to pass -fvia-C all
the way GHC.

I hope this helps,
Jason