Opened 15 years ago

Closed 13 years ago

#19431 closed defect (duplicate)

proctools-0.4pre1 Compile error - fails to compile with coreutils +with_default_names

Reported by: mike@… Owned by: akitada@…
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc: kenyon@…
Port: proctools

Description

Proctools fails to compile with coreutils built and installed with +with_default_names as GNU's tsort does not have the necessary "-q" option.

Change History (10)

comment:1 Changed 15 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to akitada@…
Port: proctools added

comment:2 Changed 15 years ago by raimue (Rainer Müller)

So, don't use coreutils +with_default_names. I don't think there is a better solution.

comment:3 Changed 15 years ago by mike@…

I disagree.

Possible solutions:

  • Call /usr/bin/tsort rather than just tsort
  • Don't use the -q option as it seems to just hide output and just pipe stdout to /dev/null instead
  • Present a warning message to the user

I don't think doing nothing is the best option.

comment:4 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:5 Changed 15 years ago by akitada@…

Status: newassigned

Thanks for the report. Would you provide a patch for this?

comment:6 Changed 15 years ago by mike@…

Not sure exactly what to patch, it seems vaguely nontrivial. Might be worth just putting up a warning.

comment:7 Changed 15 years ago by dj_mook@…

Temporarily deactivating coreutils to install procutils worked to get it installed.

It seems that if you want the specific behvaior of a system supplied tool you should explicitly reference it (/usr/bin/tsort). This is usually good scripting practice anyway when you are not sure of the environment you are being executed in.

comment:8 Changed 15 years ago by tobypeterson

see #20748

comment:9 Changed 14 years ago by kenyon@…

Cc: kenyon@… added

Cc Me!

comment:10 Changed 13 years ago by jmroot (Joshua Root)

Resolution: duplicate
Status: assignedclosed

#20748 is our solution to this, report a bug upstream if you'd like them to change what they do.

Note: See TracTickets for help on using tickets.