Hi,
I encountered the same problem building for amd64 on a
Core 2 Duo machine using gcc-3.3.6. The fix, I believe, is to modify the
build flags when making the shared library, replacing occurrences
of CCFLAGS (one) with CCFLAG0 in debian/rules. Certain objects in the
library get built with CCF
Hi Camm,
On Fri, May 05, 2006 at 06:48:56PM -0400, Camm Maguire wrote:
> semop(1): encountered an error: Invalid argument
> [...]
> Just wondering if you happen to be aware of
> this issue or similar and might know of a workaround.
No, I have never encountered something like this.
But if you som
Greetings, and thanks for all the reports! I've been preparing a new
atlas3 upload over the past few days fixing some outstanding items,
notably the broken custom target. Occasionally, I run into a make
failure:
semop(1): encountered an error: Invalid argument
I've done a fresh upgrade and am
Package: atlas3
Version: 3.6.0-20
Severity: important
Justification: fails to build from source
Hi,
release 3.6.0-20 of atlas3 fails to build on up-to-date amd64 unstable
system. The error message, when compiled with pbuilder, is as
follows:
[...]
ln -snf $(basename debian/tmp/usr/lib/a
4 matches
Mail list logo
