[bug #14925] Non-portable binary compilations on linux

[bug #14925] Non-portable binary compilations on linux

[anonymous]

URL:
  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>

                 Summary: Non-portable binary compilations on linux
                 Project: Guile
            Submitted by: None
            Submitted on: Mon 11/07/05 at 17:04
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open

    _______________________________________________________

Details:

By default, when I built guile on my linux box (debian sarge). it uses the
"__libc_stack_end" symbol.  This symbol is not portable.  When I compile and
link my program with the guile libraries, and then try to move the binary to
a different linux platform (with a different version of GNU libc), the
program won't load with the error:

./no-repl: relocation error: ./no-repl: symbol __libc_stack_end, version
GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference

ldd --version shows glic 2.3.2 on one box, 2.3.5 on the other (it also fails
between 2.3.2 and 2.3.3)

My solution was to rebuild guile, but remove the line
"#define HAVE_LIBC_STACK_END 1" from config.h before recompiling (after
reconfiguring)

After relinking my executeable with this new version of guile, it still
failed due to:
ERROR: In procedure primitive-load-path:
ERROR: Unable to find file "ice-9/boot-9.scm" in load path

which meant I had to distribute along with the contents of
<install dir>/share/guile/1.6/ 
and set up run scripts to configure GUILE_LOAD_PATH before running my
executeable.  

As __libc_stack_end is a non-portable symbol, I would like to see it not used
by default on the guile build.  (or not used at all honestly)

Also, it would be nice if there was a way to statically link the file from
the share directory.  If there already is and I just missed it while browsing
the documentation, I apologize, but I was unable to find it.







    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: [bug #14925] Non-portable binary compilations on linux

[Neil Jerram]

anonymous <savannah-bounces@gnu.org> writes:

> URL:
>   <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>

Well I'd like to ask two questions in response to this.

- Can you be more precise about how __libc_stack_end is non-portable?
  (Is it just a matter of having a recent enough glibc?)

- What do you mean "statically linking from the share directory"?

But I don't see any way, either in this mail or in the bug report on
savannah, to contact the submitter ...

Regards,
     Neil



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: [bug #14925] Non-portable binary compilations on linux

[Kevin Ryde]

Neil Jerram <neil@ossau.uklinux.net> writes:
>
> - Can you be more precise about how __libc_stack_end is non-portable?
>   (Is it just a matter of having a recent enough glibc?)

My guess would be __libc_stack_end is portable enough, in the sense of
being upward compatible between glibc versions.  Maybe the OP was
moving to an older one.

> - What do you mean "statically linking from the share directory"?

I can't tell what that means either.  Moved directories or something.
Unlikely to be a good thing.

> But I don't see any way, either in this mail or in the bug report on
> savannah, to contact the submitter ...

Unless the submitter is lurking here we'll have to close it as unable
to be actioned, not aware of such a problem ...


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: [bug #14925] Non-portable binary compilations on linux

[Neil Jerram]

Kevin Ryde <user42@zip.com.au> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> - Can you be more precise about how __libc_stack_end is non-portable?
>>   (Is it just a matter of having a recent enough glibc?)
>
> My guess would be __libc_stack_end is portable enough, in the sense of
> being upward compatible between glibc versions.  Maybe the OP was
> moving to an older one.

That would be my guess too, and hence (I think) not a scenario that we
need to worry about.

>> - What do you mean "statically linking from the share directory"?
>
> I can't tell what that means either.  Moved directories or something.
> Unlikely to be a good thing.

I thought it could mean somehow linking the Scheme code as text into
the libguile library or guile executable - which I've vaguely mulled
as being possibly useful for embedded systems without a filesystem...

>> But I don't see any way, either in this mail or in the bug report on
>> savannah, to contact the submitter ...
>
> Unless the submitter is lurking here we'll have to close it as unable
> to be actioned, not aware of such a problem ...

I guess we should just allow a few days to pass first, then.

  Neil



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

[bug #14925] Non-portable binary compilations on linux

[Kevin Ryde]

Update of bug #14925 (project guile):

                  Status:                    None => Need Info              
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

We think __libc_stack_end is portable enough, we think it's upwardly
compatible between glibc versions, which should be enough.

Incidentally, it must be very difficult doing "binary compilations on linux",
I wasn't aware the kernel came with a compiler or shell or tools.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile