-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default configuration on x86_64-linux-gnu cannot build binary extension modules #15629
Comments
From dschepler@gmail.comCreated by dschepler@gmail.comFor example, when subsequently configuring texinfo, I got these errors /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. Perl Info
|
From @jkeenanOn Sun, 25 Sep 2016 20:47:45 GMT, dschepler@gmail.com wrote:
I don't see much evidence of a bug in perl here. You are experiencing some kind of failure when using 'libtool'. That tool is not part of the Perl 5 core distribution and so is outside our scope. Can you provide an example of this problem outside of 'libtool'? I would recommend first trying to understand all the output like this: ##### Whatever that is, it's not perl. Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @LeontOn Sun, Sep 25, 2016 at 10:47 PM, Daniel Schepler <perlbug-followup@perl.org
If you want to use libperl in a shared library, you need to compile your Leon |
@Leont - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#129354 (status was 'resolved')
Searchable as RT129354$
The text was updated successfully, but these errors were encountered: