search for: nopi

I made a patch that depending of gcc flavor add -no-pie or -nopie on libutil and dos Makefile. This fix fatal error like this sha1hash.c: In function `SHA1Transform': ../include/netinet/in.h:24: error: can't find a register in class `BREG' while reloading `asm' ../include/netinet/in.h:24: error: can't find a register in class `BREG' while...

...6 @@ SP_FLAGS := $(shell $(SP_TEST) && $(ECHO) '-fno-stack-protector') CFLAGS += $(SP_FLAGS) endif +# Some widespread patched versions of gcc include -fPIE -Wl,-pie by +# default. gpxe does not support pie code in get_cpuinfo. +# +ifeq ($(CCTYPE),gcc) +PIE_TEST = $(CC) -fno-PIE -nopie -x c -c /dev/null \ + -o /dev/null >/dev/null 2>&1 +PIE_FLAGS := $(shell $(PIE_TEST) && $(ECHO) '-fno-PIE -nopie') +CFLAGS += $(PIE_FLAGS) +endif + # gcc 4.4 generates .eh_frame sections by default, which distort the # output of "size". Inhibit this. # --...

...f gcc include -fPIE -Wl,-pie by +# default. Note that gcc will exit *successfully* if it fails to +# recognise an option that starts with "no", so we have to test for +# output on stderr instead of checking the exit status. +# +ifeq ($(CCTYPE),gcc) +PIE_TEST = [ -z "`$(CC) -fno-PIE -nopie -x c -c /dev/null -o /dev/null 2>&1`" ] +PIE_FLAGS := $(shell $(PIE_TEST) && $(ECHO) '-fno-PIE -nopie') +CFLAGS += $(PIE_FLAGS) +endif + # gcc 4.4 generates .eh_frame sections by default, which distort the # output of "size". Inhibit this. # -- 1.5.6.5

...1); } +#else /* SKEY */ +#ifdef OPIE +#include <opie.h> + +char * +get_challenge(Authctxt *authctxt, char *devs) +{ + static char challenge[OPIE_CHALLENGE_MAX+64]; + if (opiechallenge(&authctxt->opie_data, authxtxt->user, challenge) != 0) + return NULL; + strlcat(challenge, "\nOPIE Password: ", sizeof challenge); + return challenge; +} +int +verify_response(Authctxt *authctxt, char *response) +{ + return authctxt->valid && opieverify(&authctxt->opie_data, response); +} + #else /* not available */ char * @@ -100,5 +119,5 @@ { return 0; } -#endif...

...art from the deploy action which fails saying that there is "No such file or directory" I''ve included the full error listing below. The SVN definately exists because we''re using for development. Does any one have any ideas what might be going wrong? Thanks Tom [nopi.textdriven.com] executing command command finished C:/InstantRails/Ruby/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/scm/ subversion.rb:90:in ``'': No such file or directory - svn log -q -rhead http://no pi.textdriven.com/svn/ssdsvn/OlderPersonsPortal (Errno::ENOENT)...

...gt; clearly define a list of options that will be supported by linkers with > their clear semantics. > Personally, I would like to see the ability to add support for additional options without having to modify the compiler. That said, I think that there are options which can be scary (e.g. -nopie). I think that the linker should make the decision of what it supports and error out on others. This allows for us to enhance the support over time without a huge overhead. As a starting point, I think that -l and -L are two that would be interesting. I can see -u being useful as well, but the...

Hi there, I''ve just built xen & dom0 kernel from gentoo ebuilds (bugs.gentoo.org), but my dom0 kernel crashes during boot. Any help is appreciated. Console log, grub.conf and .config are included, machine is celeron/466, 128MB of RAM. Console log: Linux version 2.6.9-xen0 (root@zirafa) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #2 Sun Nov 14

...a list of options that will be supported by linkers with their clear >> semantics. > > Personally, I would like to see the ability to add support for additional > options without having to modify the compiler. That said, I think that > there are options which can be scary (e.g. -nopie). I think that the linker > should make the decision of what it supports and error out on others. This > allows for us to enhance the support over time without a huge overhead. As > a starting point, I think that -l and -L are two that would be interesting. > I can see -u being usef...

I just set up a new box that has been giving me trouble since I first cloned the xen repo to it. I started off with "error: can''t find a register in class ''BREG'' while reloading ''asm''" errors that I fixed by changing my gcc profile(gentoo) to nopie. That introduced me to a ''__guard'' error that I fixed by changing my gcc profile to nopiesse. I will note for posterity that this was a new Gentoo install onto a old celeron with gcc 3.4.5-r1. Now I''ve booted dom0 and have a file backed image that I''m trying to...

...at will be supported by linkers with their clear >>> semantics. >> >> Personally, I would like to see the ability to add support for additional >> options without having to modify the compiler. That said, I think that >> there are options which can be scary (e.g. -nopie). I think that the linker >> should make the decision of what it supports and error out on others. This >> allows for us to enhance the support over time without a huge overhead. As >> a starting point, I think that -l and -L are two that would be interesting. >> I can s...

...f options that will be supported by linkers with >> their clear semantics. >> > > Personally, I would like to see the ability to add support for additional > options without having to modify the compiler. That said, I think that > there are options which can be scary (e.g. -nopie). I think that the > linker should make the decision of what it supports and error out on > others. This allows for us to enhance the support over time without a huge > overhead. As a starting point, I think that -l and -L are two that would > be interesting. I can see -u being use...

...E POSSIBILITY OF SUCH DAMAGE. + */ +#include "includes.h" +RCSID("$Id"); + +#ifdef OPIE + +#include <opie.h> + +#include "xmalloc.h" +#include "auth.h" + +static void * +opie_init_ctx(Authctxt *authctxt) +{ + return authctxt; +} + +#define PROMPT "\nOPIE Password: " + +static int +opie_query(void *ctx, char **name, char **infotxt, + u_int* numprompts, char ***prompts, u_int **echo_on) +{ + Authctxt *authctxt = ctx; + char challenge[OPIE_CHALLENGE_MAX+64], *p; + int len; + struct opie opie; + + if (opiechallenge(&opie, authctxt->use...

...You need to clearly define a list of options that will be supported by linkers with their clear semantics. Personally, I would like to see the ability to add support for additional options without having to modify the compiler. That said, I think that there are options which can be scary (e.g. -nopie). I think that the linker should make the decision of what it supports and error out on others. This allows for us to enhance the support over time without a huge overhead. As a starting point, I think that -l and -L are two that would be interesting. I can see -u being useful as well, but the...

Added two new sets of compile flags, and pass them to the check scripts, so libraries and includes are searched there also. Resend this patches because they suffered some modifications and where scattered along the mailing list. Please review, thanks Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...by linkers with their clear >>>> semantics. >>> >>> Personally, I would like to see the ability to add support for additional >>> options without having to modify the compiler. That said, I think that >>> there are options which can be scary (e.g. -nopie). I think that the linker >>> should make the decision of what it supports and error out on others. This >>> allows for us to enhance the support over time without a huge overhead. As >>> a starting point, I think that -l and -L are two that would be interesting. >...

...it. Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu> diff -r cd47dde439e6 -r a1986ef30b7d Config.mk --- a/Config.mk Sat Jan 14 19:04:48 2012 +0100 +++ b/Config.mk Sun Jan 15 06:56:00 2012 +0100 @@ -181,6 +181,11 @@ CHECK_INCLUDES = $(EXTRA_INCLUDES) $(PRE EMBEDDED_EXTRA_CFLAGS := -nopie -fno-stack-protector -fno-stack-protector-all EMBEDDED_EXTRA_CFLAGS += -fno-exceptions +CONFIG_YAJL_VERSION := $(shell export OS="`uname -s`"; \ + export CHECK_INCLUDES="$(CHECK_INCLUDES)"; \ + . $(XEN_ROOT)/tools/check/funcs.sh; \...

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

...other thread that cropped up with similar error messages was also a Gentoo hardened box and there was no resolution posted although the fellow''s initial problem (failure to compile) was apparently resolved by the elimination of some (all?) of the hardened flags during compilation: "-nopie fixed the originally reported error, but I subsequently got other errors that said something like "undefined reference to `__guard''" and "undefined reference to `__stack_smash_handler''". Adding -fno-stack-protector seems to have solved these as well, and I...

Thank you for starting the discussion thread. In general I'm in favor of the proposal. Defining a generic way to convey some information from the compiler to the linker is useful, and it looks like it is just a historical reason that the ELF lacks the feature at the moment. This is a scenario in which the feature is useful: when you include math.h, a compiler (which is driven by some pragma)

...to clearly define a list of options that will be supported by linkers with their clear semantics. > > Personally, I would like to see the ability to add support for additional options without having to modify the compiler. That said, I think that there are options which can be scary (e.g. -nopie). I think that the linker should make the decision of what it supports and error out on others. This allows for us to enhance the support over time without a huge overhead. As a starting point, I think that -l and -L are two that would be interesting. I can see -u being useful as well, but the...