On 10.2.2011 22:41, Sascha Manns wrote:

Now i have just this Problem: + make DESTDIR=/usr/src/packages/BUILDROOT/fltk-flu-2.14-6.1.i386  install === installing FLU === Installing binaries in /usr/bin... cp: cannot create regular file `/usr/bin/flu-config': Permission denied

But that i don't understand. I've set %{buildroot} and flu-config is a binary and should placed in %{_bindir}.

You need to patch the Makefile to understand DESTDIR. Michal -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 11.2.2011 16:51, Sascha Manns wrote:

Hi Michal,

Michal Marek wrote at Friday 11 February 2011:

...

On 10.2.2011 22:41, Sascha Manns wrote:

...

Now i have just this Problem: + make DESTDIR=/usr/src/packages/BUILDROOT/fltk-flu-2.14-6.1.i386  install === installing FLU === Installing binaries in /usr/bin... cp: cannot create regular file `/usr/bin/flu-config': Permission de nied

But that i don't understand. I've set %{buildroot} and flu-config is a binary and should placed in %{_bindir}.

You need to patch the Makefile to understand DESTDIR. Thanks for spending time :-) The Problem i see is, that the Makefile is created by the configure Script. But the Configure Script is self written by the Author, no "normal" configure.

Have you an idea, what i must change to make it runable?

In general, the commands in the Makefile need to be changed from install somebinary /usr/bin/somebinary to install somebinary $(DESTDIR)/usr/bin/somebinary Often the Makefile is generated by configure from Makefile.in, in that case you need to make the changes there. Otherwise, try to find out what generates such commands and add the $(DESTDIR) there. hth, Michal -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

created request id 60623 Added Patch with the intention of using DESTDIR and added devel, libs packages. This doesn't fix the build errors, which seem to be related to GCC versioning ;) %if 0%{?suse_version} >= 11xx PatchY: foobar.patch %endif and on %prep %if 0%{?suse_version} >= 11xx %patchY ... %endif once you have the patch for the gcc version present on newer releases. Hope it helps, NM On Fri, Feb 11, 2011 at 6:54 PM, Sascha Manns wrote:

Michal Marek wrote at Friday 11 February 2011:

...

On 11.2.2011 16:51, Sascha Manns wrote:

...

Hi Michal,

Michal Marek wrote at Friday 11 February 2011:

...

On 10.2.2011 22:41, Sascha Manns wrote:

...

Now i have just this Problem: + make DESTDIR=/usr/src/packages/BUILDROOT/fltk-flu-2.14-6.1.i386  install === installing FLU === Installing binaries in /usr/bin... cp: cannot create regular file `/usr/bin/flu-config': Permission de nied

But that i don't understand. I've set %{buildroot} and flu-config is a binary and should placed in %{_bindir}.

You need to patch the Makefile to understand DESTDIR.

Thanks for spending time :-) The Problem i see is, that the Makefile is created by the configure Script. But the Configure Script is self written by the Author, no "normal" configure.

Have you an idea, what i must change to make it runable?

In general, the commands in the Makefile need to be changed from

    install somebinary /usr/bin/somebinary

to

    install somebinary $(DESTDIR)/usr/bin/somebinary

Often the Makefile is generated by configure from Makefile.in, in that case you need to make the changes there. Otherwise, try to find out what generates such commands and add the $(DESTDIR) there. A part of the Problem is solved. If i use configure --prefix=%{_prefix} i got the Permission denied Issue. If i use configure --prefix=%{buildroot}%{_prefix} i got: file-contains-buildroot (Badness: 10000) /usr/bin/flu-config

I've pasted the configure there: http://susepaste.org/27212307

Any ideas? -- Sincerely Yours

Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team

Blog: http://saigkill.wordpress.com German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

-- nelson marques nmo.marques@gmail.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Hello, Can someone suggest a fix for this error message when compiling grub-1.99 rc1 I get compile error in grub-1.99 rc1 Part of log se [1] Full log listing see [2] other details see [3] Glenn [1] mv -f tests/lib/.deps-core/functional_test_module-test.Tpo tests/lib/.deps-core/functional_test_module-test.Po gcc -Os -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -mno-stack-arg-probe -Werror -mrtd -mregparm=3 -ffreestanding -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -static -m32 -Wl,--build-id=none -nostdlib -Wl,-N,-r,-d -o functional_test.module tests/lib/functional_test_module-functional_test.o tests/lib/functional_test_module-test.o gcc -DHAVE_CONFIG_H -I. -I.. -Wall -W -I../include -I../include -DGRUB_MACHINE_PCBIOS=1 -DGRUB_MACHINE=I386_PC -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.5/include -DGRUB_FILE=\"tests/example_functional_test.c\" -I. -I. -I.. -I.. -I../include -I../include -Os -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -mno-stack-arg-probe -Werror -mrtd -mregparm=3 -ffreestanding -Wno-format -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT tests/example_functional_test_module-example_functional_test.o -MD -MP -MF tests/.deps-core/example_functional_test_module-example_functional_test.Tpo -c -o tests/example_functional_test_module-example_functional_test.o `test -f 'tests/example_functional_test.c' || echo './'`tests/example_functional_test.c cc1: warnings being treated as errors tests/example_functional_test.c: In function 'example_test': tests/example_functional_test.c:30:3: error: too many arguments for format tests/example_functional_test.c:31:3: error: too many arguments for format make[3]: *** [tests/example_functional_test_module-example_functional_test.o] Error 1 make[3]: Leaving directory `/usr/src/packages/BUILD/grub-1.99rc1/grub-core' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/packages/BUILD/grub-1.99rc1/grub-core' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/grub-1.99rc1' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.FEmX8w (%build) [2] https://build.opensuse.org/package/rawlog?arch=x86_64&package=grub2&project=home%3Adoiggl&repository=openSUSE_Factory [3] https://build.opensuse.org/package/show?package=grub2&project=home%3Adoiggl -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Fri, Feb 18, 2011 at 6:39 PM, Cristian Rodríguez wrote:

On Sat, Feb 12, 2011 at 12:35 AM,   wrote:

...

cc1: warnings being treated as errors

You are building with -Werror so when a warning is emitted it is considered fatal and compilation aborts.

Hi, I've also run across this in the past with some packages from Ayatana Project, and Cristian is right, you need to remove -Werror. This is how I tinkered it on one of my packages [1], removed -Werror from configure.ac through a patch. [1] - https://build.opensuse.org/package/files?package=libgwibber&project=home:ketheriel:ayatana NM

...

tests/example_functional_test.c: In function 'example_test': tests/example_functional_test.c:30:3: error: too many arguments for format tests/example_functional_test.c:31:3: error: too many arguments for format

what does that lines say ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

-- nelson marques nmo.marques@gmail.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Am Sonntag, 20. Februar 2011, 14:17:27 schrieb Philipp Thomas:

On Sat, 19 Feb 2011 19:02:04 +0000, Nelson Marques

wrote:

...

I've also run across this in the past with some packages from Ayatana Project, and Cristian is right, you need to remove -Werror.

No! The right way to deal with it is to remove the cause of the warning, not removing -Werror.

IMO Werror shouldn't really be used in openSUSE packages - especially not for tests/examples. Upstream projects should aim for having no warnings in their code, but if they fail, it's clearly not the packager's job. Greetings, Stephan -- Sent from openSUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

2011/2/12 Sascha Manns :

Maybe anyone has an idea?

SR #60638 I'm not a C++ dev. And I fail to see the sense of FluSimpleString instead of the standard string class... but compiles. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 11.2.2011 22:19, Nelson Marques wrote:

created request id 60623

Added Patch with the intention of using DESTDIR and added devel, libs packages. This doesn't fix the build errors, which seem to be related to GCC versioning ;)

%if 0%{?suse_version} >= 11xx PatchY: foobar.patch %endif

There is no reason to make the preamble (and thus the .src.rpm) dependent on the distribution you are building against. Michal -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org