Skip to content
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

[BUG? Configure 5.5.64] Warnings during C symbol check #1132

Closed
p5pRT opened this issue Feb 3, 2000 · 2 comments
Closed

[BUG? Configure 5.5.64] Warnings during C symbol check #1132

p5pRT opened this issue Feb 3, 2000 · 2 comments

Comments

@p5pRT
Copy link

p5pRT commented Feb 3, 2000

Migrated from rt.perl.org#2092 (status was 'resolved')

Searchable as RT2092$

@p5pRT
Copy link
Author

p5pRT commented Feb 3, 2000

From @schwern

I'm in the middle of configuring 5.5.64 right now and I noticed the
following little burp​:

Guessing which symbols your C compiler and preprocessor define...
:2​: warning​: `#ifdef' argument starts with a digit
:7​: warning​: `#ifdef' argument starts with a digit
Your C compiler and pre-processor define these symbols​:
i386
unix

Is this a problem? I don't have nearly enough masochistic knowledge
of Bourne Shell to attempt to understand what's going on in Configure.

--
Summary of my perl5 (revision 5.0 version 5 subversion 640) configuration​:
  Platform​:
  osname=linux, osvers=2.2.10, archname=i686-linux
  uname='linux athens 2.2.10 #3 smp mon aug 2 16​:48​:09 edt 1999 i686 unknown '
  config_args=''
  hint=recommended, useposix=true, d_sigaction=define
  usethreads=undef use5005threads=undef useithreads=undef
  usesocks=undef useperlio=undef d_sfio=undef
  use64bits=undef uselargefiles=undef usemultiplicity=undef
  Compiler​:
  cc='cc', optimize='-g', gccversion=2.95.2 20000116 (Debian GNU/Linux)
  cppflags='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -DDEBUGGING_OPS -DDEBUGGING_MSTATS'
  ccflags ='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -DDEBUGGING_OPS -DDEBUGGING_MSTATS'
  stdchar='char', d_stdstdio=define, usevfork=false
  intsize=4, longsize=4, ptrsize=4, doublesize=8
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
  alignbytes=4, usemymalloc=y, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags =' -L/usr/local/lib'
  libpth=/usr/local/lib /lib /usr/lib
  libs=-lnsl -lndbm -lgdbm -ldbm -ldb -ldl -lm -lc -lposix -lcrypt
  libc=/lib/libc-2.1.2.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
  cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'

Characteristics of this binary (from libperl)​:
  Compile-time options​: DEBUGGING USE_LONG_DOUBLE USE_LARGE_FILES
  Built under linux
  Compiled at Feb 3 2000 22​:10​:17
  @​INC​:
  /usr/local/perl5.5.64/lib/i686-linux
  /usr/local/perl5.5.64/lib
  /usr/local/perl5.5.64/lib/site_perl/i686-linux
  /usr/local/perl5.5.64/lib/site_perl
  .

--

Michael G Schwern schwern@​pobox.com
  http​://www.pobox.com/~schwern
  /(?​:(?​:(1)[.-]?)?\(?(\d{3})\)?[.-]?)?(\d{3})[.-]?(\d{4})(x\d+)?/i

@p5pRT
Copy link
Author

p5pRT commented Feb 3, 2000

From @doughera88

On Thu, 3 Feb 2000, Michael G Schwern wrote​:

I'm in the middle of configuring 5.5.64 right now and I noticed the
following little burp​:

Guessing which symbols your C compiler and preprocessor define...
:2​: warning​: `#ifdef' argument starts with a digit
:7​: warning​: `#ifdef' argument starts with a digit

These can be safely ignored. (It's testing if you're on a 3B1, for
example. Even I don't have one of those running anymore. (The last perl5
I built on one was probably 5.001e or so.)

Is this a problem? I don't have nearly enough masochistic knowledge
of Bourne Shell to attempt to understand what's going on in Configure.

Don't bother. Jarkko's rewritten the underlying unit anyway, so 641's
version will look rather different, I expect.

  Andy Dougherty doughera@​lafayette.edu
  Dept. of Physics
  Lafayette College, Easton PA 18042

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant